Tasks | Description | Allowed options |
Adds a new PKCS #11 module to the | ||
| database. The module must be | installation_directory |
| contained in the named JAR file. | |
| The JAR file identifies all files to |
|
| install, the module name, and |
|
| mechanism flags. It should also |
|
| contain any files to be installed on the |
|
| target machine, including the PKCS |
|
| #11 module library and other files, |
|
| such as documentation. |
|
| The JAR file uses the Netscape Server |
|
| PKCS #11 JAR format. See “JAR |
|
| information file” for more |
|
| information on creating JAR files. |
|
|
|
|
Shows basic information about the |
| |
| contents of the secmod.db file. To |
|
| display detailed information about a |
|
| particular module, including its slots |
|
| and tokens, specify a value for |
|
| moduleName. |
|
|
|
|
Specifies the security mechanisms for | ||
| which the named module will not be |
|
| a default provider. |
|
|
|
|
Table
Option | Description |
Specifies a folder in which to access or create security module database files. | |
| This argument is required for every command. This should point to the Admin |
| Server configuration directory. For example: |
| |
|
|
Specifies the root installation folder for the files supplied with the | |
installation_directory | |
| in which it is appropriate to store dynamic library files. |
|
|
Specifies the library file which contains the PKCS #11 module that is being | |
| added to the database. Use the full path to identify the file. |
|
|
4.2 modutil | 47 |