Reference Guide

Chapter 1: Changes Between MES 4.0.1 and 4.1.n.n 9
RSA BSAFE Micro Edition Suite 4.4 Migration Guide
Cryptographic Message Syntax
MES 4.0.2 included a redeveloped implementation of the Cryptographic Message
Syntax (CMS). This section describes the functionality available if implementing
CMS into your applications.
CMS Object Model
The MES CMS implementation uses the following objects to represent the features
described in the syntax (RFC 5652):
• The cryptographic message context (
R_CM_CTX) is the base object from which all
other cryptographic message objects are created.
• Cryptographic message objects (
R_CM), created from the cryptographic message
context, are used to represent the following supported cryptographic message
content types:
–
Data
–
SignedData
–
EnvelopedData
–
AuthenticatedEnvelopedData.
• Cryptographic message information objects (
R_CM_INF), also created from the
cryptographic message context, are used to create to represent the following
information types:
–
SignerInfo to represent signer information for SignedData content types.
– RecipientInfo to hold recipient and key management information for
EnvelopedData content types.
RecipientInfo Information Objects
For EnvelopedData content types, MES provides the following RecipientInfo
information objects to support different key management techniques:
•
KeyTransRecipientInfo information object, for transferring the content
encryption key to recipients using asymmetric key encryption.
•
KeyAgreeRecipientInfo information object, for transferring the content
encryption key to recipients using a key agreement algorithm.
•
KEKRecipientInfo information object, for transferring the content encryption
key to recipients using a previously distributed key encryption key (KEK).
For more information about the MES CMS implementation and how to process
cryptographic messages, see the RSA BSAFE Micro Edition Suite Developers Guide.