Re: [cifs-protocol] [REG:116102514847681]: [MS-PAR] Q 1/2 3.1.4.2.7 RpcAsyncInstallPrinterDriverFromPackage; performing additional validation steps

2016-11-24 Thread Edgar Olougouna via cifs-protocol
Andreas, Thanks for confirming. Indeed the CRL URL would be of importance. Testing signtool on a signed driver catalog file should reveal more detail how it works, then use Process Monitor and Network Monitor to see files that are opened and calls going on. SignTool is in SDK, and would

[cifs-protocol] Authenticated at RODC flag?

2016-11-24 Thread Andrew Bartlett via cifs-protocol
I remember somewhere there being a flag or special SID that indicated the a session is authenticated at the RODC. However I can't find any evidence of it. Is there any such flag, ideally for connections made to the LDAP server, to tell me if the user session was authenticated at the RODC, or if

Re: [cifs-protocol] [REG:116102514847681]: [MS-PAR] Q 1/2 3.1.4.2.7 RpcAsyncInstallPrinterDriverFromPackage; performing additional validation steps

2016-11-24 Thread Andreas Schneider via cifs-protocol
On Tuesday, 22 November 2016 06:30:20 CET Edgar Olougouna wrote: > Andreas, > The drivers are generally signed through Windows Hardware Dev Center > Dashboard. This is normally achieved through WHQL program. From my > understanding, in Windows, print driver certificate verification is done >