Re: Code Signing
(topic) is a CANCEROUS TOLLBOOTH that implies REVOCATION.
NO. Just No. [yet, for 64-bit drivers in 7, and everything later on, this is "the standard" now]
This puts a HUGE BURDEN on open source developers being able to deploy things *like* "soft drivers". Let's say alternative compressed and/or encrypted file systems, for one. Let's say "soft devices" for another [emulating a device through software, like MIDI loopback or CDROM 'file image']. Let's say "special driver for your USB IOT thingy that uses some of the publically available vendor/hardware IDs that can identify themselves by name".
All of this is *OPPRESSED* by the use of CODE SIGNAGE REQUIREMENTS where code must be SIGNED to be used! how can you *REALLY* comply with the GPL with this kind of requirement, as another example?
besides, it's possible to get around the "requirement" if you can get end-users to shut it off (using a non-obvious but well documented procedure). Then it becomes POINTLESS to even HAVE it in the FIRST place, except for Micro-shaft to SCRAPE REVENUE for every "signage" [yes, win-10-nic drivers NOW have to be signed by MICRO-SHAFT].
Code signage is like a broken condom, a FALSE SENSE OF SECURITY while one is getting SCREWED!