This is a bit of a mess. I wouldn't trust the revocation to work, since that involves a request over a network that has already been compromised. Interesting t

This is a bit of a mess. I wouldn't trust the revocation to work, since that involves a request over a network that has already been compromised. Interesting to find what the Chrome team did to fix this: http://src.chromium.org/viewvc/chrome/trunk/src/net/base/x509_certificate.cc?r1=76824&r2=78478&pathrev=78478 http://src.chromium.org/viewvc/chrome/trunk/src/net/base/x50... Good reason to upgrade! (Edit: this happen a few weeks ago, it has apparently taken the browser makers 8 days to issue an update while in the interim there were rogue signed certs out in the wild)