1 .TH SLAPPASSWD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
3 .\" Copyright 1998-2003 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slappasswd \- OpenLDAP password utility
11 .B [\-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.
40 are absent, the user will be prompted for the secret to hash.
44 and mutually exclusive flags.
47 Hash the contents of the file.
50 are absent, the user will be prompted for the secret to hash.
54 and mutually exclusive flags.
57 If -h is specified, one of the following RFC 2307 schemes may
70 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
75 use the MD5 algorithm (RFC 1321), the latter with a seed.
82 indicates that the new password should be added to userPassword as
85 .BI \-c " crypt-salt-format"
86 Specify the format of the salt passed to
88 when generating {CRYPT} passwords.
89 This string needs to be in
91 format and may include one (and only one) %s conversion.
92 This conversion will be substituted with a string random
93 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
94 provides a two character salt and "$1$%.8s" tells some
95 versions of crypt(3) to use an MD5 algorithm and provides
96 8 random characters of salt. The default is "%s", which
97 provides 31 characters of salt.
99 The practice storing hashed passwords in userPassword violates
100 Standard Track (RFC 2256) schema specifications and may hinder
101 interoperability. A new attribute type, authPassword, to hold
102 hashed passwords has been defined (RFC 3112), but is not yet
106 It should also be noted that the behavior of
108 is platform specific.
109 .SH "SECURITY CONSIDERATIONS"
110 Use of hashed passwords does not protect passwords during
111 protocol transfer. TLS or other eavesdropping protections
112 should be in\-place before using LDAP simple bind.
114 The hashed password values should be protected as if they
115 were clear text passwords.
125 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
127 OpenLDAP is developed and maintained by
128 The OpenLDAP Project (http://www.openldap.org/).
129 OpenLDAP is derived from University of Michigan LDAP 3.3 Release.