Welcome to SSLFail!
Lately there seems to be a lot of SSL discussion, and not just the recently released ‘Rogue CA‘ presentation. There have been speakers at several cons, blog posts, and conversations lately around the subject of SSL.
Marcin and I were discussing some of the recent failures that we’ve seen and that others have mentioned and decided that we needed a place to bring all of these together, to point out that companies are failing at SSL. Marcin suggested mismatched.com, however the domain was already taken and as I typed in random things, I stumbled across the availability of SSLFail.com. It seemed to work well, so I registered it and 24 hours later here we are.
One of my coworkers, Jay, spends a lot of time playing with SSL… both at work and on his own. So naturally when the thought of blogging about SSL came to mind, so did his name. I pinged him and sure enough, he was interested.
So here we are, the three of us (for now). I invite anyone interested in writing here to contact us.
Enjoy,
Tyler.


January 13, 2009
Pre-comment question: Are you accepted screenshots of prominent sites whose logins are not SSL-protected?
Ugh. The state of browsers right now has made screenshots of ssl failures so amazing. Every little discrepancy (or less money spent on ‘normal’ certs) results in error pages. It’s pretty ridiculous.
I can’t wait to go to IE7/FF3 in my work environment (I use it, but it’s not installed widely on users). I have about 40 internal-only web servers hosting roughly 300 different sites internally (mostly development copies of public sites). Every one is protected by a non-EV SSL internally-signed cert. Let alone almost all of my network devices…
The band-aid of error alerts and green address bars to increase user awareness doesn’t work, and was a stupid idea in the first place (way to make more money for CAs). It would be just a minorly stupid idea if it weren’t so forced…
Sorry, the state of SSL is a bit of a peeve of mine. I don’t mind if a site like http://www.gmail.com uses the http://www.google.com SSL, but I do mind that browsers have moved away from pop-up warnings that can be turned off to obscure full-page warnings that make it sound like the site is evil and broken.