Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This structure is used with the CryptMsgGetParamfunction to get information on a key transport, key agreement, or mail list envelope message recipient. This structure is returned in pvDatawhen CryptMsgGetParamis called with dwParamTypeset to CMSG_CMS_RECIPIENT_INFO_PARAM.

Syntax 

typedef struct _CMSG_CMS_RECIPIENT_INFO {
  DWORD 
dwRecipientChoice;
  union {
	PCMSG_KEY_TRANS_RECIPIENT_INFO 
pKeyTrans;
	PCMSG_KEY_AGREE_RECIPIENT_INFO 
pKeyAgree;
	PCMSG_MAIL_LIST_RECIPIENT_INFO 
pMailList;
  };
} CMSG_CMS_RECIPIENT_INFO, *PCMSG_CMS_RECIPIENT_INFO;

Members

dwRecipientChoice

Indicates the member of the union to be used.

Possible values are:

Value Description

CMSG_KEY_TRANS_RECIPIENT

pKeyTrans

CMSG_KEY_AGREE_RECIPIENT

pKeyAgree

CMSG_MAIL_LIST_RECIPIENT

pMailList
pKeyTrans

Pointer to a CMSG_KEY_TRANS_RECIPIENT_INFOstructure identifying a key transport recipient. Used for RSA recipients.

pKeyAgree

Pointer to a CMSG_KEY_AGREE_RECIPIENT_INFO structure identifying a key agreement recipient. Used for Diffie Hellman recipients

pMailList

Pointer to a CMSG_MAIL_LIST_RECIPIENT_INFOstructure identifying a recipient using a previously distributed key encryption key for the encryption/decryption of the envelopes message's symmetric key.

Requirements

Header wincrypt.h
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.