2 ms·
"Chrome has a sort-of-solution built on top of this" … which scales up about as far as every domain Google owns/cares about, and a few of their friends/partner
by bigiain 12y ago
"Chrome has a sort-of-solution built on top of this"
… which scales up about as far as every domain Google owns/cares about, and a few of their friends/partners/sites-that're-politically-or-business-beneficial-to-Google-to-pin.
I suspect in my 20 odd years of working with ssl protected websites, there's maybe 2 or 3 sites I've worked on that hav a hope in hell of getting into Chrome's pin list. If you're outside the US Fortune500 or any other countries Fortune100, how easy is it gonne be to get Google to pin your cert? It's nice if you're Twitter - it's _never_ gonna work for mygreatcatphotos.org.au...
It's useful, and a great thing they're doing, but as you say, it's _very much_ a sort-of-solution. Perhaps more like a very good two or three bandaid solution, directed at the problem of someone with 99% full body covered 3rd degree burns. "Here, I've got your left thumb and your right big toe covered!"
- TheDong 12y agoThey have pretty little form for it :) https://hstspreload.appspot.com/ https://hstspreload.appspot.com/ My guess is no one bothers to fill out the form due to lack of knowledge about its existence. Surely they let in more than just their friends ... though yes, I do recognize this isn't scalable.
- geofft 12y agoThey've been pushing back against new people preloading public key pins because it's hard to make sure that someone else understands exactly what the consequences are. (Cryptocat, notably, got this wrong.) But yes, HSTS preloading is totally open, and has been scaling as well as it's been needed.