Using the Security Module Database (modutil)
Newsgroup: mozilla.dev.tech.crypto
The Security Module Database Tool is a command-line utility for managing PKCS #11 module information within secmod.db files or within hardware tokens. You can use the tool to add and delete PKCS #11 modules, change passwords, set defaults, list module contents, enable or disable slots, enable or disable FIPS 140-2 compliance, and assign default providers for cryptographic operations. This tool can also create key3.db, cert8.db, and secmod.db security database files.
key3.db files) and certificate databases (cert8.db files). The key, certificate, and PKCS #11 module management process generally begins with creating the keys and key database necessary to generate and manage certificates and the certificate database.
This document discusses security module database management. For information on certificate database and key database management, see Using the Certificate Database Tool.
Availability
This tool is known to build on Solaris 2.5.1 (SunOS 5.5.1) and Windows NT 4.0.Syntax
To run the Security Module Database Tool, type the commandmodutil option [arguments]
where option and arguments are combinations of the options and arguments listed in the following section. Each command takes one option. Each option may take zero or more arguments. To see a usage string, issue the command without options.
Options and Arguments
Options specify an action. Option arguments modify an action. The options and arguments for themodutil command are defined as follows:
Usage
The Security Module Database Tool's capabilities are grouped as follows, using these combinations of options and arguments. The options and arguments in square brackets are optional, those without square brackets are required.-
Creating a set of security management database files (
key3.db,cert8.db, andsecmod.db): - Displaying basic module information or detailed information about the contents of a given module:
- Adding a PKCS #11 module, which includes setting a supporting library file, enabling ciphers, and setting default provider status for various security mechanisms:
- Adding a PKCS #11 module from an existing JAR file:
- Deleting a specific PKCS #11 module from a security module database:
- Initializing or changing a token's password:
- Setting the default provider status of various security mechanisms in an existing PKCS #11 module:
- Clearing the default provider status of various security mechanisms in an existing PKCS #11 module:
- Enabling a specific slot or all slots within a module:
- Disabling a specific slot or all slots within a module:
- Enabling or disabling FIPS 140-2 compliance within the Netscape Communicator internal module:
- Disabling interactive prompts for the Security Module Database Tool, to support scripted operation:
-create
-list [modulename]
-addmodulename-libfilelibrary-file[-cipherscipher-enable-list]mechanism-list
[-mechanisms]
-jarJAR-file-installdirroot-installation-directorytemporary-directory
[-tempdir]
-delete modulename
-changepwtokenname[-pwfileold-password-file]new-password-file
[-newpwfile]
-defaultmodulename-mechanismsmechanism-list
-undefaultmodulename-mechanismsmechanism-list
-enablemodulename[-slotslotname]
-disablemodulename[-slotslotname]
-fips [true | false]
-force
JAR Installation File
When a JAR file is run by a server, by the Security Module Database Tool, or by any program that does not interpret JavaScript, a special information file must be included in the format described below. This information file contains special scripting and must be declared in the JAR archive's manifest file. The script can have any name. The metainfo tag for this isPkcs11_install_script. To declare meta-information in the manifest file, put it in a file that is passed to the Netscape Signing Tool.
Sample Script
For example, the PKCS #11 installer script could be in the filepk11install. If so, the metainfo file for the Netscape Signing Tool would include a line such as this:
+ Pkcs11_install_script: pk11installForwardCompatible { IRIX:6.2:mips SUNOS:5.5.1:sparc }
Platforms {
WINNT::x86 {
ModuleName { "Fortezza Module" }
ModuleFile { win32/fort32.dll }
DefaultMechanismFlags{0x0001}
DefaultCipherFlags{0x0001}
Files {
win32/setup.exe {
Executable
RelativePath { %temp%/setup.exe }
}
win32/setup.hlp {
RelativePath { %temp%/setup.hlp }
}
win32/setup.cab {
RelativePath { %temp%/setup.cab }
}
}
}
WIN95::x86 {
EquivalentPlatform {WINNT::x86}
}
SUNOS:5.5.1:sparc {
ModuleName { "Fortezza UNIX Module" }
ModuleFile { unix/fort.so }
DefaultMechanismFlags{0x0001}
CipherEnableFlags{0x0001}
Files {
unix/fort.so {
RelativePath{%root%/lib/fort.so}
AbsolutePath{/usr/local/netscape/lib/fort.so}
FilePermissions{555}
}
xplat/instr.html {
RelativePath{%root%/docs/inst.html}
AbsolutePath{/usr/local/netscape/docs/inst.html}
FilePermissions{555}
}
}
}
IRIX:6.2:mips {
EquivalentPlatform { SUNOS:5.5.1:sparc }
}
}
Script Grammar
The script file grammar is as follows:--> valuelistvaluelist-->value valuelist<null>
value--->key_value_pairstring
key_value_pair-->key{valuelist}
key --> stringstring-->simple_string"complex_string"
simple_string --> [^ \t\n\""{""}"]+
(No whitespace, quotes, or braces.)complex_stringOutside of complex strings, all white space (for example, spaces, tabs, and carriage returns) is considered equal and is used only to delimit tokens.--> ([^\"\\\r\n]|(\\\")|(\\\\))+(Quotes and
backslashes must be escaped with a backslash. A complex string must not
include newlines or carriage returns.)
Keys
Keys are case-insensitive. This section discusses the following keys: Global KeysPer-Platform Keys
Per-File Keys
Global Keys
ForwardCompatible
Gives a list of platforms that are forward compatible. If the current platform cannot be found in the list of supported platforms, then the ForwardCompatible list is checked for any platforms that have the same OS and architecture in an earlier version. If one is found, its attributes are used for the current platform.
Platforms (required)
Gives a list of platforms. Each entry in the list is itself a key-value pair: the key is the name of the platform and the value list contains various attributes of the platform. The ModuleName, ModuleFile, and Files attributes must be specified for each platform unless an EquivalentPlatform attribute is specified. The platform string is in the following format: system name:OS release:architecture. The installer obtains these values from NSPR. OS release is an empty string on non-Unix operating systems. The following system names and platforms are currently defined by NSPR:
- AIX (rs6000)
- BSDI (x86)
- FREEBSD (x86)
- HPUX (hppa1.1)
- IRIX (mips)
- LINUX (ppc, alpha, x86)
- MacOS (PowerPC)
- NCR (x86)
- NEC (mips)
- OS2 (x86)
- OSF (alpha)
- ReliantUNIX (mips)
- SCO (x86)
- SOLARIS (sparc)
- SONY (mips)
- SUNOS (sparc)
- UnixWare (x86)
- WIN16 (x86)
- WIN95 (x86)
- WINNT (x86)
IRIX:6.2:mips
SUNOS:5.5.1:sparc
Linux:2.0.32:x86
WIN95::x86.
Per-Platform Keys
These keys have meaning only within the value list of an entry in thePlatforms list.
ModuleName (required)
Gives the common name for the module. This name will be used to reference the module from Netscape Communicator, the Security Module Database tool (modutil), servers, or any other program that uses the Netscape security module database.
ModuleFile (required)
Names the PKCS #11 module file (DLL or .so) for this platform. The name is given as the relative path of the file within the JAR archive.
Files (required)
Lists the files that need to be installed for this module. Each entry in the file list is a key-value pair: the key is the path of the file in the JAR archive, and the value list contains attributes of the file. At least RelativePath or AbsolutePath must be specified for each file.
DefaultMechanismFlags
Specifies mechanisms for which this module will be a default provider. This key-value pair is a bitstring specified in hexadecimal (0x) format. It is constructed as a bitwise OR of the following constants. If the DefaultMechanismFlags entry is omitted, the value defaults to 0x0.
RSA: 0x00000001
DSA: 0x00000002
RC2: 0x00000004
RC4: 0x00000008
DES: 0x00000010
DH: 0x00000020
FORTEZZA: 0x00000040
RC5: 0x00000080
SHA1: 0x00000100
MD5: 0x00000200
MD2: 0x00000400
RANDOM: 0x08000000
FRIENDLY: 0x10000000
OWN_PW_DEFAULTS: 0x20000000
DISABLE: 0x40000000CipherEnableFlags
Specifies ciphers that this module provides but Netscape Communicator does not, so that Communicator can enable them. This key is a bitstring specified in hexadecimal (0x) format. It is constructed as a bitwise OR of the following constants. If the CipherEnableFlags entry is omitted, the value defaults to 0x0.
FORTEZZA: 0x0000 0001
EquivalentPlatform
Specifies that the attributes of the named platform should also be used for the current platform. Saves typing when there is more than one platform using the same settings.
Per-File Keys
These keys have meaning only within the value list of an entry in aFiles list. At least one of RelativePath and AbsolutePath must be specified. If both are specified, the relative path is tried first, and the absolute path is used only if no relative root directory is provided by the installer program.
RelativePath
Specifies the destination directory of the file, relative to some directory decided at install time. Two variables can be used in the relative path: "%root%" and "%temp%". "%root%" is replaced at run time with the directory relative to which files should be installed; for example, it may be the server's root directory or the Netscape Communicator root directory. The "%temp%" directory is created at the beginning of the installation and destroyed at the end.
The purpose of "%temp%" is to hold executable files (such as setup programs) or files that are used by these programs. For example, a Windows installation might consist of a setup.exe installation program, a help file, and a .cab file containing compressed information. All these files could be installed in the temporary directory. Files destined for the temporary directory are guaranteed to be in place before any executable file is run; they are not deleted until all executable files have finished.
AbsolutePath
Specifies the destination directory of the file as an absolute path. If both RelativePath and AbsolutePath are specified, the installer attempts to use the relative path; if it is unable to determine a relative path, it uses the absolute path.
Executable
Specifies that the file is to be executed during the course of the installation. Typically this string would be used for a setup program provided by a module vendor, such as a self-extracting setup.exe. More than one file can be specified as executable, in which case the files are run in the order in which they are specified in the script file.
FilePermissions
Interpreted as a string of octal digits, according to the standard Unix format. This string is a bitwise OR of the following constants:
user read: 0400Some platforms may not understand these permissions. They are applied only insofar as they make sense for the current platform. If this attribute is omitted, a default of 777 is assumed.
user write: 0200
user execute: 0100
group read: 0040
group write: 0020
group execute: 0010
other read: 0004
other write: 0002
other execute: 0001
Examples
Creating Database FilesDisplaying Module Information
Setting a Default Provider
Enabling a Slot
Enabling FIPS Compliance
Adding a Cryptographic Module
Installing a Cryptographic Module from a JAR File
Changing the Password on a Token
Creating Database Files
This example creates a set of security management database files in the specified directory:modutil -create -dbdir c:\databasesThe Security Module Database Tool displays a warning:
WARNING: Performing this operation while Communicator is running couldAfter you press Enter, the tool displays the following:
cause corruption of your security databases. If Communicator is
currently running, you should exit Communicator before continuing this
operation. Type 'q <enter>' to abort, or <enter> to continue:
Creating "c:\databases\key3.db"...done.
Creating "c:\databases\cert8.db"...done.
Creating "c:\databases\secmod.db"...done.
Displaying Module Information
This example gives detailed information about the specified module:modutil -list "Netscape Internal PKCS #11 Module" -dbdir c:\databasesThe Security Module Database Tool displays information similar to this:
Using database directory c:\databases...
--------------------------------------------------------
Name: Netscape Internal PKCS #11 Module
Library file: **Internal ONLY module**
Manufacturer: Netscape Communications Corp
Description: Communicator Internal Crypto Svc
PKCS #11 Version 2.0
Library Version: 4.0
Cipher Enable Flags: None
Default Mechanism Flags: RSA:DSA:RC2:RC4:DES:SHA1:MD5:MD2
Slot: Communicator Internal Cryptographic Services Version 4.0
Manufacturer: Netscape Communications Corp
Type: Software
Version Number: 4.1
Firmware Version: 0.0
Status: Enabled
Token Name: Communicator Generic Crypto Svcs
Token Manufacturer: Netscape Communications Corp
Token Model: Libsec 4.0
Token Serial Number: 0000000000000000
Token Version: 4.0
Token Firmware Version: 0.0
Access: Write Protected
Login Type: Public (no login required)
User Pin: NOT Initialized
Slot: Communicator User Private Key and Certificate Services
Manufacturer: Netscape Communications Corp
Type: Software
Version Number: 3.0
Firmware Version: 0.0
Status: Enabled
Token Name: Communicator Certificate DB
Token Manufacturer: Netscape Communications Corp
Token Model: Libsec 4.0
Token Serial Number: 0000000000000000
Token Version: 7.0
Token Firmware Version: 0.0
Access: NOT Write Protected
Login Type: Login required
User Pin: NOT Initialized
Setting a Default Provider
This example makes the specified module a default provider for the RSA, DSA, and RC2 security mechanisms:modutil -default "Cryptographic Module" -dbdirThe Security Module Database Tool displays a warning:
c:\databases -mechanisms RSA:DSA:RC2
WARNING: Performing this operation while Communicator is running couldAfter you press Enter, the tool displays the following:
cause corruption of your security databases. If Communicator is
currently running, you should exit Communicator before continuing this
operation. Type 'q <enter>' to abort, or <enter> to continue:
Using database directory c:\databases...
Successfully changed defaults.
Enabling a Slot
This example enables a particular slot in the specified module:modutil -enable "Cryptographic Module" -slotThe Security Module Database Tool displays a warning:
"Cryptographic Reader" -dbdir c:\databases
WARNING: Performing this operation while Communicator is running couldAfter you press Enter, the tool displays the following:
cause corruption of your security databases. If Communicator is
currently running, you should exit Communicator before continuing this
operation. Type 'q <enter>' to abort, or <enter> to continue:
Using database directory c:\databases...
Slot "Cryptographic Reader" enabled.
Enabling FIPS Compliance
This example enables FIPS 140-2 compliance in Communicator's internal module:modutil -dbdir "C:\databases" -fips trueThe Security Module Database Tool displays a warning:
WARNING: Performing this operation while the browser is running could causeAfter you press Enter, the tool displays the following:
corruption of your security databases. If the browser is currently running,
you should exit browser before continuing this operation. Type
'q <enter>' to abort, or <enter> to continue:
FIPS mode enabled.
Adding a Cryptographic Module
This example adds a new cryptographic module to the database:C:\modutil> modutil -dbdir "C:\databases" -add "Cryptorific Module" -The Security Module Database Tool displays a warning:
libfile "C:\winnt\system32\crypto.dll" -mechanisms RSA:DSA:RC2:RANDOM
WARNING: Performing this operation while Communicator is running couldAfter you press Enter, the tool displays the following:
cause corruption of your security databases. If Communicator is
currently running, you should exit Communicator before continuing this
operation. Type 'q <enter>' to abort, or <enter> to continue:
Using database directory C:\databases...
Module "Cryptorific Module" added to database.
C:\modutil>
Installing a Cryptographic Module from a JAR File
This example installs a cryptographic module from the following sample installation script.Platforms {To install from the script, use the following command. The root directory should be the Windows root directory (for example,
WinNT::x86 {
ModuleName { "Cryptorific Module" }
ModuleFile { crypto.dll }
DefaultMechanismFlags{0x0000}
CipherEnableFlags{0x0000}
Files {
crypto.dll {
RelativePath{ %root%/system32/crypto.dll }
}
setup.exe {
Executable
RelativePath{ %temp%/setup.exe }
}
}
}
Win95::x86 {
EquivalentPlatform { Winnt::x86 }
}
}
c:\\windows, or c:\\winnt).
C:\modutil> modutil -dbdir "c:\databases" -jarThe Security Module Database Tool displays a warning:
install.jar -installdir "C:/winnt"
WARNING: Performing this operation while Communicator is running couldAfter you press Enter, the tool displays the following:
cause corruption of your security databases. If Communicator is
currently running, you should exit Communicator before continuing this
operation. Type 'q <enter>' to abort, or <enter> to continue:
Using database directory c:\databases...
This installation JAR file was signed by:
----------------------------------------------
**SUBJECT NAME**
C=US, ST=California, L=Mountain View, CN=Cryptorific Inc., OU=Digital ID
Class 3 - Netscape Object Signing, OU="www.verisign.com/repository/CPS
Incorp. by Ref.,LIAB.LTD(c)9 6", OU=www.verisign.com/CPS Incorp.by Ref
. LIABILITY LTD.(c)97 VeriSign, OU=VeriSign Object Signing CA - Class 3
Organization, OU="VeriSign, Inc.", O=VeriSign Trust Network **ISSUER
NAME**, OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97
VeriSign, OU=VeriSign Object Signing CA - Class 3 Organization,
OU="VeriSign, Inc.", O=VeriSign Trust Network
----------------------------------------------
Do you wish to continue this installation? (y/n) y
Using installer script "installer_script"
Successfully parsed installation script
Current platform is WINNT::x86
Using installation parameters for platform WinNT::x86
Installed file crypto.dll to C:/winnt/system32/crypto.dll
Installed file setup.exe to ./pk11inst.dir/setup.exe
Executing "./pk11inst.dir/setup.exe"...
"./pk11inst.dir/setup.exe" executed successfully
Installed module "Cryptorific Module" into module database
Installation completed successfully
C:\modutil>
Changing the Password on a Token
This example changes the password for a token on an existing module.C:\modutil> modutil -dbdir "c:\databases" -changepwThe Security Module Database Tool displays a warning:
"Communicator Certificate DB"
WARNING: Performing this operation while Communicator is running couldAfter you press Enter, the tool displays the following:
cause corruption of your security databases. If Communicator is
currently running, you should exit Communicator before continuing this
operation. Type 'q <enter>' to abort, or <enter> to continue:
Using database directory c:\databases...
Enter old password:
Incorrect password, try again...
Enter old password:
Enter new password:
Re-enter new password:
Token "Communicator Certificate DB" password changed successfully.
C:\modutil>