3 ms·
> They refuse to change security defaults, even when it starts getting absurd, and then lay the responsibility (and blame) at the feet of their customers. They
by omnibrain 6y ago
> They refuse to change security defaults, even when it starts getting absurd, and then lay the responsibility (and blame) at the feet of their customers.
They changed a lot of security defaults with Windows Vista and literally(figuratively) everybody dumped on them. It got called worst Windows ever, unusable, and names I don’t want to spell out from the public and the press.
That made them reluctant to attempt such drastic measures again. But at least they disable SMBv1 by default nowadays.
- jiggawatts 6y agoThe crypto wasn't at all the criticism most (any?) people had with Vista. My criticism is that they didn't implement the Vista-era crypto enough. In 2020, most Microsoft software doesn't support ECC certificates because their server products are still written to use the 2000/XP/2003 era crypto APIs instead of the Vista and later crypto APIs. I remind you that none of those operating systems are supported any longer, but apparently for "comptibility reasons" SQL Server 2019, AD FS 2019, and System Centre 2019 can't use elliptic certs. Or use TPM-hosted certs. Or anything at all really other than RSA 2048-bit certs stored in software. IIS can, but that's the lone exception, not the rule.