Table 4-2 Options for modutil (continued)

Option

Description

-mechanismsmechanismList

Specifies the security mechanisms for which a particular module is the default

 

provider. The mechanismList is a colon-separated list of mechanism names.

 

Enclose this list in quotation marks if it contains spaces. The module becomes

 

a default provider for the listed mechanisms when those mechanisms are

 

enabled. If more than one module is assigned as a mechanism's default

 

provider, the mechanism's default provider is listed as undefined. The

 

following mechanisms are currently available:

 

RSA

 

DSA

 

RC2, RC4, and RC5

 

AES

 

DES

 

DH

 

SHA1 and SHA256

 

SSL and TLS

 

MD2 and MD5

 

RANDOM (for random number generation)

 

FRIENDLY (for certificates that are publicly readable).

-newpwfilenewPasswordFile

Specifies a text file containing a token's new password. This allows the

 

password to be automatically updated when using the -changepwcommand.

-nocertdb

Instructs modutil not to open the certificate or key databases. This has several

 

effects:

 

When used with the -changepwcommand, no one is able to set or change

 

 

the password on the internal module, because the password is stored in

 

 

key3.db.

 

When used with the -createcommand, only a secmod.db file will be

 

 

created; cert8.db and key3.db will not be created.

 

When used with the -jarcommand, signatures on the JAR file will not

 

 

be checked.

-pwfilepasswordFile

Specifies a text file containing a token's current password. This allows

 

automatic entry of the password when using the -changepwcommand.

-slotslotName

Specifies a particular slot to enable or disable when using the -enableor

 

-disableoptions.

-tempdirtemporaryFolder

Specifies a folder in which to store temporary files created by the -jar

 

command. If a temporary folder is not specified, the current folder is used.

JAR information file JAR (Java Archive) is a platform-independent file format that aggregates many files into one. JAR files are used by modutil to install PKCS #11 modules. When modutil uses a JAR file, a special JAR information file must be included. This information file contains special scripting instructions and must be specified in the JAR file's MANIFEST file. Although the information file can have any name, it is specified using the Pkcs11_install_script METAINFO command.

For details on how to declare this METAINFO command in the MANIFEST, see http://docs.sun.com/ source/816-6164-10/contents.htm.

If a PKCS #11 installer script is stored in the information file pk11install, the text file for the Signing Tool contains the following METAINFO tag:

+Pkcs11_install_script: pk11install

Examples of using modutil

“Creating database files”

“Displaying module information”

“Setting a default provider”

48 Admin Server command-line tools

Page 48
Image 48
HP UX Direry Server manual Examples of using modutil

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.