News for hackers. Stuff that matters.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by MichaelGG on Thursday February 19, 2015 @11:08PM (#9078861)
Well continue the process. Suppose Chrome did flag such things. That'd break a lot of "legitimate" use cases, and someone would implement a workaround. For instance, they could just patch the Chrome binaries to disable the warnings or change the pinning logic. Insert their own certs into the pin list. Without something like Intel SGX, you or Google can't totally win.

Of course, Chrome could give some indication like a lock+eyeball or something, and hope the interception vendors are too lazy to bother modifying the code. They could also only disable warnings if the machine is connected to a domain or other management system.

There are no comments on this comment yet.