Let’s Encrypt: Why Create a Free, Automated, and Open CA?

14

During the summer of 2012, Eric Rescorla and I decided to start a Certificate Authority (CA). A CA acts as a third-party to issue digital certificates, which certify public keys for certificate holders. The free, automated, and open CA we envisioned, which came to be called Let’s Encrypt, has been built and is now one of the larger CAs in the world in terms of issuance volume.

Starting a new CA is a lot of work—it’s not a decision to be made lightly. In this article, I’ll explain why we decided to start Let’s Encrypt, and why we decided to build a new CA from scratch.

We had a good reason to start building Let’s Encrypt back in 2012. At that time, work on an HTTP/2 specification had started in the Internet Engineering Task Force (IETF), a standards body with a focus on network protocols. 

Read more at OpenSource.com