]>
Commit | Line | Data |
---|---|---|
e3775a33 DSH |
1 | =pod |
2 | ||
3 | =head1 NAME | |
4 | ||
b6b66573 | 5 | openssl-smime - S/MIME utility |
e3775a33 DSH |
6 | |
7 | =head1 SYNOPSIS | |
8 | ||
9 | B<openssl> B<smime> | |
169394d4 | 10 | [B<-help>] |
e3775a33 DSH |
11 | [B<-encrypt>] |
12 | [B<-decrypt>] | |
13 | [B<-sign>] | |
d884c5ba | 14 | [B<-resign>] |
e3775a33 DSH |
15 | [B<-verify>] |
16 | [B<-pk7out>] | |
2197494d DSH |
17 | [B<-binary>] |
18 | [B<-crlfeol>] | |
e8769719 RS |
19 | [B<->I<cipher>] |
20 | [B<-in> I<file>] | |
21 | [B<-CAfile> I<file>] | |
22 | [B<-CApath> I<dir>] | |
40e2d76b MC |
23 | [B<-no-CAfile>] |
24 | [B<-no-CApath>] | |
e8769719 | 25 | [B<-attime> I<timestamp>] |
e42d84be HK |
26 | [B<-check_ss_sig>] |
27 | [B<-crl_check>] | |
28 | [B<-crl_check_all>] | |
29 | [B<-explicit_policy>] | |
30 | [B<-extended_crl>] | |
31 | [B<-ignore_critical>] | |
32 | [B<-inhibit_any>] | |
33 | [B<-inhibit_map>] | |
e42d84be | 34 | [B<-partial_chain>] |
e8769719 | 35 | [B<-policy> I<arg>] |
e42d84be HK |
36 | [B<-policy_check>] |
37 | [B<-policy_print>] | |
e8769719 | 38 | [B<-purpose> I<purpose>] |
e42d84be HK |
39 | [B<-suiteB_128>] |
40 | [B<-suiteB_128_only>] | |
41 | [B<-suiteB_192>] | |
6d3d5793 | 42 | [B<-trusted_first>] |
fa7b0111 | 43 | [B<-no_alt_chains>] |
e42d84be | 44 | [B<-use_deltas>] |
e8769719 RS |
45 | [B<-auth_level> I<num>] |
46 | [B<-verify_depth> I<num>] | |
47 | [B<-verify_email> I<email>] | |
48 | [B<-verify_hostname> I<hostname>] | |
49 | [B<-verify_ip> I<ip>] | |
50 | [B<-verify_name> I<name>] | |
e42d84be | 51 | [B<-x509_strict>] |
e8769719 RS |
52 | [B<-certfile> I<file>] |
53 | [B<-signer> I<file>] | |
54 | [B<-recip> I< file>] | |
55 | [B<-inform> B<DER>|B<PEM>|B<SMIME>] | |
56 | [B<-passin> I<arg>] | |
57 | [B<-inkey> I<file_or_id>] | |
58 | [B<-out> I<file>] | |
59 | [B<-outform> B<DER>|B<PEM>|B<SMIME>] | |
60 | [B<-content> I<file>] | |
61 | [B<-to> I<addr>] | |
62 | [B<-from> I<ad>] | |
63 | [B<-subject> I<s>] | |
e3775a33 | 64 | [B<-text>] |
76b46e77 DSH |
65 | [B<-indef>] |
66 | [B<-noindef>] | |
67 | [B<-stream>] | |
e8769719 RS |
68 | [B<-rand> I<file...>] |
69 | [B<-writerand> I<file>] | |
70 | [B<-md> I<digest>] | |
e3775a33 DSH |
71 | [cert.pem]... |
72 | ||
1738c0ce RS |
73 | =for comment ifdef engine |
74 | ||
e3775a33 DSH |
75 | =head1 DESCRIPTION |
76 | ||
77 | The B<smime> command handles S/MIME mail. It can encrypt, decrypt, sign and | |
78 | verify S/MIME messages. | |
79 | ||
3dfda1a6 | 80 | =head1 OPTIONS |
e3775a33 | 81 | |
76b46e77 | 82 | There are six operation options that set the type of operation to be performed. |
e3775a33 DSH |
83 | The meaning of the other options varies according to the operation type. |
84 | ||
85 | =over 4 | |
86 | ||
169394d4 MR |
87 | =item B<-help> |
88 | ||
89 | Print out a usage message. | |
90 | ||
e3775a33 DSH |
91 | =item B<-encrypt> |
92 | ||
c4de074e | 93 | Encrypt mail for the given recipient certificates. Input file is the message |
e3775a33 DSH |
94 | to be encrypted. The output file is the encrypted mail in MIME format. |
95 | ||
2a9afa40 RS |
96 | Note that no revocation check is done for the recipient cert, so if that |
97 | key has been compromised, others may be able to decrypt the text. | |
98 | ||
e3775a33 DSH |
99 | =item B<-decrypt> |
100 | ||
c4de074e | 101 | Decrypt mail using the supplied certificate and private key. Expects an |
e3775a33 DSH |
102 | encrypted mail message in MIME format for the input file. The decrypted mail |
103 | is written to the output file. | |
104 | ||
105 | =item B<-sign> | |
106 | ||
c4de074e | 107 | Sign mail using the supplied certificate and private key. Input file is |
e3775a33 DSH |
108 | the message to be signed. The signed message in MIME format is written |
109 | to the output file. | |
110 | ||
111 | =item B<-verify> | |
112 | ||
c4de074e | 113 | Verify signed mail. Expects a signed mail message on input and outputs |
e3775a33 DSH |
114 | the signed data. Both clear text and opaque signing is supported. |
115 | ||
116 | =item B<-pk7out> | |
117 | ||
c4de074e | 118 | Takes an input message and writes out a PEM encoded PKCS#7 structure. |
e3775a33 | 119 | |
d884c5ba DSH |
120 | =item B<-resign> |
121 | ||
c4de074e | 122 | Resign a message: take an existing message and one or more new signers. |
d884c5ba | 123 | |
e8769719 | 124 | =item B<-in> I<filename> |
e3775a33 | 125 | |
c4de074e | 126 | The input message to be encrypted or signed or the MIME message to |
e3775a33 DSH |
127 | be decrypted or verified. |
128 | ||
e8769719 | 129 | =item B<-inform> B<DER>|B<PEM>|B<SMIME> |
fd13f0ee | 130 | |
c4de074e | 131 | This specifies the input format for the PKCS#7 structure. The default |
fd13f0ee DSH |
132 | is B<SMIME> which reads an S/MIME format message. B<PEM> and B<DER> |
133 | format change this to expect PEM and DER format PKCS#7 structures | |
134 | instead. This currently only affects the input format of the PKCS#7 | |
135 | structure, if no PKCS#7 structure is being input (for example with | |
136 | B<-encrypt> or B<-sign>) this option has no effect. | |
137 | ||
e8769719 | 138 | =item B<-out> I<filename> |
e3775a33 | 139 | |
c4de074e | 140 | The message text that has been decrypted or verified or the output MIME |
e3775a33 DSH |
141 | format message that has been signed or verified. |
142 | ||
e8769719 | 143 | =item B<-outform> B<DER>|B<PEM>|B<SMIME> |
fd13f0ee | 144 | |
c4de074e | 145 | This specifies the output format for the PKCS#7 structure. The default |
fd13f0ee DSH |
146 | is B<SMIME> which write an S/MIME format message. B<PEM> and B<DER> |
147 | format change this to write PEM and DER format PKCS#7 structures | |
148 | instead. This currently only affects the output format of the PKCS#7 | |
149 | structure, if no PKCS#7 structure is being output (for example with | |
150 | B<-verify> or B<-decrypt>) this option has no effect. | |
151 | ||
e8769719 | 152 | =item B<-stream>, B<-indef>, B<-noindef> |
76b46e77 | 153 | |
c4de074e | 154 | The B<-stream> and B<-indef> options are equivalent and enable streaming I/O |
76b46e77 DSH |
155 | for encoding operations. This permits single pass processing of data without |
156 | the need to hold the entire contents in memory, potentially supporting very | |
157 | large files. Streaming is automatically set for S/MIME signing with detached | |
158 | data if the output format is B<SMIME> it is currently off by default for all | |
159 | other operations. | |
160 | ||
161 | =item B<-noindef> | |
162 | ||
c4de074e | 163 | Disable streaming I/O where it would produce and indefinite length constructed |
76b46e77 DSH |
164 | encoding. This option currently has no effect. In future streaming will be |
165 | enabled by default on all relevant operations and this option will disable it. | |
166 | ||
e8769719 | 167 | =item B<-content> I<filename> |
fd13f0ee DSH |
168 | |
169 | This specifies a file containing the detached content, this is only | |
170 | useful with the B<-verify> command. This is only usable if the PKCS#7 | |
171 | structure is using the detached signature form where the content is | |
172 | not included. This option will override any content if the input format | |
173 | is S/MIME and it uses the multipart/signed MIME content type. | |
174 | ||
e3775a33 DSH |
175 | =item B<-text> |
176 | ||
c4de074e | 177 | This option adds plain text (text/plain) MIME headers to the supplied |
e3775a33 | 178 | message if encrypting or signing. If decrypting or verifying it strips |
1bc74519 | 179 | off text headers: if the decrypted or verified message is not of MIME |
e3775a33 DSH |
180 | type text/plain then an error occurs. |
181 | ||
e8769719 | 182 | =item B<-CAfile> I<file> |
e3775a33 | 183 | |
c4de074e | 184 | A file containing trusted CA certificates, only used with B<-verify>. |
e3775a33 | 185 | |
e8769719 | 186 | =item B<-CApath> I<dir> |
e3775a33 | 187 | |
c4de074e | 188 | A directory containing trusted CA certificates, only used with |
e3775a33 DSH |
189 | B<-verify>. This directory must be a standard certificate directory: that |
190 | is a hash of each subject name (using B<x509 -hash>) should be linked | |
191 | to each certificate. | |
192 | ||
40e2d76b MC |
193 | =item B<-no-CAfile> |
194 | ||
c4de074e | 195 | Do not load the trusted CA certificates from the default file location. |
40e2d76b MC |
196 | |
197 | =item B<-no-CApath> | |
198 | ||
c4de074e | 199 | Do not load the trusted CA certificates from the default directory location. |
40e2d76b | 200 | |
e8769719 | 201 | =item B<-md> I<digest> |
d884c5ba | 202 | |
c4de074e | 203 | Digest algorithm to use when signing or resigning. If not present then the |
d884c5ba DSH |
204 | default digest algorithm for the signing key will be used (usually SHA1). |
205 | ||
e8769719 | 206 | =item B<->I<cipher> |
e3775a33 | 207 | |
c4de074e | 208 | The encryption algorithm to use. For example DES (56 bits) - B<-des>, |
e5fa864f | 209 | triple DES (168 bits) - B<-des3>, |
1bc74519 | 210 | EVP_get_cipherbyname() function) can also be used preceded by a dash, for |
9446daac | 211 | example B<-aes-128-cbc>. See L<B<enc>|enc(1)> for list of ciphers |
e5fa864f | 212 | supported by your version of OpenSSL. |
d884c5ba | 213 | |
6f719f06 | 214 | If not specified triple DES is used. Only used with B<-encrypt>. |
e3775a33 DSH |
215 | |
216 | =item B<-nointern> | |
217 | ||
c4de074e | 218 | When verifying a message normally certificates (if any) included in |
e3775a33 DSH |
219 | the message are searched for the signing certificate. With this option |
220 | only the certificates specified in the B<-certfile> option are used. | |
221 | The supplied certificates can still be used as untrusted CAs however. | |
222 | ||
223 | =item B<-noverify> | |
224 | ||
c4de074e | 225 | Do not verify the signers certificate of a signed message. |
e3775a33 DSH |
226 | |
227 | =item B<-nochain> | |
228 | ||
c4de074e | 229 | Do not do chain verification of signers certificates: that is don't |
e3775a33 DSH |
230 | use the certificates in the signed message as untrusted CAs. |
231 | ||
232 | =item B<-nosigs> | |
233 | ||
c4de074e | 234 | Don't try to verify the signatures on the message. |
e3775a33 DSH |
235 | |
236 | =item B<-nocerts> | |
237 | ||
c4de074e | 238 | When signing a message the signer's certificate is normally included |
e3775a33 DSH |
239 | with this option it is excluded. This will reduce the size of the |
240 | signed message but the verifier must have a copy of the signers certificate | |
241 | available locally (passed using the B<-certfile> option for example). | |
242 | ||
243 | =item B<-noattr> | |
244 | ||
c4de074e | 245 | Normally when a message is signed a set of attributes are included which |
e3775a33 DSH |
246 | include the signing time and supported symmetric algorithms. With this |
247 | option they are not included. | |
248 | ||
249 | =item B<-binary> | |
250 | ||
c4de074e | 251 | Normally the input message is converted to "canonical" format which is |
3fc9635e DSH |
252 | effectively using CR and LF as end of line: as required by the S/MIME |
253 | specification. When this option is present no translation occurs. This | |
254 | is useful when handling binary data which may not be in MIME format. | |
e3775a33 | 255 | |
2197494d DSH |
256 | =item B<-crlfeol> |
257 | ||
c4de074e | 258 | Normally the output file uses a single B<LF> as end of line. When this |
2197494d DSH |
259 | option is present B<CRLF> is used instead. |
260 | ||
e3775a33 DSH |
261 | =item B<-nodetach> |
262 | ||
c4de074e | 263 | When signing a message use opaque signing: this form is more resistant |
e3775a33 DSH |
264 | to translation by mail relays but it cannot be read by mail agents that |
265 | do not support S/MIME. Without this option cleartext signing with | |
266 | the MIME type multipart/signed is used. | |
267 | ||
e8769719 | 268 | =item B<-certfile> I<file> |
e3775a33 | 269 | |
c4de074e | 270 | Allows additional certificates to be specified. When signing these will |
e3775a33 DSH |
271 | be included with the message. When verifying these will be searched for |
272 | the signers certificates. The certificates should be in PEM format. | |
273 | ||
e8769719 | 274 | =item B<-signer> I<file> |
e3775a33 | 275 | |
c4de074e | 276 | A signing certificate when signing or resigning a message, this option can be |
d884c5ba DSH |
277 | used multiple times if more than one signer is required. If a message is being |
278 | verified then the signers certificates will be written to this file if the | |
279 | verification was successful. | |
e3775a33 | 280 | |
e8769719 | 281 | =item B<-recip> I<file> |
e3775a33 | 282 | |
c4de074e | 283 | The recipients certificate when decrypting a message. This certificate |
e3775a33 DSH |
284 | must match one of the recipients of the message or an error occurs. |
285 | ||
e8769719 | 286 | =item B<-inkey> I<file_or_id> |
e3775a33 | 287 | |
c4de074e | 288 | The private key to use when signing or decrypting. This must match the |
e3775a33 DSH |
289 | corresponding certificate. If this option is not specified then the |
290 | private key must be included in the certificate file specified with | |
d884c5ba DSH |
291 | the B<-recip> or B<-signer> file. When signing this option can be used |
292 | multiple times to specify successive keys. | |
48b53522 RS |
293 | If no engine is used, the argument is taken as a file; if an engine is |
294 | specified, the argument is given to the engine as a key identifier. | |
e3775a33 | 295 | |
e8769719 | 296 | =item B<-passin> I<arg> |
84b65340 | 297 | |
c4de074e | 298 | The private key password source. For more information about the format of B<arg> |
e8769719 | 299 | see L<openssl(1)/Pass phrase options>. |
84b65340 | 300 | |
e8769719 | 301 | =item B<-rand> I<file...> |
d13e4eb0 | 302 | |
c4de074e | 303 | A file or files containing random data used to seed the random number |
3ee1eac2 | 304 | generator. |
35ed393e | 305 | Multiple files can be specified separated by an OS-dependent character. |
b87ef946 | 306 | The separator is B<;> for MS-Windows, B<,> for OpenVMS, and B<:> for |
a4cfd178 | 307 | all others. |
d13e4eb0 | 308 | |
e8769719 | 309 | =item B<-writerand> I<file> |
3ee1eac2 RS |
310 | |
311 | Writes random data to the specified I<file> upon exit. | |
312 | This can be used with a subsequent B<-rand> flag. | |
313 | ||
e3775a33 DSH |
314 | =item B<cert.pem...> |
315 | ||
c4de074e | 316 | One or more certificates of message recipients: used when encrypting |
1bc74519 | 317 | a message. |
e3775a33 DSH |
318 | |
319 | =item B<-to, -from, -subject> | |
320 | ||
c4de074e | 321 | The relevant mail headers. These are included outside the signed |
e3775a33 DSH |
322 | portion of a message so they may be included manually. If signing |
323 | then many S/MIME mail clients check the signers certificate's email | |
324 | address matches that specified in the From: address. | |
325 | ||
e42d84be | 326 | =item B<-attime>, B<-check_ss_sig>, B<-crl_check>, B<-crl_check_all>, |
d33def66 VD |
327 | B<-explicit_policy>, B<-extended_crl>, B<-ignore_critical>, B<-inhibit_any>, |
328 | B<-inhibit_map>, B<-no_alt_chains>, B<-partial_chain>, B<-policy>, | |
e42d84be | 329 | B<-policy_check>, B<-policy_print>, B<-purpose>, B<-suiteB_128>, |
d33def66 | 330 | B<-suiteB_128_only>, B<-suiteB_192>, B<-trusted_first>, B<-use_deltas>, |
fbb82a60 VD |
331 | B<-auth_level>, B<-verify_depth>, B<-verify_email>, B<-verify_hostname>, |
332 | B<-verify_ip>, B<-verify_name>, B<-x509_strict> | |
e5fa864f DSH |
333 | |
334 | Set various options of certificate chain verification. See | |
9b86974e | 335 | L<verify(1)> manual page for details. |
e5fa864f | 336 | |
e3775a33 DSH |
337 | =back |
338 | ||
339 | =head1 NOTES | |
340 | ||
341 | The MIME message must be sent without any blank lines between the | |
342 | headers and the output. Some mail programs will automatically add | |
343 | a blank line. Piping the mail directly to sendmail is one way to | |
344 | achieve the correct format. | |
345 | ||
3fc9635e | 346 | The supplied message to be signed or encrypted must include the |
60250017 | 347 | necessary MIME headers or many S/MIME clients won't display it |
3fc9635e DSH |
348 | properly (if at all). You can use the B<-text> option to automatically |
349 | add plain text headers. | |
350 | ||
e3775a33 DSH |
351 | A "signed and encrypted" message is one where a signed message is |
352 | then encrypted. This can be produced by encrypting an already signed | |
3fc9635e | 353 | message: see the examples section. |
e3775a33 DSH |
354 | |
355 | This version of the program only allows one signer per message but it | |
356 | will verify multiple signers on received messages. Some S/MIME clients | |
19d2bb57 | 357 | choke if a message contains multiple signers. It is possible to sign |
e3775a33 DSH |
358 | messages "in parallel" by signing an already signed message. |
359 | ||
3fc9635e DSH |
360 | The options B<-encrypt> and B<-decrypt> reflect common usage in S/MIME |
361 | clients. Strictly speaking these process PKCS#7 enveloped data: PKCS#7 | |
362 | encrypted data is used for other purposes. | |
363 | ||
d884c5ba DSH |
364 | The B<-resign> option uses an existing message digest when adding a new |
365 | signer. This means that attributes must be present in at least one existing | |
366 | signer using the same message digest or this operation will fail. | |
367 | ||
e4ef2e25 | 368 | The B<-stream> and B<-indef> options enable streaming I/O support. |
76b46e77 DSH |
369 | As a result the encoding is BER using indefinite length constructed encoding |
370 | and no longer DER. Streaming is supported for the B<-encrypt> operation and the | |
371 | B<-sign> operation if the content is not detached. | |
372 | ||
373 | Streaming is always used for the B<-sign> operation with detached data but | |
374 | since the content is no longer part of the PKCS#7 structure the encoding | |
375 | remains DER. | |
376 | ||
e3775a33 DSH |
377 | =head1 EXIT CODES |
378 | ||
379 | =over 4 | |
380 | ||
c8919dde | 381 | =item Z<>0 |
e3775a33 | 382 | |
c4de074e | 383 | The operation was completely successfully. |
e3775a33 | 384 | |
c8919dde | 385 | =item Z<>1 |
e3775a33 | 386 | |
c4de074e | 387 | An error occurred parsing the command options. |
e3775a33 | 388 | |
c8919dde | 389 | =item Z<>2 |
e3775a33 | 390 | |
c4de074e | 391 | One of the input files could not be read. |
e3775a33 | 392 | |
c8919dde | 393 | =item Z<>3 |
e3775a33 | 394 | |
c4de074e | 395 | An error occurred creating the PKCS#7 file or when reading the MIME |
e3775a33 DSH |
396 | message. |
397 | ||
c8919dde | 398 | =item Z<>4 |
e3775a33 | 399 | |
c4de074e | 400 | An error occurred decrypting or verifying the message. |
e3775a33 | 401 | |
c8919dde | 402 | =item Z<>5 |
e3775a33 | 403 | |
c4de074e | 404 | The message was verified correctly but an error occurred writing out |
e3775a33 DSH |
405 | the signers certificates. |
406 | ||
407 | =back | |
408 | ||
409 | =head1 EXAMPLES | |
410 | ||
3fc9635e DSH |
411 | Create a cleartext signed message: |
412 | ||
1675f6eb | 413 | openssl smime -sign -in message.txt -text -out mail.msg \ |
1bc74519 | 414 | -signer mycert.pem |
3fc9635e | 415 | |
0d638dc1 | 416 | Create an opaque signed message: |
3fc9635e | 417 | |
1675f6eb | 418 | openssl smime -sign -in message.txt -text -out mail.msg -nodetach \ |
1bc74519 | 419 | -signer mycert.pem |
3fc9635e DSH |
420 | |
421 | Create a signed message, include some additional certificates and | |
422 | read the private key from another file: | |
423 | ||
1675f6eb | 424 | openssl smime -sign -in in.txt -text -out mail.msg \ |
1bc74519 | 425 | -signer mycert.pem -inkey mykey.pem -certfile mycerts.pem |
3fc9635e | 426 | |
d884c5ba DSH |
427 | Create a signed message with two signers: |
428 | ||
429 | openssl smime -sign -in message.txt -text -out mail.msg \ | |
1bc74519 | 430 | -signer mycert.pem -signer othercert.pem |
d884c5ba | 431 | |
3fc9635e DSH |
432 | Send a signed message under Unix directly to sendmail, including headers: |
433 | ||
1675f6eb | 434 | openssl smime -sign -in in.txt -text -signer mycert.pem \ |
1bc74519 RS |
435 | -from steve@openssl.org -to someone@somewhere \ |
436 | -subject "Signed message" | sendmail someone@somewhere | |
3fc9635e DSH |
437 | |
438 | Verify a message and extract the signer's certificate if successful: | |
439 | ||
440 | openssl smime -verify -in mail.msg -signer user.pem -out signedtext.txt | |
441 | ||
442 | Send encrypted mail using triple DES: | |
443 | ||
1675f6eb | 444 | openssl smime -encrypt -in in.txt -from steve@openssl.org \ |
1bc74519 RS |
445 | -to someone@somewhere -subject "Encrypted message" \ |
446 | -des3 user.pem -out mail.msg | |
3fc9635e DSH |
447 | |
448 | Sign and encrypt mail: | |
449 | ||
1675f6eb | 450 | openssl smime -sign -in ml.txt -signer my.pem -text \ |
1bc74519 RS |
451 | | openssl smime -encrypt -out mail.msg \ |
452 | -from steve@openssl.org -to someone@somewhere \ | |
453 | -subject "Signed and Encrypted message" -des3 user.pem | |
3fc9635e | 454 | |
d884c5ba DSH |
455 | Note: the encryption command does not include the B<-text> option because the |
456 | message being encrypted already has MIME headers. | |
3fc9635e DSH |
457 | |
458 | Decrypt mail: | |
459 | ||
460 | openssl smime -decrypt -in mail.msg -recip mycert.pem -inkey key.pem | |
461 | ||
fd13f0ee DSH |
462 | The output from Netscape form signing is a PKCS#7 structure with the |
463 | detached signature format. You can use this program to verify the | |
464 | signature by line wrapping the base64 encoded structure and surrounding | |
465 | it with: | |
466 | ||
a8c12555 DSH |
467 | -----BEGIN PKCS7----- |
468 | -----END PKCS7----- | |
fd13f0ee | 469 | |
1bc74519 | 470 | and using the command: |
fd13f0ee DSH |
471 | |
472 | openssl smime -verify -inform PEM -in signature.pem -content content.txt | |
473 | ||
0d638dc1 | 474 | Alternatively you can base64 decode the signature and use: |
fd13f0ee DSH |
475 | |
476 | openssl smime -verify -inform DER -in signature.der -content content.txt | |
477 | ||
f3dea9a5 BM |
478 | Create an encrypted message using 128 bit Camellia: |
479 | ||
480 | openssl smime -encrypt -in plain.txt -camellia128 -out mail.msg cert.pem | |
481 | ||
d884c5ba DSH |
482 | Add a signer to an existing message: |
483 | ||
484 | openssl smime -resign -in mail.msg -signer newsign.pem -out mail2.msg | |
485 | ||
3fc9635e DSH |
486 | =head1 BUGS |
487 | ||
d884c5ba DSH |
488 | The MIME parser isn't very clever: it seems to handle most messages that I've |
489 | thrown at it but it may choke on others. | |
3fc9635e | 490 | |
d884c5ba DSH |
491 | The code currently will only write out the signer's certificate to a file: if |
492 | the signer has a separate encryption certificate this must be manually | |
493 | extracted. There should be some heuristic that determines the correct | |
494 | encryption certificate. | |
3fc9635e | 495 | |
d884c5ba DSH |
496 | Ideally a database should be maintained of a certificates for each email |
497 | address. | |
3fc9635e DSH |
498 | |
499 | The code doesn't currently take note of the permitted symmetric encryption | |
7e0de9e8 | 500 | algorithms as supplied in the SMIMECapabilities signed attribute. This means the |
3fc9635e DSH |
501 | user has to manually include the correct encryption algorithm. It should store |
502 | the list of permitted ciphers in a database and only use those. | |
503 | ||
504 | No revocation checking is done on the signer's certificate. | |
505 | ||
506 | The current code can only handle S/MIME v2 messages, the more complex S/MIME v3 | |
507 | structures may cause parsing errors. | |
e3775a33 | 508 | |
d884c5ba DSH |
509 | =head1 HISTORY |
510 | ||
511 | The use of multiple B<-signer> options and the B<-resign> command were first | |
fb552ac6 | 512 | added in OpenSSL 1.0.0 |
d884c5ba | 513 | |
fc5ecadd | 514 | The -no_alt_chains option was added in OpenSSL 1.1.0. |
d884c5ba | 515 | |
e2f92610 RS |
516 | =head1 COPYRIGHT |
517 | ||
b6b66573 | 518 | Copyright 2000-2019 The OpenSSL Project Authors. All Rights Reserved. |
e2f92610 | 519 | |
449040b4 | 520 | Licensed under the Apache License 2.0 (the "License"). You may not use |
e2f92610 RS |
521 | this file except in compliance with the License. You can obtain a copy |
522 | in the file LICENSE in the source distribution or at | |
523 | L<https://www.openssl.org/source/license.html>. | |
524 | ||
525 | =cut |