Lines Matching full:structure

108 structures associated with a CMS EnvelopedData structure.
110 \&\fBCMS_RecipientInfo_type()\fR returns the type of CMS_RecipientInfo structure \fBri\fR.
115 identifier associated with a specific CMS_RecipientInfo structure \fBri\fR, which
120 CMS_RecipientInfo structure \fBri\fR, which must be of type CMS_RECIPINFO_TRANS.
124 the CMS_RecipientInfo structure \fBri\fR, which must be of type
128 and peer certificate \fBpeer\fR with the CMS_RecipientInfo structure \fBri\fR, which
132 CMS_RecipientInfo structure \fBri\fR, which must be of type CMS_RECIPINFO_AGREE.
135 CMS_RecipientInfo structure \fBri\fR which must be of type CMS_RECIPINFO_KEK.  Any
145 parameters against the \fBkeyIdentifier\fR CMS_RecipientInfo structure \fBri\fR,
150 \&\fBkeylen\fR with the CMS_RecipientInfo structure \fBri\fR, which must be of type
153 \&\fBCMS_RecipientInfo_decrypt()\fR attempts to decrypt CMS_RecipientInfo structure
154 \&\fBri\fR in structure \fBcms\fR. A key must have been associated with the structure
157 \&\fBCMS_RecipientInfo_encrypt()\fR attempts to encrypt CMS_RecipientInfo structure
158 \&\fBri\fR in structure \fBcms\fR. A key must have been associated with the structure
169 \&\fBCMS_RecipientInfo_type()\fR. Depending on the type the CMS_RecipientInfo structure
172 any appropriate means it can then associated with the structure and
177 existing enveloped data structure. Typically an application will first decrypt
178 an appropriate CMS_RecipientInfo structure to make the content encrypt key