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 [\-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
67 Note that scheme names may need to be protected, due to
71 from expansion by the user's command interpreter.
76 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
81 use the MD5 algorithm (RFC 1321), the latter with a seed.
88 indicates that the new password should be added to userPassword as
91 .BI \-c " crypt-salt-format"
92 Specify the format of the salt passed to
94 when generating {CRYPT} passwords.
95 This string needs to be in
97 format and may include one (and only one) %s conversion.
98 This conversion will be substituted with a string random
99 characters from [A\-Za\-z0\-9./]. For example, '%.2s'
100 provides a two character salt and '$1$%.8s' tells some
101 versions of crypt(3) to use an MD5 algorithm and provides
102 8 random characters of salt. The default is '%s', which
103 provides 31 characters of salt.
105 The practice storing hashed passwords in userPassword violates
106 Standard Track (RFC 2256) schema specifications and may hinder
107 interoperability. A new attribute type, authPassword, to hold
108 hashed passwords has been defined (RFC 3112), but is not yet
112 It should also be noted that the behavior of
114 is platform specific.
115 .SH "SECURITY CONSIDERATIONS"
116 Use of hashed passwords does not protect passwords during
117 protocol transfer. TLS or other eavesdropping protections
118 should be in\-place before using LDAP simple bind.
120 The hashed password values should be protected as if they
121 were clear text passwords.
131 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
133 OpenLDAP is developed and maintained by
134 The OpenLDAP Project (http://www.openldap.org/).
135 OpenLDAP is derived from University of Michigan LDAP 3.3 Release.