2 {- OpenSSL::safe::output_do_not_edit_headers(); -}
6 openssl-pkcs12 - PKCS#12 file utility
14 [B<-inkey> I<file_or_id>]
15 [B<-certfile> I<filename>]
27 [B<-des> B<-des3> B<-idea> B<-aes128> B<-aes192> B<-aes256> B<-aria128> B<-aria192> B<-aria256> B<-camellia128> B<-camellia192> B<-camellia256> B<-nodes>]
28 [B<-iter> I<count> | B<-noiter> | B<-nomaciter>]
33 [B<-certpbe> I<cipher>]
34 [B<-keypbe> I<cipher>]
35 [B<-macalg> I<digest>]
42 {- $OpenSSL::safe::opt_trust_synopsis -}
43 {- $OpenSSL::safe::opt_r_synopsis -}
45 =for openssl ifdef engine
49 This command allows PKCS#12 files (sometimes referred to as
50 PFX files) to be created and parsed. PKCS#12 files are used by several
51 programs including Netscape, MSIE and MS Outlook.
55 There are a lot of options the meaning of some depends of whether a PKCS#12 file
56 is being created or parsed. By default a PKCS#12 file is parsed. A PKCS#12
57 file can be created by using the B<-export> option (see below).
59 =head1 PARSING OPTIONS
65 Print out a usage message.
67 =item B<-in> I<filename>
69 This specifies filename of the PKCS#12 file to be parsed. Standard input is used
72 =item B<-out> I<filename>
74 The filename to write certificates and private keys to, standard output by
75 default. They are all written in PEM format.
77 =item B<-password> I<arg>
79 With B<-export>, B<-password> is equivalent to B<-passout>,
80 otherwise it is equivalent to B<-passin>.
84 This option inhibits output of the keys and certificates to the output file
85 version of the PKCS#12 file.
89 Only output client certificates (not CA certificates).
93 Only output CA certificates (not client certificates).
97 No certificates at all will be output.
101 No private keys will be output.
105 Output additional information about the PKCS#12 file structure, algorithms
106 used and iteration counts.
110 Use DES to encrypt private keys before outputting.
114 Use triple DES to encrypt private keys before outputting, this is the default.
118 Use IDEA to encrypt private keys before outputting.
120 =item B<-aes128>, B<-aes192>, B<-aes256>
122 Use AES to encrypt private keys before outputting.
124 =item B<-aria128>, B<-aria192>, B<-aria256>
126 Use ARIA to encrypt private keys before outputting.
128 =item B<-camellia128>, B<-camellia192>, B<-camellia256>
130 Use Camellia to encrypt private keys before outputting.
134 Don't encrypt the private keys at all.
138 Don't attempt to verify the integrity MAC before reading the file.
142 Prompt for separate integrity and encryption passwords: most software
143 always assumes these are the same so this option will render such
144 PKCS#12 files unreadable. Cannot be used in combination with the options
145 B<-password>, B<-passin> if importing, or B<-passout> if exporting.
149 =head1 FILE CREATION OPTIONS
155 This option specifies that a PKCS#12 file will be created rather than
158 =item B<-out> I<filename>
160 This specifies filename to write the PKCS#12 file to. Standard output is used
163 =item B<-in> I<filename>
165 The filename to read certificates and private keys from, standard input by
166 default. They must all be in PEM format. The order doesn't matter but one
167 private key and its corresponding certificate should be present. If additional
168 certificates are present they will also be included in the PKCS#12 file.
170 =item B<-inkey> I<file_or_id>
172 File to read private key from. If not present then a private key must be present
174 If no engine is used, the argument is taken as a file; if an engine is
175 specified, the argument is given to the engine as a key identifier.
177 =item B<-name> I<friendlyname>
179 This specifies the "friendly name" for the certificate and private key. This
180 name is typically displayed in list boxes by software importing the file.
182 =item B<-certfile> I<filename>
184 A filename to read additional certificates from.
186 =item B<-caname> I<friendlyname>
188 This specifies the "friendly name" for other certificates. This option may be
189 used multiple times to specify names for all certificates in the order they
190 appear. Netscape ignores friendly names on other certificates whereas MSIE
193 =item B<-passin> I<arg>, B<-passout> I<arg>
195 The password source for the input, and for encrypting any private keys that
197 For more information about the format of B<arg>
198 see L<openssl(1)/Pass Phrase Options>.
202 If this option is present then an attempt is made to include the entire
203 certificate chain of the user certificate. The standard CA store is used
204 for this search. If the search fails it is considered a fatal error.
208 Encrypt the certificate using triple DES, this may render the PKCS#12
209 file unreadable by some "export grade" software. By default the private
210 key is encrypted using triple DES and the certificate using 40 bit RC2
211 unless RC2 is disabled in which case triple DES is used.
213 =item B<-keypbe> I<alg>, B<-certpbe> I<alg>
215 These options allow the algorithm used to encrypt the private key and
216 certificates to be selected. Any PKCS#5 v1.5 or PKCS#12 PBE algorithm name
217 can be used (see L</NOTES> section for more information). If a cipher name
218 (as output by C<openssl list -cipher-algorithms>) is specified then it
219 is used with PKCS#5 v2.0. For interoperability reasons it is advisable to only
220 use PKCS#12 algorithms.
222 =item B<-keyex>|B<-keysig>
224 Specifies that the private key is to be used for key exchange or just signing.
225 This option is only interpreted by MSIE and similar MS software. Normally
226 "export grade" software will only allow 512 bit RSA keys to be used for
227 encryption purposes but arbitrary length keys for signing. The B<-keysig>
228 option marks the key for signing only. Signing only keys can be used for
229 S/MIME signing, authenticode (ActiveX control signing) and SSL client
230 authentication, however due to a bug only MSIE 5.0 and later support
231 the use of signing only keys for SSL client authentication.
233 =item B<-macalg> I<digest>
235 Specify the MAC digest algorithm. If not included them SHA1 will be used.
237 =item B<-iter> I<count>
239 This option specifies the iteration count for the encryption key and MAC. The
240 default value is 2048.
242 To discourage attacks by using large dictionaries of common passwords the
243 algorithm that derives keys from passwords can have an iteration count applied
244 to it: this causes a certain part of the algorithm to be repeated and slows it
245 down. The MAC is used to check the file integrity but since it will normally
246 have the same password as the keys and certificates it could also be attacked.
248 =item B<-nomaciter>, B<-noiter>
250 By default both MAC and encryption iteration counts are set to 2048, using
251 these options the MAC and encryption iteration counts can be set to 1, since
252 this reduces the file security you should not use these options unless you
253 really have to. Most software supports both MAC and key iteration counts.
254 MSIE 4.0 doesn't support MAC iteration counts so it needs the B<-nomaciter>
259 This option is included for compatibility with previous versions, it used
260 to be needed to use MAC iterations counts but they are now used by default.
264 Don't attempt to provide the MAC integrity.
266 =item B<-CSP> I<name>
268 Write I<name> as a Microsoft CSP name.
270 {- $OpenSSL::safe::opt_trust_item -}
272 {- $OpenSSL::safe::opt_r_item -}
278 Although there are a large number of options most of them are very rarely
279 used. For PKCS#12 file parsing only B<-in> and B<-out> need to be used
280 for PKCS#12 file creation B<-export> and B<-name> are also used.
282 If none of the B<-clcerts>, B<-cacerts> or B<-nocerts> options are present
283 then all certificates will be output in the order they appear in the input
284 PKCS#12 files. There is no guarantee that the first certificate present is
285 the one corresponding to the private key. Certain software which requires
286 a private key and certificate and assumes the first certificate in the
287 file is the one corresponding to the private key: this may not always
288 be the case. Using the B<-clcerts> option will solve this problem by only
289 outputting the certificate corresponding to the private key. If the CA
290 certificates are required then they can be output to a separate file using
291 the B<-nokeys> B<-cacerts> options to just output CA certificates.
293 The B<-keypbe> and B<-certpbe> algorithms allow the precise encryption
294 algorithms for private keys and certificates to be specified. Normally
295 the defaults are fine but occasionally software can't handle triple DES
296 encrypted private keys, then the option B<-keypbe> I<PBE-SHA1-RC2-40> can
297 be used to reduce the private key encryption to 40 bit RC2. A complete
298 description of all algorithms is contained in L<openssl-pkcs8(1)>.
300 Prior 1.1 release passwords containing non-ASCII characters were encoded
301 in non-compliant manner, which limited interoperability, in first hand
302 with Windows. But switching to standard-compliant password encoding
303 poses problem accessing old data protected with broken encoding. For
304 this reason even legacy encodings is attempted when reading the
305 data. If you use PKCS#12 files in production application you are advised
306 to convert the data, because implemented heuristic approach is not
307 MT-safe, its sole goal is to facilitate the data upgrade with this
312 Parse a PKCS#12 file and output it to a file:
314 openssl pkcs12 -in file.p12 -out file.pem
316 Output only client certificates to a file:
318 openssl pkcs12 -in file.p12 -clcerts -out file.pem
320 Don't encrypt the private key:
322 openssl pkcs12 -in file.p12 -out file.pem -nodes
324 Print some info about a PKCS#12 file:
326 openssl pkcs12 -in file.p12 -info -noout
328 Create a PKCS#12 file:
330 openssl pkcs12 -export -in file.pem -out file.p12 -name "My Certificate"
332 Include some extra certificates:
334 openssl pkcs12 -export -in file.pem -out file.p12 -name "My Certificate" \
335 -certfile othercerts.pem
341 L<ossl_store-file(7)>
345 Copyright 2000-2019 The OpenSSL Project Authors. All Rights Reserved.
347 Licensed under the Apache License 2.0 (the "License"). You may not use
348 this file except in compliance with the License. You can obtain a copy
349 in the file LICENSE in the source distribution or at
350 L<https://www.openssl.org/source/license.html>.