Let's Encrypt, the non-profit, community-controlled certification center that provides free certificates to all interested parties, summarized last year's results and discussed plans for 2019.
In 2018, the percentage of page requests over HTTPS increased from 67% to 77%. The Let's Encrypt project issued 87 million certificates covering approximately 150 million domains (a year ago, 61 million domains were covered, and growth was expected to reach 120 million by the end of 2018).
In 2019, the service plans to overcome the barrier of 120 million active certificates and 215 million sites.
About Let's Encrypt
The project aims to make encrypted connections to servers by eliminating payment, web server configuration, email validation management, and certificate renewal tasks, which is intended to significantly reduce the complexity of setting up and maintaining TLS encryption.
On a Linux web server, running two commands is enough to configure HTTPS encryption and acquire and install certificates within 20 to 30 seconds.
For this, a software package was included in the official Debian software repositories. Current efforts by major browser developers such as Mozilla and Google to disregard unencrypted HTTP are counting on the availability of Let's Encrypt.
What Let's Encrypt has for this year
In 2019, it is planned to introduce a multi-element verification system, in which the confirmation of the authority to receive a certificate for a domain is done through various verifications performed from geographically distributed subnets linked to different autonomous systems.
This system will minimize the risks of obtaining certificates for other people's domains by carrying out targeted attacks that redirect traffic through the substitution of fictitious routes through BGP.
When using a multipoint verification system, an attacker will have to simultaneously achieve re-routing of routes for several autonomous provider systems with different uplinks, which is much more complicated than re-routing a single route.
Of the other plans, the formation of the public magazine Transparency of certificates (CT) stands out, in which all the certificates issued will be reflected.
The public registry will provide the opportunity to conduct an independent audit of all changes and actions of the certification center.

To protect against data corruption in hindsight when stored in the Certificate Transparency record, a Merkle Tree structure is used, in which each branch checks all underlying branches and nodes for set (tree) hashing.
By having a final hash, the user can verify the correctness of all the history of operations, as well as the correctness of the past states of the database (the root verification hash of the new state of the database is calculated taking into account the past state).
Let's Encrypt wants to expand its certificates
In the next year, it is also planned to put into operation the root and intermediate certificates created with the ECDSA algorithm, more efficient than the RSA currently used.
The plans also mention preparing the nginx module to automate the receipt and maintenance of certificates using the ACME protocol (Automatic Certificate Management Environment).
Last year, a similar module was already included in Apache httpd.
Let's Encrypt's current server infrastructure processes approximately 5.5 billion requests per day. A 40% increase in load is projected for 2019.
The team is located in two data centers. Servers, storage, HSMs, switches, and firewalls occupy 55 units in racks.
The infrastructure is maintained by a team of six engineers who are employed full-time. In 2019, faster storage systems for servers with DBMS are planned to be introduced.
The projected budget for 2019 will be $ 3.6 million, which is $ 600,000 more than the 2018 budget.
The funds are raised primarily through financial assistance from major sponsors such as Cisco, OVH, Mozilla, Google Chrome, the Electronic Frontier Foundation, and the Internet Society.
Table of Contents