1 .TH SLAPPASSWD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
3 .\" Copyright 1998-2006 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slappasswd \- OpenLDAP password utility
11 .B [\-g|\-s secret|\-T file]
19 is used to generate an userPassword value
25 configuration directive.
32 Generate RFC 2307 userPassword values (the default). Future
33 versions of this program may generate alternative syntaxes
34 by default. This option is provided for forward compatibility.
42 are absent, the user will be prompted for the secret to hash.
47 and mutually exclusive flags.
55 are absent, the user will be prompted for the secret to hash.
60 and mutually exclusive flags.
67 are mutually exclusive flags.
70 Hash the contents of the file.
75 are absent, the user will be prompted for the secret to hash.
80 and mutually exclusive flags.
83 If -h is specified, one of the following RFC 2307 schemes may
93 Note that scheme names may need to be protected, due to
97 from expansion by the user's command interpreter.
102 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
107 use the MD5 algorithm (RFC 1321), the latter with a seed.
114 indicates that the new password should be added to userPassword as
118 is used, this flag is incompatible with
121 .BI \-c " crypt-salt-format"
122 Specify the format of the salt passed to
124 when generating {CRYPT} passwords.
125 This string needs to be in
127 format and may include one (and only one) %s conversion.
128 This conversion will be substituted with a string random
129 characters from [A\-Za\-z0\-9./]. For example, '%.2s'
130 provides a two character salt and '$1$%.8s' tells some
131 versions of crypt(3) to use an MD5 algorithm and provides
132 8 random characters of salt. The default is '%s', which
133 provides 31 characters of salt.
135 The practice storing hashed passwords in userPassword violates
136 Standard Track (RFC 2256) schema specifications and may hinder
137 interoperability. A new attribute type, authPassword, to hold
138 hashed passwords has been defined (RFC 3112), but is not yet
142 It should also be noted that the behavior of
144 is platform specific.
145 .SH "SECURITY CONSIDERATIONS"
146 Use of hashed passwords does not protect passwords during
147 protocol transfer. TLS or other eavesdropping protections
148 should be in\-place before using LDAP simple bind.
150 The hashed password values should be protected as if they
151 were clear text passwords.
161 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
163 OpenLDAP is developed and maintained by
164 The OpenLDAP Project (http://www.openldap.org/).
165 OpenLDAP is derived from University of Michigan LDAP 3.3 Release.