These resources are from 2007 and thus contain no information about Windows 7 and up, SHA-2, or the Windows Hardware Developer Center Dashboard portal. When I wrote this article in 2012 and for many years subsequently, the authoritative documents on kernel-mode code signing were kmsigning.doc and KMCS_walkthrough.doc. I learned the hard way and now you can learn the easy way.Ī lot of this information can be verified in official Microsoft documentation found on MSDN, and I will try to cite the official documentation when needed. If you are going through the same process, I sincerely hope that this document can clear up all of your confusion and save you a lot of time. I encountered so many problems along the way that could have been easily avoided if someone had told me about them ahead of time. In 2012 I went through the process of signing all of our company's USB drivers and most of our installers for Windows.
My name is David Grayson and I work at Pololu Robotics & Electronics. If you are a developer figuring out how to sign drivers or software, the aim of this guide is to tell you everything you need to know so that you can do it correctly. In the case of device drivers, signing is generally required. Signing your software is important: by showing a nicer dialog to the end user, it gives end users more confidence that they are not installing malware. This means that the publisher has cryptographically signed their work. If you have ever installed some software or drivers in Windows, you have probably seen a dialog telling you the name of the company or person that published that software.
0 kommentar(er)
