Admin Control Panel v2.0

✎ Editing: pkcs12.html ← Back

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>pkcs12</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<ul id="index">
 <li><a href="#NAME">NAME</a></li>
 <li><a href="#SYNOPSIS">SYNOPSIS</a></li>
 <li><a href="#DESCRIPTION">DESCRIPTION</a></li>
 <li><a href="#OPTIONS">OPTIONS</a></li>
 <li><a href="#PARSING-OPTIONS">PARSING OPTIONS</a></li>
 <li><a href="#FILE-CREATION-OPTIONS">FILE CREATION OPTIONS</a></li>
 <li><a href="#NOTES">NOTES</a></li>
 <li><a href="#EXAMPLES">EXAMPLES</a></li>
 <li><a href="#SEE-ALSO">SEE ALSO</a></li>
 <li><a href="#COPYRIGHT">COPYRIGHT</a></li>
</ul>

openssl-pkcs12, pkcs12 - PKCS#12 file utility

<h1 id="SYNOPSIS">SYNOPSIS</h1>

<h1 id="DESCRIPTION">DESCRIPTION</h1>

The pkcs12 command allows PKCS#12 files (sometimes referred to as PFX files) to be created and parsed. PKCS#12 files are used by several programs including Netscape, MSIE and MS Outlook.

<h1 id="OPTIONS">OPTIONS</h1>

There are a lot of options the meaning of some depends of whether a PKCS#12 file is being created or parsed. By default a PKCS#12 file is parsed. A PKCS#12 file can be created by using the -export option (see below).

<h1 id="PARSING-OPTIONS">PARSING OPTIONS</h1>

<dl>

Print out a usage message.

</dd>
<dt id="in-filename">-in filename</dt>
<dd>

This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.

</dd>
<dt id="out-filename">-out filename</dt>
<dd>

The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.

</dd>
<dt id="passin-arg">-passin arg</dt>
<dd>

The PKCS#12 file (i.e. input file) password source. For more information about the format of arg see <a href="../man1/openssl.html">&quot;Pass Phrase Options&quot; in openssl(1)</a>.

</dd>
<dt id="passout-arg">-passout arg</dt>
<dd>

Pass phrase source to encrypt any outputted private keys with. For more information about the format of arg see <a href="../man1/openssl.html">&quot;Pass Phrase Options&quot; in openssl(1)</a>.

</dd>
<dt id="password-arg">-password arg</dt>
<dd>

With -export, -password is equivalent to -passout. Otherwise, -password is equivalent to -passin.

</dd>
<dt id="noout">-noout</dt>
<dd>

This option inhibits output of the keys and certificates to the output file version of the PKCS#12 file.

</dd>
<dt id="clcerts">-clcerts</dt>
<dd>

Only output client certificates (not CA certificates).

</dd>
<dt id="cacerts">-cacerts</dt>
<dd>

Only output CA certificates (not client certificates).

</dd>
<dt id="nocerts">-nocerts</dt>
<dd>

No certificates at all will be output.

</dd>
<dt id="nokeys">-nokeys</dt>
<dd>

No private keys will be output.

</dd>
<dt id="info">-info</dt>
<dd>

Output additional information about the PKCS#12 file structure, algorithms used and iteration counts.

</dd>
<dt id="des">-des</dt>
<dd>

Use DES to encrypt private keys before outputting.

</dd>
<dt id="des3">-des3</dt>
<dd>

Use triple DES to encrypt private keys before outputting, this is the default.

</dd>
<dt id="idea">-idea</dt>
<dd>

Use IDEA to encrypt private keys before outputting.

</dd>
<dt id="aes128--aes192--aes256">-aes128, -aes192, -aes256</dt>
<dd>

Use AES to encrypt private keys before outputting.

</dd>
<dt id="aria128--aria192--aria256">-aria128, -aria192, -aria256</dt>
<dd>

Use ARIA to encrypt private keys before outputting.

</dd>
<dt id="camellia128--camellia192--camellia256">-camellia128, -camellia192, -camellia256</dt>
<dd>

Use Camellia to encrypt private keys before outputting.

</dd>
<dt id="nodes">-nodes</dt>
<dd>

Don&#39;t encrypt the private keys at all.

</dd>
<dt id="nomacver">-nomacver</dt>
<dd>

Don&#39;t attempt to verify the integrity MAC before reading the file.

</dd>
<dt id="twopass">-twopass</dt>
<dd>

Prompt for separate integrity and encryption passwords: most software always assumes these are the same so this option will render such PKCS#12 files unreadable. Cannot be used in combination with the options -password, -passin (if importing) or -passout (if exporting).

</dd>
</dl>

<h1 id="FILE-CREATION-OPTIONS">FILE CREATION OPTIONS</h1>

<dl>

<dt id="export">-export</dt>
<dd>

This option specifies that a PKCS#12 file will be created rather than parsed.

</dd>
<dt id="out-filename1">-out filename</dt>
<dd>

This specifies filename to write the PKCS#12 file to. Standard output is used by default.

</dd>
<dt id="in-filename1">-in filename</dt>
<dd>

The filename to read certificates and private keys from, standard input by default. They must all be in PEM format. The order doesn&#39;t matter but one private key and its corresponding certificate should be present. If additional certificates are present they will also be included in the PKCS#12 file.

</dd>
<dt id="inkey-file_or_id">-inkey file_or_id</dt>
<dd>

File to read private key from. If not present then a private key must be present in the input file. If no engine is used, the argument is taken as a file; if an engine is specified, the argument is given to the engine as a key identifier.

</dd>
<dt id="name-friendlyname">-name friendlyname</dt>
<dd>

This specifies the &quot;friendly name&quot; for the certificate and private key. This name is typically displayed in list boxes by software importing the file.

</dd>
<dt id="certfile-filename">-certfile filename</dt>
<dd>

A filename to read additional certificates from.

</dd>
<dt id="caname-friendlyname">-caname friendlyname</dt>
<dd>

This specifies the &quot;friendly name&quot; for other certificates. This option may be used multiple times to specify names for all certificates in the order they appear. Netscape ignores friendly names on other certificates whereas MSIE displays them.

</dd>
<dt id="pass-arg--passout-arg">-pass arg, -passout arg</dt>
<dd>

The PKCS#12 file (i.e. output file) password source. For more information about the format of arg see <a href="../man1/openssl.html">&quot;Pass Phrase Options&quot; in openssl(1)</a>.

</dd>
<dt id="passin-password">-passin password</dt>
<dd>

Pass phrase source to decrypt any input private keys with. For more information about the format of arg see <a href="../man1/openssl.html">&quot;Pass Phrase Options&quot; in openssl(1)</a>.

</dd>
<dt id="chain">-chain</dt>
<dd>

If this option is present then an attempt is made to include the entire certificate chain of the user certificate. The standard CA store is used for this search. If the search fails it is considered a fatal error.

</dd>
<dt id="descert">-descert</dt>
<dd>

Encrypt the certificate using triple DES, this may render the PKCS#12 file unreadable by some &quot;export grade&quot; software. By default the private key is encrypted using triple DES and the certificate using 40 bit RC2 unless RC2 is disabled in which case triple DES is used.

</dd>
<dt id="keypbe-alg--certpbe-alg">-keypbe alg, -certpbe alg</dt>
<dd>

These options allow the algorithm used to encrypt the private key and certificates to be selected. Any PKCS#5 v1.5 or PKCS#12 PBE algorithm name can be used (see NOTES section for more information). If a cipher name (as output by the list-cipher-algorithms command is specified then it is used with PKCS#5 v2.0. For interoperability reasons it is advisable to only use PKCS#12 algorithms.

</dd>
<dt id="keyex--keysig">-keyex|-keysig</dt>
<dd>

Specifies that the private key is to be used for key exchange or just signing. This option is only interpreted by MSIE and similar MS software. Normally &quot;export grade&quot; software will only allow 512 bit RSA keys to be used for encryption purposes but arbitrary length keys for signing. The -keysig option marks the key for signing only. Signing only keys can be used for S/MIME signing, authenticode (ActiveX control signing) and SSL client authentication, however, due to a bug only MSIE 5.0 and later support the use of signing only keys for SSL client authentication.

</dd>
<dt id="macalg-digest">-macalg digest</dt>
<dd>

Specify the MAC digest algorithm. If not included them SHA1 will be used.

</dd>
<dt id="nomaciter--noiter">-nomaciter, -noiter</dt>
<dd>

These options affect the iteration counts on the MAC and key algorithms. Unless you wish to produce files compatible with MSIE 4.0 you should leave these options alone.

To discourage attacks by using large dictionaries of common passwords the algorithm that derives keys from passwords can have an iteration count applied to it: this causes a certain part of the algorithm to be repeated and slows it down. The MAC is used to check the file integrity but since it will normally have the same password as the keys and certificates it could also be attacked. By default both MAC and encryption iteration counts are set to 2048, using these options the MAC and encryption iteration counts can be set to 1, since this reduces the file security you should not use these options unless you really have to. Most software supports both MAC and key iteration counts. MSIE 4.0 doesn&#39;t support MAC iteration counts so it needs the -nomaciter option.

</dd>
<dt id="maciter">-maciter</dt>
<dd>

This option is included for compatibility with previous versions, it used to be needed to use MAC iterations counts but they are now used by default.

</dd>
<dt id="nomac">-nomac</dt>
<dd>

Don&#39;t attempt to provide the MAC integrity.

</dd>
<dt id="rand-file">-rand file...</dt>
<dd>

A file or files containing random data used to seed the random number generator. Multiple files can be specified separated by an OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others.

</dd>
<dt id="writerand-file">[-writerand file]</dt>
<dd>

Writes random data to the specified file upon exit. This can be used with a subsequent -rand flag.

</dd>
<dt id="CAfile-file">-CAfile file</dt>
<dd>

CA storage as a file.

</dd>
<dt id="CApath-dir">-CApath dir</dt>
<dd>

CA storage as a directory. This directory must be a standard certificate directory: that is a hash of each subject name (using x509 -hash) should be linked to each certificate.

</dd>
<dt id="no-CAfile">-no-CAfile</dt>
<dd>

Do not load the trusted CA certificates from the default file location.

</dd>
<dt id="no-CApath">-no-CApath</dt>
<dd>

Do not load the trusted CA certificates from the default directory location.

</dd>
<dt id="CSP-name">-CSP name</dt>
<dd>

Write name as a Microsoft CSP name.

</dd>
</dl>

<h1 id="NOTES">NOTES</h1>

Although there are a large number of options most of them are very rarely used. For PKCS#12 file parsing only -in and -out need to be used for PKCS#12 file creation -export and -name are also used.

If none of the -clcerts, -cacerts or -nocerts options are present then all certificates will be output in the order they appear in the input PKCS#12 files. There is no guarantee that the first certificate present is the one corresponding to the private key. Certain software which requires a private key and certificate and assumes the first certificate in the file is the one corresponding to the private key: this may not always be the case. Using the -clcerts option will solve this problem by only outputting the certificate corresponding to the private key. If the CA certificates are required then they can be output to a separate file using the -nokeys -cacerts options to just output CA certificates.

The -keypbe and -certpbe algorithms allow the precise encryption algorithms for private keys and certificates to be specified. Normally the defaults are fine but occasionally software can&#39;t handle triple DES encrypted private keys, then the option -keypbe PBE-SHA1-RC2-40 can be used to reduce the private key encryption to 40 bit RC2. A complete description of all algorithms is contained in the pkcs8 manual page.

Prior 1.1 release passwords containing non-ASCII characters were encoded in non-compliant manner, which limited interoperability, in first hand with Windows. But switching to standard-compliant password encoding poses problem accessing old data protected with broken encoding. For this reason even legacy encodings is attempted when reading the data. If you use PKCS#12 files in production application you are advised to convert the data, because implemented heuristic approach is not MT-safe, its sole goal is to facilitate the data upgrade with this utility.

<h1 id="EXAMPLES">EXAMPLES</h1>

Parse a PKCS#12 file and output it to a file:

<pre><code> openssl pkcs12 -in file.p12 -out file.pem</code></pre>

Output only client certificates to a file:

<pre><code> openssl pkcs12 -in file.p12 -clcerts -out file.pem</code></pre>

Don&#39;t encrypt the private key:

<pre><code> openssl pkcs12 -in file.p12 -out file.pem -nodes</code></pre>

Print some info about a PKCS#12 file:

<pre><code> openssl pkcs12 -in file.p12 -info -noout</code></pre>

Create a PKCS#12 file:

<pre><code> openssl pkcs12 -export -in file.pem -out file.p12 -name &quot;My Certificate&quot;</code></pre>

Include some extra certificates:

<pre><code> openssl pkcs12 -export -in file.pem -out file.p12 -name &quot;My Certificate&quot; \
 -certfile othercerts.pem</code></pre>

<h1 id="COPYRIGHT">COPYRIGHT</h1>

Licensed under the OpenSSL license (the &quot;License&quot;). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <a href="https://www.openssl.org/source/license.html">https://www.openssl.org/source/license.html</a>.

</body>

</html>

Cancel