2 {- OpenSSL::safe::output_do_not_edit_headers(); -}
6 openssl-cms - CMS utility
25 [B<-EncryptedData_encrypt>]
27 [B<-verify_receipt> I<receipt>]
30 [B<-inform> B<DER>|B<PEM>|B<SMIME>]
31 [B<-outform> B<DER>|B<PEM>|B<SMIME>]
32 [B<-rctform> B<DER>|B<PEM>|B<SMIME>]
33 [B<-keyform> B<DER>|B<PEM>|B<ENGINE>]
38 [B<-content> I<filename>]
42 [B<-attime> I<timestamp>]
56 [B<-purpose> I<purpose>]
63 [B<-auth_level> I<num>]
64 [B<-verify_depth> I<num>]
65 [B<-verify_email> I<email>]
66 [B<-verify_hostname> I<hostname>]
68 [B<-verify_name> I<name>]
81 [B<-certfile> I<file>]
82 [B<-certsout> I<file>]
86 [B<-receipt_request_all>]
87 [B<-receipt_request_first>]
88 [B<-receipt_request_from> I<emailaddress>]
89 [B<-receipt_request_to> I<emailaddress>]
90 [B<-receipt_request_print>]
91 [B<-secretkey> I<key>]
92 [B<-secretkeyid> I<id>]
93 [B<-econtent_type> I<type>]
95 [B<-keyopt> I<name>:I<parameter>]
100 {- $OpenSSL::safe::opt_trust_synopsis -}
101 {- $OpenSSL::safe::opt_r_synopsis -}
104 =for openssl ifdef des-wrap engine
108 This command handles S/MIME v3.1 mail. It can encrypt, decrypt,
109 sign and verify, compress and uncompress S/MIME messages.
113 There are fourteen operation options that set the type of operation to be
114 performed. The meaning of the other options varies according to the operation
121 Print out a usage message.
125 Encrypt mail for the given recipient certificates. Input file is the message
126 to be encrypted. The output file is the encrypted mail in MIME format. The
127 actual CMS type is <B>EnvelopedData<B>.
129 Note that no revocation check is done for the recipient cert, so if that
130 key has been compromised, others may be able to decrypt the text.
134 Decrypt mail using the supplied certificate and private key. Expects an
135 encrypted mail message in MIME format for the input file. The decrypted mail
136 is written to the output file.
138 =item B<-debug_decrypt>
140 This option sets the B<CMS_DEBUG_DECRYPT> flag. This option should be used
141 with caution: see the notes section below.
145 Sign mail using the supplied certificate and private key. Input file is
146 the message to be signed. The signed message in MIME format is written
151 Verify signed mail. Expects a signed mail message on input and outputs
152 the signed data. Both clear text and opaque signing is supported.
156 Takes an input message and writes out a PEM encoded CMS structure.
160 Resign a message: take an existing message and one or more new signers.
164 Add an ESS signing-certificate or ESS signing-certificate-v2 signed-attribute to the SignerInfo, in order to make
165 the signature comply with the requirements for a CAdES Basic Electronic Signature (CAdES-BES). See the NOTES
166 section for more details.
168 =item B<-data_create>
170 Create a CMS B<Data> type.
174 B<Data> type and output the content.
176 =item B<-digest_create>
178 Create a CMS B<DigestedData> type.
180 =item B<-digest_verify>
182 Verify a CMS B<DigestedData> type and output the content.
186 Create a CMS B<CompressedData> type. OpenSSL must be compiled with B<zlib>
187 support for this option to work, otherwise it will output an error.
191 Uncompress a CMS B<CompressedData> type and output the content. OpenSSL must be
192 compiled with B<zlib> support for this option to work, otherwise it will
195 =item B<-EncryptedData_encrypt>
197 Encrypt content using supplied symmetric key and algorithm using a CMS
198 B<EncryptedData> type and output the content.
200 =item B<-sign_receipt>
202 Generate and output a signed receipt for the supplied message. The input
203 message B<must> contain a signed receipt request. Functionality is otherwise
204 similar to the B<-sign> operation.
206 =item B<-verify_receipt> I<receipt>
208 Verify a signed receipt in filename B<receipt>. The input message B<must>
209 contain the original receipt request. Functionality is otherwise similar
210 to the B<-verify> operation.
212 =item B<-in> I<filename>
214 The input message to be encrypted or signed or the message to be decrypted
217 =item B<-out> I<filename>
219 The message text that has been decrypted or verified or the output MIME
220 format message that has been signed or verified.
222 =item B<-inform> B<DER>|B<PEM>|B<SMIME>
224 The input format of the CMS structure (if one is being read);
225 the default is B<SMIME>.
226 See L<openssl(1)/Format Options> for details.
228 =item B<-outform> B<DER>|B<PEM>|B<SMIME>
230 The output format of the CMS structure (if one is being written);
231 the default is B<SMIME>.
232 See L<openssl(1)/Format Options> for details.
234 =item B<-keyform> B<DER>|B<PEM>|B<ENGINE>
236 The format of the private key file; the default is B<PEM>.
237 See L<openssl(1)/Format Options> for details.
239 =item B<-rctform> B<DER>|B<PEM>|B<SMIME>
241 The signed receipt format for use with the B<-receipt_verify>; the default
243 See L<openssl(1)/Format Options> for details.
245 =item B<-stream>, B<-indef>, B<-noindef>
247 The B<-stream> and B<-indef> options are equivalent and enable streaming I/O
248 for encoding operations. This permits single pass processing of data without
249 the need to hold the entire contents in memory, potentially supporting very
250 large files. Streaming is automatically set for S/MIME signing with detached
251 data if the output format is B<SMIME> it is currently off by default for all
256 Disable streaming I/O where it would produce and indefinite length constructed
257 encoding. This option currently has no effect. In future streaming will be
258 enabled by default on all relevant operations and this option will disable it.
260 =item B<-content> I<filename>
262 This specifies a file containing the detached content, this is only
263 useful with the B<-verify> command. This is only usable if the CMS
264 structure is using the detached signature form where the content is
265 not included. This option will override any content if the input format
266 is S/MIME and it uses the multipart/signed MIME content type.
270 This option adds plain text (text/plain) MIME headers to the supplied
271 message if encrypting or signing. If decrypting or verifying it strips
272 off text headers: if the decrypted or verified message is not of MIME
273 type text/plain then an error occurs.
277 For the B<-cmsout> operation do not output the parsed CMS structure. This
278 is useful when combined with the B<-print> option or if the syntax of the CMS
279 structure is being checked.
283 For the B<-cmsout> operation print out all fields of the CMS structure. This
284 is mainly useful for testing purposes.
286 =item B<-md> I<digest>
288 Digest algorithm to use when signing or resigning. If not present then the
289 default digest algorithm for the signing key will be used (usually SHA1).
293 The encryption algorithm to use. For example triple DES (168 bits) - B<-des3>
294 or 256 bit AES - B<-aes256>. Any standard algorithm name (as used by the
295 EVP_get_cipherbyname() function) can also be used preceded by a dash, for
296 example B<-aes-128-cbc>. See L<openssl-enc(1)> for a list of ciphers
297 supported by your version of OpenSSL.
299 If not specified triple DES is used. Only used with B<-encrypt> and
300 B<-EncryptedData_create> commands.
304 When verifying a message normally certificates (if any) included in
305 the message are searched for the signing certificate. With this option
306 only the certificates specified in the B<-certfile> option are used.
307 The supplied certificates can still be used as untrusted CAs however.
311 Do not verify the signers certificate of a signed message.
315 When signing a message the signer's certificate is normally included
316 with this option it is excluded. This will reduce the size of the
317 signed message but the verifier must have a copy of the signers certificate
318 available locally (passed using the B<-certfile> option for example).
322 Normally when a message is signed a set of attributes are included which
323 include the signing time and supported symmetric algorithms. With this
324 option they are not included.
328 Exclude the list of supported algorithms from signed attributes, other options
329 such as signing time and content type are still included.
333 Normally the input message is converted to "canonical" format which is
334 effectively using CR and LF as end of line: as required by the S/MIME
335 specification. When this option is present no translation occurs. This
336 is useful when handling binary data which may not be in MIME format.
340 Normally the output file uses a single B<LF> as end of line. When this
341 option is present B<CRLF> is used instead.
345 When signing use ASCII CRLF format canonicalisation. This strips trailing
346 whitespace from all lines, deletes trailing blank lines at EOF and sets
347 the encapsulated content type. This option is normally used with detached
348 content and an output signature format of DER. This option is not normally
349 needed when verifying as it is enabled automatically if the encapsulated
350 content format is detected.
354 When signing a message use opaque signing: this form is more resistant
355 to translation by mail relays but it cannot be read by mail agents that
356 do not support S/MIME. Without this option cleartext signing with
357 the MIME type multipart/signed is used.
359 =item B<-certfile> I<file>
361 Allows additional certificates to be specified. When signing these will
362 be included with the message. When verifying these will be searched for
363 the signers certificates. The certificates should be in PEM format.
365 =item B<-certsout> I<file>
367 Any certificates contained in the message are written to I<file>.
369 =item B<-signer> I<file>
371 A signing certificate when signing or resigning a message, this option can be
372 used multiple times if more than one signer is required. If a message is being
373 verified then the signers certificates will be written to this file if the
374 verification was successful.
376 =item B<-recip> I<file>
378 When decrypting a message this specifies the recipients certificate. The
379 certificate must match one of the recipients of the message or an error
382 When encrypting a message this option may be used multiple times to specify
383 each recipient. This form B<must> be used if customised parameters are
384 required (for example to specify RSA-OAEP).
386 Only certificates carrying RSA, Diffie-Hellman or EC keys are supported by this
391 Use subject key identifier to identify certificates instead of issuer name and
392 serial number. The supplied certificate B<must> include a subject key
393 identifier extension. Supported by B<-sign> and B<-encrypt> options.
395 =item B<-receipt_request_all>, B<-receipt_request_first>
397 For B<-sign> option include a signed receipt request. Indicate requests should
398 be provided by all recipient or first tier recipients (those mailed directly
399 and not from a mailing list). Ignored it B<-receipt_request_from> is included.
401 =item B<-receipt_request_from> I<emailaddress>
403 For B<-sign> option include a signed receipt request. Add an explicit email
404 address where receipts should be supplied.
406 =item B<-receipt_request_to> I<emailaddress>
408 Add an explicit email address where signed receipts should be sent to. This
409 option B<must> but supplied if a signed receipt it requested.
411 =item B<-receipt_request_print>
413 For the B<-verify> operation print out the contents of any signed receipt
416 =item B<-secretkey> I<key>
418 Specify symmetric key to use. The key must be supplied in hex format and be
419 consistent with the algorithm used. Supported by the B<-EncryptedData_encrypt>
420 B<-EncryptedData_decrypt>, B<-encrypt> and B<-decrypt> options. When used
421 with B<-encrypt> or B<-decrypt> the supplied key is used to wrap or unwrap the
422 content encryption key using an AES key in the B<KEKRecipientInfo> type.
424 =item B<-secretkeyid> I<id>
426 The key identifier for the supplied symmetric key for B<KEKRecipientInfo> type.
427 This option B<must> be present if the B<-secretkey> option is used with
428 B<-encrypt>. With B<-decrypt> operations the I<id> is used to locate the
429 relevant key if it is not supplied then an attempt is used to decrypt any
430 B<KEKRecipientInfo> structures.
432 =item B<-econtent_type> I<type>
434 Set the encapsulated content type to I<type> if not supplied the B<Data> type
435 is used. The I<type> argument can be any valid OID name in either text or
438 =item B<-inkey> I<file>
440 The private key to use when signing or decrypting. This must match the
441 corresponding certificate. If this option is not specified then the
442 private key must be included in the certificate file specified with
443 the B<-recip> or B<-signer> file. When signing this option can be used
444 multiple times to specify successive keys.
446 =item B<-keyopt> I<name>:I<parameter>
448 For signing and encryption this option can be used multiple times to
449 set customised parameters for the preceding key or certificate. It can
450 currently be used to set RSA-PSS for signing, RSA-OAEP for encryption
451 or to modify default parameters for ECDH.
453 =item B<-passin> I<arg>
455 The private key password source. For more information about the format of B<arg>
456 see L<openssl(1)/Pass Phrase Options>.
458 =item B<-to>, B<-from>, B<-subject>
460 The relevant mail headers. These are included outside the signed
461 portion of a message so they may be included manually. If signing
462 then many S/MIME mail clients check the signers certificate's email
463 address matches that specified in the From: address.
465 =item B<-attime>, B<-check_ss_sig>, B<-crl_check>, B<-crl_check_all>,
466 B<-explicit_policy>, B<-extended_crl>, B<-ignore_critical>, B<-inhibit_any>,
467 B<-inhibit_map>, B<-no_alt_chains>, B<-no_check_time>, B<-partial_chain>, B<-policy>,
468 B<-policy_check>, B<-policy_print>, B<-purpose>, B<-suiteB_128>,
469 B<-suiteB_128_only>, B<-suiteB_192>, B<-trusted_first>, B<-use_deltas>,
470 B<-auth_level>, B<-verify_depth>, B<-verify_email>, B<-verify_hostname>,
471 B<-verify_ip>, B<-verify_name>, B<-x509_strict>
473 Set various certificate chain validation options. See the
474 L<openssl-verify(1)> manual page for details.
476 {- $OpenSSL::safe::opt_trust_item -}
478 {- $OpenSSL::safe::opt_r_item -}
480 =item I<cert.pem> ...
482 One or more certificates of message recipients: used when encrypting
489 The MIME message must be sent without any blank lines between the
490 headers and the output. Some mail programs will automatically add
491 a blank line. Piping the mail directly to sendmail is one way to
492 achieve the correct format.
494 The supplied message to be signed or encrypted must include the
495 necessary MIME headers or many S/MIME clients won't display it
496 properly (if at all). You can use the B<-text> option to automatically
497 add plain text headers.
499 A "signed and encrypted" message is one where a signed message is
500 then encrypted. This can be produced by encrypting an already signed
501 message: see the examples section.
503 This version of the program only allows one signer per message but it
504 will verify multiple signers on received messages. Some S/MIME clients
505 choke if a message contains multiple signers. It is possible to sign
506 messages "in parallel" by signing an already signed message.
508 The options B<-encrypt> and B<-decrypt> reflect common usage in S/MIME
509 clients. Strictly speaking these process CMS enveloped data: CMS
510 encrypted data is used for other purposes.
512 The B<-resign> option uses an existing message digest when adding a new
513 signer. This means that attributes must be present in at least one existing
514 signer using the same message digest or this operation will fail.
516 The B<-stream> and B<-indef> options enable streaming I/O support.
517 As a result the encoding is BER using indefinite length constructed encoding
518 and no longer DER. Streaming is supported for the B<-encrypt> operation and the
519 B<-sign> operation if the content is not detached.
521 Streaming is always used for the B<-sign> operation with detached data but
522 since the content is no longer part of the CMS structure the encoding
525 If the B<-decrypt> option is used without a recipient certificate then an
526 attempt is made to locate the recipient by trying each potential recipient
527 in turn using the supplied private key. To thwart the MMA attack
528 (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) all recipients are
529 tried whether they succeed or not and if no recipients match the message
530 is "decrypted" using a random key which will typically output garbage.
531 The B<-debug_decrypt> option can be used to disable the MMA attack protection
532 and return an error if no recipient can be found: this option should be used
533 with caution. For a fuller description see L<CMS_decrypt(3)>).
535 =head1 CADES BASIC ELECTRONIC SIGNATURE (CADES-BES)
537 A CAdES Basic Electronic Signature (CAdES-BES), as defined in the European Standard ETSI EN 319 122-1 V1.1.1, contains:
543 The signed user data as defined in CMS (RFC 3852);
547 Content-type of the EncapsulatedContentInfo value being signed;
551 Message-digest of the eContent OCTET STRING within encapContentInfo being signed;
555 An ESS signing-certificate or ESS signing-certificate-v2 attribute, as defined in Enhanced Security Services (ESS), RFC 2634 and RFC 5035.
556 An ESS signing-certificate attribute only allows for the use of SHA-1 as a digest algorithm.
557 An ESS signing-certificate-v2 attribute allows for the use of any digest algorithm.
561 The digital signature value computed on the user data and, when present, on the signed attributes.
563 Note that currently the B<-cades> option applies only to the B<-sign> operation and is ignored during
564 the B<-verify> operation, i.e. the signing certification is not checked during the verification process.
565 This feature might be added in a future version.
575 The operation was completely successfully.
579 An error occurred parsing the command options.
583 One of the input files could not be read.
587 An error occurred creating the CMS file or when reading the MIME
592 An error occurred decrypting or verifying the message.
596 The message was verified correctly but an error occurred writing out
597 the signers certificates.
601 =head1 COMPATIBILITY WITH PKCS#7 FORMAT
603 L<openssl-smime(1)> can only process the older B<PKCS#7> format.
604 B<openssl cms> supports Cryptographic Message Syntax format.
605 Use of some features will result in messages which cannot be processed by
606 applications which only support the older format. These are detailed below.
608 The use of the B<-keyid> option with B<-sign> or B<-encrypt>.
610 The B<-outform> I<PEM> option uses different headers.
612 The B<-compress> option.
614 The B<-secretkey> option when used with B<-encrypt>.
616 The use of PSS with B<-sign>.
618 The use of OAEP or non-RSA keys with B<-encrypt>.
620 Additionally the B<-EncryptedData_create> and B<-data_create> type cannot
621 be processed by the older L<openssl-smime(1)> command.
625 Create a cleartext signed message:
627 openssl cms -sign -in message.txt -text -out mail.msg \
630 Create an opaque signed message
632 openssl cms -sign -in message.txt -text -out mail.msg -nodetach \
635 Create a signed message, include some additional certificates and
636 read the private key from another file:
638 openssl cms -sign -in in.txt -text -out mail.msg \
639 -signer mycert.pem -inkey mykey.pem -certfile mycerts.pem
641 Create a signed message with two signers, use key identifier:
643 openssl cms -sign -in message.txt -text -out mail.msg \
644 -signer mycert.pem -signer othercert.pem -keyid
646 Send a signed message under Unix directly to sendmail, including headers:
648 openssl cms -sign -in in.txt -text -signer mycert.pem \
649 -from steve@openssl.org -to someone@somewhere \
650 -subject "Signed message" | sendmail someone@somewhere
652 Verify a message and extract the signer's certificate if successful:
654 openssl cms -verify -in mail.msg -signer user.pem -out signedtext.txt
656 Send encrypted mail using triple DES:
658 openssl cms -encrypt -in in.txt -from steve@openssl.org \
659 -to someone@somewhere -subject "Encrypted message" \
660 -des3 user.pem -out mail.msg
662 Sign and encrypt mail:
664 openssl cms -sign -in ml.txt -signer my.pem -text \
665 | openssl cms -encrypt -out mail.msg \
666 -from steve@openssl.org -to someone@somewhere \
667 -subject "Signed and Encrypted message" -des3 user.pem
669 Note: the encryption command does not include the B<-text> option because the
670 message being encrypted already has MIME headers.
674 openssl cms -decrypt -in mail.msg -recip mycert.pem -inkey key.pem
676 The output from Netscape form signing is a PKCS#7 structure with the
677 detached signature format. You can use this program to verify the
678 signature by line wrapping the base64 encoded structure and surrounding
681 -----BEGIN PKCS7-----
684 and using the command,
686 openssl cms -verify -inform PEM -in signature.pem -content content.txt
688 alternatively you can base64 decode the signature and use
690 openssl cms -verify -inform DER -in signature.der -content content.txt
692 Create an encrypted message using 128 bit Camellia:
694 openssl cms -encrypt -in plain.txt -camellia128 -out mail.msg cert.pem
696 Add a signer to an existing message:
698 openssl cms -resign -in mail.msg -signer newsign.pem -out mail2.msg
700 Sign mail using RSA-PSS:
702 openssl cms -sign -in message.txt -text -out mail.msg \
703 -signer mycert.pem -keyopt rsa_padding_mode:pss
705 Create encrypted mail using RSA-OAEP:
707 openssl cms -encrypt -in plain.txt -out mail.msg \
708 -recip cert.pem -keyopt rsa_padding_mode:oaep
710 Use SHA256 KDF with an ECDH certificate:
712 openssl cms -encrypt -in plain.txt -out mail.msg \
713 -recip ecdhcert.pem -keyopt ecdh_kdf_md:sha256
717 The MIME parser isn't very clever: it seems to handle most messages that I've
718 thrown at it but it may choke on others.
720 The code currently will only write out the signer's certificate to a file: if
721 the signer has a separate encryption certificate this must be manually
722 extracted. There should be some heuristic that determines the correct
723 encryption certificate.
725 Ideally a database should be maintained of a certificates for each email
728 The code doesn't currently take note of the permitted symmetric encryption
729 algorithms as supplied in the SMIMECapabilities signed attribute. this means the
730 user has to manually include the correct encryption algorithm. It should store
731 the list of permitted ciphers in a database and only use those.
733 No revocation checking is done on the signer's certificate.
737 L<ossl_store-file(7)>
741 The use of multiple B<-signer> options and the B<-resign> command were first
742 added in OpenSSL 1.0.0.
744 The B<-keyopt> option was added in OpenSSL 1.0.2.
746 Support for RSA-OAEP and RSA-PSS was added in OpenSSL 1.0.2.
748 The use of non-RSA keys with B<-encrypt> and B<-decrypt>
749 was added in OpenSSL 1.0.2.
751 The -no_alt_chains option was added in OpenSSL 1.0.2b.
755 Copyright 2008-2019 The OpenSSL Project Authors. All Rights Reserved.
757 Licensed under the Apache License 2.0 (the "License"). You may not use
758 this file except in compliance with the License. You can obtain a copy
759 in the file LICENSE in the source distribution or at
760 L<https://www.openssl.org/source/license.html>.