The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I've been working off and on getting my customer's old driver ported to the new driver framework and compiling an x64 version. I got the driver working a few months ago, but had to put it on the back burner while they got an EV certificate from IdenTrust. I got the certificate installed and I was able to export a .cer file. I tried to sign the driver using signtool. It found the certificate and tried to sign the driver, but I got the error message
"The specified timestamp server either could not be reached or returned an invalid response"
I double checked and I entered the address of the timestamp server correctly. I tried writing IdenTrust tech support and they said the server address is intended to be entered into an IDE. I tried running the tool with my virus scanner off. Their tech support has not been great.
As I understand it the next step after this is for my customer to set up a Hardware Dashboard account? I thought that was just for drivers included in Windows Update, but comments I've seen in other signing threads here indicate it needs to be done for all drivers? This is for industrial hardware with a limited user base who all know where to go for software updates.
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||12 September 2022||Live, Online|
|Internals & Software Drivers||23 October 2022||Live, Online|
|Kernel Debugging||14 November 2022||Live, Online|
|Developing Minifilters||5 December 2022||Live, Online|