News for hackers. Stuff that matters.
Re:Server Side TLS by serialx on Monday August 01, 2016 @10:24PM (#12207483)
Worth mentioning https://cipherli.st/ too. But I think more warning about HSTS is needed, since misconfiguring HSTS will cause the domain to be inaccessible for long periods.
Re:Server Side TLS by mdewinter on Monday August 01, 2016 @11:20PM (#12207653)
I'm behind https://cipherli.st, together with some friends. IMHO there is no reason not to have HTTPS everywhere, especially now Let's Encrypt exists. I did think and discuss a lot with people on how 'strong' the page is, and if we might want to change that. The page is targeted at sysadmins who I expect to do at least some research before bluntly copy-pasting config files off somewhere, there are enough warnings on the page.
Re:Server Side TLS by laumars on Tuesday August 02, 2016 @05:09AM (#12208649)
I'm not normally someone who complains about other people's designs but is there a chance you could fade the watermark a lot more? It's still quite bold and immensely distracting which makes it harder to read the content (or at least it does me, but being dyslexic I do have to concentrate harder with reading blocks of text anyway).

That aside, your site looks at valuable resource. Thank you for publishing it.

Re:Server Side TLS by BinaryIdiot on Tuesday August 02, 2016 @02:03AM (#12208041)
> IMHO there is no reason not to have HTTPS everywhere, especially now Let's Encrypt exists

I don't want to disagree with you but I do. I most certainly agree that HTTPS must be everywhere and it's easier than ever before. Where I disagree comes with less experienced developers. I can write a quick PHP / Rails / Node / whatever web server to show some website real fast, deploy by uploading it to a shared hosting package or something fancier like elastic beanstalk, and it's done and up there. Yes it's on HTTP but it's so easy. Now you want to add HTTPS to it? It's not easy. Let's Encrypt makes some aspects of it easier but until the amount of fiction is similar to the process of deploying HTTP you'll never see HTTPS ubiquity in my opinion.

Re:Server Side TLS by okket on Tuesday August 02, 2016 @02:25AM (#12208123)
> Now you want to add HTTPS to it? It's not easy.

Try Caddy with automatic HTTPS [0] in reverse proxy mode [1].

[0] https://caddyserver.com/docs/automatic-https

[1] https://caddyserver.com/docs/proxy

Re:Server Side TLS by Teichopsia on Tuesday August 02, 2016 @02:37AM (#12208161)
Pardon my ignorance, but as a complete beginner how do you hook that up with a python (flask / gunicorn) app?
Re:Server Side TLS by okket on Tuesday August 02, 2016 @02:53AM (#12208221)
Run the python process on a different port and let Caddy act as a proxy, forwarding requests from the original port to it. As described in the second (proxy) link.
Re:Server Side TLS by pg_is_a_butt on Tuesday August 02, 2016 @02:15AM (#12208081)
i use let's encrypt on google app engine... it took less than 5 minutes. google could very easily automate it for everyone, but that removes the direct verification between domain owners and certificate authorities.

granted, you're already giving up this control when you host with any 3rd party, but the CAs are being reckless if they encourage it.

Re:Server Side TLS by hannob on Monday August 01, 2016 @11:02PM (#12207599)
For HPKP that's true, for HSTS not really. It may just force you to deploy HTTPS and not go back - which some might say is a good thing :-)
Re:Server Side TLS by newman314 on Monday August 01, 2016 @10:55PM (#12207576)
IMO, too many of these websites recommend includeSubdomains as part of the HSTS stanza right out the gate.

Personally, I'd deploy HSTS incrementally and wait until such time there is a majority of subdomains that are TLS capable before deploying includeSubDomains. Otherwise, there could likely be some nasty surprises.

Re:Server Side TLS by aianus on Monday August 01, 2016 @11:25PM (#12207671)
You can't get on the HSTS preload list included with browsers without includeSubDomains.
Re:Server Side TLS by newman314 on Tuesday August 02, 2016 @08:34PM (#12214586)
To clarify, most of the customers I deal with are enterprise customers and so as such have many internet facing hostnames/domains/subdomains.

Arbitrarily enabling includeSubDomains is going to lead to nasty surprises if there is no prior coordination.

Re:Server Side TLS by hunter2_ on Monday August 01, 2016 @11:49PM (#12207738)
> majority

I'd argue that all, not most, subdomains must be HTTPS capable (I won't say TLS generally, either; this is only dealing with HTTP). Any that aren't will not be accessible by a user agent that recently (within the max-age) visited the parent domain if it had an HSTS header with that flag.

Re:Server Side TLS by yeukhon on Tuesday August 02, 2016 @12:41AM (#12207864)
Agree. I started with extremely low max-age like 120 seconds, and once I am comfortable I change to a larger value like 6 months.