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.
Re:Server Side TLS by Erwin on Tuesday August 02, 2016 @01:36AM (#12207982)
You can check your configuration afterwards using this tool: https://www.ssllabs.com/ssltest/

For command line, this his nice: https://github.com/iSECPartners/sslyze

Re:Server Side TLS by cimnine on Tuesday August 02, 2016 @03:23AM (#12208319)
Another cool util to test/debug HTTPS is https://testssl.sh

It especially useful in locked-up environments where the server-to-server communication must be TLS, yet both servers are not directly accessible from the 'public' internet.

Re:Server Side TLS by jvehent on Monday August 01, 2016 @10:47PM (#12207556)
If you want to contribute to this page, or the config generator [1] that goes with it, check out its repository on github: https://github.com/mozilla/server-side-tls

[1] https://mozilla.github.io/server-side-tls/ssl-config-generat...

Re:Server Side TLS by michaeljsmalley on Tuesday August 02, 2016 @09:28AM (#12209752)
I've already used it a few times buddy :)
Re:Server Side TLS by magthor on Tuesday August 02, 2016 @12:36AM (#12207849)
Lately I've just been throwing everything behind Caddy (caddyserver.com) in reverse proxy mode. This is all you need in your Caddyfile to get automatic TLS. It's genius.

<hostname> { tls <your email> proxy / localhost:<port> }

Re:Server Side TLS by mwpmaybe on Tuesday August 02, 2016 @05:26PM (#12213545)
Wow, this might actually be good enough / full-featured enough to let me stop copying around my huge HAproxy configuration boilerplate and Ansible roles for every project I spin up. Very cool!
Re:Server Side TLS by allannienhuis on Tuesday August 02, 2016 @06:48AM (#12208967)
Thanks for that recommendation - Caddy looks awesome.
Re:Server Side TLS by z3t4 on Tuesday August 02, 2016 @02:05AM (#12208050)
For automation with Nginx and Letsencrypt: https://github.com/Z3TA/letsencrypt-nodejs-nginx
Re:Server Side TLS by akerro on Tuesday August 02, 2016 @04:22AM (#12208495)
> return 301 https://$host$request_uri;

Don't do this. After I did it, my 3 websites were completely wiped-out from search results. From 3k UU to 20-30UU /day.

Re:Server Side TLS by webtechgal on Tuesday August 02, 2016 @06:20AM (#12208882)
Sorry to hear that, but academically very interesting.

Did you try to recover the traffic? If yes, what did you try and did it work?

Also, after setting the permanent redirect, I believe it would be a good idea to update the internal navigation of the site so that all links are formed with https. That way, both the crawlers and the web server will have less work to do and eventually, the entire site will be indexed/updated in the search engines with the https protocol.

Re:Server Side TLS by akerro on Tuesday August 02, 2016 @07:28AM (#12209117)
I updated all navigation, RSS, links to images, menu, search, sitemap, everything. Dump of my site didn't contain any 'http' link to the same domain.

nginx was redirecting everything with 301.

I let once website work on http and https and made most links protocol-independent, only site map and search results are forced to https. There was a thread about it on reddit where a few more people said the same.

I slightly recovered from it, got 101 UU yesterday.

Re:Server Side TLS by webtechgal on Tuesday August 02, 2016 @08:46AM (#12209500)
How long since you changed to https? It may take Google a few weeks to fully recognize the changed/redirected URLs. During this period, the rankings frequently drop but once everything settles down, the rankings and traffic should gradually come back to normal.

If it has been a while (at least a month or two) since the changes were made and the traffic has not returned, that would be a cause for concern.

Re:Server Side TLS by akerro on Tuesday August 02, 2016 @08:47AM (#12209518)
I switched to full HTTPS in January/February (depends which domain), by end of April I had less than 100UU/day from search results.
Re:Server Side TLS by webtechgal on Tuesday August 02, 2016 @09:08AM (#12209626)
And before the switch, the traffic used to be around 3k UV/day? If so, this is definitely a (big) problem. If you share your URL, I'll take a look and give you some input.
Re:Server Side TLS by mwpmaybe on Tuesday August 02, 2016 @05:12PM (#12213457)
This recently changed. Google is no longer penalizing redirects, and is in fact rewarding http->https redirects. Hopefully other search engines will follow suit.

https://moz.com/blog/301-redirection-rules-for-seo

Re:Server Side TLS by StavrosK on Tuesday August 02, 2016 @08:11AM (#12209309)
The things that can make your website drop seem random. I had my visitors plummet after a redesign, even though I kept most of the URLs and redirected the old ones properly. Things never recovered, I don't know why, since I was serving the exact same content as before.
Re:Server Side TLS by wanda on Tuesday August 02, 2016 @06:13AM (#12208859)
Did you also set your website up with Google Webmaster Tools to register the 301?
Re:Server Side TLS by akerro on Tuesday August 02, 2016 @07:30AM (#12209122)
No, I don't have google account and was never registered there. I don't want any US corporation or government to spy on my visitors.
Re:Server Side TLS by nathancahill on Tuesday August 02, 2016 @08:11AM (#12209304)
That's a hard argument to stand on, considering that your search traffic is coming from Google.
Re:Server Side TLS by akerro on Tuesday August 02, 2016 @08:39AM (#12209450)
Also form: bing, baidu, duckduckgo, yahoo. My posts were many times on reddit and in 3 years I've been 4 times on HN with +500 upvotes. Currently 1-3 visitors per day come from search results, 0 or 1 are from google. I use goaccess and piwik.
Re:Server Side TLS by pfg on Tuesday August 02, 2016 @11:18AM (#12210556)
Any chance this is a tracking issue? You might be losing referer information because of the 301, see [1].

[1]: http://piwik.org/faq/troubleshooting/#faq_51

Re:Server Side TLS by webtechgal on Tuesday August 02, 2016 @09:18AM (#12209687)
I disagree. A site can get (a decent amount of) traffic from Google even without giving it (Google) the open access to ALL the activity taking place on the site by way of using the Webmaster Tools.
Re:Server Side TLS by nathancahill on Tuesday August 02, 2016 @10:04AM (#12209983)
That's.. not how Google Webmaster works.