Re: slappasswd compiles but fails to work without --enable-crypt (ITS#2906)

[cat@reptiles.org]

On Thu, 8 Jan 2004, Kurt D. Zeilenga wrote:
> At 07:36 PM 1/8/2004, Cat Okita wrote:
> >Was there a specific design reason for using curly brackets,
> RFC 2307.

I'm sorry - I should be clearer. My question is about the design
decisions for slappasswd, not the ldap standard ;>

I'm aware that the attribute descriptions require the presence of
curly brackets, and think that it's grand to have the output of
slappasswd in the correct format for inclusion as a userPassword
attribute.

Essentially I'm curious about the use of -h {CRYPT} rather than
-h CRYPT, given that curly brackets have different reactions to
different shells.

Beyond that, would submitting a patch to slappasswd to add the --help
option, and modify the usage information that appears below to be more
verbose be worthwhile?

/usr/sbin/slappasswd --help
/usr/sbin/slappasswd: invalid option -- -
Usage: /usr/sbin/slappasswd [options]
   -h hash       password scheme
   -s secret     new password
   -c format     crypt(3) salt format
   -u            generate RFC2307 values (default)
   -v            increase verbosity

cheers!
==========================================================================
"A cat spends her life conflicted between a deep, passionate and profound
desire for fish and an equally deep, passionate and profound desire to
avoid getting wet.  This is the defining metaphor of my life right now."