5.26 Creating a CryptoAPI Key Object from Raw Key Data

5.26.1 Problem

You have a symmetric key from another API, such as OpenSSL, that you would like to use with CryptoAPI. Therefore, you must create a CryptoAPI key object with the key data.

5.26.2 Solution

The Microsoft CryptoAPI is designed to prevent unintentional disclosure of sensitive key information. To do this, key information is stored in opaque data objects by the Cryptographic Service Provider (CSP) used to create the key object. Key data is exportable from key objects, but the data must be encrypted with another key to prevent accidental disclosure of the raw key data.

5.26.3 Discussion

In Recipe 5.25, we created a convenience function, SpcGetCryptContext( ), for obtaining a handle to a CSP context object. This function uses the CRYPT_VERIFYCONTEXT flag with the underlying CryptAcquireContext( ) function, which serves to prevent the use of private keys with the obtained context object. To be able to import and export symmetric encryption keys, you need to obtain a handle to a CSP context object without that flag, and use that CSP context object for creating the keys you wish to use. We'll create a new function called SpcGetExportableContext( ) that will return a CSP context object suitable for creating, importing, and exporting symmetric encryption keys.

#include <windows.h> #include <wincrypt.h>     HCRYPTPROV SpcGetExportableContext(void) {   HCRYPTPROV hProvider;       if (!CryptAcquireContext(&hProvider, 0, MS_ENHANCED_PROV, PROV_RSA_FULL, 0)) {     if (GetLastError(  ) != NTE_BAD_KEYSET) return 0;     if (!CryptAcquireContext(&hProvider, 0, MS_ENHANCED_PROV, PROV_RSA_FULL,                              CRYPT_NEWKEYSET)) return 0;   }   return hProvider; }

SpcGetExportableContext( ) will obtain a handle to the Microsoft Enhanced Cryptographic Service Provider that allows for the use of private keys. Public key pairs are stored in containers by the underlying CSP. This function will use the default container, creating it if it doesn't already exist.

Every public key container can have a special public key pair known as an exchange key, which is the key that we'll use to encrypt the exported key data. The function CryptGetUserKey( ) is used to obtain the exchange key. If it doesn't exist, SpcImportKeyData( ), listed later in this section, will create a 1,024-bit exchange key, which will be stored as the exchange key in the public key container so future attempts to get the key will succeed. The special algorithm identifier AT_KEYEXCHANGE is used to reference the exchange key.

Symmetric keys are always imported via CryptImportKey( ) in "simple blob" format, specified by the SIMPLEBLOB constant passed to CryptImportKey( ). A simple blob is composed of a BLOBHEADER structure, followed by an ALG_ID for the algorithm used to encrypt the key data. The raw key data follows the BLOBHEADER and ALG_ID header information. To import the raw key data into a CryptoAPI key, a simple blob structure must be constructed and passed to CryptImportKey( ).

Finally, the raw key data must be encrypted using CryptEncrypt( ) and the exchange key. (The CryptEncrypt( ) function is described in more detail in Recipe 5.25.) The return from SpcImportKeyData( ) will be a handle to a CryptoAPI key object if the operation was performed successfully; otherwise, it will be 0. The CryptoAPI makes a copy of the key data internally in the key object it creates, so the key data passed into the function may be safely freed. The spc_memset( ) function from Recipe 13.2 is used here to destroy the unencrypted key data before returning.

HCRYPTKEY SpcImportKeyData(HCRYPTPROV hProvider, ALG_ID Algid, BYTE *pbKeyData,                            DWORD cbKeyData) {   BOOL       bResult = FALSE;   BYTE       *pbData = 0;   DWORD      cbData, cbHeaderLen, cbKeyLen, dwDataLen;   ALG_ID     *pAlgid;   HCRYPTKEY  hImpKey = 0, hKey;   BLOBHEADER *pBlob;       if (!CryptGetUserKey(hProvider, AT_KEYEXCHANGE, &hImpKey)) {     if (GetLastError(  ) != NTE_NO_KEY) goto done;     if (!CryptGenKey(hProvider, AT_KEYEXCHANGE, (1024 << 16), &hImpKey))       goto done;   }       cbData = cbKeyData;   cbHeaderLen = sizeof(BLOBHEADER) + sizeof(ALG_ID);   if (!CryptEncrypt(hImpKey, 0, TRUE, 0, 0, &cbData, cbData)) goto done;   if (!(pbData = (BYTE *)LocalAlloc(LMEM_FIXED, cbData + cbHeaderLen)))     goto done;   CopyMemory(pbData + cbHeaderLen, pbKeyData, cbKeyData);   cbKeyLen = cbKeyData;   if (!CryptEncrypt(hImpKey, 0, TRUE, 0, pbData + cbHeaderLen, &cbKeyLen, cbData))     goto done;       pBlob  = (BLOBHEADER *)pbData;   pAlgid = (ALG_ID *)(pbData + sizeof(BLOBHEADER));   pBlob->bType    = SIMPLEBLOB;   pBlob->bVersion = 2;   pBlob->reserved = 0;   pBlob->aiKeyAlg = Algid;   dwDataLen = sizeof(ALG_ID);   if (!CryptGetKeyParam(hImpKey, KP_ALGID, (BYTE *)pAlgid, &dwDataLen, 0))     goto done;       bResult = CryptImportKey(hProvider, pbData, cbData + cbHeaderLen, hImpKey, 0,                            &hKey);   if (bResult) spc_memset(pbKeyData, 0, cbKeyData);     done:   if (pbData) LocalFree(pbData);   CryptDestroyKey(hImpKey);   return (bResult ? hKey : 0); }

5.26.4 See Also

Recipe 5.25, Recipe 13.2



Secure Programming Cookbook for C and C++
Secure Programming Cookbook for C and C++: Recipes for Cryptography, Authentication, Input Validation & More
ISBN: 0596003943
EAN: 2147483647
Year: 2005
Pages: 266

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net