// d3d10umddi.h
PFND3D11_1DDI_ENCRYPTIONBLT Pfnd3d111DdiEncryptionblt;
VOID Pfnd3d111DdiEncryptionblt(
D3D10DDI_HDEVICE hDevice,
D3D11_1DDI_HCRYPTOSESSION hCryptoSession,
D3D10DDI_HRESOURCE hSrcResource,
D3D10DDI_HRESOURCE hDstResource,
UINT IVSize,
const VOID *pIV
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
Reads encrypted data from a protected surface.
hDeviceA handle to the display device (graphics context).
hCryptoSessionA handle to the driver's private data for the cryptographic session. This handle was created by the Direct3D runtime and passed to the driver in the call to the CreateCryptoSession function.
hSrcResourceA handle to the resource that contains the source data.
hDstResourceA pointer to the resource where the encrypted data is to be written.
IVSizeThe size, in bytes, of the initialization vector (IV).
pIVA pointer to a block of memory that contains the initialization vector that is required to encrypt the bitblt data. For more information, see the Remarks section.
Note
If pIV is NULL, the graphics adapter does not require a separate initialization vector to encrypt the data. That is, the session key is used to encrypt the data.
This function has the following limitations:
For 128-bit AES-CTR encryption, the pIV parameter points to a D3D11_1DDI_AES_CTR_IV structure that is allocated by the application. However, the actual contents of this structure are filled in by the driver or graphics adapter. When the first IV is generated, the driver or adapter initializes the IV member of this structure to a random number. For each subsequent IV, the caller increments the IV member, ensuring that the value always increases. This procedure enables the application to validate that the same IV is never used more than once with the same key pair.
For other encryption types, a different structure might be used, or the encryption might not use an IV.
Note This function does not honor a Direct3D version 11 predicate that may have been set.