2.2.10.7 KERB_KEY_DATA_NEW
The KERB_KEY_DATA_NEW structure holds a cryptographic key. This structure is used in conjunction with KERB_STORED_CREDENTIAL_NEW. For more information, see section 3.1.1.8.11.6.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Reserved1 |
Reserved2 |
||||||||||||||||||||||||||||||
Reserved3 |
|||||||||||||||||||||||||||||||
IterationCount |
|||||||||||||||||||||||||||||||
KeyType |
|||||||||||||||||||||||||||||||
KeyLength |
|||||||||||||||||||||||||||||||
KeyOffset |
Reserved1 (2 bytes): This value MUST be ignored by the recipient and MUST be set to zero.
Reserved2 (2 bytes): This value MUST be ignored by the recipient and MUST be set to zero.
Reserved3 (4 bytes): This value MUST be ignored by the recipient and MUST be set to zero.
IterationCount (4 bytes): Indicates the iteration count used to calculate the password hashes.
KeyType (4 bytes): Indicates the type of key, stored as a 32-bit unsigned integer in little-endian byte order. This MUST be one of the values listed in section 2.2.10.8.
KeyLength (4 bytes): The length, in bytes, of the value beginning at KeyOffset. The value of this field is stored in little-endian byte order.
KeyOffset (4 bytes): An offset, in little-endian byte order, from the beginning of the property value (that is, from the beginning of the Revision field of KERB_STORED_CREDENTIAL_NEW) to where the key value starts.