opencryptoki.conf(5) [centos man page]
OPENCRYPTOKI.CONF(5) openCryptoki OPENCRYPTOKI.CONF(5) NAME
opencryptoki.conf - Configuration file for pkcsslotd. DESCRIPTION
pkcsslotd uses a configuration file at "/etc"/opencryptoki.conf This is a text file that contains information used to configure pkcs#11 slots. At startup, the pkcsslotd daemon parses this file to deter- mine which slots will be made available. SYNTAX
This file is made up of slot descriptions. Each slot description is composed of a slot number, brackets and key-value pairs. slot number { key = value ... } More than one key-value pair may be used within a slot description. A key-value pair is composed of, keyword = value. The following keywords are valid: description A Description of the slot. PKCS#11v2.20 defined this as a 64-byte max character-string. stdll This keyword is used to define the name of the stdll or token library that will be used for this slot. The stdll is an available token library in opencryptoki. manufacturer This keyword is used to name the ID of the slot manufacturer. PKCS#11v2.20 defines this as a 32 byte long string. hwversion Version number of the slot's hardware, if any. The version number is composed of a major version number (the integer portion of the version) and a minor version number (the hundredths portion of the version). For example, version 1.2, major = 1, minor = 2 firmwareversion Version number of the slot's firmware, if any. The version number is composed of a major version number (the integer portion of the version) and a minor version number (the hundredths portion of the version). SEE ALSO opencryptoki(7), pkcsslotd(8), 3.0 September 2012 OPENCRYPTOKI.CONF(5)
Check Out this Related Man Page
PKCSICSF(1) openCryptoki PKCSICSF(1) NAME
pkcsicsf - configuration utility for the ICSF token SYNOPSIS
pkcsicsf [-h] [-l|-a token name] [-b BINDDN] [-c client-cert-file] [-C CA-cert-file] [-k privatekey] [-m mechanism] [-u URI] DESCRIPTION
The pkcsicsf utility lists available ICSF tokens and allows user to add one specific ICSF token to opencryptoki. The ICSF token must be added first to opencryptoki. This creates an entry in the opencryptoki.conf file for the ICSF token. It also creates a token_name.conf configuration file in the same directory as the opencryptoki.conf file, containing ICSF specific information. This information is read by the ICSF token. The ICSF token must bind and authenticate to an LDAP server. The supported authentication mechanisms are simple and sasl. One of these mechanisms must be entered when listing the available ICSF tokens or when adding an ICSF token. Opencryptoki currently supports adding only one ICSF token. The system admin can either allow the ldap calls to utilize exisiting ldap configs, such as ldap.conf or .ldaprc for bind and authentica- tion information or set the bind and authentication information within opencryptoki by using this utility and its options. The information will then be placed in the token_name.conf file to be used in the ldap calls. When using simple authentication, the user will be prompted for the racf password when listing or adding a token. OPTIONS
-a token name add the specified ICSF token to opencryptoki. -b BINDND the distinguish name to bind when using simple authentication -c client-cert-file the client certificate file when using SASL authentication -C CA-cert-file the CA certificate file when using SASL authentication -h show usage information -k privatekey the client private key file when using SASL authentication -m mechanism the authentication mechanism to use when binding to the LDAP server (this should be either simple or sasl) -l list available ICSF tokens -h show usage information FILES
/etc/opencryptoki/opencryptoki.conf the opencryptoki config file containing token configuration information /etc/opencryptoki/token_name.conf contains ICSF configuration information for the ICSF token SEE ALSO
opencryptoki(7), pkcsslotd(8). pkcsconf(8). 3.0 April 2013 PKCSICSF(1)