Writes encrypted data to a protected surface.
HRESULT DecryptionBlt( IDirect3DSurface9 *pSrcSurface, IDirect3DSurface9 *pDstSurface, UINT SrcSurfaceSize, D3DENCRYPTED_BLOCK_INFO *pEncryptedBlockInfo, VOID *pContentKey, VOID *pIV );
A pointer to the surface that contains the source data.
A pointer to the protected surface where the encrypted data is written.
The size of the surface memory that pSrcSurface points to, in bytes. The size must be aligned to the value of BlockAlignmentSize in the driver capabilities structure; see Remarks.
A pointer to a D3DENCRYPTED_BLOCK_INFO structure, or NULL.
If the driver supports partially encrypted buffers, pEncryptedBlockInfo indicates which portions of the buffer are encrypted. If the entire surface is encrypted, set this parameter to NULL.
To check whether the driver supports partially encrypted buffers, call IDirect3DDevice9Video::GetContentProtectionCaps and check for the D3DCPCAPS_PARTIALDECRYPTION capabilities flag. If the driver does not support partially encrypted buffers, set this parameter to NULL.
A pointer to a buffer that contains a content encryption key, or NULL. To query whether the driver supports the use of content keys, call IDirect3DDevice9Video::GetContentProtectionCaps and check for the D3DCPCAPS_CONTENTKEY capabilities flag.
If the driver supports content keys, use the content key to encrypt the surface. Encrypt the content key using the session key, and place the resulting cipher text in pContentKey. If the driver does not support content keys, use the session key to encrypt the surface and set pContentKey to NULL.
A pointer to a buffer that contains the initialization vector (IV).
If the encryption type is D3DCRYPTOTYPE_AES128_CTR, the buffer is a D3DAES_CTR_IV structure. The caller allocates the structure and generates the IV. When you generate the first IV, initialize the structure to a random number. For each subsequent IV, simply increment the IV member of the structure, ensuring that the value always increases. This procedure enables the driver 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.
If this method succeeds, it returns S_OK. Otherwise, it returns an HRESULT error code.
Not all hardware or drivers support this functionality for all cryptographic types.
The source surface must be a system memory surface created with the proper alignment restrictions. The buffer must be large enough to accommodate the pitch and height of the protected surface, plus padding to accommodate the starting alignment restrictions and block transfer size.
Specifically, you should allocate the source surface as follows:
- Call IDirect3DCryptoSession9::GetSurfacePitch to get the stride of the protected surface.
- Call the IDirect3DDevice9Video::GetContentProtectionCaps method to get the value of the BufferAlignmentStart and BlockAlignmentSize members in the D3DCONTENTPROTECTIONCAPS structure.
- Calculate the minimum size of the surface memory as SysMemSize = protected surface stride × protected surface height.
- Add padding to accommodate the values of BufferAlignmentStart and BlockAlignmentSize.
- Allocate a buffer in system memory, with size equal to SysMemSize (including padding).
- If the address of the system memory buffer is not aligned to the value of BufferAlignmentStart, calculate a memory-aligned pointer that is an offset from the start of the buffer.
- Call IDirect3DDevice9Ex::CreateOffscreenPlainSurfaceEx to create the source surface. Pass the memory-aligned pointer as the shared-resource handle (pSharedHandle).
If you lock the surface, the stride reported in the D3DLOCKED_RECT structure might not match the stride of the protected surface. When you interpret the data, however, always use the stride of the protected surface.
This method does not support writing to subrectangles of the surface.
Minimum supported client
|Windows 7 [desktop apps only]|
Minimum supported server
|Windows Server 2008 R2 [desktop apps only]|