News for hackers. Stuff that matters.
Re:Why isn't HTTPS everywhere yet? by cm2187 on Tuesday January 19, 2016 @05:35AM (#10929797)
Cost is going to be taken care of by let's encrypt.

I am surprised complexity of setting up SSL isn't mentioned in the article.

First the tools are complex to use, use various formats for storing keys that are incompatible. In Linux you pretty much have to rely on cryptic command lines. Windows is slightly simpler. And you need more tools to convert certificates between the different formats (for instance using an IIS certificate with FileZilla).

Then you have to deal with the complexity of the algorithms used, the fact that chrome won't accept sha1 anymore, the fact that http2 is very picky in the cryptographic methods used.

What is a best practice today breaks tomorrow. For instance the following script written only a couple of years ago shows how to set up windows to get an A on SSLLabs:

https://www.hass.de/content/setup-your-iis-ssl-perfect-forwa...

But with IIS10 / http2, this list of ciphers is incompatible with chrome. I found a list that works here:

https://code.google.com/p/chromium/issues/detail?id=529994

but I am sure it will break older browsers.

Etc, etc, etc. This is hard work. Until setting up SSL will be a simple box to tick in IIS or a single setting to change in apache, only developers who really care about security and are really motivated will deal with this shit.

Re:Why isn't HTTPS everywhere yet? by Loic on Tuesday January 19, 2016 @07:06AM (#10930151)
The cipher list is effectively a big issue. When using the good old Sun Fortran compiler, I was used to have a -fast flag which would be smart to detect the hardware and be as fast as possible while respecting the IEEE maths (as far as I can remember).

I would love a -secure flag to just use the most secure option of the current version of the software even at the cost of X years of backward compatibility at the tool/client/browser level.

For example for nginx instead of something like:

    ssl_ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS;
You would get:

    ssl_ciphers SECURE;
Re:Why isn't HTTPS everywhere yet? by nailer on Tuesday January 19, 2016 @06:18PM (#10934879)
> I would love a -secure flag to just use the most secure option of the current version of the software even at the cost of X years of backward compatibility at the tool/client/browser level.

> ssl_ciphers SECURE;

That's actually pretty close to nginx's default (unpatched) config (http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_c...), except openssl calls it HIGH.

ssl_ciphers HIGH:!aNULL:!MD5;

How high HIGH is depends on your version of openssl, ie, you probably don't want it for, say RHEL 5's openssl. Which (openssl has a long lifecycle, LTS Linux distros extend it further) some places may still be using.

https://www.openssl.org/docs/manmaster/apps/ciphers.html

A better implementation of the same concept is Mozilla's SSL Config Generator (which is what CertSimple point customers to - we also maintain the node port): it has Modern/Intermediate/Old with a clear idea of the compatibility you're losing with each: https://mozilla.github.io/server-side-tls/ssl-config-generat...

Re:Why isn't HTTPS everywhere yet? by cm2187 on Tuesday January 19, 2016 @07:18AM (#10930199)
Or they should package it in vestions. "TLS 1.3" would come with a standard list of ciphers and other parameters. All you would have to do is tell your system "Disable SSL3.0" "Enable TLS 1.3", etc.

Right now it feels like trying to fly a B747.

Re:Why isn't HTTPS everywhere yet? by brians on Tuesday January 19, 2016 @08:39AM (#10930608)
That does happen! Enable TLS 1.2 only and you're in pretty good shape. TLS 1.3 will drop more bad stuff and add a bit more good stuff.
Re:Why isn't HTTPS everywhere yet? by stealthyb on Tuesday January 19, 2016 @10:31AM (#10931350)
It definitely helps, but if you're trying to keep up with the latest security, you'd be susceptible to Logjam (due to DHE-supporting ciphers in the default TLS 1.2 list).

There's the Mozilla SSL Configuration Generator which helps with the madness, but they still aren't keeping up with the latest recommendations.

Re:Why isn't HTTPS everywhere yet? by grey-area on Tuesday January 19, 2016 @07:06AM (#10930149)
It can be as simple as that.

I just set up a site a few days ago with caddy - http://caddyserver.com. Getting certs for multiple domains was a matter of adding a single line for tls to the config, it generates a key locally, requests the cert, and installs it transparently on the first request. Pretty smooth. I hope they will autorenew without intervention, haven't tested that bit yet, but so far it was painless.

I imagine most mainstream servers will incorporate this sort of smooth tls flow at some point now that services like letsencrypt are available to base it on. I'm considering moving web server for other sites (usually use nginx) for this single feature.

Re:Why isn't HTTPS everywhere yet? by cm2187 on Tuesday January 19, 2016 @07:15AM (#10930192)
I'll look into it, but to illustrate my point, when clicking on your link I get an invalid certificate error in chrome. Granted I am using an old browser (Win XP / Chrome 40) but it illustrates my point that it is hard to get SSL to work well.
Re:Why isn't HTTPS everywhere yet? by grey-area on Tuesday January 19, 2016 @07:21AM (#10930207)
Wasn't XP EOL in 2014 or something after being unsupported since 2009? That's long enough ago that many websites don't test on XP any more, or even work (like sites which require SNI AFAIK). I'm happy to drop XP users I'm afraid, given it has been unsupported for some time (I understand some workplaces mandate it still).
Re:Why isn't HTTPS everywhere yet? by bigbugbag on Wednesday January 20, 2016 @06:58AM (#10937471)
Following in the footsteps of IE 6, Windows XP refuses to disappear for sometimes unbelievable reasons.

It was exposed in a conference at "pas sage en seine 2015"[1] that almost every french banks websites use broken security because their ATMs are still running windows XP and go through the same web server.

[1]: http://passageenseine.org/

Re:Why isn't HTTPS everywhere yet? by cm2187 on Tuesday January 19, 2016 @07:25AM (#10930222)
As you suggest, I am not using XP by choice...
Re:Why isn't HTTPS everywhere yet? by lucaspiller on Tuesday January 19, 2016 @07:31AM (#10930243)
Why is your employer forcing to use a severely outdated system? Do you often come across broken or very slow websites (I imagine the hardware is from the same era as the OS)?
Re:Why isn't HTTPS everywhere yet? by cm2187 on Tuesday January 19, 2016 @07:54AM (#10930358)
Hardware is high end 2009 workstations.

We as an organisation like to take our time. We wouldn't welcome a new joiner with a PC on his desk. Much more fun to see him struggling for weeks with our internal IT approval processes. We happily pay millions to Microsoft to get the privilege of using Windows Xp / 32 bit systems a little bit longer (I have now almost more RAM in my mobile phone than my workstation). In fact I suspect many of the critical infrastructures of the organisation are running on COBOL. We'd probably still use CRT screens if our IT department could source them. We are certainly still using blackberries (I hope they will stash enough devices before RIM goes bust).

Re:Why isn't HTTPS everywhere yet? by lucaspiller on Thursday January 21, 2016 @04:08AM (#10944145)
Eugh... best of luck :D
Re:Why isn't HTTPS everywhere yet? by vox_mollis on Tuesday January 26, 2016 @01:56PM (#10975136)
Let's Encrypt is still completely unusable. We fought useless error messages for two hours for our recent renewal, gave up, and renewed with our old CA. Old CA was a very painless process by comparison.