Netscape MANAGEMENT SYSTEM 6.2 - COMMAND-LINE Manual page 47

Use this argument to specify the message digest algorithm the tool should use
to hash the PINs before storing them in the authentication directory. If you
want to store PINs as SHA-1 or MD5 hashed values in the directory, be sure to
specify an output file for storing PINs in plain text. You will need the PINs in
plain text for delivering them to end entities.
produces a 160-bit message digest. This option is used by default.
sha1
produces a 128-bit message digest.
md5
does not hash the PINs.
none
• [saltattribute=<LDAP_attribute_to_use_for_salt_creation>]
Use this argument to specify the LDAP attribute the tool should use for salt
creation. If you specify an attribute, the tool integrates the corresponding value
of the attribute with each PIN, and hashes the resulting string with the hash
routine specified in the hash argument.
If you don't specify this argument, the DN of the user is used. For details, see
"How PINs Are Stored in the Directory" on page 54.
• [input=<file_name>]
Use this argument to specify the name of the file that contains the list of DNs to
process. Using this argument is optional. If you do, the tool compares the
filtered DNs to the ones specified by the input file and generates PINs for only
those DNs that are also in the file.
• [output=<file_name>]
Use this argument to specify the absolute path to the file to which the tool
should write the PINs as it generates them; this is the file to which the tool will
capture the output.
If you don't specify a filename, the tool will write the output to the standard
output. In any case, all the error messages will be directed to the standard
error.
• [write]
Use this argument to specify whether the tool should write PINs to the
directory. If specified, the tool writes PINs (as it generates) to the directory.
Otherwise, the tool does not make any changes to the directory.
For example, if you want to check PINs—that the PINs are being given to the
correct users and that they are conforming to the length and character-set
restrictions—before updating the directory, do not specify this option. You can
check the PINs before updating the directory by looking at the output file; for
details, see "Output File" on page 53.
The setpin Command
Chapter 5 PIN Generator Tool 47