1 .TH SLAPPASSWD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2012 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slappasswd \- OpenLDAP password utility
14 .BR \-g \||\| \-s \ \fIsecret\fR \||\| \fB\-T \ \fIfile\fR]
18 .BI \-c \ salt-format\fR]
26 is used to generate an userPassword value
31 configuration directive or the
34 configuration directive.
42 Generate RFC 2307 userPassword values (the default). Future
43 versions of this program may generate alternative syntaxes
44 by default. This option is provided for forward compatibility.
52 are absent, the user will be prompted for the secret to hash.
57 are mutually exclusive flags.
65 are absent, the user will be prompted for the secret to hash.
70 are mutually exclusive flags.
77 are mutually exclusive flags.
80 Hash the contents of the file.
85 are absent, the user will be prompted for the secret to hash.
90 and mutually exclusive flags.
93 If \fB\-h\fP is specified, one of the following RFC 2307 schemes may
103 Note that scheme names may need to be protected, due to
107 from expansion by the user's command interpreter.
112 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
117 use the MD5 algorithm (RFC 1321), the latter with a seed.
124 indicates that the new password should be added to userPassword as
128 is used, this flag is incompatible with option
131 .BI \-c \ crypt-salt-format
132 Specify the format of the salt passed to
134 when generating {CRYPT} passwords.
135 This string needs to be in
137 format and may include one (and only one)
140 This conversion will be substituted with a string of random
141 characters from [A\-Za\-z0\-9./]. For example,
143 provides a two character salt and
148 to use an MD5 algorithm and provides
149 8 random characters of salt.
152 which provides 31 characters of salt.
155 Omit the trailing newline; useful to pipe the credentials
158 The practice of storing hashed passwords in userPassword violates
159 Standard Track (RFC 4519) schema specifications and may hinder
160 interoperability. A new attribute type, authPassword, to hold
161 hashed passwords has been defined (RFC 3112), but is not yet
165 It should also be noted that the behavior of
167 is platform specific.
168 .SH "SECURITY CONSIDERATIONS"
169 Use of hashed passwords does not protect passwords during
170 protocol transfer. TLS or other eavesdropping protections
171 should be in-place before using LDAP simple bind.
173 The hashed password values should be protected as if they
174 were clear text passwords.
180 .BR slapd\-config (5),
185 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)