6 ms·
For those, like me, wondering who the author might be, it appears to be this guy: "Adam Langley works on both Google’s HTTPS serving infrastructure and Google C
by wpietri 13y ago
For those, like me, wondering who the author might be, it appears to be this guy: "Adam Langley works on both Google’s HTTPS serving infrastructure and Google Chrome’s network stack. From the point of view of a browser, Langley has seen many HTTPS sites getting it dreadfully wrong and, from the point of view of a server, he’s part of what is probably the largest HTTPS serving system in the world - See more at: http://www.rsaconference.com/speakers/adam-langley#sthash.HMdxPRI7.dpuf" http://www.rsaconference.com/speakers/adam-langley#sthash.HM...
- timothya 13y agoHe was also one of the two people who prepared the fix for Heartbleed in OpenSSL[0]. [0]: https://github.com/openssl/openssl/commit/731f431497f463f3a2a97236fe0187b11c44aead https://github.com/openssl/openssl/commit/731f431497f463f3a2...
- tptacek 13y agoHe's also the author of Golang's native crypto/tls TLS stack, a longtime contributor to the IETF TLS WG, and the author of some of OpenSSL's curve software. He's not messing around.
- einhverfr 13y agoOn the other hand we found that as of Friday, Chrome DID NOT recognize that one of our wildcard certs for Efficito had been revoked. We sent out an email to our customers saying to enable cert revocation checking. Revovation isn't perfect and I would not suggest the current status quo is OK but the intermediary approach Chrome takes cannot be trusted as they have now shown. If Chome will not show our cert as revoked what is the point of revoking the cert? The author has points but the approach Google ie taking is a cure worse than the disease...
- chmars 13y agoHonestly, I don't see a point in certificate revocations anymore, i.e., your implicit conclusion seems to be correct. And I don't blame Google for our broken revocation system – especially because the even the best revocation system couldn't fix the current certification system that is broken in its core.
- einhverfr 13y agoGoogle's problem is they decide which revocations are worth passing on to the browser. That's at least as broken by design..... Believe me I am aware of the limits of soft-fail, but the answer cannot be even in the short-run to let a browser vendor tell us which revocations are worth knowing about.
- tptacek 13y agoDo you know the limits of "soft-fail"? Because I don't see you addressing them.
- enneff 13y agoSoft fail doesn't work at all. CRLset works for the certificates that it covers (some 25k of them, btw). Which approach is worse?
- mpyne 13y ago> but the answer cannot be even in the short-run to let a browser vendor tell us which revocations are worth knowing about. So you trust the browser vendor to ship you executable native code but you don't trust the browser vendor to apply reasonably decent criteria for the top x% most-needed cert revocations on the Internet?
- richardwhiuk 13y agoRevoking certificates is pointless - that's Adam's point here.
- 13y ago