Code Signing for Windows 10 and Windows 10 1607/Later
Xiaofan Chen <[email protected]> Sat, 4 Mar 2017 17:59:44 +0800
| Newsgroups | gmane.comp.lib.libusb.devel.windows |
|---|---|
| Message-ID | <CAGjSPUC4hkLcCjgWOvUrY+rLbOaBF0_1Wvq0eCHn3DwOLCr1kQ@mail.gmail.com> |
Interesting stuff: https://blogs.msdn.microsoft.com/windows_hardware_certification/2015/04/01/driver-signing-changes-in-windows-10/ https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/ Both are Windows 10 and yet they are different. The good thing is that existing driver will still work. "What about existing drivers? Do I need to re-sign these drivers to get them to work with Windows 10, version 1607? No. Existing drivers do not need to be re-signed. To ensure backwards compatibility, drivers which are properly signed by a valid cross-signing certificate issued prior to July 29th, 2015 will continue to pass signing checks on Windows 10, version 1607." In reality Windows 10 code signing becomes more and more complicated and there are many discussions in OSR NTDEV here. https://www.osronline.com/showlists.cfm?list=ntdev -- Xiaofan ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot