2002-06-13 11:59:10 +08:00
|
|
|
.TH SLAPPASSWD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
|
2000-06-16 14:43:55 +08:00
|
|
|
.\" $OpenLDAP$
|
2004-01-02 03:15:16 +08:00
|
|
|
.\" Copyright 1998-2004 The OpenLDAP Foundation All Rights Reserved.
|
2000-06-16 14:43:55 +08:00
|
|
|
.\" Copying restrictions apply. See COPYRIGHT/LICENSE.
|
|
|
|
|
.SH NAME
|
2000-07-23 02:32:33 +08:00
|
|
|
slappasswd \- OpenLDAP password utility
|
2000-06-16 14:43:55 +08:00
|
|
|
.SH SYNOPSIS
|
|
|
|
|
.B SBINDIR/slappasswd
|
|
|
|
|
.B [\-v]
|
2000-08-25 15:55:08 +08:00
|
|
|
.B [\-u]
|
2003-03-31 14:29:59 +08:00
|
|
|
.B [\-s secret|\-T file]
|
2000-08-25 15:55:08 +08:00
|
|
|
.B [\-h hash]
|
2001-06-13 13:40:24 +08:00
|
|
|
.B [\-c salt-format]
|
2000-06-16 14:43:55 +08:00
|
|
|
.B
|
|
|
|
|
.LP
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
|
.LP
|
|
|
|
|
.B Slappasswd
|
2000-08-25 15:42:11 +08:00
|
|
|
is used to generate an userPassword value
|
2000-08-25 13:31:59 +08:00
|
|
|
suitable for use with
|
|
|
|
|
.BR ldapmodify (1)
|
|
|
|
|
or
|
2000-06-16 14:43:55 +08:00
|
|
|
.BR slapd.conf (5)
|
2000-08-25 13:31:59 +08:00
|
|
|
.I rootpw
|
2001-06-13 13:40:24 +08:00
|
|
|
configuration directive.
|
2000-06-16 14:43:55 +08:00
|
|
|
.SH OPTIONS
|
|
|
|
|
.TP
|
|
|
|
|
.B \-v
|
|
|
|
|
enable verbose mode.
|
2001-06-13 13:40:24 +08:00
|
|
|
.TP
|
2000-08-25 15:55:08 +08:00
|
|
|
.B \-u
|
2002-09-21 01:27:08 +08:00
|
|
|
Generate RFC 2307 userPassword values (the default). Future
|
2000-08-25 15:55:08 +08:00
|
|
|
versions of this program may generate alternative syntaxes
|
|
|
|
|
by default. This option is provided for forward compatibility.
|
2000-06-16 14:43:55 +08:00
|
|
|
.TP
|
|
|
|
|
.BI \-s " secret"
|
2003-03-31 14:29:59 +08:00
|
|
|
The secret to hash.
|
|
|
|
|
If this and
|
|
|
|
|
.B \-T
|
|
|
|
|
are absent, the user will be prompted for the secret to hash.
|
|
|
|
|
.B \-s
|
|
|
|
|
and
|
|
|
|
|
.B \-T
|
|
|
|
|
and mutually exclusive flags.
|
|
|
|
|
.TP
|
|
|
|
|
.BI \-T " file"
|
|
|
|
|
Hash the contents of the file.
|
|
|
|
|
If this and
|
|
|
|
|
.B \-s
|
|
|
|
|
are absent, the user will be prompted for the secret to hash.
|
|
|
|
|
.B \-s
|
|
|
|
|
and
|
|
|
|
|
.B \-T
|
|
|
|
|
and mutually exclusive flags.
|
2000-06-16 14:43:55 +08:00
|
|
|
.TP
|
2001-06-13 13:40:24 +08:00
|
|
|
.BI \-h " scheme"
|
2002-09-21 01:27:08 +08:00
|
|
|
If -h is specified, one of the following RFC 2307 schemes may
|
2000-08-25 13:31:59 +08:00
|
|
|
be specified:
|
2000-06-16 14:43:55 +08:00
|
|
|
.IR {CRYPT} ,
|
|
|
|
|
.IR {MD5} ,
|
|
|
|
|
.IR {SMD5} ,
|
|
|
|
|
.IR {SSHA} ", and"
|
|
|
|
|
.IR {SHA} .
|
|
|
|
|
The default is
|
|
|
|
|
.IR {SSHA} .
|
2002-09-21 01:27:08 +08:00
|
|
|
|
2004-01-09 12:11:57 +08:00
|
|
|
Note that scheme names may need to be protected, due to
|
|
|
|
|
.B {
|
|
|
|
|
and
|
|
|
|
|
.BR } ,
|
|
|
|
|
from expansion by the user's command interpreter.
|
|
|
|
|
|
2002-09-21 01:12:58 +08:00
|
|
|
.B {SHA}
|
|
|
|
|
and
|
|
|
|
|
.B {SSHA}
|
|
|
|
|
use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
|
2002-09-21 01:27:08 +08:00
|
|
|
|
2002-09-21 01:12:58 +08:00
|
|
|
.B {MD5}
|
|
|
|
|
and
|
|
|
|
|
.B {SMD5}
|
|
|
|
|
use the MD5 algorithm (RFC 1321), the latter with a seed.
|
2002-09-21 01:27:08 +08:00
|
|
|
|
2002-09-21 01:12:58 +08:00
|
|
|
.B {CRYPT}
|
|
|
|
|
uses the
|
|
|
|
|
.BR crypt (3).
|
2002-09-21 01:27:08 +08:00
|
|
|
|
2002-09-21 01:12:58 +08:00
|
|
|
.B {CLEARTEXT}
|
|
|
|
|
indicates that the new password should be added to userPassword as
|
|
|
|
|
clear text.
|
|
|
|
|
.TP
|
2001-06-13 13:40:24 +08:00
|
|
|
.BI \-c " crypt-salt-format"
|
|
|
|
|
Specify the format of the salt passed to
|
|
|
|
|
.BR crypt (3)
|
|
|
|
|
when generating {CRYPT} passwords.
|
|
|
|
|
This string needs to be in
|
|
|
|
|
.BR sprintf (3)
|
|
|
|
|
format and may include one (and only one) %s conversion.
|
|
|
|
|
This conversion will be substituted with a string random
|
|
|
|
|
characters from [A\-Za\-z0\-9./]. For example, "%.2s"
|
|
|
|
|
provides a two character salt and "$1$%.8s" tells some
|
|
|
|
|
versions of crypt(3) to use an MD5 algorithm and provides
|
|
|
|
|
8 random characters of salt. The default is "%s", which
|
|
|
|
|
provides 31 characters of salt.
|
2000-06-16 14:43:55 +08:00
|
|
|
.SH LIMITATIONS
|
2000-08-25 13:31:59 +08:00
|
|
|
The practice storing hashed passwords in userPassword violates
|
2002-09-21 01:27:08 +08:00
|
|
|
Standard Track (RFC 2256) schema specifications and may hinder
|
|
|
|
|
interoperability. A new attribute type, authPassword, to hold
|
|
|
|
|
hashed passwords has been defined (RFC 3112), but is not yet
|
|
|
|
|
implemented in
|
|
|
|
|
.BR slapd (8).
|
2003-12-30 09:37:38 +08:00
|
|
|
.TP
|
|
|
|
|
It should also be noted that the behavior of
|
|
|
|
|
.BR crypt (3)
|
|
|
|
|
is platform specific.
|
2000-06-16 14:43:55 +08:00
|
|
|
.SH "SECURITY CONSIDERATIONS"
|
|
|
|
|
Use of hashed passwords does not protect passwords during
|
|
|
|
|
protocol transfer. TLS or other eavesdropping protections
|
2003-12-30 09:37:38 +08:00
|
|
|
should be in\-place before using LDAP simple bind.
|
|
|
|
|
.TP
|
|
|
|
|
The hashed password values should be protected as if they
|
2000-06-16 14:43:55 +08:00
|
|
|
were clear text passwords.
|
|
|
|
|
.SH "SEE ALSO"
|
2000-07-23 02:32:33 +08:00
|
|
|
.BR ldappasswd (1),
|
|
|
|
|
.BR ldapmodify (1),
|
2000-06-16 14:43:55 +08:00
|
|
|
.BR slapd (8)
|
2000-08-25 13:31:59 +08:00
|
|
|
.BR slapd.conf (5)
|
2002-09-21 01:27:08 +08:00
|
|
|
.B RFC 2307
|
|
|
|
|
.B RFC 2256
|
|
|
|
|
.B RFC 3112
|
2000-08-14 06:06:01 +08:00
|
|
|
.LP
|
2000-08-25 07:18:06 +08:00
|
|
|
"OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
|
2000-06-16 14:43:55 +08:00
|
|
|
.SH ACKNOWLEDGEMENTS
|
2000-08-25 13:31:59 +08:00
|
|
|
OpenLDAP is developed and maintained by
|
|
|
|
|
The OpenLDAP Project (http://www.openldap.org/).
|
|
|
|
|
OpenLDAP is derived from University of Michigan LDAP 3.3 Release.
|
