1 .TH SLAPPASSWD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2009 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slappasswd \- OpenLDAP password utility
11 .B [\-g|\-s secret|\-T file]
20 is used to generate an userPassword value
25 configuration directive or the
28 configuration directive.
36 Generate RFC 2307 userPassword values (the default). Future
37 versions of this program may generate alternative syntaxes
38 by default. This option is provided for forward compatibility.
46 are absent, the user will be prompted for the secret to hash.
51 and mutually exclusive flags.
59 are absent, the user will be prompted for the secret to hash.
64 and mutually exclusive flags.
71 are mutually exclusive flags.
74 Hash the contents of the file.
79 are absent, the user will be prompted for the secret to hash.
84 and mutually exclusive flags.
87 If -h is specified, one of the following RFC 2307 schemes may
97 Note that scheme names may need to be protected, due to
101 from expansion by the user's command interpreter.
106 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
111 use the MD5 algorithm (RFC 1321), the latter with a seed.
118 indicates that the new password should be added to userPassword as
122 is used, this flag is incompatible with
125 .BI \-c " crypt-salt-format"
126 Specify the format of the salt passed to
128 when generating {CRYPT} passwords.
129 This string needs to be in
131 format and may include one (and only one) %s conversion.
132 This conversion will be substituted with a string random
133 characters from [A\-Za\-z0\-9./]. For example, '%.2s'
134 provides a two character salt and '$1$%.8s' tells some
135 versions of crypt(3) to use an MD5 algorithm and provides
136 8 random characters of salt. The default is '%s', which
137 provides 31 characters of salt.
140 Omit the trailing newline; useful to pipe the credentials
143 The practice of storing hashed passwords in userPassword violates
144 Standard Track (RFC 4519) schema specifications and may hinder
145 interoperability. A new attribute type, authPassword, to hold
146 hashed passwords has been defined (RFC 3112), but is not yet
150 It should also be noted that the behavior of
152 is platform specific.
153 .SH "SECURITY CONSIDERATIONS"
154 Use of hashed passwords does not protect passwords during
155 protocol transfer. TLS or other eavesdropping protections
156 should be in\-place before using LDAP simple bind.
158 The hashed password values should be protected as if they
159 were clear text passwords.
165 .BR slapd\-config (5),
170 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)