4 ms·
Interesting. If I understand correctly, this will render some hardware whose drivers were signed with that certificate unusable. Very expensive, hard-to-repla
by CamperBob2 3y ago
Interesting. If I understand correctly, this will render some hardware whose drivers were signed with that certificate unusable. Very expensive, hard-to-replace hardware in my company's case.
Nobody seems to be talking about an outrageous act of value destruction on Microsoft's part, so maybe I'm interpreting it wrong.
- deceptionatd 3y agoThis Reddit thread has a script with a workaround: https://www.reddit.com/r/sysadmin/comments/15ysxgs/application_with_revoked_certificate_revocation/ https://www.reddit.com/r/sysadmin/comments/15ysxgs/applicati... There are comments saying it's worked on several Quickbooks integrations. Regarding hardware drivers, I _think_ the same fundamental process of removing signatures should work, but you'll get a UAC prompt to force installation of an unsigned driver. I'm not as familiar with driver signature enforcement though, so take that with a grain of salt. P.S: I still have running XP installs for some $300k industrial hardware. It could be worse...
- shartte 3y agoHashes of known good drivers should be whitelisted explicitly if they are known to have been signed correctly before revocation. Direct trust should trump a PKI here.