]>
Commit | Line | Data |
---|---|---|
7122aafc | 1 | =pod |
625c781d | 2 | {- OpenSSL::safe::output_do_not_edit_headers(); -} |
9fcb9702 | 3 | |
7122aafc DSH |
4 | =head1 NAME |
5 | ||
4b537191 | 6 | openssl-cms - CMS command |
7122aafc DSH |
7 | |
8 | =head1 SYNOPSIS | |
9 | ||
10 | B<openssl> B<cms> | |
169394d4 | 11 | [B<-help>] |
7122aafc DSH |
12 | [B<-encrypt>] |
13 | [B<-decrypt>] | |
65718c51 | 14 | [B<-debug_decrypt>] |
7122aafc | 15 | [B<-sign>] |
7122aafc | 16 | [B<-verify>] |
65718c51 RS |
17 | [B<-verify_retcode>] |
18 | [B<-no_attr_verify>] | |
19 | [B<-nosigs>] | |
20 | [B<-no_content_verify>] | |
7122aafc | 21 | [B<-cmsout>] |
41f81a01 | 22 | [B<-resign>] |
e85d19c6 | 23 | [B<-cades>] |
41f81a01 DSH |
24 | [B<-data_create>] |
25 | [B<-data_out>] | |
26 | [B<-digest_create>] | |
27 | [B<-digest_verify>] | |
28 | [B<-compress>] | |
29 | [B<-uncompress>] | |
65718c51 | 30 | [B<-EncryptedData_decrypt>] |
41f81a01 DSH |
31 | [B<-EncryptedData_encrypt>] |
32 | [B<-sign_receipt>] | |
e8769719 RS |
33 | [B<-verify_receipt> I<receipt>] |
34 | [B<-in> I<filename>] | |
e8769719 | 35 | [B<-out> I<filename>] |
777182a0 | 36 | [B<-inform> B<DER>|B<PEM>|B<SMIME>] |
e8769719 | 37 | [B<-outform> B<DER>|B<PEM>|B<SMIME>] |
777182a0 | 38 | [B<-rctform> B<DER>|B<PEM>|B<SMIME>] |
6d382c74 | 39 | [B<-keyform> B<DER>|B<PEM>|B<P12>|B<ENGINE>] |
e8769719 RS |
40 | [B<-stream>] |
41 | [B<-indef>] | |
41f81a01 | 42 | [B<-noindef>] |
e8769719 | 43 | [B<-content> I<filename>] |
41f81a01 DSH |
44 | [B<-text>] |
45 | [B<-noout>] | |
46 | [B<-print>] | |
922f1565 | 47 | [B<-nameopt> I<option>] |
e8769719 | 48 | [B<-md> I<digest>] |
8dc57d76 | 49 | [B<-I<cipher>>] |
34890077 | 50 | [B<-wrap> I<cipher>] |
41f81a01 | 51 | [B<-nointern>] |
e75138ab | 52 | [B<-noverify>] |
41f81a01 DSH |
53 | [B<-nocerts>] |
54 | [B<-noattr>] | |
55 | [B<-nosmimecap>] | |
56 | [B<-binary>] | |
2197494d | 57 | [B<-crlfeol>] |
847865d0 | 58 | [B<-asciicrlf>] |
41f81a01 | 59 | [B<-nodetach>] |
68581885 | 60 | [B<-certfile> I<file>] |
e8769719 RS |
61 | [B<-certsout> I<file>] |
62 | [B<-signer> I<file>] | |
34890077 | 63 | [B<-originator> I<file>] |
e8769719 | 64 | [B<-recip> I<file>] |
41f81a01 | 65 | [B<-keyid>] |
dfee8626 RS |
66 | [B<-receipt_request_all>] |
67 | [B<-receipt_request_first>] | |
e8769719 RS |
68 | [B<-receipt_request_from> I<emailaddress>] |
69 | [B<-receipt_request_to> I<emailaddress>] | |
41f81a01 | 70 | [B<-receipt_request_print>] |
65718c51 | 71 | [B<-pwri_password> I<password>] |
e8769719 RS |
72 | [B<-secretkey> I<key>] |
73 | [B<-secretkeyid> I<id>] | |
74 | [B<-econtent_type> I<type>] | |
75 | [B<-inkey> I<file>] | |
76 | [B<-keyopt> I<name>:I<parameter>] | |
77 | [B<-passin> I<arg>] | |
e8769719 RS |
78 | [B<-to> I<addr>] |
79 | [B<-from> I<addr>] | |
80 | [B<-subject> I<subj>] | |
21d08b9e | 81 | {- $OpenSSL::safe::opt_v_synopsis -} |
9fcb9702 RS |
82 | {- $OpenSSL::safe::opt_trust_synopsis -} |
83 | {- $OpenSSL::safe::opt_r_synopsis -} | |
65718c51 | 84 | {- $OpenSSL::safe::opt_engine_synopsis -} |
6bd4e3f2 | 85 | {- $OpenSSL::safe::opt_provider_synopsis -} |
c1669f41 | 86 | {- $OpenSSL::safe::opt_config_synopsis -} |
6d382c74 | 87 | [I<recipient-cert> ...] |
7122aafc | 88 | |
9f3c076b | 89 | =for openssl ifdef des-wrap engine |
1738c0ce | 90 | |
7122aafc DSH |
91 | =head1 DESCRIPTION |
92 | ||
35a810bb RL |
93 | This command handles S/MIME v3.1 mail. It can encrypt, decrypt, |
94 | sign and verify, compress and uncompress S/MIME messages. | |
7122aafc | 95 | |
3dfda1a6 | 96 | =head1 OPTIONS |
7122aafc | 97 | |
41f81a01 DSH |
98 | There are fourteen operation options that set the type of operation to be |
99 | performed. The meaning of the other options varies according to the operation | |
7122aafc DSH |
100 | type. |
101 | ||
102 | =over 4 | |
103 | ||
169394d4 MR |
104 | =item B<-help> |
105 | ||
106 | Print out a usage message. | |
107 | ||
7122aafc DSH |
108 | =item B<-encrypt> |
109 | ||
c4de074e | 110 | Encrypt mail for the given recipient certificates. Input file is the message |
7122aafc | 111 | to be encrypted. The output file is the encrypted mail in MIME format. The |
3f2a8d97 | 112 | actual CMS type is B<EnvelopedData>. |
7122aafc | 113 | |
2a9afa40 RS |
114 | Note that no revocation check is done for the recipient cert, so if that |
115 | key has been compromised, others may be able to decrypt the text. | |
116 | ||
7122aafc DSH |
117 | =item B<-decrypt> |
118 | ||
c4de074e | 119 | Decrypt mail using the supplied certificate and private key. Expects an |
7122aafc DSH |
120 | encrypted mail message in MIME format for the input file. The decrypted mail |
121 | is written to the output file. | |
122 | ||
0dd5b94a DSH |
123 | =item B<-debug_decrypt> |
124 | ||
c4de074e | 125 | This option sets the B<CMS_DEBUG_DECRYPT> flag. This option should be used |
0dd5b94a DSH |
126 | with caution: see the notes section below. |
127 | ||
7122aafc DSH |
128 | =item B<-sign> |
129 | ||
c4de074e | 130 | Sign mail using the supplied certificate and private key. Input file is |
7122aafc DSH |
131 | the message to be signed. The signed message in MIME format is written |
132 | to the output file. | |
133 | ||
134 | =item B<-verify> | |
135 | ||
c4de074e | 136 | Verify signed mail. Expects a signed mail message on input and outputs |
7122aafc DSH |
137 | the signed data. Both clear text and opaque signing is supported. |
138 | ||
65718c51 RS |
139 | =item B<-verify_retcode> |
140 | ||
141 | Exit nonzero on verification failure. | |
142 | ||
143 | =item B<-no_attr_verify> | |
144 | ||
145 | Do not verify signed attribute signatures. | |
146 | ||
147 | =item B<-no_content_verify> | |
148 | ||
149 | Do not verify signed content signatures. | |
150 | ||
151 | =item B<-nosigs> | |
152 | ||
153 | Don't verify message signature. | |
154 | ||
7122aafc DSH |
155 | =item B<-cmsout> |
156 | ||
c4de074e | 157 | Takes an input message and writes out a PEM encoded CMS structure. |
7122aafc DSH |
158 | |
159 | =item B<-resign> | |
160 | ||
c4de074e | 161 | Resign a message: take an existing message and one or more new signers. |
7122aafc | 162 | |
e85d19c6 AI |
163 | =item B<-cades> |
164 | ||
165 | Add an ESS signing-certificate or ESS signing-certificate-v2 signed-attribute to the SignerInfo, in order to make | |
166 | the signature comply with the requirements for a CAdES Basic Electronic Signature (CAdES-BES). See the NOTES | |
167 | section for more details. | |
168 | ||
7122aafc DSH |
169 | =item B<-data_create> |
170 | ||
171 | Create a CMS B<Data> type. | |
172 | ||
173 | =item B<-data_out> | |
174 | ||
175 | B<Data> type and output the content. | |
176 | ||
177 | =item B<-digest_create> | |
178 | ||
179 | Create a CMS B<DigestedData> type. | |
180 | ||
181 | =item B<-digest_verify> | |
182 | ||
183 | Verify a CMS B<DigestedData> type and output the content. | |
184 | ||
185 | =item B<-compress> | |
186 | ||
187 | Create a CMS B<CompressedData> type. OpenSSL must be compiled with B<zlib> | |
188 | support for this option to work, otherwise it will output an error. | |
189 | ||
190 | =item B<-uncompress> | |
191 | ||
192 | Uncompress a CMS B<CompressedData> type and output the content. OpenSSL must be | |
193 | compiled with B<zlib> support for this option to work, otherwise it will | |
194 | output an error. | |
195 | ||
65718c51 RS |
196 | =item B<-EncryptedData_decrypt> |
197 | ||
198 | Decrypt content using supplied symmetric key and algorithm using a CMS | |
199 | B<EncryptedData> type and output the content. | |
200 | ||
7122aafc DSH |
201 | =item B<-EncryptedData_encrypt> |
202 | ||
a9661e45 | 203 | Encrypt content using supplied symmetric key and algorithm using a CMS |
27b138e9 | 204 | B<EncryptedData> type and output the content. |
7122aafc | 205 | |
41f81a01 DSH |
206 | =item B<-sign_receipt> |
207 | ||
1bc74519 | 208 | Generate and output a signed receipt for the supplied message. The input |
41f81a01 DSH |
209 | message B<must> contain a signed receipt request. Functionality is otherwise |
210 | similar to the B<-sign> operation. | |
211 | ||
e8769719 | 212 | =item B<-verify_receipt> I<receipt> |
41f81a01 | 213 | |
1bc74519 | 214 | Verify a signed receipt in filename B<receipt>. The input message B<must> |
41f81a01 DSH |
215 | contain the original receipt request. Functionality is otherwise similar |
216 | to the B<-verify> operation. | |
217 | ||
e8769719 | 218 | =item B<-in> I<filename> |
7122aafc | 219 | |
c4de074e | 220 | The input message to be encrypted or signed or the message to be decrypted |
41f81a01 | 221 | or verified. |
7122aafc | 222 | |
777182a0 RS |
223 | =item B<-out> I<filename> |
224 | ||
225 | The message text that has been decrypted or verified or the output MIME | |
226 | format message that has been signed or verified. | |
227 | ||
e8769719 | 228 | =item B<-inform> B<DER>|B<PEM>|B<SMIME> |
7122aafc | 229 | |
777182a0 RS |
230 | The input format of the CMS structure (if one is being read); |
231 | the default is B<SMIME>. | |
232 | See L<openssl(1)/Format Options> for details. | |
7122aafc | 233 | |
777182a0 | 234 | =item B<-outform> B<DER>|B<PEM>|B<SMIME> |
41f81a01 | 235 | |
777182a0 RS |
236 | The output format of the CMS structure (if one is being written); |
237 | the default is B<SMIME>. | |
238 | See L<openssl(1)/Format Options> for details. | |
41f81a01 | 239 | |
6d382c74 | 240 | =item B<-keyform> B<DER>|B<PEM>|B<P12>|B<ENGINE> |
7122aafc | 241 | |
777182a0 | 242 | The format of the private key file; the default is B<PEM>. |
6d382c74 | 243 | The only value with effect is B<ENGINE>; all others have become obsolete. |
777182a0 | 244 | See L<openssl(1)/Format Options> for details. |
7122aafc | 245 | |
777182a0 | 246 | =item B<-rctform> B<DER>|B<PEM>|B<SMIME> |
7122aafc | 247 | |
777182a0 RS |
248 | The signed receipt format for use with the B<-receipt_verify>; the default |
249 | is B<SMIME>. | |
250 | See L<openssl(1)/Format Options> for details. | |
7122aafc | 251 | |
65718c51 | 252 | =item B<-stream>, B<-indef> |
7122aafc | 253 | |
c4de074e | 254 | The B<-stream> and B<-indef> options are equivalent and enable streaming I/O |
7122aafc DSH |
255 | for encoding operations. This permits single pass processing of data without |
256 | the need to hold the entire contents in memory, potentially supporting very | |
257 | large files. Streaming is automatically set for S/MIME signing with detached | |
258 | data if the output format is B<SMIME> it is currently off by default for all | |
259 | other operations. | |
260 | ||
261 | =item B<-noindef> | |
262 | ||
c4de074e | 263 | Disable streaming I/O where it would produce and indefinite length constructed |
7122aafc DSH |
264 | encoding. This option currently has no effect. In future streaming will be |
265 | enabled by default on all relevant operations and this option will disable it. | |
266 | ||
e8769719 | 267 | =item B<-content> I<filename> |
7122aafc DSH |
268 | |
269 | This specifies a file containing the detached content, this is only | |
270 | useful with the B<-verify> command. This is only usable if the CMS | |
271 | structure is using the detached signature form where the content is | |
272 | not included. This option will override any content if the input format | |
273 | is S/MIME and it uses the multipart/signed MIME content type. | |
274 | ||
275 | =item B<-text> | |
276 | ||
c4de074e | 277 | This option adds plain text (text/plain) MIME headers to the supplied |
7122aafc | 278 | message if encrypting or signing. If decrypting or verifying it strips |
1bc74519 | 279 | off text headers: if the decrypted or verified message is not of MIME |
7122aafc DSH |
280 | type text/plain then an error occurs. |
281 | ||
41f81a01 DSH |
282 | =item B<-noout> |
283 | ||
c4de074e | 284 | For the B<-cmsout> operation do not output the parsed CMS structure. This |
41f81a01 DSH |
285 | is useful when combined with the B<-print> option or if the syntax of the CMS |
286 | structure is being checked. | |
287 | ||
288 | =item B<-print> | |
289 | ||
c4de074e | 290 | For the B<-cmsout> operation print out all fields of the CMS structure. This |
41f81a01 DSH |
291 | is mainly useful for testing purposes. |
292 | ||
922f1565 DB |
293 | =item B<-nameopt> I<option> |
294 | ||
295 | For the B<-cmsout> operation when B<-print> option is in use, specifies | |
296 | printing options for string fields. For most cases B<utf8> is reasonable value. | |
297 | See L<openssl(1)/Name Format Options> for details. | |
298 | ||
e8769719 | 299 | =item B<-md> I<digest> |
7122aafc | 300 | |
c4de074e | 301 | Digest algorithm to use when signing or resigning. If not present then the |
7122aafc DSH |
302 | default digest algorithm for the signing key will be used (usually SHA1). |
303 | ||
8dc57d76 | 304 | =item B<-I<cipher>> |
7122aafc | 305 | |
c4de074e | 306 | The encryption algorithm to use. For example triple DES (168 bits) - B<-des3> |
e5fa864f | 307 | or 256 bit AES - B<-aes256>. Any standard algorithm name (as used by the |
1bc74519 | 308 | EVP_get_cipherbyname() function) can also be used preceded by a dash, for |
8bc93d2f | 309 | example B<-aes-128-cbc>. See L<openssl-enc(1)> for a list of ciphers |
e5fa864f | 310 | supported by your version of OpenSSL. |
7122aafc | 311 | |
924663c3 JZ |
312 | Currently the AES variants with GCM mode are the only supported AEAD |
313 | algorithms. | |
314 | ||
1bc74519 | 315 | If not specified triple DES is used. Only used with B<-encrypt> and |
7122aafc DSH |
316 | B<-EncryptedData_create> commands. |
317 | ||
34890077 DB |
318 | =item B<-wrap> I<cipher> |
319 | ||
320 | Cipher algorithm to use for key wrap when encrypting the message using Key | |
321 | Agreement for key transport. The algorithm specified should be suitable for key | |
322 | wrap. | |
323 | ||
7122aafc DSH |
324 | =item B<-nointern> |
325 | ||
c4de074e | 326 | When verifying a message normally certificates (if any) included in |
7122aafc DSH |
327 | the message are searched for the signing certificate. With this option |
328 | only the certificates specified in the B<-certfile> option are used. | |
329 | The supplied certificates can still be used as untrusted CAs however. | |
330 | ||
e75138ab | 331 | =item B<-noverify> |
7122aafc | 332 | |
c4de074e | 333 | Do not verify the signers certificate of a signed message. |
7122aafc DSH |
334 | |
335 | =item B<-nocerts> | |
336 | ||
c4de074e | 337 | When signing a message the signer's certificate is normally included |
7122aafc DSH |
338 | with this option it is excluded. This will reduce the size of the |
339 | signed message but the verifier must have a copy of the signers certificate | |
340 | available locally (passed using the B<-certfile> option for example). | |
341 | ||
342 | =item B<-noattr> | |
343 | ||
c4de074e | 344 | Normally when a message is signed a set of attributes are included which |
7122aafc DSH |
345 | include the signing time and supported symmetric algorithms. With this |
346 | option they are not included. | |
347 | ||
348 | =item B<-nosmimecap> | |
349 | ||
c4de074e | 350 | Exclude the list of supported algorithms from signed attributes, other options |
7122aafc DSH |
351 | such as signing time and content type are still included. |
352 | ||
353 | =item B<-binary> | |
354 | ||
c4de074e | 355 | Normally the input message is converted to "canonical" format which is |
7122aafc DSH |
356 | effectively using CR and LF as end of line: as required by the S/MIME |
357 | specification. When this option is present no translation occurs. This | |
358 | is useful when handling binary data which may not be in MIME format. | |
359 | ||
2197494d DSH |
360 | =item B<-crlfeol> |
361 | ||
c4de074e | 362 | Normally the output file uses a single B<LF> as end of line. When this |
2197494d DSH |
363 | option is present B<CRLF> is used instead. |
364 | ||
847865d0 DSH |
365 | =item B<-asciicrlf> |
366 | ||
c4de074e | 367 | When signing use ASCII CRLF format canonicalisation. This strips trailing |
847865d0 DSH |
368 | whitespace from all lines, deletes trailing blank lines at EOF and sets |
369 | the encapsulated content type. This option is normally used with detached | |
370 | content and an output signature format of DER. This option is not normally | |
371 | needed when verifying as it is enabled automatically if the encapsulated | |
372 | content format is detected. | |
373 | ||
7122aafc DSH |
374 | =item B<-nodetach> |
375 | ||
c4de074e | 376 | When signing a message use opaque signing: this form is more resistant |
7122aafc DSH |
377 | to translation by mail relays but it cannot be read by mail agents that |
378 | do not support S/MIME. Without this option cleartext signing with | |
379 | the MIME type multipart/signed is used. | |
380 | ||
e8769719 | 381 | =item B<-certfile> I<file> |
7122aafc | 382 | |
c4de074e | 383 | Allows additional certificates to be specified. When signing these will |
7122aafc | 384 | be included with the message. When verifying these will be searched for |
6d382c74 | 385 | the signers certificates. |
b3c5aadf | 386 | The input can be in PEM, DER, or PKCS#12 format. |
7122aafc | 387 | |
e8769719 | 388 | =item B<-certsout> I<file> |
4a954b56 | 389 | |
2f0ea936 | 390 | Any certificates contained in the message are written to I<file>. |
4a954b56 | 391 | |
e8769719 | 392 | =item B<-signer> I<file> |
7122aafc | 393 | |
c4de074e | 394 | A signing certificate when signing or resigning a message, this option can be |
7122aafc DSH |
395 | used multiple times if more than one signer is required. If a message is being |
396 | verified then the signers certificates will be written to this file if the | |
397 | verification was successful. | |
398 | ||
34890077 DB |
399 | =item B<-originator> I<file> |
400 | ||
401 | A certificate of the originator of the encrypted message. Necessary for | |
402 | decryption when Key Agreement is in use for a shared key. | |
403 | ||
e8769719 | 404 | =item B<-recip> I<file> |
7122aafc | 405 | |
c4de074e | 406 | When decrypting a message this specifies the recipients certificate. The |
4bf4a650 DSH |
407 | certificate must match one of the recipients of the message or an error |
408 | occurs. | |
409 | ||
410 | When encrypting a message this option may be used multiple times to specify | |
411 | each recipient. This form B<must> be used if customised parameters are | |
412 | required (for example to specify RSA-OAEP). | |
7122aafc | 413 | |
ecd4b8fe MC |
414 | Only certificates carrying RSA, Diffie-Hellman or EC keys are supported by this |
415 | option. | |
416 | ||
7122aafc DSH |
417 | =item B<-keyid> |
418 | ||
c4de074e | 419 | Use subject key identifier to identify certificates instead of issuer name and |
7122aafc DSH |
420 | serial number. The supplied certificate B<must> include a subject key |
421 | identifier extension. Supported by B<-sign> and B<-encrypt> options. | |
422 | ||
dfee8626 | 423 | =item B<-receipt_request_all>, B<-receipt_request_first> |
41f81a01 | 424 | |
c4de074e | 425 | For B<-sign> option include a signed receipt request. Indicate requests should |
4c583c36 | 426 | be provided by all recipient or first tier recipients (those mailed directly |
41f81a01 DSH |
427 | and not from a mailing list). Ignored it B<-receipt_request_from> is included. |
428 | ||
e8769719 | 429 | =item B<-receipt_request_from> I<emailaddress> |
41f81a01 | 430 | |
c4de074e | 431 | For B<-sign> option include a signed receipt request. Add an explicit email |
41f81a01 DSH |
432 | address where receipts should be supplied. |
433 | ||
e8769719 | 434 | =item B<-receipt_request_to> I<emailaddress> |
41f81a01 | 435 | |
1bc74519 | 436 | Add an explicit email address where signed receipts should be sent to. This |
41f81a01 DSH |
437 | option B<must> but supplied if a signed receipt it requested. |
438 | ||
439 | =item B<-receipt_request_print> | |
440 | ||
441 | For the B<-verify> operation print out the contents of any signed receipt | |
442 | requests. | |
443 | ||
65718c51 RS |
444 | =item B<-pwri_password> I<password> |
445 | ||
446 | Specify password for recipient. | |
447 | ||
e8769719 | 448 | =item B<-secretkey> I<key> |
7122aafc | 449 | |
c4de074e | 450 | Specify symmetric key to use. The key must be supplied in hex format and be |
7122aafc | 451 | consistent with the algorithm used. Supported by the B<-EncryptedData_encrypt> |
4c583c36 | 452 | B<-EncryptedData_decrypt>, B<-encrypt> and B<-decrypt> options. When used |
7122aafc DSH |
453 | with B<-encrypt> or B<-decrypt> the supplied key is used to wrap or unwrap the |
454 | content encryption key using an AES key in the B<KEKRecipientInfo> type. | |
455 | ||
e8769719 | 456 | =item B<-secretkeyid> I<id> |
7122aafc | 457 | |
c4de074e | 458 | The key identifier for the supplied symmetric key for B<KEKRecipientInfo> type. |
7122aafc | 459 | This option B<must> be present if the B<-secretkey> option is used with |
2f0ea936 | 460 | B<-encrypt>. With B<-decrypt> operations the I<id> is used to locate the |
7122aafc DSH |
461 | relevant key if it is not supplied then an attempt is used to decrypt any |
462 | B<KEKRecipientInfo> structures. | |
463 | ||
e8769719 | 464 | =item B<-econtent_type> I<type> |
7122aafc | 465 | |
2f0ea936 RL |
466 | Set the encapsulated content type to I<type> if not supplied the B<Data> type |
467 | is used. The I<type> argument can be any valid OID name in either text or | |
1bc74519 | 468 | numerical format. |
7122aafc | 469 | |
e8769719 | 470 | =item B<-inkey> I<file> |
7122aafc | 471 | |
c4de074e | 472 | The private key to use when signing or decrypting. This must match the |
7122aafc DSH |
473 | corresponding certificate. If this option is not specified then the |
474 | private key must be included in the certificate file specified with | |
475 | the B<-recip> or B<-signer> file. When signing this option can be used | |
476 | multiple times to specify successive keys. | |
477 | ||
e8769719 | 478 | =item B<-keyopt> I<name>:I<parameter> |
4bf4a650 | 479 | |
c4de074e | 480 | For signing and encryption this option can be used multiple times to |
4bf4a650 | 481 | set customised parameters for the preceding key or certificate. It can |
dfcb42c6 DSH |
482 | currently be used to set RSA-PSS for signing, RSA-OAEP for encryption |
483 | or to modify default parameters for ECDH. | |
4bf4a650 | 484 | |
e8769719 | 485 | =item B<-passin> I<arg> |
7122aafc | 486 | |
c4de074e | 487 | The private key password source. For more information about the format of B<arg> |
3a4e43de | 488 | see L<openssl(1)/Pass Phrase Options>. |
7122aafc | 489 | |
e8769719 | 490 | =item B<-to>, B<-from>, B<-subject> |
7122aafc | 491 | |
c4de074e | 492 | The relevant mail headers. These are included outside the signed |
7122aafc DSH |
493 | portion of a message so they may be included manually. If signing |
494 | then many S/MIME mail clients check the signers certificate's email | |
495 | address matches that specified in the From: address. | |
496 | ||
21d08b9e | 497 | {- $OpenSSL::safe::opt_v_item -} |
e5fa864f | 498 | |
21d08b9e | 499 | Any verification errors cause the command to exit. |
e5fa864f | 500 | |
9fcb9702 RS |
501 | {- $OpenSSL::safe::opt_trust_item -} |
502 | ||
503 | {- $OpenSSL::safe::opt_r_item -} | |
504 | ||
65718c51 RS |
505 | {- $OpenSSL::safe::opt_engine_item -} |
506 | ||
6bd4e3f2 P |
507 | {- $OpenSSL::safe::opt_provider_item -} |
508 | ||
c1669f41 SL |
509 | {- $OpenSSL::safe::opt_config_item -} |
510 | ||
6d382c74 | 511 | =item I<recipient-cert> ... |
9fcb9702 RS |
512 | |
513 | One or more certificates of message recipients: used when encrypting | |
514 | a message. | |
515 | ||
7122aafc DSH |
516 | =back |
517 | ||
518 | =head1 NOTES | |
519 | ||
520 | The MIME message must be sent without any blank lines between the | |
521 | headers and the output. Some mail programs will automatically add | |
522 | a blank line. Piping the mail directly to sendmail is one way to | |
523 | achieve the correct format. | |
524 | ||
525 | The supplied message to be signed or encrypted must include the | |
60250017 | 526 | necessary MIME headers or many S/MIME clients won't display it |
7122aafc DSH |
527 | properly (if at all). You can use the B<-text> option to automatically |
528 | add plain text headers. | |
529 | ||
530 | A "signed and encrypted" message is one where a signed message is | |
531 | then encrypted. This can be produced by encrypting an already signed | |
532 | message: see the examples section. | |
533 | ||
534 | This version of the program only allows one signer per message but it | |
535 | will verify multiple signers on received messages. Some S/MIME clients | |
536 | choke if a message contains multiple signers. It is possible to sign | |
537 | messages "in parallel" by signing an already signed message. | |
538 | ||
539 | The options B<-encrypt> and B<-decrypt> reflect common usage in S/MIME | |
540 | clients. Strictly speaking these process CMS enveloped data: CMS | |
541 | encrypted data is used for other purposes. | |
542 | ||
543 | The B<-resign> option uses an existing message digest when adding a new | |
544 | signer. This means that attributes must be present in at least one existing | |
545 | signer using the same message digest or this operation will fail. | |
546 | ||
e4ef2e25 | 547 | The B<-stream> and B<-indef> options enable streaming I/O support. |
7122aafc DSH |
548 | As a result the encoding is BER using indefinite length constructed encoding |
549 | and no longer DER. Streaming is supported for the B<-encrypt> operation and the | |
550 | B<-sign> operation if the content is not detached. | |
551 | ||
552 | Streaming is always used for the B<-sign> operation with detached data but | |
553 | since the content is no longer part of the CMS structure the encoding | |
554 | remains DER. | |
555 | ||
0dd5b94a DSH |
556 | If the B<-decrypt> option is used without a recipient certificate then an |
557 | attempt is made to locate the recipient by trying each potential recipient | |
558 | in turn using the supplied private key. To thwart the MMA attack | |
559 | (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) all recipients are | |
560 | tried whether they succeed or not and if no recipients match the message | |
1bc74519 | 561 | is "decrypted" using a random key which will typically output garbage. |
0dd5b94a DSH |
562 | The B<-debug_decrypt> option can be used to disable the MMA attack protection |
563 | and return an error if no recipient can be found: this option should be used | |
9b86974e | 564 | with caution. For a fuller description see L<CMS_decrypt(3)>). |
0dd5b94a | 565 | |
485d3361 | 566 | =head1 CADES BASIC ELECTRONIC SIGNATURE (CADES-BES) |
e85d19c6 AI |
567 | |
568 | A CAdES Basic Electronic Signature (CAdES-BES), as defined in the European Standard ETSI EN 319 122-1 V1.1.1, contains: | |
569 | ||
570 | =over 4 | |
571 | ||
572 | =item * | |
573 | ||
574 | The signed user data as defined in CMS (RFC 3852); | |
575 | ||
576 | =item * | |
577 | ||
578 | Content-type of the EncapsulatedContentInfo value being signed; | |
579 | ||
580 | =item * | |
581 | ||
582 | Message-digest of the eContent OCTET STRING within encapContentInfo being signed; | |
583 | ||
584 | =item * | |
585 | ||
9e3c510b F |
586 | An ESS signing-certificate or ESS signing-certificate-v2 attribute, as defined |
587 | in Enhanced Security Services (ESS), RFC 2634 and RFC 5035. | |
e85d19c6 AI |
588 | An ESS signing-certificate attribute only allows for the use of SHA-1 as a digest algorithm. |
589 | An ESS signing-certificate-v2 attribute allows for the use of any digest algorithm. | |
590 | ||
591 | =item * | |
592 | ||
593 | The digital signature value computed on the user data and, when present, on the signed attributes. | |
594 | ||
9e3c510b F |
595 | NOTE that the B<-cades> option applies to the B<-sign> or B<-verify> operations. |
596 | With this option, the B<-verify> operation also checks that the signing-certificates | |
597 | attribute is present, and its value matches the verification trust chain built | |
598 | during the verification process. | |
e85d19c6 AI |
599 | |
600 | =back | |
601 | ||
7122aafc DSH |
602 | =head1 EXIT CODES |
603 | ||
604 | =over 4 | |
605 | ||
c8919dde | 606 | =item Z<>0 |
7122aafc | 607 | |
c4de074e | 608 | The operation was completely successfully. |
7122aafc | 609 | |
c8919dde | 610 | =item Z<>1 |
7122aafc | 611 | |
c4de074e | 612 | An error occurred parsing the command options. |
7122aafc | 613 | |
c8919dde | 614 | =item Z<>2 |
7122aafc | 615 | |
c4de074e | 616 | One of the input files could not be read. |
7122aafc | 617 | |
c8919dde | 618 | =item Z<>3 |
7122aafc | 619 | |
c4de074e | 620 | An error occurred creating the CMS file or when reading the MIME |
7122aafc DSH |
621 | message. |
622 | ||
c8919dde | 623 | =item Z<>4 |
7122aafc | 624 | |
c4de074e | 625 | An error occurred decrypting or verifying the message. |
7122aafc | 626 | |
c8919dde | 627 | =item Z<>5 |
7122aafc | 628 | |
c4de074e | 629 | The message was verified correctly but an error occurred writing out |
7122aafc DSH |
630 | the signers certificates. |
631 | ||
632 | =back | |
633 | ||
485d3361 | 634 | =head1 COMPATIBILITY WITH PKCS#7 FORMAT |
7122aafc | 635 | |
35a810bb RL |
636 | L<openssl-smime(1)> can only process the older B<PKCS#7> format. |
637 | B<openssl cms> supports Cryptographic Message Syntax format. | |
638 | Use of some features will result in messages which cannot be processed by | |
639 | applications which only support the older format. These are detailed below. | |
7122aafc DSH |
640 | |
641 | The use of the B<-keyid> option with B<-sign> or B<-encrypt>. | |
642 | ||
e8769719 | 643 | The B<-outform> I<PEM> option uses different headers. |
7122aafc DSH |
644 | |
645 | The B<-compress> option. | |
646 | ||
647 | The B<-secretkey> option when used with B<-encrypt>. | |
648 | ||
dfcb42c6 DSH |
649 | The use of PSS with B<-sign>. |
650 | ||
651 | The use of OAEP or non-RSA keys with B<-encrypt>. | |
652 | ||
7122aafc | 653 | Additionally the B<-EncryptedData_create> and B<-data_create> type cannot |
35a810bb | 654 | be processed by the older L<openssl-smime(1)> command. |
7122aafc DSH |
655 | |
656 | =head1 EXAMPLES | |
657 | ||
658 | Create a cleartext signed message: | |
659 | ||
660 | openssl cms -sign -in message.txt -text -out mail.msg \ | |
1bc74519 | 661 | -signer mycert.pem |
7122aafc DSH |
662 | |
663 | Create an opaque signed message | |
664 | ||
665 | openssl cms -sign -in message.txt -text -out mail.msg -nodetach \ | |
1bc74519 | 666 | -signer mycert.pem |
7122aafc DSH |
667 | |
668 | Create a signed message, include some additional certificates and | |
669 | read the private key from another file: | |
670 | ||
671 | openssl cms -sign -in in.txt -text -out mail.msg \ | |
1bc74519 | 672 | -signer mycert.pem -inkey mykey.pem -certfile mycerts.pem |
7122aafc DSH |
673 | |
674 | Create a signed message with two signers, use key identifier: | |
675 | ||
676 | openssl cms -sign -in message.txt -text -out mail.msg \ | |
1bc74519 | 677 | -signer mycert.pem -signer othercert.pem -keyid |
7122aafc DSH |
678 | |
679 | Send a signed message under Unix directly to sendmail, including headers: | |
680 | ||
681 | openssl cms -sign -in in.txt -text -signer mycert.pem \ | |
1bc74519 RS |
682 | -from steve@openssl.org -to someone@somewhere \ |
683 | -subject "Signed message" | sendmail someone@somewhere | |
7122aafc DSH |
684 | |
685 | Verify a message and extract the signer's certificate if successful: | |
686 | ||
687 | openssl cms -verify -in mail.msg -signer user.pem -out signedtext.txt | |
688 | ||
689 | Send encrypted mail using triple DES: | |
690 | ||
691 | openssl cms -encrypt -in in.txt -from steve@openssl.org \ | |
1bc74519 RS |
692 | -to someone@somewhere -subject "Encrypted message" \ |
693 | -des3 user.pem -out mail.msg | |
7122aafc DSH |
694 | |
695 | Sign and encrypt mail: | |
696 | ||
697 | openssl cms -sign -in ml.txt -signer my.pem -text \ | |
1bc74519 RS |
698 | | openssl cms -encrypt -out mail.msg \ |
699 | -from steve@openssl.org -to someone@somewhere \ | |
700 | -subject "Signed and Encrypted message" -des3 user.pem | |
7122aafc DSH |
701 | |
702 | Note: the encryption command does not include the B<-text> option because the | |
703 | message being encrypted already has MIME headers. | |
704 | ||
705 | Decrypt mail: | |
706 | ||
707 | openssl cms -decrypt -in mail.msg -recip mycert.pem -inkey key.pem | |
708 | ||
709 | The output from Netscape form signing is a PKCS#7 structure with the | |
710 | detached signature format. You can use this program to verify the | |
711 | signature by line wrapping the base64 encoded structure and surrounding | |
712 | it with: | |
713 | ||
714 | -----BEGIN PKCS7----- | |
715 | -----END PKCS7----- | |
716 | ||
1bc74519 | 717 | and using the command, |
7122aafc DSH |
718 | |
719 | openssl cms -verify -inform PEM -in signature.pem -content content.txt | |
720 | ||
721 | alternatively you can base64 decode the signature and use | |
722 | ||
723 | openssl cms -verify -inform DER -in signature.der -content content.txt | |
724 | ||
725 | Create an encrypted message using 128 bit Camellia: | |
726 | ||
727 | openssl cms -encrypt -in plain.txt -camellia128 -out mail.msg cert.pem | |
728 | ||
729 | Add a signer to an existing message: | |
730 | ||
731 | openssl cms -resign -in mail.msg -signer newsign.pem -out mail2.msg | |
732 | ||
4bf4a650 DSH |
733 | Sign mail using RSA-PSS: |
734 | ||
735 | openssl cms -sign -in message.txt -text -out mail.msg \ | |
1bc74519 | 736 | -signer mycert.pem -keyopt rsa_padding_mode:pss |
4bf4a650 DSH |
737 | |
738 | Create encrypted mail using RSA-OAEP: | |
739 | ||
dfcb42c6 | 740 | openssl cms -encrypt -in plain.txt -out mail.msg \ |
1bc74519 | 741 | -recip cert.pem -keyopt rsa_padding_mode:oaep |
4bf4a650 | 742 | |
dfcb42c6 DSH |
743 | Use SHA256 KDF with an ECDH certificate: |
744 | ||
745 | openssl cms -encrypt -in plain.txt -out mail.msg \ | |
1bc74519 | 746 | -recip ecdhcert.pem -keyopt ecdh_kdf_md:sha256 |
dfcb42c6 | 747 | |
7122aafc DSH |
748 | =head1 BUGS |
749 | ||
750 | The MIME parser isn't very clever: it seems to handle most messages that I've | |
751 | thrown at it but it may choke on others. | |
752 | ||
753 | The code currently will only write out the signer's certificate to a file: if | |
754 | the signer has a separate encryption certificate this must be manually | |
755 | extracted. There should be some heuristic that determines the correct | |
756 | encryption certificate. | |
757 | ||
758 | Ideally a database should be maintained of a certificates for each email | |
759 | address. | |
760 | ||
761 | The code doesn't currently take note of the permitted symmetric encryption | |
762 | algorithms as supplied in the SMIMECapabilities signed attribute. this means the | |
763 | user has to manually include the correct encryption algorithm. It should store | |
764 | the list of permitted ciphers in a database and only use those. | |
765 | ||
766 | No revocation checking is done on the signer's certificate. | |
767 | ||
fd3397fc RL |
768 | =head1 SEE ALSO |
769 | ||
770 | L<ossl_store-file(7)> | |
771 | ||
7122aafc DSH |
772 | =head1 HISTORY |
773 | ||
774 | The use of multiple B<-signer> options and the B<-resign> command were first | |
ecd4b8fe | 775 | added in OpenSSL 1.0.0. |
4bf4a650 | 776 | |
2f0ea936 | 777 | The B<-keyopt> option was added in OpenSSL 1.0.2. |
4bf4a650 | 778 | |
fc5ecadd | 779 | Support for RSA-OAEP and RSA-PSS was added in OpenSSL 1.0.2. |
7122aafc | 780 | |
fc5ecadd DMSP |
781 | The use of non-RSA keys with B<-encrypt> and B<-decrypt> |
782 | was added in OpenSSL 1.0.2. | |
dfcb42c6 | 783 | |
fc5ecadd | 784 | The -no_alt_chains option was added in OpenSSL 1.0.2b. |
fa7b0111 | 785 | |
6d382c74 DDO |
786 | All B<-keyform> values except B<ENGINE> have become obsolete in OpenSSL 3.0.0 |
787 | and have no effect. | |
788 | ||
922f1565 DB |
789 | The B<-nameopt> option was added in OpenSSL 3.0.0. |
790 | ||
0f221d9c P |
791 | The B<-engine> option was deprecated in OpenSSL 3.0. |
792 | ||
e2f92610 RS |
793 | =head1 COPYRIGHT |
794 | ||
33388b44 | 795 | Copyright 2008-2020 The OpenSSL Project Authors. All Rights Reserved. |
e2f92610 | 796 | |
449040b4 | 797 | Licensed under the Apache License 2.0 (the "License"). You may not use |
e2f92610 RS |
798 | this file except in compliance with the License. You can obtain a copy |
799 | in the file LICENSE in the source distribution or at | |
800 | L<https://www.openssl.org/source/license.html>. | |
801 | ||
802 | =cut |