In case you've been in a cave, you may not have noticed Web security is a mess. Gmail had fits this weekend with sending mail because the mail server tasked with sending messages had an expired security certificate. Before that, a Secure-Socket Layer (SSL) encryption problem that had been hiding in the code since the 1990s opened the door to the FREAK security hole. It's clear the industry needs to get its act together when it comes to web site encryption. The Internet Security Research Group (ISRG) with its Let's Encrypt project wants to give us that fix.The ISRG's membership includes Akamai, Cisco, Electronic Frontier Foundation (EFF), and Mozilla; the group is being managed by The Linux Foundation. The group's purpose with its Let's Encrypt program is to provide free, automated and open security certificate authority (CA) for everyone's benefit. Let's Encrypt will allow website owners to obtain security certificates within minutes, enabling a safer web experience for all.
We've known since 2010 when Firesheep demonstrated your login could be stolen over Wi-Fi that the only way to have reliable security is for every website to be encrypted. One reason why this hasn't happened is that Transport Layer Security (TLS) certificates are both expensive and cumbersome to administer.
So, late last year the EFF and Mozilla came with the idea of a free one-click TLS CA. Today, it's getting closer to reality.
"Encryption should be the default for the web," said Josh Aas, the ISRG's executive director and senior technology strategist at Mozilla in a statement. "The web is a complicated place these days; it's difficult for consumers to be in control of their data. The only reliable strategy for making sure that everyone's private data and information is protected while in transit over the web is to encrypt everything. Let's Encrypt simplifies this."
Once in place in mid-2015, Let's Encrypt will make enabling HTTPS for your site as easy as installing software on the server. In Linux, for example, it would look like this
$ sudo apt-get install lets-encrypt $ lets-encrypt example.com
And, that would be all there is to it. The now secure site, https://example.com, would be live immediately.
The Let's Encrypt management software uses Automated Certificate Management Environment (ACME) to enable you to do the following:
Less technically, the key principles behind Let's Encrypt are:
That may sound great to most of you. I like it. But I suspect one group isn't going to care for this at all: The commercial CAs such as Comodo, Symantec, and GoDaddy.
It's likely they will argue that the kind of SSL/TLS certificates that Let's Encrypt will provide won't be good enough. There are three levels of SSL certificates: Domain Validated (DV), Organization Validated (OV) and Extended Validation (EV). Let's Encrypt will provide only DV certifications.
For an OV cert, the CA must check with third parties to ensure that the name of the applying organization is the same as the domain's owner. For an EV cert, you need to prove that your business, agency, or organization really is who it says it is. It's only with EV certification that web browser's address bars turn green to show that the site is both secure and that it belongs to its claimed owner.
For the CA businesses this means their high-end services are unlikely to be damaged by ISRG's efforts. For companies that rely upon cheap, $4.95 a year SSL certificates, it will be a different story.