PKCS7_encrypt.pod 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  1. =pod
  2. =head1 NAME
  3. PKCS7_encrypt_ex, PKCS7_encrypt
  4. - create a PKCS#7 envelopedData structure
  5. =head1 SYNOPSIS
  6. #include <openssl/pkcs7.h>
  7. PKCS7 *PKCS7_encrypt_ex(STACK_OF(X509) *certs, BIO *in,
  8. const EVP_CIPHER *cipher, int flags,
  9. OSSL_LIB_CTX *libctx, const char *propq);
  10. PKCS7 *PKCS7_encrypt(STACK_OF(X509) *certs, BIO *in, const EVP_CIPHER *cipher,
  11. int flags);
  12. =head1 DESCRIPTION
  13. PKCS7_encrypt_ex() creates and returns a PKCS#7 envelopedData structure.
  14. I<certs> is a list of recipient certificates. I<in> is the content to be
  15. encrypted. I<cipher> is the symmetric cipher to use. I<flags> is an optional set
  16. of flags. The library context I<libctx> and the property query I<propq> are used
  17. when retrieving algorithms from providers.
  18. Only RSA keys are supported in PKCS#7 and envelopedData so the recipient
  19. certificates supplied to this function must all contain RSA public keys, though
  20. they do not have to be signed using the RSA algorithm.
  21. EVP_des_ede3_cbc() (triple DES) is the algorithm of choice for S/MIME use
  22. because most clients will support it.
  23. Some old "export grade" clients may only support weak encryption using 40 or 64
  24. bit RC2. These can be used by passing EVP_rc2_40_cbc() and EVP_rc2_64_cbc()
  25. respectively.
  26. The algorithm passed in the B<cipher> parameter must support ASN1 encoding of
  27. its parameters.
  28. Many browsers implement a "sign and encrypt" option which is simply an S/MIME
  29. envelopedData containing an S/MIME signed message. This can be readily produced
  30. by storing the S/MIME signed message in a memory BIO and passing it to
  31. PKCS7_encrypt().
  32. The following flags can be passed in the B<flags> parameter.
  33. If the B<PKCS7_TEXT> flag is set MIME headers for type B<text/plain> are
  34. prepended to the data.
  35. Normally the supplied content is translated into MIME canonical format (as
  36. required by the S/MIME specifications) if B<PKCS7_BINARY> is set no translation
  37. occurs. This option should be used if the supplied data is in binary format
  38. otherwise the translation will corrupt it. If B<PKCS7_BINARY> is set then
  39. B<PKCS7_TEXT> is ignored.
  40. If the B<PKCS7_STREAM> flag is set a partial B<PKCS7> structure is output
  41. suitable for streaming I/O: no data is read from the BIO B<in>.
  42. If the flag B<PKCS7_STREAM> is set the returned B<PKCS7> structure is B<not>
  43. complete and outputting its contents via a function that does not
  44. properly finalize the B<PKCS7> structure will give unpredictable
  45. results.
  46. Several functions including SMIME_write_PKCS7(), i2d_PKCS7_bio_stream(),
  47. PEM_write_bio_PKCS7_stream() finalize the structure. Alternatively finalization
  48. can be performed by obtaining the streaming ASN1 B<BIO> directly using
  49. BIO_new_PKCS7().
  50. PKCS7_encrypt() is similar to PKCS7_encrypt_ex() but uses default
  51. values of NULL for the library context I<libctx> and the property query I<propq>.
  52. =head1 RETURN VALUES
  53. PKCS7_encrypt_ex() and PKCS7_encrypt() return either a PKCS7 structure
  54. or NULL if an error occurred. The error can be obtained from ERR_get_error(3).
  55. =head1 SEE ALSO
  56. L<ERR_get_error(3)>, L<PKCS7_decrypt(3)>
  57. =head1 HISTORY
  58. The function PKCS7_encrypt_ex() was added in OpenSSL 3.0.
  59. The B<PKCS7_STREAM> flag was added in OpenSSL 1.0.0.
  60. =head1 COPYRIGHT
  61. Copyright 2002-2020 The OpenSSL Project Authors. All Rights Reserved.
  62. Licensed under the Apache License 2.0 (the "License"). You may not use
  63. this file except in compliance with the License. You can obtain a copy
  64. in the file LICENSE in the source distribution or at
  65. L<https://www.openssl.org/source/license.html>.
  66. =cut