3 ms·
But having updates cryptographically signed and checked against a list of (presumably) trusted certificates is in my best interest. The "bug" here was in key m
by zvrba 14y ago
But having updates cryptographically signed and checked against a list of (presumably) trusted certificates is in my best interest.
The "bug" here was in key management, not in SW that's running in my computer.
- MiguelHudnandez 14y agoI shouldn't have used the word "certificate." What I meant was "license." The code that caused the certificate chain to be compromised is related to licensing Terminal Services on Windows Server. That is how their key management failed, and that is what I'm railing against--The fact that this ability to sign binaries with a legitimate Microsoft certificate has been hidden away in copies of Windows Server for years by mistake. And not for any direct customer benefit, but to employ a licensing scheme.