News for hackers. Stuff that matters.
Re:Fencing Your SSL Errors With HSTS by FlyingAvatar on Sunday January 20, 2013 @07:02AM (#5086667)
What is the benefit of using this over simply redirecting / forcing SSL use for form handlers and other sensitive URLs on the application end.

Doesn't this just add more complexity to a problem that is not that hard to solve?

Re:Fencing Your SSL Errors With HSTS by mguillemot on Sunday January 20, 2013 @07:14AM (#5086692)
It prevents anyone controlling the DNS resolvers of your clients to redirect to faked HTTP website (of course, only for those of your clients who already visited your real website).

Imagine you're using my WiFi connection. Without HSTS, I could redirect you to a fake http://www.facebook.com to steal your login credentials if you do not notice the login page is not served over HTTPS (and let's be realistic: most non-technical people won't notice something that's supposed to be there, but is not).

Re:Fencing Your SSL Errors With HSTS by tptacek on Sunday January 20, 2013 @07:15AM (#5086697)
FWIW this is called "SSL stripping".