8 ms·
> It is clear that the cost and bureaucracy of obtaining certificates was forcing many websites to continue with the insecure HTTP protocol I never realized t
by StavrosK 11y ago
> It is clear that the cost and bureaucracy of obtaining certificates was forcing many websites to continue with the insecure HTTP protocol
I never realized this so clearly, but it's true. The biggest hindrance to security until LE was that certs were expensive and hard to install. I don't think it was so much the former as the latter. I'd gladly pay 10% more for my cert if it meant my server could renew automatically without me touching it at all.
Then again, for small things, like my home computer that I want to access some stuff on but don't want to pay $10 for, self-signed was fine, so I guess the price was a problem, to a degree.
- lrem 11y agoHowever, imho, he biggest reason to ever use self signed is that you can set expiry @2099 and it won't degrade anything.
- Ao7bei3s 11y ago1. You'd have install the custom CA in all devices. Ever tried it on Android? The "network may be monitored" warning doesn't go away. 2. If the certificate is ever compromised, you'll have to keep it in the revocation list forever, or replace the entire CA. (And I hope your CA contains a DNS name restriction.)
- technofiend 11y ago>1. You'd have install the custom CA in all devices. Ever tried it on Android? The "network may be monitored" warning doesn't go away. This is the most annoying part of using certs for Radius authentication with Android. Either you self-sign a cert and forever get these warnings, or you let someone else sign your cert and then that CA can issue device certs for your domain.
- Ao7bei3s 11y agoAt least modern Android version support setting the CA certificate in the wifi settings. (And then there's the university way of things: just run your own trusted (!) CA ;-) (e.g. in Germany: signed by DFN)
- Ayaz 11y ago> I never realized this so clearly, but it's true. The biggest hindrance to security until LE was that certs were expensive and hard to install. I don't think it was so much the former as the latter. I'd gladly pay 10% more for my cert if it meant my server could renew automatically without me touching it at all. Absolutely! Every time I had to create a CSR and install an SSL certificate on a server (having done it before in the past), I felt repeatedly terribly painful the process was.
- zemanel 11y agoI've wondered if this issue could have been solved a long time ago by commercial companies (the way LetsEncrypt solves it or similar), it just wasn't as good business :-)
- ygjb 11y agoHeh. If the CAs had done this ages ago the cost of certs would have collapsed. I can't help but think that collusion between the CAs was a regular thing to prevent something like LE from happening in order to prevent the business model from souring.
- joepie91_ 11y agoSSLMate has been doing that for a while.
- Ayaz 11y agoI'd imagine so. I also like the approach that Amazon has taken with its recently launched AWS Certificate Manager. You can create as many SSL certificates as you like free of cost, even wild-card ones (which if I am correct Let's Encrypt does not support yet), and the AWS Certificate Manager takes care of the rest. The only restrictions, off the top of what I've read, are: 1) You have to be using the AWS infrastructure; b) You'd have to use their load balancer or CDN solutions, against which the certificates are placed.
- sbierwagen 11y agoCertsimple does autorenewal. https://certsimple.com/ https://certsimple.com/
- kristofferR 11y agoYeah. I was really against SPDY/HTTP2 only supporting encrypted websites until Let's Encrypt came along, as it would have "forced" all the small sites to keep using HTTP 1.1 forever. Now I don't mind the requirement at all. https://news.ycombinator.com/item?id=6724292 https://news.ycombinator.com/item?id=6724292
- lucb1e 11y agoFrom what I got, it forces opportunistic encryption only. If there is no special signed cert available, it just generates one randomly and uses that. Unsafe against people who can modify your connection, but it protects against passive eavesdropping.
- pfg 11y agoAll major browser vendors decided not to implement opportunistic encryption in HTTP/2.
- lucb1e 11y agoSo they force either a valid cert or nothing? Not even unencrypted http/2? Because that would be quite awesome. Edit: are there statements where they say they don't intend to implement it ever, or is it just not supported yet and e.g. Microsoft might still implement it later to please some enterprise stakeholder?
- pfg 11y agoAccording to this[1], that's a permanent decision. Given that both Google and Mozilla have discussed plans that would eventually mark http:// http:// as unsafe in the UI, I don't think that decision is going to change. [1]: https://daniel.haxx.se/blog/2015/03/06/tls-in-http2/ https://daniel.haxx.se/blog/2015/03/06/tls-in-http2/
- lucb1e 11y agoWell there is a difference between unsigned encrypted and unencrypted, I'm not saying marking http:// http:// as unsafe implies that they'll always regard unsigned encrypted as completely unprotected, especially with closed source browsers (or browsers where development is a closed process). Thanks for all the information though! :)
- nly 11y agoI personally find the hassle of installing, configuring and, crucially, testing, both LetsEncrypts scripts, and an accompanying cronjob, much more work and worry than a static nginx ssl config.
- tokenizerrr 11y agoWhat are you talking about? My nginx ssl config is static as well. It looks at a specific path for my certs, which just happens to be a symlink managed my by letsencrypt tooling. You're going to have to renew anyway. Previously you would have to remember to do that once a year, or maybe once every two years. Now let's ignore the security implications of having certificates that are valid for a year for a moment, and just focus on the actual work. Every year, you have to request a new certificate, wait for your certificate authority, upload the new certificate to the server, reload your webserver, check if everything works. With LE, you do all of that once. You set up the tooling and the cronjob once. You make sure it works once. And you're done. No more hassle.
- nly 11y ago"Once" assuming nothing randomly breaks while you're not looking. What if your cronjob doesn't fire? What if LEs script has a bug and you're not up to date? What if one of the (Python?) dependencies has a bug or breaks? What if LEs servers are being DDoS'd? Can you enumerate and account for all the failure scenarios? I've already botched things with acme-tiny&LE in several different ways. I'm not claiming these risks are that significant, but given that LE takes just as much time and effort for initial set-up as a standard multi-year cert, if not more, I think the mantra "some risk of failure is more risk of failure than no risk of failure" is something worth baring in mind. And I'm not convinced having 90 day certs is a huge security win. Not only can someone do a lot of damage in 90 days, but your private key (the important bit) can't be rolled every 90 days anyway without integrating your rollover scripts with your HPKP config. If you botch that then your visitors can't come back to your website until the pin expires. Scary. Site ending scary. And if you're not using HPKP then i'm not even going to debate the security pros and cons. On remembering to renew certs... there are many many services out there to send you reminders. Pick 2 or 3 and use them all. Or use a CA that sends reminders. I'm glad LetsEncrypt exists, but let's not treat it like the be-all-and-end-all.
- akerro 11y agoI tried to get SSL cert for my fathers company and different kinds of certificates just scared me. Do you know there is a kind of cert where you need to go in person with your ID and register yourself? I'm currently using LE for 6 domains, 2 of them joined as first 100 LE domains, before LE was supported by Ubuntu.
- mholt 11y ago> I'd gladly pay 10% more for my cert if it meant my server could renew automatically without me touching it at all. I wrote a server that does this. Would be happy to have your feedback sometime: https://caddyserver.com https://caddyserver.com - here's how it works with regards to Let's Encrypt certs: https://www.youtube.com/watch?v=OE5UhQGg_Fo&t=32m https://www.youtube.com/watch?v=OE5UhQGg_Fo&t=32m
- vincentleeuwen 11y agoFound this tutorial yesterday about how to do it with letsencrypt https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-14-04#step-4-—-set-up-auto-renewal https://www.digitalocean.com/community/tutorials/how-to-secu...
- StavrosK 11y agoI use simp_le for that. I more meant "I'd have paid a CA 10% more for automation", but that ship has sailed now that LE has launched. I'm probably not going to be using anything else any time soon.
- StavrosK 11y agoOh, I've downloaded Caddy and used it a few times, I love it but haven't switched anything to it yet. To me, the killer feature right now is that I can just drop it in my /usr/bin directory and have a performant HTTP server in the current dir with just one command. I don't use the LE integration (even though I love the feature) because I haven't deployed it in anything outward-facing. One small nit would be that I'm not very clear on how the LE fetching is done (where all the files are placed). The docs do mention this, but I left with a feeling that I was still not very clear on where the files go after reading it. Other than that, great job on Caddy!
- deepnet 11y agoAnd hosting companies selling certs are incentivised to not provide HTTPS by default. The number of not https wordpress admin pages and plain text ftp logins still in regular use is chilling and directly attributable to this misaligned incentive.
- technion 11y agoThere's an oft-neglected issue with this. From experience, when a hosting company supplies an SSL certificate to a customer, here's the usual process. The first thing that happens is the site totally breaks because browsers won't render mixed content. So the customer calls their developer and their developer calls the host and insists it's a server problem and someone spends an hour or more explaining what mixed content is to a developer and how to fix it. Then someone runs it through the SSLLabs test and decides they don't like seeing RC4 supported. So you provide some warnings regarding it, confirm, and then oblige, but then you get angry, aggressive emails because their entire office uses Windows XP and their website doesn't work. A company can burn hours on every individual SSL deployment. There's plenty of unfortunate incentives against hosting companies.