Lines Matching full:structure

181 structures associated with a \s-1CMS\s0 EnvelopedData structure.
183 \&\fBCMS_RecipientInfo_type()\fR returns the type of CMS_RecipientInfo structure \fBri\fR.
188 identifier associated with a specific CMS_RecipientInfo structure \fBri\fR, which
193 CMS_RecipientInfo structure \fBri\fR, which must be of type \s-1CMS_RECIPINFO_TRANS.\s0
197 the CMS_RecipientInfo structure \fBri\fR, which must be of type
201 and peer certificate \fBpeer\fR with the CMS_RecipientInfo structure \fBri\fR, which
205 CMS_RecipientInfo structure \fBri\fR, which must be of type \s-1CMS_RECIPINFO_AGREE.\s0
208 CMS_RecipientInfo structure \fBri\fR which must be of type \s-1CMS_RECIPINFO_KEK.\s0  Any
218 parameters against the \fBkeyIdentifier\fR CMS_RecipientInfo structure \fBri\fR,
223 \&\fBkeylen\fR with the CMS_RecipientInfo structure \fBri\fR, which must be of type
226 \&\fBCMS_RecipientInfo_decrypt()\fR attempts to decrypt CMS_RecipientInfo structure
227 \&\fBri\fR in structure \fBcms\fR. A key must have been associated with the structure
230 \&\fBCMS_RecipientInfo_encrypt()\fR attempts to encrypt CMS_RecipientInfo structure
231 \&\fBri\fR in structure \fBcms\fR. A key must have been associated with the structure
242 \&\fBCMS_RecipientInfo_type()\fR. Depending on the type the CMS_RecipientInfo structure
245 any appropriate means it can then associated with the structure and
250 existing enveloped data structure. Typically an application will first decrypt
251 an appropriate CMS_RecipientInfo structure to make the content encrypt key