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
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
>
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 through some generic setup API call.
At the moment, I am planning to explore
On Monday, 14 November 2016 07:23:35 CET Edgar Olougouna wrote:
> Andreas,
Hello Edgar,
> Here is and update to this set of questions:
Thank you very much for the update!
> c) whether there is any requirement for checksum verification of the
> Microsoft catalog file (driver.cat)?
>
> Both
Andreas,
Here is and update to this set of questions:
a) what sections of the control file needs to be inspected?
Windows print system uses the underlying SetupAPI's to conduct the installation
and inspection of the INF files. For example, the inf file is passed to
