PFND3DDDI_CRYPTOSESSIONKEYEXCHANGE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3dumddi.h
PFND3DDDI_CRYPTOSESSIONKEYEXCHANGE Pfnd3dddiCryptosessionkeyexchange;
HRESULT Pfnd3dddiCryptosessionkeyexchange(
HANDLE hDevice,
D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE *unnamedParam2
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The CryptoSessionKeyExchange function negotiates a session key.
hDeviceA handle to the display device (graphics context).
unnamedParam2pData [in, out]
A pointer to a D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE structure that describes a session key that is used for encryption.
CryptoSessionKeyExchange returns one of the following values:
| Return code | Description |
|---|---|
| S_OK | The session key is successfully exchanged. |
| E_OUTOFMEMORY | CryptoSessionKeyExchange could not allocate the required memory for it to complete. |
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.
D3DDDIARG_CRYPTOSESSIONKEYEXCHANGE