2.2.4 Server ExtendedAuthenticator NTP Response

The subfields of the ExtendedAuthenticator field of the Server ExtendedAuthenticator NTP Response message include the following.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

Key Identifier

Reserved

Flags

ClientHashIDHints

SignatureHashID

Crypto-Checksum (64 bytes)

...

...

Key Identifier (4 bytes): A 32-bit, unsigned integer in little-endian byte order (least significant byte first). This field identifies the cryptographic key used to generate the crypto-checksum.

Reserved (1 byte): MUST be set to zero and MUST be ignored upon receipt.

Flags (1 byte): An 8-bit, unsigned integer in little-endian byte order that contains bit values from the following table. All other values are reserved for future use.

Value

Meaning

USE_OLDKEY_VERSION

0x00000001

The older cryptographic key of the pair of keys associated with the account is used.

ClientHashIDHints (1 byte): An 8-bit, unsigned integer in little-endian byte order that contains bit values from the following table. All other values are reserved for future use.

Value

Meaning

NTLM_PWD_HASH

0x00000001

The client supports the mechanism described in section 3.1.5.5 for computing the crypto-checksum.

SignatureHashID (1 byte): An 8-bit, unsigned integer in little-endian byte order containing one of the values from the following table. All other values are reserved for future use.

Value

Meaning

NTLM_PWD_HASH

0x00000001

The Crypto-CheckSum field was computed using the mechanism described in section 3.1.5.5.

Crypto-Checksum (64 bytes): A 512-bit crypto-checksum that the encryption procedure computes.

All other fields are returned according to [RFC1305].<6>