News for hackers. Stuff that matters.
Re:Enhancing digital certificate security (Fake *.Google.com... by mseebach on Thursday January 03, 2013 @03:29PM (#5004463)
Judging by how Google says they stumbled over this, "Chrome detected and blocked an unauthorized digital certificate", it seems that's roughly what they're doing. I wonder how many sites it's able to do this for.

(but yes, that is definitely a good solution)

Re:Enhancing digital certificate security (Fake *.Google.com... by schoen on Thursday January 03, 2013 @05:53PM (#5005229)
You can see the pins list at

https://src.chromium.org/viewvc/chrome/trunk/src/net/base/tr...

Those are the sites that they're currently able to do it for. :-)

If anyone reading wants to have your own site added to the HSTS preload (or perhaps cert pin) lists, I think the Chromium developers are interested in hearing from you. I know they'll add HSTS preloads for any site, but I don't know for sure whether there's a size or popularity threshold of some sort for a cert pin.

Re:Enhancing digital certificate security (Fake *.Google.com... by danielweber on Thursday January 03, 2013 @03:52PM (#5004590)
Chrome (the browser) is super-paranoid about other people replacing google.com certificates. It knows exactly what they should be and anything else is cause for alarm. 'tptacek talks about it from time to time.
Re:Enhancing digital certificate security (Fake *.Google.com... by jcase on Thursday January 03, 2013 @04:24PM (#5004754)
Indeed. Chrome has baked-in public key pinning for their services.

http://www.imperialviolet.org/2011/05/04/pinning.html