The PKCS #12 utility makes sharing of certificates among Enterprise server 3.x and any server (Netscape products or non-Netscape products) that supports PKCS#12 possible. The tool allows you to import certificates and keys from pkcs #12 files into NSS or export them and also list certificates and keys in such files.
-i p12File [-h tokenname] [-v] [common-options]
-o p12File -n certname [-c keyCipher]
[-C certCipher] [-m | --key_len keyLen] [-n | --cert_key_len certKeyLen] [common-options]
-l p12File [-h tokenname] [-r] [common-options]
[-d dir] [-P dbprefix]
[-k slotPasswordFile | -K slotPassword] [-w p12filePasswordFile | -W p12filePassword]
pk12util option [arguments]
where option and arguments are
combinations of the options and arguments listed in the following
section. Three of the options, -i, -o, and -l, should be considered commands
of the pk12util invocation. Each command takes several options. Options may take zero or
more arguments. To see a usage string, issue the pkcs12util command without any
options.
pk12util command are defined as follows:
| Options | |
|
Import a certificate and private key from the p12file into the database. |
|
|
Export certificate and private key, specified by the -n option, from the database to the p12 file. |
|
|
Specify the nickname of the cert and private key to export. |
|
|
|
Specify the prefix used on the |
|
|
Specify the text file containing the pkcs 12 file's password |
|
|
Specify the pkcs 12 file's password |
|
|
Specify the key encryption algorithm |
|
|
Specify the PFX encryption algorithm |
|
|
Specify the desired length of the symmetric key to be used to encrypt the private key |
|
|
Specify the desired length of the symmetric key to be used to encrypt the top level protocol data unit |
PKCS #12 provides for not only the protection of the private keys but also the certificate and meta-data associated with the keys. Password based encryption is used to protect private keys on export to a PKCS #12 file and also the entire package when allowed. If no algorithm is specified, the tool defaults to using "PKCS12 V2 PBE With SHA1 And 3KEY Triple DES-cbc" for private key encryption. For historical export control reasons "PKCS12 V2 PBE With SHA1 And 40 Bit RC4" is the default for the overall package encryption when not in FIPS mode and no package encryption when in FIPS mode. The private key is always protected with strong encryption by default. A list of ciphers follows.
It should be noted that the crypto provider may be the softtoken module or an external hardware module. It may be the case that the cryptographic module does not support the requested algorithm and a best fit will be selected, likely to be the default. If no suitable replacement for the desired algorithm can be found a "no security module can perform the requested operation" will appear on the error message.
0 - No error
1 - User Cancelled
2 - Usage error
6 - NLS init error
8 - Certificate DB open error
9 - Key DB open error
10 - File initialization error
11 - Unicode conversion error
12 - Temporary file creation error
13 - PKCS11 get slot error
14 - PKCS12 decoder start error
15 - error read from import file
16 - pkcs12 decode error
17 - pkcs12 decoder verify error
18 - pkcs12 decoder validate bags error
19 - pkcs12 decoder import bags error
20 - key db conversion version 3 to version 2 error
21 - cert db conversion version 7 to version 5 error
22 - cert and key dbs patch error
23 - get default cert db error
24 - find cert by nickname error
25 - create export context error
26 - PKCS12 add password itegrity error
27 - cert and key Safes creation error
28 - PKCS12 add cert and key error
29 - PKCS12 encode error