Blt
Expandir Minimizar

CryptoSessionKeyExchange routine

The CryptoSessionKeyExchange function negotiates a session key.

Syntax


PFND3DDDI_CRYPTOSESSIONKEYEXCHANGE CryptoSessionKeyExchange;

__checkReturn HRESULT APIENTRY CryptoSessionKeyExchange(
  _In_     HANDLE hDevice,
  _Inout_  D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE *pData
)
{ ... }

Parameters

hDevice [in]

A handle to the display device (graphics context).

pData [in, out]

A pointer to a D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE structure that describes a session key that is used for encryption.

Return value

CryptoSessionKeyExchange returns one of the following values:

Return codeDescription
S_OK

The session key is successfully exchanged.

E_OUTOFMEMORY

CryptoSessionKeyExchange could not allocate the required memory for it to complete.

 

Remarks

The driver should only support a single key exchange mechanism for each encryption type. Microsoft has standardized the key exchange type D3DKEYEXCHANGE_RSAES_OAEP. However, hardware vendors can use proprietary key exchange mechanisms.

For D3DKEYEXCHANGE_RSAES_OAEP, the pData member of the D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE structure points to a buffer that contains the session key that an application previously RSAES-OAEP-encrypted with the public key from the driver's crypto session certificate. The actual size of the buffer is 256 bytes. This exchange is identical to how the Output Protection Manager (OPM) key exchange works, except the OPM buffer contains additional data besides the session key. The same certificate that is used for OPM key exchange can be used for the D3DKEYEXCHANGE_RSAES_OAEP key exchange.

Requirements

Version

CryptoSessionKeyExchange is supported beginning with the Windows 7 operating system.

Header

D3dumddi.h (include D3dumddi.h)

See also

D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE

 

 

Send comments about this topic to Microsoft

Mostrar:
© 2014 Microsoft