You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
typedef struct _SECPKG_CLIENT_INFO {
LUID LogonId; // Effective Logon Id
ULONG ProcessID; // Process Id of caller
ULONG ThreadID; // Thread Id of caller
BOOLEAN HasTcbPrivilege; // Client has TCB
BOOLEAN Impersonating; // Client is impersonating
BOOLEAN Restricted; // Client is restricted
//
// NT 5.1
//
UCHAR ClientFlags; // Extra flags about the client
SECURITY_IMPERSONATION_LEVEL ImpersonationLevel; // Impersonation level of client
//
// NT 6
//
HANDLE ClientToken;
} SECPKG_CLIENT_INFO, * PSECPKG_CLIENT_INFO;
it has an extra HANDLE field.
when calling GetClientInfo (in this header file), the type of the parameter is PSECPKG_CLIENT_INFO, a stack overflow would happen, and I have not found a method to know the actual size of the SECPKG_CLIENT_INFO in advance in runtime.
The text was updated successfully, but these errors were encountered:
in ntsecpkg, the defination of SECPKG_CLIENT_INFO is:
typedef struct _SECPKG_CLIENT_INFO {
LUID LogonId;
ULONG ProcessID;
ULONG ThreadID;
BOOLEAN HasTcbPrivilege;
BOOLEAN Impersonating;
BOOLEAN Restricted;
UCHAR ClientFlags;
SECURITY_IMPERSONATION_LEVEL ImpersonationLevel;
} SECPKG_CLIENT_INFO,*PSECPKG_CLIENT_INFO;
but in Windows SDK 8.1 and 10, it is
typedef struct _SECPKG_CLIENT_INFO {
LUID LogonId; // Effective Logon Id
ULONG ProcessID; // Process Id of caller
ULONG ThreadID; // Thread Id of caller
BOOLEAN HasTcbPrivilege; // Client has TCB
BOOLEAN Impersonating; // Client is impersonating
BOOLEAN Restricted; // Client is restricted
//
// NT 5.1
//
UCHAR ClientFlags; // Extra flags about the client
SECURITY_IMPERSONATION_LEVEL ImpersonationLevel; // Impersonation level of client
//
// NT 6
//
HANDLE ClientToken;
} SECPKG_CLIENT_INFO, * PSECPKG_CLIENT_INFO;
it has an extra HANDLE field.
when calling GetClientInfo (in this header file), the type of the parameter is PSECPKG_CLIENT_INFO, a stack overflow would happen, and I have not found a method to know the actual size of the SECPKG_CLIENT_INFO in advance in runtime.
The text was updated successfully, but these errors were encountered: