HP-UX Directory Server 8.1 administration server guide

Where task is one of the commands listed in Table 4-1 “Task commands for modutil” and
option is from Table 4-2 “Options for modutil”. Each modutil command can take one task
and one option.
Tasks and options You can use the modutil tool to perform a number of different tasks. These
tasks are specified through the use of commands and options. Commands specify the task to
perform. Options modify a task command.
NOTE:
Each modutil command can take one task and one option.
Table 4-1 “Task commands for modutil” describes what the modutil commands do and what
options are available for each. Table 4-2 “Options for modutil” defines what the options do.
Table 4-1 Task commands for modutil
Allowed optionsDescriptionTasks
-libfile libraryFile
-mechanisms mechanismList
Adds the named PKCS #11 module
to the database.
-add moduleName
-pwfile passwordFile
-newpwfile newPasswordFile
Changes the password for the named
token. If the token has not been
initialized, this option initializes it
with the supplied password. In this
context, the term password is
equivalent to a personal identification
number (PIN).
-changepw token
-dbdir dbFolderCreates new secmod.db, key3.db,
and cert8.db files. If any of these
security databases already exist in a
specified directory, the modutil tool
displays an error message.
-create
-mechanisms mechanismList
Sets the security mechanisms for
which the named module is a default
provider.
-default moduleName
Deletes the named module.
You cannot delete the internal PKCS
#11 module.
-delete moduleName
-slot slotName
Disables all slots on the named
module. To disable a specific slot, use
the -slot option.
-disable moduleName
-slot slotName
Enables all slots on the named
module. To enable a specific slot, use
the -slot option.
-enable moduleName
Enables or disables FIPS-140-1
compliance for the internal module.
true enabled FIPS compliance, and
false disable FIPS compliance.
-fips true | false
Disables the modutil tool's
interactive prompts so it can be run
from a script. Use this command only
after manually testing each planned
operation to check for warnings and
to ensure that bypassing the prompts
will cause no security lapses or loss
of database integrity.
-force
46 Admin Server command-line tools