6 pkcs12 - PKCS#12 file utility
14 [B<-certfile filename>]
38 [B<-password password>]
43 The B<pkcs12> command allows PKCS#12 files (sometimes referred to as
44 PFX files) to be created and parsed. PKCS#12 files are used by several
45 programs including Netscape, MSIE and MS Outlook.
47 =head1 COMMAND OPTIONS
49 There are a lot of options the meaning of some depends of whether a PKCS#12 file
50 is being created or parsed. By default a PKCS#12 file is parsed a PKCS#12
51 file can be created by using the B<-export> option (see below).
53 =head1 PARSING OPTIONS
59 This specifies filename of the PKCS#12 file to be parsed. Standard input is used
62 =item B<-out filename>
64 The filename to write certificates and private keys to, standard output by default.
65 They are all written in PEM format.
67 =item B<-pass password>
69 the PKCS#12 file password. Since certain utilities like "ps" make the command line
70 visible this option should be used with caution.
74 read the PKCS#12 file password from the environment variable B<var>.
78 this option inhibits output of the keys and certificates to the output file version
83 only output client certificates (not CA certificates).
87 only output CA certificates (not client certificates).
91 no certificates at all will be output.
95 no private keys will be output.
99 output additional information about the PKCS#12 file structure, algorithms used and
104 use DES to encrypt private keys before outputting.
108 use triple DES to encrypt private keys before outputting, this is the default.
112 use IDEA to encrypt private keys before outputting.
116 don't encrypt the private keys at all.
120 don't attempt to verify the integrity MAC before reading the file.
124 prompt for separate integrity and encryption passwords: most software
125 always assumes these are the same so this option will render such
126 PKCS#12 files unreadable.
130 =head1 FILE CREATION OPTIONS
136 This option specifies that a PKCS#12 file will be created rather than
139 =item B<-out filename>
141 This specifies filename to write the PKCS#12 file to. Standard output is used
144 =item B<-in filename>
146 The filename to read certificates and private keys from, standard input by default.
147 They must all be in PEM format. The order doesn't matter but one private key and
148 its corresponding certificate should be present. If additional certificates are
149 present they will also be included in the PKCS#12 file.
151 =item B<-inkey filename>
153 file to read private key from. If not present then a private key must be present
156 =item B<-name friendlyname>
158 This specifies the "friendly name" for the certificate and private key. This name
159 is typically displayed in list boxes by software importing the file.
161 =item B<-certfile filename>
163 A filename to read additional certificates from.
165 =item B<-caname friendlyname>
167 This specifies the "friendly name" for other certificates. This option may be
168 used multiple times to specify names for all certificates in the order they
169 appear. Netscape ignores friendly names on other certificates whereas MSIE
172 =item B<-pass password>
174 the PKCS#12 file password. Since certain utilities like "ps" make the command line
175 visible this option should be used with caution.
177 =item B<-envpass var>
179 read the PKCS#12 file password from the environment variable B<var>.
183 if this option is present then an attempt is made to include the entire
184 certificate chain of the user certificate. The standard CA store is used
185 for this search. If the search fails it is considered a fatal error.
189 encrypt the certificate using triple DES, this may render the PKCS#12
190 file unreadable by some "export grade" software. By default the private
191 key is encrypted using triple DES and the certificate using 40 bit RC2.
193 =item B<-keypbe alg>, B<-certpbe alg>
195 these options allow the algorithm used to encrypt the private key and
196 certificates to be selected. Although any PKCS#5 v1.5 or PKCS#12 algorithms
197 can be selected it is advisable only to use PKCS#12 algorithms. See the list
198 in the B<NOTES> section for more information.
200 =item B<-keyex|-keysig>
202 specifies that the private key is to be used for key exchange or just signing.
203 This option is only interpreted by MSIE and similar MS software. Normally
204 "export grade" software will only allow 512 bit RSA keys to be used for
205 encryption purposes but arbitrary length keys for signing. The B<-keysig>
206 option marks the key for signing only. Signing only keys can be used for
207 S/MIME signing, authenticode (ActiveX control signing) and SSL client
208 authentication, however due to a bug only MSIE 5.0 and later support
209 the use of signing only keys for SSL client authentication.
211 =item B<-nomaciter>, B<-noiter>
213 these options affect the iteration counts on the MAC and key algorithms.
214 Unless you wish to produce files compatible with MSIE 4.0 you should leave
217 To discourage attacks by using large dictionaries of common passwords the
218 algorithm that derives keys from passwords can have an iteration count applied
219 to it: this causes a certain part of the algorithm to be repeated and slows it
220 down. The MAC is used to check the file integrity but since it will normally
221 have the same password as the keys and certificates it could also be attacked.
222 By default both MAC and encryption iteration counts are set to 2048, using
223 these options the MAC and encryption iteration counts can be set to 1, since
224 this reduces the file security you should not use these options unless you
225 really have to. Most software supports both MAC and key iteration counts.
226 MSIE 4.0 doesn't support MAC iteration counts so it needs the B<-nomaciter>
231 This option is included for compatibility with previous versions, it used
232 to be needed to use MAC iterations counts but they are now used by default.
238 Although there are a large number of options most of them are very rarely
239 used. For PKCS#12 file parsing only B<-in> and B<-out> need to be used
240 for PKCS#12 file creation B<-export> and B<-name> are also used.
242 The B<-keypbe> and B<-certpbe> algorithms allow the precise encryption
243 algorithms for private keys and certificates to be specified. Normally
244 the defaults are fine but occasionally software can't handle triple DES
245 encrypted private keys, then the option B<-keypbe PBE-SHA1-RC2-40> can
246 be used to reduce the private key encryption to 40 bit RC2. A complete
247 description of all algorithms is contained in the B<pkcs8> manual page.
251 Parse a PKCS#12 file and output it to a file:
253 openssl pkcs12 -in file.p12 -out file.pem
255 Output only client certificates to a file:
257 openssl pkcs12 -in file.p12 -clcerts -out file.pem
259 Don't encrypt the private key:
261 openssl pkcs12 -in file.p12 -out file.pem -nodes
263 Print some info about a PKCS#12 file:
265 openssl pkcs12 -in file.p12 -info -noout
267 Create a PKCS#12 file:
269 openssl pkcs12 -export -in file.pem -out file.p12 -name "My Certificate"
271 Include some extra certificates:
273 openssl pkcs12 -export -in file.pem -out file.p12 -name "My Certificate" \
274 -certfile othercerts.pem
278 Some would argue that the PKCS#12 standard is one big bug :-)
280 Need password options for the PEM files: this will probably be fixed before