1 .\" $NetBSD: CMS_decrypt.3,v 1.14 2015/06/12 17:01:13 christos Exp $
3 .\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28)
6 .\" ========================================================================
7 .de Sp \" Vertical space (when we can't use .PP)
11 .de Vb \" Begin verbatim text
16 .de Ve \" End verbatim text
20 .\" Set up some character translations and predefined strings. \*(-- will
21 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
22 .\" double quote, and \*(R" will give a right double quote. \*(C+ will
23 .\" give a nicer C++. Capital omega is used to do unbreakable dashes and
24 .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
25 .\" nothing in troff, for use with C<>.
27 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
31 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
32 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
47 .\" Escape single quotes in literal strings from groff's Unicode transform.
51 .\" If the F register is turned on, we'll generate index entries on stderr for
52 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
53 .\" entries marked with X<> in POD. Of course, you'll have to process the
54 .\" output yourself in some meaningful fashion.
56 .\" Avoid warning from groff about undefined register 'F'.
60 .if \n(.g .if rF .nr rF 1
61 .if (\n(rF:(\n(.g==0)) \{
64 . tm Index:\\$1\t\\n%\t"\\$2"
74 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
75 .\" Fear. Run. Save yourself. No user-serviceable parts.
76 . \" fudge factors for nroff and troff
85 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
91 . \" simple accents for nroff and troff
101 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
102 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
103 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
104 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
105 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
106 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
108 . \" troff and (daisy-wheel) nroff accents
109 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
110 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
111 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
112 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
113 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
114 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
115 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
116 .ds ae a\h'-(\w'a'u*4/10)'e
117 .ds Ae A\h'-(\w'A'u*4/10)'E
118 . \" corrections for vroff
119 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
120 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
121 . \" for low resolution devices (crt and lpr)
122 .if \n(.H>23 .if \n(.V>19 \
135 .\" ========================================================================
137 .IX Title "CMS_decrypt 3"
138 .TH CMS_decrypt 3 "2014-06-05" "1.0.1n" "OpenSSL"
139 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
140 .\" way too many mistakes in technical documents.
145 \& CMS_decrypt \- decrypt content from a CMS envelopedData structure
150 .IX Header "SYNOPSIS"
152 \& #include <openssl/cms.h>
154 \& int CMS_decrypt(CMS_ContentInfo *cms, EVP_PKEY *pkey, X509 *cert, BIO *dcont, BIO *out, unsigned int flags);
157 .IX Header "DESCRIPTION"
158 \&\fICMS_decrypt()\fR extracts and decrypts the content from a \s-1CMS\s0 EnvelopedData
159 structure. \fBpkey\fR is the private key of the recipient, \fBcert\fR is the
160 recipient's certificate, \fBout\fR is a \s-1BIO\s0 to write the content to and
161 \&\fBflags\fR is an optional set of flags.
163 The \fBdcont\fR parameter is used in the rare case where the encrypted content
164 is detached. It will normally be set to \s-1NULL.\s0
167 \&\fIOpenSSL_add_all_algorithms()\fR (or equivalent) should be called before using this
168 function or errors about unknown algorithms will occur.
170 Although the recipients certificate is not needed to decrypt the data it is
171 needed to locate the appropriate (of possible several) recipients in the \s-1CMS\s0
174 If \fBcert\fR is set to \s-1NULL\s0 all possible recipients are tried. This case however
175 is problematic. To thwart the \s-1MMA\s0 attack (Bleichenbacher's attack on
176 \&\s-1PKCS\s0 #1 v1.5 \s-1RSA\s0 padding) all recipients are tried whether they succeed or
177 not. If no recipient succeeds then a random symmetric key is used to decrypt
178 the content: this will typically output garbage and may (but is not guaranteed
179 to) ultimately return a padding error only. If \fICMS_decrypt()\fR just returned an
180 error when all recipient encrypted keys failed to decrypt an attacker could
181 use this in a timing attack. If the special flag \fB\s-1CMS_DEBUG_DECRYPT\s0\fR is set
182 then the above behaviour is modified and an error \fBis\fR returned if no
183 recipient encrypted key can be decrypted \fBwithout\fR generating a random
184 content encryption key. Applications should use this flag with
185 \&\fBextreme caution\fR especially in automated gateways as it can leave them
188 It is possible to determine the correct recipient key by other means (for
189 example looking them up in a database) and setting them in the \s-1CMS\s0 structure
190 in advance using the \s-1CMS\s0 utility functions such as \fICMS_set1_pkey()\fR. In this
191 case both \fBcert\fR and \fBpkey\fR should be set to \s-1NULL.\s0
193 To process KEKRecipientInfo types \fICMS_set1_key()\fR or \fICMS_RecipientInfo_set0_key()\fR
194 and \fICMS_ReceipientInfo_decrypt()\fR should be called before \fICMS_decrypt()\fR and
195 \&\fBcert\fR and \fBpkey\fR set to \s-1NULL.\s0
197 The following flags can be passed in the \fBflags\fR parameter.
199 If the \fB\s-1CMS_TEXT\s0\fR flag is set \s-1MIME\s0 headers for type \fBtext/plain\fR are deleted
200 from the content. If the content is not of type \fBtext/plain\fR then an error is
203 .IX Header "RETURN VALUES"
204 \&\fICMS_decrypt()\fR returns either 1 for success or 0 for failure.
205 The error can be obtained from \fIERR_get_error\fR\|(3)
208 The lack of single pass processing and the need to hold all data in memory as
209 mentioned in \fICMS_verify()\fR also applies to \fICMS_decrypt()\fR.
211 .IX Header "SEE ALSO"
212 \&\fIERR_get_error\fR\|(3), \fICMS_encrypt\fR\|(3)
215 \&\fICMS_decrypt()\fR was added to OpenSSL 0.9.8