News for hackers. Stuff that matters.
Re:Fencing Your SSL Errors With HSTS by nodesocket on Sunday January 20, 2013 @06:45AM (#5086634)
At http://commando.io we implement HSTS in the nginx server block:

    # Enable Strict-Transport-Security for one year
    add_header Strict-Transport-Security max-age=31556926;
Re:Fencing Your SSL Errors With HSTS by Kudos on Sunday January 20, 2013 @09:24AM (#5086968)
https://commando.io/ serves up your PHPMyAdmin.

Edit: also, because of HSTS I can only visit your "secure" site and can no longer get to your marketing page to see what it is you do.

Re:Fencing Your SSL Errors With HSTS by nodesocket on Sunday January 20, 2013 @10:04AM (#5087092)
Good catch, fixing that now.
Re:Fencing Your SSL Errors With HSTS by Kudos on Sunday January 20, 2013 @10:23AM (#5087135)
I'll just wait a year for the cached HSTS flag to expire ;)
Re:Fencing Your SSL Errors With HSTS by nodesocket on Sunday January 20, 2013 @11:35AM (#5087304)
Should be good now. Just working on a solution for GitHub buttons not supported over SSL.