"Let's Encrypt" Project To Issue First Free Digital Certificates Next Month
An anonymous reader writes: Let's Encrypt, the project that hopes to increase the use of encryption across websites by issuing free digital certificates, is planning to issue the first ones next month. Backed by the EFF, the Mozilla Foundation, the Linux Foundation, Akamai, IdenTrust, Automattic, and Cisco, Let's Encrypt will provide free-of-charge SSL and TSL certificates to any webmaster interested in implementing HTTPS for their products. The Stack reports: "Let's Encrypt's root certificate will be cross-signed by IdenTrust, a public key CA owned by smartphone government ID card provider HID Global. Website operators are generally hesitant to use SSL/TLS certificates due to their cost. An extended validation (EV) SSL certificates can cost up to $1,000. It is also a complication for operators to set up encryption for larger web services. Let's Encrypt aims to remove these obstacles by eliminating the related costs and automating the entire process."
StartSSL has already been doing this. I believe Let's Encrypt real goal is to make the deployment and unkeep easier?
I wonder how this differs from the existing free offerings provided by cacert.org.
There is still the problem of shared hosting where they force you to use their own certificates which aren't free.
Let's Encrypt, a division of Shell Company, LLC., a wholly-owned subsidiary of Totally Not The NSA, Inc.
That's a new one!
Why should I trust that?
“He’s not deformed, he’s just drunk!”
Slashdot could cough up the money for an SSL cert. So why isn't all Slashdot traffic encrypted then?
Akamai and Cisco are involved. Your data will be "safe" and not shared with anyone, except everyone.
Maybe it will be enough to get you guys at Slashdot to do it! ;-)
How do they verify you're not hijacking a Web site? What if you block HTTPS (there's no https server!) and submit CSR, and it tries to verify a cookie on the associated HTTP site, which you're MITM and so replace by inserting your cookie?
Support my political activism on Patreon.
You can get cheap certs or roll your own. People aren't doing SSL because it's "hard" and you need a smidgen of attention to detail.
I don't see how cost is an issue nowadays. At $5 a year anyone with a domain name and hosting can easily afford that. EV's are $150 a yr, not cost prohibitive for those that need them. Let's Encrypt doesn't even support EV so not sure why it is even brought up as a comparison.
The convenience of Let's Encrypt is nice however I don't see how most people can take advantage of this. It is a proxy daemon running on the server. So it needs to be installed and configured by the administrator of said server. It also takes over port 443 as a proxy adding extra overhead but more importantly a layer of insecure transmission.
I would like to see it (and I'm sure we will) as a cPanel and Plesk addon so users can easily add their certificates to their servers current configuration. Then I will see it as being very useful to the majority of people that don't have SSL certificates already installed. Since it is not the cost, but ease of use.
Regular SSL certificates aren't that expensive. The EV certs are a ripoff. Unfortunately, Lets Encrypt will not support EV.
Where the VPS wins is that you have your own IP
How many people can have a VPS at the same time when we're already essentially out of IPv4 addresses?
Because historically, ad networks have not supported TLS. Running HTTP ads on an HTTPS site will get blocked as "mixed active content". The first major ad network to deploy TLS was Google AdSense in September 2013, roughly thirteen years after SSL/TLS entered the public domain. Slashdot used to offer subscriptions and make HTTPS available to subscribers, but those are no longer available for some vague reason.
The ad network that Slashdot uses would have to support HTTPS first.
Let's Encrypt is a good idea but there should be a larger equivalent choice of roots to choose from.
Hopefully there is nothing stopping other CA's using a similar method of certificate distribution.
Having the majority of certificates rooted to the same supplier is a governments/spooks wet dream.
letsencrypt my.domain with my.ca
... a free PSK.
now we need to go OSS in diesel cars
"Let’s Encrypt’s root certificate will be cross-signed by ..." i was expecting "NSA".
now we need to go OSS in diesel cars
Seriously? What are they contributing? Proprietary blobs? Screen Doors?
Can these certs be used for S/MIME authentication, or could they be used to generate personal certs for S/MIME?
We're started using S/MIME extensively at my office, and I'd like to be able to do it at home... it seems significantly easier than using PGP.
- chrish