OpenSSL PKCS7_encrypt(3openssl)
NNNNAAAAMMMMEEEEPKCS7_encrypt - create a PKCS#7 envelopedData structure
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS#include
PKCS7 *PKCS7_encrypt(STACK_OF(X509) *certs, BIO *in, const EVP_CIPHER *cipher, int flags);
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNNPKCS7_encrypt() creates and returns a PKCS#7 envelopedData
structure. cccceeeerrrrttttssss is a list of recipient certificates. iiiinnnn is the content to be encrypted. cccciiiipppphhhheeeerrrr is the symmetric cipher to use. ffffllllaaaaggggssss is an optional set of flags. NNNNOOOOTTTTEEEESSSSOnly RSA keys are supported in PKCS#7 and envelopedData so
the recipient certificates supplied to this function must all contain RSA public keys, though they do not have to be signed using the RSA algorithm.EVP_des_ede3_cbc() (triple DES) is the algorithm of choice
for S/MIME use because most clients will support it. Some old "export grade" clients may only support weak encryption using 40 or 64 bit RC2. These can be used by
passing EVP_rc2_40_cbc() and EVP_rc2_64_cbc() respectively.
The algorithm passed in the cccciiiipppphhhheeeerrrr parameter must support ASN1 encoding of its parameters. Many browsers implement a "sign and encrypt" option which issimply an S/MIME envelopedData containing an S/MIME signed
message. This can be readily produced by storing the S/MIME signed message in a memory BIO and passing it to
PKCS7_encrypt().
The following flags can be passed in the ffffllllaaaaggggssss parameter.If the PPPPKKKKCCCCSSSS7777_TTTTEEEEXXXXTTTT flag is set MIME headers for type
tttteeeexxxxtttt////ppppllllaaaaiiiinnnn are prepended to the data. Normally the supplied content is translated into MIMEcanonical format (as required by the S/MIME specifications)
if PPPPKKKKCCCCSSSS7777_BBBBIIIINNNNAAAARRRRYYYY is set no translation occurs. This option
should be used if the supplied data is in binary formatotherwise the translation will corrupt it. If PPPPKKKKCCCCSSSS7777_BBBBIIIINNNNAAAARRRRYYYY
is set then PPPPKKKKCCCCSSSS7777_TTTTEEEEXXXXTTTT is ignored.
RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEESSSSPKCS7_encrypt() returns either a valid PKCS7 structure or
NULL if an error occurred. The error can be obtained from27/Mar/2010 Last change: 0.9.8o 1
OpenSSL PKCS7_encrypt(3openssl)
ERR_get_error(3).
BBBBUUUUGGGGSSSS The lack of single pass processing and need to hold all datain memory as mentioned in PKCS7_sign() also applies to
PKCS7_verify().
SSSSEEEEEEEE AAAALLLLSSSSOOOOERR_get_error(3), PKCS7_decrypt(3)
HHHHIIIISSSSTTTTOOOORRRRYYYYPKCS7_decrypt() was added to OpenSSL 0.9.5
27/Mar/2010 Last change: 0.9.8o 2