Lines Matching full:message

69 Print out a usage message.
73 Encrypt mail for the given recipient certificates. Input file is the message
82 encrypted mail message in MIME format for the input file. The decrypted mail
88 the message to be signed. The signed message in MIME format is written
93 Verify signed mail. Expects a signed mail message on input and outputs
98 Takes an input message and writes out a PEM encoded PKCS#7 structure.
102 Resign a message: take an existing message and one or more new signers.
106 The input message to be encrypted or signed or the MIME message to
111 The message text that has been decrypted or verified or the output MIME
112 format message that has been signed or verified.
157 message if encrypting or signing. If decrypting or verifying it strips
158 off text headers: if the decrypted or verified message is not of MIME
178 When verifying a message normally certificates (if any) included in
179 the message are searched for the signing certificate. With this option
185 Do not verify the signers certificate of a signed message.
190 use the certificates in the signed message as untrusted CAs.
194 Don't try to verify the signatures on the message.
198 When signing a message, the signer's certificate is normally included.
200 signed message, but the verifier must have a copy of the signers certificate
205 Normally, when a message is signed, a set of attributes are included which
211 When signing a message use opaque signing. This form is more resistant
218 When signing a message, do not include the B<SMIMECapabilities> attribute.
222 Normally the input message is converted to "canonical" format which is
235 be included with the message. When verifying these will be searched for
241 A signing certificate when signing or resigning a message, this option can be
242 used multiple times if more than one signer is required. If a message is being
248 The recipients certificate when decrypting a message. This certificate
249 must match one of the recipients of the message or an error occurs.
267 portion of a message so they may be included manually. If signing
287 One or more certificates of message recipients, used when encrypting
288 a message.
294 The MIME message must be sent without any blank lines between the
299 The supplied message to be signed or encrypted must include the
304 A "signed and encrypted" message is one where a signed message is
306 message: see the examples section.
308 This version of the program only allows one signer per message but it
310 choke if a message contains multiple signers. It is possible to sign
311 messages "in parallel" by signing an already signed message.
317 The B<-resign> option uses an existing message digest when adding a new
319 signer using the same message digest or this operation will fail.
349 message.
353 An error occurred decrypting or verifying the message.
357 The message was verified correctly but an error occurred writing out
364 Create a cleartext signed message:
366  openssl smime -sign -in message.txt -text -out mail.msg \
369 Create an opaque signed message:
371  openssl smime -sign -in message.txt -text -out mail.msg -nodetach \
374 Create a signed message, include some additional certificates and
380 Create a signed message with two signers:
382  openssl smime -sign -in message.txt -text -out mail.msg \
385 Send a signed message under Unix directly to sendmail, including headers:
389         -subject "Signed message" | sendmail someone@somewhere
391 Verify a message and extract the signer's certificate if successful:
398         -to someone@somewhere -subject "Encrypted message" \
406         -subject "Signed and Encrypted message" -des3 user.pem
409 message being encrypted already has MIME headers.
431 Create an encrypted message using 128 bit Camellia:
435 Add a signer to an existing message: