View source for PKCS11 Module Specs


== PKCS #11 Module Specs ==

The following is a proposal to the PKCS #11 working group made in August 2001 for configuring PKCS #11 modules. NSS currently implements this proposal internally.

The file format consists of name/value pairs of the form ''name''=''value''. 
Each name/value pair is separated by a blank value. A single line, 
terminated by a '\n', '\r\n', or '\r' represents a single pkcs #11 library.

Names can be any alpha/numeric combination, and are parsed case-insensitive.

Values can contain any printable ascii value, including UTF8 characters. 
Values can contain imbedded blanks either through quoting the entire 
value, or by escaping the imbedded blanks with '\'. The value is 
considered quoted if the first character after the '=' is ', ", {,  [, 
(, or <. If the value is quoted, then the value is terminated with and 
ending quote of the form ', ", ), ], }, or > matching the respective 
starting quote. Ending quotes can be escaped. Imbedded '\' charaters are 
considered escape characters for the next character in the stream. Note 
that case must be preserved in the values.

These modules specs can be passed by the application directly to NSS via the SECMOD_LoadUserModule() call. To initialize a PKCS #11 module 'on-the-fly'.

=== Recognized Names: ===

All applications/libraries must be able recognize the following name values:

<br>'''library''' - This specifies the path to the pkcs #11 library.
<br>'''name''' - This specifies the name of the pkcs #11 library.
<br>'''parameter''' - This specifies a pkcs #11 library parameter with the application must pass to the pkcs #11 library at C_Initialize() time (see below).

In additions applications/libraries should be able to ignore additional 
name value pairs which are used to specify configuration for other applications.
Of course these application/libraries should be able to parse their own 
name/value pairs.

Each of these name/value pairs are optional.

If the library is not specified, the line represents some application 
specific meta configuration data. Other applications and libraries can 
safely ignore this line.

If the name is not specified, the application can use the library path 
to describe the PKCS #11 library in any UI it may have.

If the parameter is not specified, no parameters are passed to the PKCS #11 module.

If the application/library does not find its application/library 
specific data, it should use it's defaults for this pkcs #11 library.

=== Parameter Passing: ===

If the parameter is specified, the application/library will strip the 
value out, processing any outter quotes and escapes appropriately, and 
pass the parameter to the pkcs #11 library when it calls C_Initialize().

A new CK_C_INITIALIZE_ARGS structure is defined as

<pre>
typedef struct CK_C_INITIALIZE_ARGS {
  CK_CREATEMUTEX CreateMutex;
  CK_DESTROYMUTEX DestroyMutex;
  CK_LOCKMUTEX LockMutex;
  CK_UNLOCKMUTEX UnlockMutex;
  CK_FLAGS flags;
  CK_VOID_PTR LibraryParameters;
  CK_VOID_PTR pReserved;
} CK_C_INITIALIZE_ARGS;
</pre>

Applications/libraries must set LibraryParameters to NULL if no 
parameter value is specified. PKCS #11 libraries which accept parameters 
must check if the 'new' pReserved field is NULL if and only if 
LibraryParameters field is not NULL.

== NSS Specific Parameters in Module Specs ==

Here are the NSS Application specific parameters in use. 
This data is currently store in secmod.db. This isn't part of the 
generic spec (that is other applications need not parse it, nor pkcs #11
modules need supply them.


'''NSS'''="''nss_params''"

''nss_params'' are themselves name/value pairs, parsed with the same rules
described above. Valid names inside nss_params are:
<dl>
<dd>'''flags''' - comma separated list of flag values, parsed case-insensitive. <br>Valid flag values are:
<dl>
<dd>'''internal''' - this library is actually the Netscape internal library
<br>'''fips''' - this library is the Netscape internal fips library.
<br>'''critical''' - if this library cannot be loaded, completely fail initialization.
<br>'''moduleDB''' - this library includes NSS specific functions to supply additional module specs for loading.
'''moduleDBOnly''' - this library has no PKCS #11 functions and is only used for loading additional modules.</dd>
</dl>
'''trustOrder''' - integer value specifying the order in which the trust information for certificates specified by tokens on this PKCS #11 library should be rolled up. '0' means that tokens on this library should not supply trust information (default). The relative order of two pkcs#11 libraries which have the same trustOrder value is undefined.
<br>'''cipherOrder''' - integer value specifiying the order in which tokens are searched when looking for a token to do a generic operation (DES/Hashing, etc).
<br>'''ciphers''' - comma separated list of ciphers this token will enable that isn't already enabled by the library (currently only '''FORTEZZA''' is defined) (case-insensitive).
<br>'''slotParams''' - space separated list of name/value pairs where the name is a slotID and the value is a space sparated list of parameters related to that slotID.
<br>Valid slotParams values are:
<dl><dd>
'''slotFlags''' - comma separated list of cipher groups which this slot is expected to be the default implementation for (case-insensitive).
<br>Valid flags are:
<dl><dd>
'''RSA''' - This token should be used for all RSA operations (other than Private key operations where the key lives in another token).
<br>'''DSA''' - This token should be used for all DSA operations (other than Private key operations where the key lives in another token).
<br>'''RC4''' - This token  should be used for all RC4 operations which are not constrained by an existing key in another token.
<br>'''RC2''' - This token  should be used for all RC2 operations which are not constrained by an existing key in another token.
<br>'''DES''' - This token  should be used for all DES, DES2, and DES3 operations which are not constrained by an existing key in another token.
<br>'''DH''' - This token should be used for all DH operations (other than Private key operations where the key lives in another token).
<br>'''FORTEZZA'''- This token should be used for all KEA operations (other than Private key operations where the key lives in another token), as well as SKIPJACK operations which are not constrained by an existing key in another token.
<br>'''RC5''' - This token  should be used for all RC5 operations which are not constrained by an existing key in another token.
<br>'''SHA1''' - - This token should be used for all basic SHA1 hashing.
<br>'''MD5''' - This token should be used for all basic MD5 hashing.
<br>'''MD2''' - This token should be used for all basic MD2 hashing.
<br>'''SSL''' - This token should be used for SSL key derivation which are not constrained by an existing key in another token.
<br>'''TLS''' - This token should be used for TLS key derivation which are not constrained by an existing key in another token.
<br>'''AES''' - This token  should be used for all AES operations which are not constrained by an existing key in another token.
<br>'''RANDOM''' - This token should be used to generate random numbers when the application call 'PK11_GenerateRandom'.
<br>'''PublicCerts''' - The certificates on this token can be read without authenticating to this token, and any user certs on this token have a patching public key which is also readable without authenticating. Setting this flags means NSS will not try to authenticate to the token when searching for Certificates. This removes spurious password prompts, but if incorrectly set it can also cause NSS to miss certificates in a token until that token is explicitly logged in.</dd>
</dl>
'''rootFlags''' - comma separated of flags describing any root certs that may be stored (case-insensitive).
<br>Valid flags are:
<dl><dd>
'''hasRootCerts''' - claims that this token has the default root certs and trust values. At init time NSS, will try to look for a default root cert device if one has not already been loaded.
<br>'''hasRootTrust''' - parsed but ignored.
<br>'''timeout'''  - time in minutes before the current authentication should be rechecked. This value is only used if askpwd is set to 'timeout'. (default = 0).
<br>'''askpwd'''   - case-insensitive flag describing how password prompts should be manages. Only one of the following can be specified.
<dl><dd>
'''every''' - prompt whenever the a private key on this token needs to be access (this is on the entire token, not on a key-by-key basis.
<br>'''timeout'''- whenever the last explicit login was longer than 'timeout' minutes ago.
<br>'''only''' - authenticate to the token only when necessary (default).</dd>
</dl></dd>
</dl></dd>
</dl>

Sample file:
<pre>
library= name="Netscape Internal Crypto Module"   parameters="configdir=/u/relyea/.netscape certprefix= secmod=secmod.db" NSS="Flags=internal,pkcs11module TrustOrder=1 CipherOrder=-1 ciphers= slotParams={0x1=[slotFlags='RSA,DSA,DH,RC4,RC2,DES,MD2,MD5,SHA1,SSL,TLS,PublicCerts,Random'] 0x2=[slotFlags='RSA' askpw=only]}"
library=dkck32.dll name="DataKey SignaSURE 3600" NSS="TrustOrder=50 ciphers= " 
library=swft32.dll name="Netscape Software Fortezza" parameters="keyfile=/u/relyea/keyfile" NSS="TrustOrder=50 ciphers=FORTEZZA slotParams=0x1=[slotFlags='FORTEZZA']"
library=core32.dll name="Litronic Netsign"
</pre>

== Softoken Specific Parameters ==

The internal NSS PKCS #11 implementation (softoken) requires Applications parameters. It will not initialize if the '''parameters'''= is not specified.
If another application wishes to load the softoken, that application must supply a non-NULL libraryParameters value in the CK_C_INITIALIZE_ARGS structure passed at C_INITIALIZE time. The parameter passed to softoken is a space separated list of name/value pairs exactly like those specified in the PKCS #11 module spec.

Valid values are:
<dl><dd>
'''configDir''' - Configuration Directory where NSS can store persistant state information (typically databases).
<br>'''secmod'''    - Name of the secmod database (default = secmod.db).
<br>'''certPrefix''' - Prefix for the cert database.
<br>'''keyPrefix''' - Prefix for the key database.
<br>'''minPWLen''' - Minimum password length in bytes.
<br>'''manufacturerID''' - Override the default manufactureID value for the module returned in the CK_INFO, CK_SLOT_INFO, and CK_TOKEN_INFO structures with an internationalize string (UTF8). This value will be truncated at 32 bytes (no NULL, partial UTF8 characters dropped).
<br>'''libraryDescription''' - Override the default libraryDescription value for the module returned in the CK_INFO structure with an internationalize string (UTF8). This value will be truncated at 32 bytes (no NULL, partial UTF8 characters dropped).
<br>'''cryptoTokenDescription''' - Override the default label value for the internal crypto token returned in the CK_TOKEN_INFO structure with an internationalize string (UTF8). This value will be truncated at 32 bytes (no NULL, partial UTF8 characters dropped).
<br>'''dbTokenDescription''' - Override the default label value for the internal DB token returned in the CK_TOKEN_INFO structure with an internationalize string (UTF8). This value will be truncated at 32 bytes (no NULL, partial UTF8 characters dropped).
<br>'''FIPSTokenDescription''' - Override the default label value for the internal FIPS token returned in the CK_TOKEN_INFO structure with an internationalize string (UTF8). This value will be truncated at 32 bytes (no NULL, partial UTF8 characters dropped).
<br>'''cryptoSlotDescription''' - Override the default slotDescription value for the internal crypto token returned in the CK_SLOT_INFO structure with an internationalize string (UTF8). This value will be truncated at 64 bytes (no NULL, partial UTF8 characters dropped).
<br>'''dbSlotDescription''' - Override the default slotDescription value for the internal DB token returned in the CK_SLOT_INFO structure with an internationalize string (UTF8). This value will be truncated at 64 bytes (no NULL, partial UTF8 characters dropped).
<br>'''FIPSSlotDescription''' - Override the default slotDecription value for the internal FIPS token returned in the CK_SLOT_INFO structure with an internationalize string (UTF8). This value will be truncated at 64 bytes (no NULL, partial UTF8 characters dropped).
<br>'''flags''' - comma separated list of flag values, parsed case-insensitive.
<br>Valid flags are:
<dl><dd>
'''noModDB''' - don't open SECMOD.db and try to supply the strings. The MOD DB function is not through standard PKCS #11 interfaces.
<br>'''readOnly''' -  Databases should be opened read only.
<br>'''noCertDB''' - Don't try to open a certificate database.
<br>'''noKeyDB''' - Don't try to open a key database.
<br>'''forceOpen''' - Don't fail to initialize the token if the databases could not be opened.
<br>'''passwordRequired''' - zero length passwords are not acceptable (valid only if there is a keyDB).
<br>'''optimizeSpace''' - allocate smaller hash tables and lock tables.When this flag is not specified, Softoken will allocate large tables to prevent lock contention.
<br>'''tokens''' - configure 'tokens' by hand. The tokens parameter specifies a space sparated list of slotIDS, each of which specify their own set of parameters affecting that token. Typically 'tokens' would not be specified unless additional databases are to be opened as additional tokens. If tokens is specified, then all tokens (including the default tokens) need to be specified. If tokens is not specified, then softoken would default to the following specs:<br>
In non-FIPS mode:
 tokens=<0x01=[configDir=''configDir'' tokenDescription=''cryptoTokenDescription'' slotDescription=''cryptoSlotDescription'' flags=noCertDB,noKeyDB,''optimizeSpace''] 0x02=[configDir=''configDir'' tokenDescription=''dbTokenDescription'' slotDescription=''dbSlotDescription'' certPrefix=''certPrefix'' keyPrefix=''keyPrefix'' flags=''flags'' minPWLen=''minPWLen'']><br>
In FIPS mode:
 tokens=<0x03=[configDir=''configDir'' tokenDescription=''FIPSTokenDescription'' slotDescription=''FIPSSlotDescription'' certPrefix=''certPrefix'' keyPrefix=''keyPrefix'' flags=''flags'' minPWLen=''minPWLen'']><br>
where ''configDir'', ''cryptoTokenDescription'', ''cryptoSlotDescription'', ''dbTokenDescription'', ''dbSlotDescription'', ''FIPSTokenDescription'', ''FIPSSlotDescription'', ''optimizeSpace'', ''certPrefix'', ''keyPrefix'', ''flags'', and ''minPWLen'' are copied from the parameters above.<br>
Parameters:
<dl><dd>
'''configDir''' - The location of the databases for this token. If configDir is not specified, the default configDir specified earlier will be used. 
<br>'''certPrefix''' - Cert prefix for this token. 
<br>'''keyPrefix''' - Prefix for the key database for this token. 
<br>'''tokenDescription''' - The label value for this token returned in the CK_TOKEN_INFO structure with an internationalize string (UTF8). This value will be truncated at 32 bytes (no NULL, partial UTF8 characters dropped). 
<br>'''slotDescription''' - The slotDescription value for this token returned in the CK_SLOT_INFO structure with an internationalize string (UTF8). This value will be truncated at 64 bytes (no NULL, partial UTF8 characters dropped). 
<br>'''minPWLen''' - minimum password length for this token. 
<br>'''flags''' - comma separated list of flag values, parsed case-insensitive.
<br>Valid flags are:
<dl><dd>
'''readOnly''' - Databases should be opened read only. 
<br>'''noCertDB''' - Don't try to open a certificate database. 
<br>'''noKeyDB''' - Don't try to open a key database. 
<br>'''forceOpen''' - Don't fail to initialize the token if the databases could not be opened. 
<br>'''passwordRequired''' - zero length passwords are not acceptable (valid only if there is a keyDB). 
<br>'''optimizeSpace''' -  allocate smaller hash tables and lock tables.When this flag is not specified, Softoken will allocate large tables to prevent lock contention.
</dd></dl>
</dd></dl>
</dd></dl>
</dd></dl>
Examples: