4 ms·
There are two separate authentication processes for drivers on Windows: Authenticode, which is used for the kernel-mode driver (.sys) and is strictly enforced,
by bri3d 7y ago
There are two separate authentication processes for drivers on Windows: Authenticode, which is used for the kernel-mode driver (.sys) and is strictly enforced, and driver package signing (.cat/.inf installation packages), which has a mutable root storage called Trusted Publisher system store. Zadig works by adding its own certificate root to the Trusted Publisher system store and self-signing the installation packages, but the three possible installed drivers (WinUSB, libusb0, and libusbK) were all still signed by Authenticode.
- swiley 7y ago> Zadig works by adding its own certificate root to the Trusted Publisher system store and self-signing the installation package Is this different than the local CA cert list? Sorry I don’t use Windows.
- bri3d 7y agoYes, it is its own list for software publisher signing specifically, and is separate from the Trusted Root Certification Authorities certificate store.