CMS_decrypt.pod 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. =pod
  2. =head1 NAME
  3. CMS_decrypt - decrypt content from a CMS envelopedData structure
  4. =head1 SYNOPSIS
  5. #include <openssl/cms.h>
  6. int CMS_decrypt(CMS_ContentInfo *cms, EVP_PKEY *pkey, X509 *cert, BIO *dcont, BIO *out, unsigned int flags);
  7. =head1 DESCRIPTION
  8. CMS_decrypt() extracts and decrypts the content from a CMS EnvelopedData
  9. structure. B<pkey> is the private key of the recipient, B<cert> is the
  10. recipient's certificate, B<out> is a BIO to write the content to and
  11. B<flags> is an optional set of flags.
  12. The B<dcont> parameter is used in the rare case where the encrypted content
  13. is detached. It will normally be set to NULL.
  14. =head1 NOTES
  15. Although the recipients certificate is not needed to decrypt the data it is
  16. needed to locate the appropriate (of possible several) recipients in the CMS
  17. structure.
  18. If B<cert> is set to NULL all possible recipients are tried. This case however
  19. is problematic. To thwart the MMA attack (Bleichenbacher's attack on
  20. PKCS #1 v1.5 RSA padding) all recipients are tried whether they succeed or
  21. not. If no recipient succeeds then a random symmetric key is used to decrypt
  22. the content: this will typically output garbage and may (but is not guaranteed
  23. to) ultimately return a padding error only. If CMS_decrypt() just returned an
  24. error when all recipient encrypted keys failed to decrypt an attacker could
  25. use this in a timing attack. If the special flag B<CMS_DEBUG_DECRYPT> is set
  26. then the above behaviour is modified and an error B<is> returned if no
  27. recipient encrypted key can be decrypted B<without> generating a random
  28. content encryption key. Applications should use this flag with
  29. B<extreme caution> especially in automated gateways as it can leave them
  30. open to attack.
  31. It is possible to determine the correct recipient key by other means (for
  32. example looking them up in a database) and setting them in the CMS structure
  33. in advance using the CMS utility functions such as CMS_set1_pkey(). In this
  34. case both B<cert> and B<pkey> should be set to NULL.
  35. To process KEKRecipientInfo types CMS_set1_key() or CMS_RecipientInfo_set0_key()
  36. and CMS_ReceipientInfo_decrypt() should be called before CMS_decrypt() and
  37. B<cert> and B<pkey> set to NULL.
  38. The following flags can be passed in the B<flags> parameter.
  39. If the B<CMS_TEXT> flag is set MIME headers for type B<text/plain> are deleted
  40. from the content. If the content is not of type B<text/plain> then an error is
  41. returned.
  42. =head1 RETURN VALUES
  43. CMS_decrypt() returns either 1 for success or 0 for failure.
  44. The error can be obtained from ERR_get_error(3)
  45. =head1 BUGS
  46. The lack of single pass processing and the need to hold all data in memory as
  47. mentioned in CMS_verify() also applies to CMS_decrypt().
  48. =head1 SEE ALSO
  49. L<ERR_get_error(3)>, L<CMS_encrypt(3)>
  50. =head1 COPYRIGHT
  51. Copyright 2008-2016 The OpenSSL Project Authors. All Rights Reserved.
  52. Licensed under the OpenSSL license (the "License"). You may not use
  53. this file except in compliance with the License. You can obtain a copy
  54. in the file LICENSE in the source distribution or at
  55. L<https://www.openssl.org/source/license.html>.
  56. =cut