12 ms·
Domain-validated SSL will soon be free from the large CAs
- sqldba 11y agoLet's Encrypt is a bit of a joke though. You have to renew every 3 months. Anyone who has used these certs knows what a huge pain in the arse it is to do even once a year. "Oh but we'll work out some way to semi-automate it". Ok, where is it for those of us on cheap cpanel providers who barely know what we're doing? I though this service was for us?
- pilif 11y ago> we'll work out some way to semi-automate it no. It will be automated completely. You set stuff up once and the certificate will be kept up to date. >Ok, where is it for those of us on cheap cpanel providers who barely know what we're doing let's encrypt support will be added into cpanel or even into the web servers powering cpanel. All you'll have to do is check a checkbox or set a configuration file entry in the style of `enable_letsencrypt=yes` and you're done. You won't have to care when the certificate expires. At that point 3 months starts to become interesting because expiration provides a nice hard cutoff date for revocation which works independently of OCSP and CRL availablility.
- jms703 11y agoThere's no joke about the benefits of automation here. I recommend you take the time to figure out how to do it, being a provider.
- vbtechguy 11y agoautomation will eventually be the way just that Letsencrypt client and 3rd party clients need time to evolve and develop to the stage that is acceptable for most folks there's a list of clients being developed on their forums some already have auto renewal automation done see https://community.letsencrypt.org/t/list-of-client-implementations/2103/5 https://community.letsencrypt.org/t/list-of-client-implement... for plesk https://community.letsencrypt.org/t/plesk-and-letsencrypt/4255/3 https://community.letsencrypt.org/t/plesk-and-letsencrypt/42... for Centmin Mod LEMP stack http://centminmod.com/letsencrypt-freessl.html http://centminmod.com/letsencrypt-freessl.html cpanel feature request at https://features.cpanel.net/topic/provide-support-for-lets-encrypt-automated-certificate-management-ssl https://features.cpanel.net/topic/provide-support-for-lets-e... where cpanel folks are interested too
- jgrahamc 11y agoIt already is free. Just use CloudFlare.
- nailer 11y agoThe article already mentions existing free providers like StartSSL and Let's Encrypt - if you really like I can add CF in there too John ;^) - but that's not news.
- tombrossman 11y agoPerfect illustration of 'free as in speech or free as in beer?'. Wonder who I should contact at CloudFlare for my 'free' DV cert that I can use on my server...
- mikeash 11y agoDoes CloudFlare provide free certs for anyone, or do you have to actually use their CDN?
- prothid 11y agoI just used this feature with them the other day. The way it works is that if you enable SSL on a site passing through them, they'll auto-generate the front-end cert. I believe you can add your own cert for a premium. The back-end cert can be set to validated/unvalidated/unencrypted.
- mikeash 11y agoIf you have to use their CDN to get the free cert, then it's completely wrong to bring it up as "already is free" in this context.
- takeda 11y agoIt seems like you need to use their CDN to get it, so that sounds to me a bit like those "free" gifts you receive with a purchase. Not truly free.
- sarciszewski 11y agoDammit. No, I mean, this is great news, but I thought I could create value by listing the CAs that provide free SSL on this page: https://paragonie.com/white-paper/2015-secure-php-data-encryption https://paragonie.com/white-paper/2015-secure-php-data-encry... And soon I won't be. Dammit. And the worst part is, I can't even be angry about that, because it's subverted by a significant security gain.
- mootothemax 11y ago>And soon I won't be. You could pivot to in-depth reviews of the various providers. I'm sure some providers will be a pain in the backside, some will be great, others somewhere in the middle, and all will have various differing support options, up-sell discounts to "premium" certs and so on and so forth.
- sarciszewski 11y agoThat sounds like a great idea for a follow-up page (or alternatively, a great way to get sued for libel).
- mootothemax 11y ago>a great way to get sued for libel I'm pretty sure you're saying that with tongue firmly in cheek. Just in case, though, even in the UK you're covered by fair comment: https://en.wikipedia.org/wiki/Fair_comment https://en.wikipedia.org/wiki/Fair_comment
- sarciszewski 11y agoAnd if I were to ever be brought into court, I would very likely lose more in legal fees than I make in a year, even if I win. (I'm in America, where going to court and hoping not to end up destitute afterwards means you already lost.)
- mootothemax 11y ago
- daigoba66 11y agoThat's great. Soon enough there won't be any excuse to not offer HTTPS.
- favadi 11y agoI think there is already no excuse to not use HTTPs at this moment, no?
- leftnode 11y agoI think you're correct. The cost for an SSL certificate is trivial for any legitimate company, and the processing overhead to encrypt every request hasn't been a concern for years.
- StavrosK 11y agoThere sometimes may be an excuse in the extra roundtrips required to set up a TLS connection. For a public blog that doesn't accept submitting any information (like comments), for example, plain HTTP may be fine.
- pfg 11y agoFair enough. TLS 1.3 might introduce a zero-RTT handshake (with some security trade-offs), but that's obviously going to take quite some time to get rolled out. Highly recommend this blog post [1] for more. [1]: https://timtaubert.de/blog/2015/11/more-privacy-less-latency-improved-handshakes-in-tls-13/ https://timtaubert.de/blog/2015/11/more-privacy-less-latency...
- StavrosK 11y agoVery interesting post, thank you!
- drdaeman 11y ago> For a public blog that doesn't accept submitting any information TLS is not about accepting information, it's about ensuring that the connection's encrypted and authenticated. It is still important to prevent unauthorized third parties from watching which articles you're reading. And it's still important that you know that you're reading a blog you expect to read, not a modified version served by someone else (although CA system isn't completely sufficient for this, at least it thwarts less-powerful adversaries from spoofing).
- michaelbuckbee 11y agoThere's a shift happening in the browser space as well to "downgrade" the UI for DV certs, much less green locks and bars and more gray and no red security warnings. We're entering a world where every site has a DV cert (most likely for free with registering a domain) but that all of the things for which we now consider "needing SSL" will require an EV cert.
- mikeash 11y agoAs long as browsers don't start popping up scary warnings about submitting forms to a site that only has DV certs, I think it'll be fine.
- angelbob 11y agoI'm looking forward to that world.
- ehPReth 11y agoFirefox recently changed DV from gray to green: https://blog.mozilla.org/security/2015/11/03/updated-firefox-security-indicators-2/ https://blog.mozilla.org/security/2015/11/03/updated-firefox...
- raesene4 11y agoEV certs will only make sense (for the vast majority of sites) when consumers start actually recognizing the difference between EV and DV, personally I don't see that happening real-soon as many non-technical consumers don't even notice if there's no SSL cert at all... Ask yourself do you remember what sites use EV certs and would you notice if one had a DV instead... if you wouldn't ask yourself why a company would pay more money for that EV cert, when they can get a perfectly good DV one for free
- dcrosta 11y agoDoes anyone know who the two CAs this post mentions are?
- nailer 11y agoYes, I do. :^)
- mikeash 11y agoNot quite on topic, but what the heck is with the bar graph at the bottom of the page? https://certsimple.com/images/blog/compare.svg https://certsimple.com/images/blog/compare.svg The vertical axis isn't labeled and I can't tell what the bars are supposed to represent from the context? Is the vertical axis pain? Cost? Customer base?
- nailer 11y agoThanks for the feedback Mike! It's speed. I've reverted the text back to the previous copy which was more specific. Further info: ask anyone you know who's got an EV cert from a traditional provider: it's a slow, painful process. CAs typically quote 7-10 days. I waited a month for GoDaddy earlier this year, and many others have too. CertSimple starts checking your details while you fill in the form, and flags a wide variety of issues before you pay us. Our average validation time is 5 hours. During validation, we provide very, very specific instructions based on a number of aspects of your order and your company. People with .io domains and Swedes really like us. As do in many other situations where the EV process typically shows down. We update in realtime during the validation, and the certs downloads automatically. We're about to replace the graph with the wall of Twitter customers from our front page, so let me know what you think of that!
- mikeash 11y agoGreat, it's totally clear now. I guess somebody changed the text and didn't realize the implications for the graph? Seems like an easy mistake to make.
- sureshv 11y agoMaybe someone listened but it recently took 2 days to get an EV cert from Comodo via Namecheap. Some of that was probably due to having a registered company with a DNB Number - YMMV.
- nailer 11y agoIt recently took 10 minutes to get an EV cert from CertSimple: https://twitter.com/webster/status/667022550594113536 https://twitter.com/webster/status/667022550594113536 Our average validation time is five hours. Nobody else has our tech or does anything close. When they catch up to what we're doing now we'll be another year ahead.
- blfr 11y agoStartCom have given out free DV SSL for years - officially only for non-profits, but in practice for anyone who asked They would refuse to renew certificates every now and then if they deemed your use commercial though.
- mtgx 11y agoWhat about support for Certificate Transparency? Can we get that, too? Otherwise, Mozilla/EFF's CA is probably more trustworthy.
- mholt 11y agoAnd I don't know if this is much of a teaser: https://twitter.com/Namecheap/status/667348562980810752 https://twitter.com/Namecheap/status/667348562980810752 That could mean a few things, but either way, things are looking good for site owners.
- huskyr 11y agoGives a 404. Care to say what was there?
- mholt 11y agoOops, they deleted it. It was a post from Namecheap answering somebody asking if they were going to support Let's Encrypt. Original question: https://twitter.com/matbacon89/status/667348413470650370 https://twitter.com/matbacon89/status/667348413470650370 Person's response: https://twitter.com/matbacon89/status/667348648741744640 https://twitter.com/matbacon89/status/667348648741744640 In between, they _did_ say something like "You'll have to wait and see! :)" I wonder if they deleted it in light of this blog post, which I find disingenuous: https://blog.namecheap.com/ssl-from-namecheap-whats-the-difference/ https://blog.namecheap.com/ssl-from-namecheap-whats-the-diff...
- tamar 11y agoHey - so I tweeted that...and to be very clear, nothing in that tweet should have been implied as a yes. But since it was potentially construed as a yes, it was deleted to avoid confusion.
- mholt 11y agoThanks for posting here to clear things up. (Sometimes deleting tweets can cause more confusion than it removes.) Does the blog post I linked to reflect the opinion of most of Namecheap, though, really? I like Namecheap and I would be disappointed if the majority of the company believed that all free CAs will be operated like Let's Encrypt.
- edent 11y agoI wonder whether spammers and phishers will make use of that? We often tell people to look for the lock symbol or "https" - those will no longer be (weak) signifiers of trust.
- thetmkay 11y agoDV SSL certificates are not effective counter-measures for phishing or scammers. That's one of major advantages of EV certificates. EV SSL (instead of the green lock) appear as the company name in a green bar (see GitHub, Stripe etc). Almost all financial institutions use EV for any account handling (in fact I think it's technically against regulation for a CA to offer DV to those). The downside to EV is that it isn't free - the validation is much stronger and actually requires (human) resources and time to validate that the domain (and buyer of the cert) represents a government-recognized company/organization.
- toddn 11y agoProbably. Let's Encrypt has a pretty good response to that: https://letsencrypt.org/2015/10/29/phishing-and-malware.html https://letsencrypt.org/2015/10/29/phishing-and-malware.html
- joshfraser 11y agoAbout time! It's insane that CAs have gotten away with charging extortionate amounts of money for a couple paragraphs of text that cost ~nothing to generate for so long.
- rakoo 11y agoThis is all good and well, but if we take a step back it pretty much means that anybody can get a DV certificate without any verification, which means CAs are useless, which means that DV certificate offer no more guarantees about anything than self-signed certificates. Which is an excellent thing: maybe we'll finally be able to just use self-signed certificates ? And ask CAs for something where they actually can provide value, ie EV certificates, for as long as we're okay to stay with this model ? This should be a call to browser vendors: when this is more widespread, accept self-signed certificates as if they were DV certificates !
- Nullabillity 11y agoDV certificates does provide a service that self-signed certificates don't, though: they verify that the server controls x.com according to the public DNS system, not just according to the user's ISP/DNS server.
- avian 11y agoStrictly speaking, they verify that server controls x.com according to the CA's ISP/DNS server/any other parties in the middle instead of the user's ISP/DNS server/any other parties in the middle.
- austerity 11y agoThat's just not true. It changes exactly nothing in the amount of guarantees provided by a DV cert. They guarantee that you are communicating with the domain you think you are communicating with and that there is no man in the middle. Self-signed certs can't provide that guarantee. Of course there's still the question of how trustworthy are the CAs. But I don't believe them charging money for DV certs has any impact on that either.
- deleted 11y ago[deleted]
- sliverstorm 11y agoAnd here I just renewed my DV cert for three years.
- ck2 11y agonon-wildcards will be free Prepare for wildcards to cost a fortune to compensate.
- Karunamon 11y agoLet 'em. With something like Let's Encrypt that uses an API to sign domains on the fly, I'm having a hard time thinking of a use case that would be appropriate for wildcards but not appropriate for this. WC certs are already a ripoff anyways.
- Narkov 11y ago> I'm having a hard time thinking of a use case that would be appropriate for wildcards but not appropriate for this. Serving multiple sub-domains from the one IP whilst still supporting clients without SNI.
- Animats 11y agoBut to what agencies will they disclose the private keys? We need a SSL system where there's both a CA-signed key and a self-generated and self-signed key. That would prevent both forged sites and CA-assisted snooping. CA-signed alone is vulnerable to Government wiretapping. Self-signed alone is vulnerable to site spoofing. Both together would provide some real security.
- phantom784 11y agoIf the government can perform an MITM with a CA-signed key, it's not hard for them to spoof the self-signed cert. It adds no extra security.
- throwaway2048 11y agoYou can achive the exact equivilent of this today with HPKP and HSTS. CAs never see your private key, they are incapable of giving it to the NSA.
- Animats 11y agoMy bad. Thanks.
- iancarroll 11y agoThat's how the CA system currently works: you generate a key and a certificate signing request, and only disclose the public key via the CSR to the CA. The CA then uses their own key to sign yours. The CA key literally cannot be exported, and this is audited. Wiretapping is immediately evident based on the key used in any malicious certificates; HPKP helps this.
- Perceptes 11y agoIf this is true, it's far better news than Let's Encrypt ever was. I tried the Let's Encrypt beta and was extremely disappointed that getting a certificate isn't possible with DNS records—you have to do the challenge response by serving a page from the live server. This is a non-starter for many use cases. If every CA is going to be offering certs free soon, at least one of them is bound to have a real API that's not encumbered by terrible tooling.
- pfg 11y agoDNS-based challenges are coming, hopefully soon after the launch date[1]. [1]: https://community.letsencrypt.org/t/shouldnt-verification-via-dns-record-be-a-priority/604/15?u=pfg https://community.letsencrypt.org/t/shouldnt-verification-vi...
- colinbartlett 11y agoAnd yet Heroku still charges $20 per month on top of their usual fees just to host your certificate. This is why I've moved so many simple static sites to Digital Ocean droplets.