2.2.2.6 LSAPR_REVISION_INFO_V1

The LSAPR_REVISION_INFO_V1 structure is used to communicate the revision and capabilities of client and server. For related information, see LsarOpenPolicy3 (section 3.1.4.4.9).

 typedef struct _LSAPR_REVISION_INFO_V1{
     ULONG Revision;
     ULONG SupportedFeatures;
 } LSAPR_REVISION_INFO_V1, *PLSAPR_REVISION_INFO_V1;

Revision:  The revision of the client or server side of this protocol (depending on which side sends the structure). Upon sending, the value MUST be set to 1 and MUST be ignored upon receipt.

SupportedFeatures (4 bytes): A bit field. When sent from the client, this field MUST be zero and ignored upon receipt by the server. When returned from the server, the following fields are handled by the client; all other bits are ignored by the client and MUST be zero when returned from the server.

Value	Meaning
0x00000001	Upon receipt by the client, this value, when set, indicates that the client SHOULD use AES encryption with the LSAPR_TRUSTED_DOMAIN_AUTH_INFORMATION_INTERNAL_AES structure (section 2.2.7.29) to encrypt password buffers when sent over the wire. Also see AES Cipher Usage (section 5.1.5).
0x00000002	Upon receipt by the client, this value, when set, indicates that the client may call LsarLookupNames4 and LsarLookupSids3 ([MS-LSAT] sections 3.1.4.5 and 3.1.4.9) using authentication other than the RPC_C_AUTHN_NETLOGON security provider. It also indicates that the server supports the method LsarOpenPolicyWithCreds (section 3.1.4.4.10).<20>
0x00000004	Upon receipt by the client, this value, when set, indicates that the client SHOULD use AES encryption with the LSAPR_AES_CIPHER_VALUE structure (section 2.2.6.2) to encrypt private data when sent over the wire. Also see AES Cipher Usage (section 5.1.5).<21>