2.2.8.1.1.2.2 Non-FIPS (TS_SECURITY_HEADER1)
The TS_SECURITY_HEADER1 structure extends the Basic Security Header (section 2.2.8.1.1.2.1) and is used to store a 64-bit Message Authentication Code.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
flags |
flagsHi |
||||||||||||||||||||||||||||||
|
dataSignature |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
flags (2 bytes): A 16-bit, unsigned integer that contains security flags as specified in section 2.2.8.1.1.2.1.
flagsHi (2 bytes): A 16-bit, unsigned integer. This field is reserved for future use. It is currently unused and all values are ignored. This field MUST contain valid data only if the SEC_FLAGSHI_VALID bit (0x8000) is set in the flags field. If this bit is not set, the flagsHi field is uninitialized and MAY contain random data.
dataSignature (8 bytes): A 64-bit Message Authentication Code generated by using one of the techniques described in section 5.3.6.1.