Admin Control Panel v2.0

✎ Editing: smime.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>smime</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="#NOTES">NOTES</a></li>
 <li><a href="#EXIT-CODES">EXIT CODES</a></li>
 <li><a href="#EXAMPLES">EXAMPLES</a></li>
 <li><a href="#BUGS">BUGS</a></li>
 <li><a href="#HISTORY">HISTORY</a></li>
 <li><a href="#COPYRIGHT">COPYRIGHT</a></li>
</ul>

openssl-smime, smime - S/MIME utility

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

openssl smime [-help] [-encrypt] [-decrypt] [-sign] [-resign] [-verify] [-pk7out] [-binary] [-crlfeol] [-cipher] [-in file] [-CAfile file] [-CApath dir] [-no-CAfile] [-no-CApath] [-attime timestamp] [-check_ss_sig] [-crl_check] [-crl_check_all] [-explicit_policy] [-extended_crl] [-ignore_critical] [-inhibit_any] [-inhibit_map] [-partial_chain] [-policy arg] [-policy_check] [-policy_print] [-purpose purpose] [-suiteB_128] [-suiteB_128_only] [-suiteB_192] [-trusted_first] [-no_alt_chains] [-use_deltas] [-auth_level num] [-verify_depth num] [-verify_email email] [-verify_hostname hostname] [-verify_ip ip] [-verify_name name] [-x509_strict] [-certfile file] [-signer file] [-recip file] [-inform SMIME|PEM|DER] [-passin arg] [-inkey file_or_id] [-out file] [-outform SMIME|PEM|DER] [-content file] [-to addr] [-from ad] [-subject s] [-text] [-indef] [-noindef] [-stream] [-rand file...] [-writerand file] [-md digest] [cert.pem]...

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

The smime command handles S/MIME mail. It can encrypt, decrypt, sign and verify S/MIME messages.

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

There are six operation options that set the type of operation to be performed. The meaning of the other options varies according to the operation type.

<dl>

Print out a usage message.

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

Encrypt mail for the given recipient certificates. Input file is the message to be encrypted. The output file is the encrypted mail in MIME format.

Note that no revocation check is done for the recipient cert, so if that key has been compromised, others may be able to decrypt the text.

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

Decrypt mail using the supplied certificate and private key. Expects an encrypted mail message in MIME format for the input file. The decrypted mail is written to the output file.

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

Sign mail using the supplied certificate and private key. Input file is the message to be signed. The signed message in MIME format is written to the output file.

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

Verify signed mail. Expects a signed mail message on input and outputs the signed data. Both clear text and opaque signing is supported.

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

Takes an input message and writes out a PEM encoded PKCS#7 structure.

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

Resign a message: take an existing message and one or more new signers.

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

The input message to be encrypted or signed or the MIME message to be decrypted or verified.

</dd>
<dt id="inform-SMIME-PEM-DER">-inform SMIME|PEM|DER</dt>
<dd>

This specifies the input format for the PKCS#7 structure. The default is SMIME which reads an S/MIME format message. PEM and DER format change this to expect PEM and DER format PKCS#7 structures instead. This currently only affects the input format of the PKCS#7 structure, if no PKCS#7 structure is being input (for example with -encrypt or -sign) this option has no effect.

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

The message text that has been decrypted or verified or the output MIME format message that has been signed or verified.

</dd>
<dt id="outform-SMIME-PEM-DER">-outform SMIME|PEM|DER</dt>
<dd>

This specifies the output format for the PKCS#7 structure. The default is SMIME which write an S/MIME format message. PEM and DER format change this to write PEM and DER format PKCS#7 structures instead. This currently only affects the output format of the PKCS#7 structure, if no PKCS#7 structure is being output (for example with -verify or -decrypt) this option has no effect.

</dd>
<dt id="stream--indef--noindef">-stream -indef -noindef</dt>
<dd>

The -stream and -indef options are equivalent and enable streaming I/O for encoding operations. This permits single pass processing of data without the need to hold the entire contents in memory, potentially supporting very large files. Streaming is automatically set for S/MIME signing with detached data if the output format is SMIME it is currently off by default for all other operations.

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

Disable streaming I/O where it would produce and indefinite length constructed encoding. This option currently has no effect. In future streaming will be enabled by default on all relevant operations and this option will disable it.

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

This specifies a file containing the detached content, this is only useful with the -verify command. This is only usable if the PKCS#7 structure is using the detached signature form where the content is not included. This option will override any content if the input format is S/MIME and it uses the multipart/signed MIME content type.

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

This option adds plain text (text/plain) MIME headers to the supplied message if encrypting or signing. If decrypting or verifying it strips off text headers: if the decrypted or verified message is not of MIME type text/plain then an error occurs.

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

A file containing trusted CA certificates, only used with -verify.

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

A directory containing trusted CA certificates, only used with -verify. 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="md-digest">-md digest</dt>
<dd>

Digest algorithm to use when signing or resigning. If not present then the default digest algorithm for the signing key will be used (usually SHA1).

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

The encryption algorithm to use. For example DES (56 bits) - -des, triple DES (168 bits) - -des3, EVP_get_cipherbyname() function) can also be used preceded by a dash, for example -aes-128-cbc. See <a href="../man1/enc.html">enc</a> for list of ciphers supported by your version of OpenSSL.

If not specified triple DES is used. Only used with -encrypt.

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

When verifying a message normally certificates (if any) included in the message are searched for the signing certificate. With this option only the certificates specified in the -certfile option are used. The supplied certificates can still be used as untrusted CAs however.

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

Do not verify the signers certificate of a signed message.

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

Do not do chain verification of signers certificates: that is don&#39;t use the certificates in the signed message as untrusted CAs.

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

Don&#39;t try to verify the signatures on the message.

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

When signing a message the signer&#39;s certificate is normally included with this option it is excluded. This will reduce the size of the signed message but the verifier must have a copy of the signers certificate available locally (passed using the -certfile option for example).

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

Normally when a message is signed a set of attributes are included which include the signing time and supported symmetric algorithms. With this option they are not included.

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

Normally the input message is converted to &quot;canonical&quot; format which is effectively using CR and LF as end of line: as required by the S/MIME specification. When this option is present no translation occurs. This is useful when handling binary data which may not be in MIME format.

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

Normally the output file uses a single LF as end of line. When this option is present CRLF is used instead.

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

When signing a message use opaque signing: this form is more resistant to translation by mail relays but it cannot be read by mail agents that do not support S/MIME. Without this option cleartext signing with the MIME type multipart/signed is used.

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

Allows additional certificates to be specified. When signing these will be included with the message. When verifying these will be searched for the signers certificates. The certificates should be in PEM format.

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

A signing certificate when signing or resigning a message, this option can be used multiple times if more than one signer is required. If a message is being verified then the signers certificates will be written to this file if the verification was successful.

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

The recipients certificate when decrypting a message. This certificate must match one of the recipients of the message or an error occurs.

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

The private key to use when signing or decrypting. This must match the corresponding certificate. If this option is not specified then the private key must be included in the certificate file specified with the -recip or -signer file. When signing this option can be used multiple times to specify successive keys. 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="passin-arg">-passin arg</dt>
<dd>

The private key 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="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="cert.pem">cert.pem...</dt>
<dd>

One or more certificates of message recipients: used when encrypting a message.

</dd>
<dt id="to--from--subject">-to, -from, -subject</dt>
<dd>

The relevant mail headers. These are included outside the signed portion of a message so they may be included manually. If signing then many S/MIME mail clients check the signers certificate&#39;s email address matches that specified in the From: address.

</dd>
<dt id="attime--check_ss_sig--crl_check--crl_check_all--explicit_policy--extended_crl--ignore_critical--inhibit_any--inhibit_map--no_alt_chains--partial_chain--policy--policy_check--policy_print--purpose--suiteB_128--suiteB_128_only--suiteB_192--trusted_first--use_deltas--auth_level--verify_depth--verify_email--verify_hostname--verify_ip--verify_name--x509_strict">-attime, -check_ss_sig, -crl_check, -crl_check_all, -explicit_policy, -extended_crl, -ignore_critical, -inhibit_any, -inhibit_map, -no_alt_chains, -partial_chain, -policy, -policy_check, -policy_print, -purpose, -suiteB_128, -suiteB_128_only, -suiteB_192, -trusted_first, -use_deltas, -auth_level, -verify_depth, -verify_email, -verify_hostname, -verify_ip, -verify_name, -x509_strict</dt>
<dd>

Set various options of certificate chain verification. See <a href="../man1/verify.html">verify(1)</a> manual page for details.

</dd>
</dl>

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

The MIME message must be sent without any blank lines between the headers and the output. Some mail programs will automatically add a blank line. Piping the mail directly to sendmail is one way to achieve the correct format.

The supplied message to be signed or encrypted must include the necessary MIME headers or many S/MIME clients won&#39;t display it properly (if at all). You can use the -text option to automatically add plain text headers.

A &quot;signed and encrypted&quot; message is one where a signed message is then encrypted. This can be produced by encrypting an already signed message: see the examples section.

This version of the program only allows one signer per message but it will verify multiple signers on received messages. Some S/MIME clients choke if a message contains multiple signers. It is possible to sign messages &quot;in parallel&quot; by signing an already signed message.

The options -encrypt and -decrypt reflect common usage in S/MIME clients. Strictly speaking these process PKCS#7 enveloped data: PKCS#7 encrypted data is used for other purposes.

The -resign option uses an existing message digest when adding a new signer. This means that attributes must be present in at least one existing signer using the same message digest or this operation will fail.

The -stream and -indef options enable streaming I/O support. As a result the encoding is BER using indefinite length constructed encoding and no longer DER. Streaming is supported for the -encrypt operation and the -sign operation if the content is not detached.

Streaming is always used for the -sign operation with detached data but since the content is no longer part of the PKCS#7 structure the encoding remains DER.

<h1 id="EXIT-CODES">EXIT CODES</h1>

<dl>

The operation was completely successfully.

</dd>
<dt id="pod1">1</dt>
<dd>

An error occurred parsing the command options.

</dd>
<dt id="pod2">2</dt>
<dd>

One of the input files could not be read.

</dd>
<dt id="pod3">3</dt>
<dd>

An error occurred creating the PKCS#7 file or when reading the MIME message.

</dd>
<dt id="pod4">4</dt>
<dd>

An error occurred decrypting or verifying the message.

</dd>
<dt id="pod5">5</dt>
<dd>

The message was verified correctly but an error occurred writing out the signers certificates.

</dd>
</dl>

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

Create a cleartext signed message:

<pre><code> openssl smime -sign -in message.txt -text -out mail.msg \
 -signer mycert.pem</code></pre>

Create an opaque signed message:

<pre><code> openssl smime -sign -in message.txt -text -out mail.msg -nodetach \
 -signer mycert.pem</code></pre>

Create a signed message, include some additional certificates and read the private key from another file:

<pre><code> openssl smime -sign -in in.txt -text -out mail.msg \
 -signer mycert.pem -inkey mykey.pem -certfile mycerts.pem</code></pre>

Create a signed message with two signers:

<pre><code> openssl smime -sign -in message.txt -text -out mail.msg \
 -signer mycert.pem -signer othercert.pem</code></pre>

Send a signed message under Unix directly to sendmail, including headers:

<pre><code> openssl smime -sign -in in.txt -text -signer mycert.pem \
 -from steve@openssl.org -to someone@somewhere \
 -subject &quot;Signed message&quot; | sendmail someone@somewhere</code></pre>

Verify a message and extract the signer&#39;s certificate if successful:

<pre><code> openssl smime -verify -in mail.msg -signer user.pem -out signedtext.txt</code></pre>

Send encrypted mail using triple DES:

<pre><code> openssl smime -encrypt -in in.txt -from steve@openssl.org \
 -to someone@somewhere -subject &quot;Encrypted message&quot; \
 -des3 user.pem -out mail.msg</code></pre>

Sign and encrypt mail:

<pre><code> openssl smime -sign -in ml.txt -signer my.pem -text \
 | openssl smime -encrypt -out mail.msg \
 -from steve@openssl.org -to someone@somewhere \
 -subject &quot;Signed and Encrypted message&quot; -des3 user.pem</code></pre>

Note: the encryption command does not include the -text option because the message being encrypted already has MIME headers.

Decrypt mail:

<pre><code> openssl smime -decrypt -in mail.msg -recip mycert.pem -inkey key.pem</code></pre>

The output from Netscape form signing is a PKCS#7 structure with the detached signature format. You can use this program to verify the signature by line wrapping the base64 encoded structure and surrounding it with:

<pre><code> -----BEGIN PKCS7-----
 -----END PKCS7-----</code></pre>

and using the command:

<pre><code> openssl smime -verify -inform PEM -in signature.pem -content content.txt</code></pre>

Alternatively you can base64 decode the signature and use:

<pre><code> openssl smime -verify -inform DER -in signature.der -content content.txt</code></pre>

Create an encrypted message using 128 bit Camellia:

<pre><code> openssl smime -encrypt -in plain.txt -camellia128 -out mail.msg cert.pem</code></pre>

Add a signer to an existing message:

<pre><code> openssl smime -resign -in mail.msg -signer newsign.pem -out mail2.msg</code></pre>

The MIME parser isn&#39;t very clever: it seems to handle most messages that I&#39;ve thrown at it but it may choke on others.

The code currently will only write out the signer&#39;s certificate to a file: if the signer has a separate encryption certificate this must be manually extracted. There should be some heuristic that determines the correct encryption certificate.

Ideally a database should be maintained of a certificates for each email address.

The code doesn&#39;t currently take note of the permitted symmetric encryption algorithms as supplied in the SMIMECapabilities signed attribute. This means the user has to manually include the correct encryption algorithm. It should store the list of permitted ciphers in a database and only use those.

No revocation checking is done on the signer&#39;s certificate.

The current code can only handle S/MIME v2 messages, the more complex S/MIME v3 structures may cause parsing errors.

<h1 id="HISTORY">HISTORY</h1>

The use of multiple -signer options and the -resign command were first added in OpenSSL 1.0.0

The -no_alt_chains option was added in OpenSSL 1.1.0.

<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