Lines Matching refs:message
71 Print out a usage message.
75 Encrypt mail for the given recipient certificates. Input file is the message
84 encrypted mail message in MIME format for the input file. The decrypted mail
90 the message to be signed. The signed message in MIME format is written
95 Resign a message: take an existing message and one or more new signers.
99 Verify signed mail. Expects a signed mail message on input and outputs
104 Takes an input message and writes out a PEM encoded PKCS#7 structure.
108 The input message to be encrypted or signed or the MIME message to
113 The message text that has been decrypted or verified or the output MIME
114 format message that has been signed or verified.
159 message if encrypting or signing. If decrypting or verifying it strips
160 off text headers: if the decrypted or verified message is not of MIME
180 When verifying a message normally certificates (if any) included in
181 the message are searched for the signing certificate. With this option
187 Do not verify the signers certificate of a signed message.
192 use the certificates in the signed message as untrusted CAs.
196 Don't try to verify the signatures on the message.
200 When signing a message, the signer's certificate is normally included.
202 signed message, but the verifier must have a copy of the signers certificate
207 Normally, when a message is signed, a set of attributes are included which
213 When signing a message use opaque signing. This form is more resistant
220 When signing a message, do not include the B<SMIMECapabilities> attribute.
224 Normally the input message is converted to "canonical" format which is
237 be included with the message. When verifying, these will be searched for
244 A signing certificate when signing or resigning a message, this option can be
245 used multiple times if more than one signer is required. If a message is being
251 The recipients certificate when decrypting a message. This certificate
252 must match one of the recipients of the message or an error occurs.
270 portion of a message so they may be included manually. If signing
290 One or more certificates of message recipients, used when encrypting
291 a message.
297 The MIME message must be sent without any blank lines between the
302 The supplied message to be signed or encrypted must include the
307 A "signed and encrypted" message is one where a signed message is
309 message: see the examples section.
311 This version of the program only allows one signer per message but it
313 choke if a message contains multiple signers. It is possible to sign
314 messages "in parallel" by signing an already signed message.
320 The B<-resign> option uses an existing message digest when adding a new
322 signer using the same message digest or this operation will fail.
352 message.
356 An error occurred decrypting or verifying the message.
360 The message was verified correctly but an error occurred writing out
367 Create a cleartext signed message:
369 openssl smime -sign -in message.txt -text -out mail.msg \
372 Create an opaque signed message:
374 openssl smime -sign -in message.txt -text -out mail.msg -nodetach \
377 Create a signed message, include some additional certificates and
383 Create a signed message with two signers:
385 openssl smime -sign -in message.txt -text -out mail.msg \
388 Send a signed message under Unix directly to sendmail, including headers:
392 -subject "Signed message" | sendmail someone@somewhere
394 Verify a message and extract the signer's certificate if successful:
401 -to someone@somewhere -subject "Encrypted message" \
409 -subject "Signed and Encrypted message" -des3 user.pem
412 message being encrypted already has MIME headers.
434 Create an encrypted message using 128 bit Camellia:
438 Add a signer to an existing message:
