DSS Version 3 Private Key BLOBs

When a version 3 DSS private key is exported, it is in a format as follows:


BLOBHEADER        blobheader; 
DSSPRIVKEY_VER3   dssprivkeyver3;
BYTE p[dssprivkeyver3.bitlenP/8]; 
                    // Where P is the prime modulus
BYTE q[dssprivkeyver3.bitlenQ/8]; 
                    // Where Q is a large factor of P-1
BYTE g[dssprivkeyver3.bitlenP/8]; 
                    // Where G is the generator parameter
BYTE j[dssprivkeyver3.bitlenJ/8]; 
                    // Where J is (P-1)/Q
BYTE y[dssprivkeyver3.bitlenP/8]; 
                    // Where Y is (G^X) mod P
BYTE x[dssprivkeyver3.bitlenX/8]; 
                    // Where X is the private exponent

This BLOB format is exported when the CRYPT_BLOB_VER3 flag is used with CryptExportKey. Because the version is in the BLOB, there is no need to specify a flag when using this BLOB with CryptImportKey.

The following table describes each component of the key BLOB.

FieldDescription
BlobheaderA BLOBHEADER structure. The bType member must have a value of PUBLICKEYBLOB.
Dssprivkeyver3A DSSPRIVKEY_VER3 structure. The magic member should be set to "DSS4" (0x34535344) for private keys.

Notice that the hexadecimal value is just an ASCII encoding of "DSS4."

PThe P value is located directly after the DSSPRIVKEY_VER3 structure, and should always be the length, in bytes, of the DSSPRIVKEY_VER3 bitlenP field (bit length of P) divided by eight (little-endian format).
QThe Q value is located directly after the P value and should always be the length, in bytes, of the DSSPRIVKEY_VER3 bitlenQ field divided by eight (little-endian format).
GThe G value is located directly after the Q value and should always be the length, in bytes, of the DSSPRIVKEY_VER3 bitlenP field (bit length of P) divided by eight. If the length of the data is one or more bytes shorter than P divided by 8, the data must be padded with the necessary bytes (of zero value) to make the data the desired length (little-endian format).
JThe J value is located directly after the G value and should always be the length, in bytes, of the DSSPRIVKEY_VER3 bitlenJ field divided by eight (little-endian format). If the bitlenJ value is 0 then the value is absent from the BLOB.
YThe Y value, (G^X) mod P, is located directly after the J value, and should always be the length, in bytes, of the DSSPRIVKEY_VER3 bitlenP field (bit length of P) divided by eight. If the length of the data that results from the calculation of (G^X) mod P is one or more bytes shorter than P divided by 8, the data must be padded with the necessary bytes (of zero value) to make the data the desired length (little-endian format).
XThe X value is a random large integer such that the public portion of the DH key pair, Y, is equal to:

Y = (G^X) mod P

 

When calling CryptExportKey, the developer can choose whether to encrypt the key. The key is encrypted if the hExpKey parameter contains a valid handle to a session key. Everything but the BLOBHEADER portion of the BLOB is encrypted. Note that the encryption algorithm and encryption key parameters are not stored along with the private key BLOB. The application must manage and store this information. If zero is passed for hExpKey, the private key will be exported without encryption.

Important  It is dangerous to export private keys without encryption because they are then vulnerable to interception and use by unauthorized entities.

 

 

Community Additions

ADD
Show:
© 2014 Microsoft