News for hackers. Stuff that matters.
Re:Windows Certificate Manager does not display the complete... by mattkrea on Saturday August 29, 2015 @01:05PM (#10140638)
Thanks! While I still find this kind of backwards at least something like this exists.
Re:Windows Certificate Manager does not display the complete... by skrebbel on Saturday August 29, 2015 @02:33PM (#10140913)
Hmm, I think it's a very elegant design, probably built to precisely address the problem you asked about. Update server manages whitelist, user/admin manages blacklist, which wins. Nice!
Re:Windows Certificate Manager does not display the complete... by mattkrea on Saturday August 29, 2015 @02:56PM (#10140994)
I prefer the situation on Linux where I don't have the certificate at all rather than getting the certificate and having to mark it untrusted.

Edit: I'm referring to configuring the package as ca-certificates is installed or via dpkg-reconfigure

Re:Windows Certificate Manager does not display the complete... by brazzledazzle on Saturday August 29, 2015 @04:02PM (#10141191)
Correct me if I'm wrong, but don't several distros come with pre-packaged root CAs?
Re:Windows Certificate Manager does not display the complete... by uxp on Saturday August 29, 2015 @04:32PM (#10141267)
I think the idea the parent is trying to express is that if the Linux distro (and OS X in this situation) comes with the root certificate trusted by default via ca_root_nss/ca-bundle or whatever the packager decides to name it they can disable it before even connecting to the internet, and if the certificate is not trusted by default then they don't need to worry about it magically getting trusted in the future outside of the simple fact of updating the root certificate store blindly without inspecting it.

Microsoft's approach means that the user would have to go find the certificate on the internet and blacklist it explicitly, which allows a small window where the computer is vulnerable to some kind of attack involving a certificate signed by the unwanted authority.