Live data from Hacker News

Why isn't HTTPS everywhere yet?

webappsec-test.info

121–130 of 130 posts

Re: Why isn't HTTPS everywhere yet?

#121
post #37

In addition to ad revenue issue r1ch mentioned (a friend of mine told me HTTPS ads provided less than half the revenue HTTP ads provide), there are a few other things I've encountered while working on HTTPS support: - More ad network misbehavior: the last time I checked, a lot of HTTPS ads on AdSense would take up 100% CPU and lag the browser, because it would try to request an HTTP resource and fail in an infinite l…

Regarding the "Annoyance" bullet point, you might have a better time if you put an Apache or nginx in the front (on ports 80/443), have it serve the acme-challenges statically and proxy_pass everything else to Node running on a high port. TLS handling would then happen in the frontend server only. Regarding the "please use sudo" issue, it's very much possible to run the letsencrypt client as a non-root user if you se…

Adding an entire piece of server software for soemthing like node or phoenix, just to answer an HTTP response is overkill. If you want to use LE, make a node client to get the certs and do the renews and shove it on npm.

Re: Why isn't HTTPS everywhere yet?

#122
post #37

In addition to ad revenue issue r1ch mentioned (a friend of mine told me HTTPS ads provided less than half the revenue HTTP ads provide), there are a few other things I've encountered while working on HTTPS support: - More ad network misbehavior: the last time I checked, a lot of HTTPS ads on AdSense would take up 100% CPU and lag the browser, because it would try to request an HTTP resource and fail in an infinite l…

Full URL (the one above is truncated) for the drag and drop issue:

https://github.com/Zarel/Pokemon-Showdown-Client/commit/53a1...

Re: Why isn't HTTPS everywhere yet?

#123
post #119
post #99

Earlier quoted context omitted.

I am interested in (a). Recently I heard from a trusted source who works for a popular CDN that some top levels CAs, who are trusted in my browser, are known to be issuing certificates for domains which they have no authority to be doing so, for the purpose of man-in-the-middle analysis by certain parties. But that there is a reluctance to pull these certificates because that would be like switching off portions of t…

just listen to security now [0]. it'll make your blood boil how, e.g., symantec fucks up over and over again. this industry is full of incompetent idiots. [0] https://twit.tv/shows/security-now (episode 532 is particularly revealing)

Thanks, interesting to hear. If I heard correctly this is a case of incompetence -- which is certainly a problem. Though the information I heard was about lesser-known CAs granting certificates to enable some kind of snooping.

It seems that a problem with the current implementation of SSL is that it conflates the requirement for encryption with that for identification.

Knowing that "Symantec thinks this is google.com" has limited benefit to me; I'm happier with the idea that "This is the same google.com you visited before".

Re: Why isn't HTTPS everywhere yet?

#124
post #85

Earlier quoted context omitted.

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.

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).

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?

#125
post #97

Earlier quoted context omitted.

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)?

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…

Eugh... best of luck :D

Re: Why isn't HTTPS everywhere yet?

#126
post #33

We just launched support for free SSL on all our plans at https://www.netlify.com , doing what we can to help getting HTTPS everywhere. Won't help on mixed content or broken ad providers, but at least give people a place to put a project on a custom domain for free with HTTPS :)

What is the Full SSL feature offered by you? From what I understand it means supporting weaker ciphers apart from SSL and older TLS versions. Is that the case?

The full ssl feature means skiing a fallback certificate for non-SNI capable browsers.

Internet explorer on windows XP and Android 2.3 doesn't support SNI based ssl and our full ssl solution assures that even these older browsers can access the site over https without any warnings...

Re: Why isn't HTTPS everywhere yet?

#127
post #33

We just launched support for free SSL on all our plans at https://www.netlify.com , doing what we can to help getting HTTPS everywhere. Won't help on mixed content or broken ad providers, but at least give people a place to put a project on a custom domain for free with HTTPS :)

What is the Full SSL feature offered by you? From what I understand it means supporting weaker ciphers apart from SSL and older TLS versions. Is that the case?

The full ssl feature means skiing a fallback certificate for non-SNI capable browsers.

Internet explorer on windows XP and Android 2.3 doesn't support SNI based ssl and our full ssl solution assures that even these older browsers can access the site over https without any warnings...

Re: Why isn't HTTPS everywhere yet?

#128
post #33

We just launched support for free SSL on all our plans at https://www.netlify.com , doing what we can to help getting HTTPS everywhere. Won't help on mixed content or broken ad providers, but at least give people a place to put a project on a custom domain for free with HTTPS :)

What is the Full SSL feature offered by you? From what I understand it means supporting weaker ciphers apart from SSL and older TLS versions. Is that the case?

The full ssl feature means skiing a fallback certificate for non-SNI capable browsers.

Internet explorer on windows XP and Android 2.3 doesn't support SNI based ssl and our full ssl solution assures that even these older browsers can access the site over https without any warnings...

Re: Why isn't HTTPS everywhere yet?

#129
post #17

Earlier quoted context omitted.

With AES-NI, a single modern CPU core can encrypt 10 gigabits/second and do about 50,000 public key operations per second. Cryptography is not that expensive.

AES isn't the only algorithm used in TLS handshakes.

That is why I also said 50,000 public key operations per second.

Re: Why isn't HTTPS everywhere yet?

#130
post #74

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 II…

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.
Post reply on HN