Lines Matching full:structure

105 structures associated with a CMS EnvelopedData structure.
107 \&\fBCMS_RecipientInfo_type()\fR returns the type of CMS_RecipientInfo structure \fBri\fR.
112 identifier associated with a specific CMS_RecipientInfo structure \fBri\fR, which
117 CMS_RecipientInfo structure \fBri\fR, which must be of type CMS_RECIPINFO_TRANS.
121 the CMS_RecipientInfo structure \fBri\fR, which must be of type
125 and peer certificate \fBpeer\fR with the CMS_RecipientInfo structure \fBri\fR, which
129 CMS_RecipientInfo structure \fBri\fR, which must be of type CMS_RECIPINFO_AGREE.
132 CMS_RecipientInfo structure \fBri\fR which must be of type CMS_RECIPINFO_KEK.  Any
142 parameters against the \fBkeyIdentifier\fR CMS_RecipientInfo structure \fBri\fR,
147 \&\fBkeylen\fR with the CMS_RecipientInfo structure \fBri\fR, which must be of type
150 \&\fBCMS_RecipientInfo_decrypt()\fR attempts to decrypt CMS_RecipientInfo structure
151 \&\fBri\fR in structure \fBcms\fR. A key must have been associated with the structure
154 \&\fBCMS_RecipientInfo_encrypt()\fR attempts to encrypt CMS_RecipientInfo structure
155 \&\fBri\fR in structure \fBcms\fR. A key must have been associated with the structure
166 \&\fBCMS_RecipientInfo_type()\fR. Depending on the type the CMS_RecipientInfo structure
169 any appropriate means it can then associated with the structure and
174 existing enveloped data structure. Typically an application will first decrypt
175 an appropriate CMS_RecipientInfo structure to make the content encrypt key