Jump to content

Let's Encrypt

Coordinates: 37°48′01″N 122°27′00″W / 37.800322°N 122.449951°W / 37.800322; -122.449951
From Wikipedia, the free encyclopedia
(Redirected from Let’s Encrypt)

Let's Encrypt
FormationNovember 18, 2014; 9 years ago (2014-11-18)
Founder
HeadquartersSan Francisco, California, U.S.
Coordinates37°48′01″N 122°27′00″W / 37.800322°N 122.449951°W / 37.800322; -122.449951
ServicesX.509 certificate authority
Parent organization
Internet Security Research Group
Budget (2019)
US$3.6 million[1]
Staff (2023)
27[2]
Websiteletsencrypt.org Edit this at Wikidata

Let's Encrypt is a non-profit certificate authority run by Internet Security Research Group (ISRG) that provides X.509 certificates for Transport Layer Security (TLS) encryption at no charge. It is the world's largest certificate authority,[3] used by more than 300 million websites,[4] with the goal of all websites being secure and using HTTPS. The Internet Security Research Group (ISRG), the provider of the service, is a public benefit organization.[5] Major sponsors include the Electronic Frontier Foundation (EFF), the Mozilla Foundation, OVH, Cisco Systems, Facebook, Google Chrome, Internet Society, AWS, NGINX, and Bill and Melinda Gates Foundation.[6] Other partners include the certificate authority IdenTrust,[7] the University of Michigan (U-M),[8] and the Linux Foundation.[9]

Overview

[edit]
Example of a website using Let's Encrypt
Example of a Let's Encrypt certificate

The mission for the organization is to create a more secure and privacy-respecting World-Wide Web by promoting the widespread adoption of HTTPS.[10] Let's Encrypt certificates are valid for 90 days, during which renewal can take place at any time.[11] This is handled by an automated process designed to overcome manual creation, validation, signing, installation, and renewal of certificates for secure websites.[12][13] The project claims its goal is to make encrypted connections to World Wide Web servers ubiquitous.[14] By eliminating payment, web server configuration, validation email management and certificate renewal tasks, it is meant to significantly lower the complexity of setting up and maintaining TLS encryption.[15]

On a Linux web server, execution of only two commands is sufficient to set up HTTPS encryption and acquire and install certificates.[16][17] To that end, a software package was included into the official Debian and Ubuntu software repositories.[18][19] Current initiatives of major browser developers such as Mozilla and Google to deprecate unencrypted HTTP are counting on the availability of Let's Encrypt.[20][21] The project is acknowledged to have the potential to accomplish encrypted connections as the default case for the entire Web.[22]

The service only issues domain-validated certificates, since they can be fully automated. Organization Validation and Extended Validation Certificates both require human validation of any registrants, and are therefore not offered by Let's Encrypt.[23] Support of ACME v2 and wildcard certificates was added in March 2018.[24] The domain validation (DV) utilized by Let's Encrypt dates back to 2002 and was at first controversial when introduced by GeoTrust before becoming a widely accepted method for the issuance of SSL certificates. [25]

By being as transparent as possible, the organization hopes to both protect its own trustworthiness and guard against attacks and manipulation attempts. For that purpose it regularly publishes transparency reports,[26] publicly logs all ACME transactions (e.g. by using Certificate Transparency), and uses open standards and free software as much as possible.[16]

History

[edit]

The Let's Encrypt project was started in 2012 by two Mozilla employees, Josh Aas and Eric Rescorla, together with Peter Eckersley at the Electronic Frontier Foundation and J. Alex Halderman at the University of Michigan. Internet Security Research Group, the company behind Let's Encrypt, was incorporated in May 2013.[8]

Let's Encrypt was announced publicly on November 18, 2014.[27]

On January 28, 2015, the ACME protocol was officially submitted to the IETF for standardization.[28] On April 9, 2015, the ISRG and the Linux Foundation declared their collaboration.[9] The root and intermediate certificates were generated in the beginning of June.[29] On June 16, 2015, the final launch schedule for the service was announced, with the first certificate expected to be issued sometime in the week of July 27, 2015, followed by a limited issuance period to test security and scalability. General availability of the service was originally planned to begin sometime in the week of September 14, 2015.[30] On August 7, 2015, the launch schedule was amended to provide more time for ensuring system security and stability, with the first certificate to be issued in the week of September 7, 2015 followed by general availability in the week of November 16, 2015.[31]

On September 14, 2015, Let's Encrypt issued its first certificate, which was for the domain helloworld.letsencrypt.org. On the same day, ISRG submitted its root program applications to Mozilla, Microsoft, Google and Apple.[32]

On October 19, 2015, the intermediate certificates became cross-signed by IdenTrust, causing all certificates issued by Let's Encrypt to be trusted by all major browsers.[7]

On November 12, 2015, Let's Encrypt announced that general availability would be pushed back and that the first public beta would commence on December 3, 2015.[33] The public beta ran from December 3, 2015[34] to April 12, 2016.[35] It launched on April 12, 2016.[36][37][5]

On March 3, 2020, Let's Encrypt announced that it would have to revoke over 3 million certificates on March 4, due to a flaw in its Certificate Authority software.[38] Through working with software vendors and contacting site operators, Let's Encrypt was able to get 1.7 million of the affected certificates renewed before the deadline. They ultimately decided not to revoke the remaining affected certificates, as the security risk was low and the certificates were to expire within the next 90 days.[39] The mass-revocation event has significantly increased the global revocation rate.[40]

In March 2020, Let's Encrypt was awarded the Free Software Foundation's annual Award for Projects of Social Benefit.[41]

On February 27, 2020, Let's Encrypt announced having issued a billion certificates.[42]

In April 2022, Let's Encrypt was awarded the Levchin Prize for “fundamental improvements to the certificate ecosystem that provide free certificates for all”.[43]

As of September 2022, Let's Encrypt reports having issued 234 million active (unexpired) certificates.[4]

Technology

[edit]

Chain of trust

[edit]

ISRG Root X1 (RSA)

[edit]

In June 2015, Let's Encrypt announced the generation of their first RSA root certificate, ISRG Root X1.[44] The root certificate was used to sign two intermediate certificates,[44] which are also cross-signed by the certificate authority IdenTrust.[7][45] One of the intermediate certificates is used to sign issued certificates, while the other is kept offline as a backup in case of problems with the first intermediate certificate.[44] Because the IdenTrust certificate was already widely trusted by major web browsers, Let's Encrypt certificates can normally be validated and accepted by relying parties[29] even before browser vendors include the ISRG root certificate as a trust anchor.

ISRG Root X2 (ECDSA)

[edit]

Let's Encrypt developers planned to generate an ECDSA root key back in 2015,[44] but then pushed back the plan to early 2016, then to 2019, and finally to 2020. On September 3, 2020, Let’s Encrypt issued six new certificates: one new ECDSA root named "ISRG Root X2", four intermediates, and one cross-sign. The new ISRG Root X2 is cross-signed with ISRG Root X1, Let's Encrypt's own root certificate. Let's Encrypt did not issue an OCSP responder for the new intermediate certificates and instead plans to rely solely on certificate revocation lists (CRLs) to recall compromised certificates and short validity periods to reduce danger of certificate compromise.[46]

ACME protocol

[edit]

The challenge–response protocol used to automate enrolling with the certificate authority is called Automated Certificate Management Environment (ACME). It can query either Web servers or DNS servers controlled by the domain covered by the certificate to be issued. Based on whether the resulting responses match the expectations, control of the enrollee over the domain is assured (domain validation). The ACME client software can set up a dedicated TLS server that gets queried by the ACME certificate authority server with requests using Server Name Indication (Domain Validation using Server Name Indication, DVSNI), or it can use hooks to publish responses to existing Web and DNS servers.

The validation processes are run multiple times over separate network paths. Checking whether DNS entries are provisioned is done from multiple geographically diverse locations to make DNS spoofing attacks harder to carry out.

ACME interactions are based on exchanging JSON documents over HTTPS connections.[47] A draft specification is available on GitHub,[48] and a version has been submitted to the Internet Engineering Task Force (IETF) as a proposal for an Internet standard.[49]

Let's Encrypt implemented its own draft of the ACME protocol. At the same time, they pushed for standardization. This led to a "proposed standard" (RFC8555) in May 2019. It introduced breaking changes and as such it has been dubbed ACMEv2. Let's Encrypt implemented the new version and started pushing existing clients into upgrades. The nudging was implemented with intermittent down-times of the ACMEv1 API. The end-of-lifetime was announced with dates and phases in "End of Life Plan for ACMEv1".[50] Since November 8, 2019, ACMEv1 no longer accepts new account registrations. Since June 2020, ACMEv1 stopped accepting new domain validations. From January 2021, ACMEv1 underwent 24-hour brownouts. The ACMEv1 API was turned off completely on June 1, 2021.[51]

Software implementation

[edit]
Domain selection dialogue

The certificate authority consists of a piece of software called Boulder, written in Go, that implements the server side of the ACME protocol. It is published as free software with source code under the terms of version 2 of the Mozilla Public License (MPL).[52] It provides a RESTful API that can be accessed over a TLS-encrypted channel.

An Apache-licensed[53] Python certificate management program called certbot (formerly letsencrypt) gets installed on the client side (the Web server of an enrollee). This is used to order the certificate, to conduct the domain validation process, to install the certificate, to configure the HTTPS encryption in the HTTP server, and later to regularly renew the certificate.[16][54] After installation and agreeing to the user license, executing a single command is enough to get a valid certificate installed. Additional options like OCSP stapling or HTTP Strict Transport Security (HSTS) can also be enabled.[47] Automatic setup initially only works with Apache and nginx.

Let's Encrypt issues certificates valid for 90 days. The reason given is that these certificates "limit damage from key compromise and mis-issuance" and encourage automation.[55]

Initially, Let's Encrypt developed its own ACME client – Certbot – as an official implementation. This has been transferred to Electronic Frontier Foundation and its name "letsencrypt" has been changed to "certbot". There is a large selection of ACME clients and projects for a number of environments developed by the community.[56]

See also

[edit]

Further reading

[edit]
  • Barnes, R.; Hoffman-Andrews, J.; McCarney, D.; Kasten, J. (March 2019). Automatic Certificate Management Environment (ACME) RFC 8555. IETF.

References

[edit]
  1. ^ Aas, Josh (December 31, 2019). "Looking Forward to 2019". Let's Encrypt. Retrieved January 26, 2019.
  2. ^ "Building A Better Internet - ISRG 2023 Annual Report" (PDF). Internet Security Research Group. December 27, 2023. Retrieved May 27, 2024.
  3. ^ "For A Better Internet - ISRG 2020 Annual Report" (PDF). Internet Security Research Group. November 17, 2020. Retrieved May 11, 2021.
  4. ^ a b "Let's Encrypt Stats - Let's Encrypt - Free SSL/TLS Certificates". letsencrypt.org. Retrieved October 1, 2022.
  5. ^ a b "About Let's Encrypt". Let's Encrypt.
  6. ^ "Current Sponsors and Funders". Let's Encrypt.
  7. ^ a b c Aas, Josh (October 19, 2015). "Let's Encrypt is Trusted".
  8. ^ a b Aas, Josh (November 18, 2014). "Let's Encrypt | Boom Swagger Boom". Boomswaggerboom.wordpress.com. Archived from the original on December 8, 2015. Retrieved January 6, 2016.
  9. ^ a b Kerner, Sean Michael (April 9, 2015). "Let's Encrypt Becomes Linux Foundation Collaborative Project". eWeek. QuinStreet Enterprise.[permanent dead link‍]
  10. ^ "Let's Encrypt - FAQ". Let's Encrypt. Retrieved May 11, 2021.
  11. ^ "Why ninety-day lifetimes for certificates? - Let's Encrypt". letsencrypt.org. Retrieved September 5, 2021.
  12. ^ Kerner, Sean Michael (November 18, 2014). "Let's Encrypt Effort Aims to Improve Internet Security". eWeek.com. Quinstreet Enterprise. Archived from the original on December 13, 2016. Retrieved February 27, 2015.
  13. ^ Eckersley, Peter (November 18, 2014). "Launching in 2015: A Certificate Authority to Encrypt the Entire Web". Electronic Frontier Foundation. Retrieved February 27, 2015.
  14. ^ "How It Works". Let's Encrypt. Retrieved July 9, 2016.
  15. ^ Tung, Liam (November 19, 2014). "EFF, Mozilla to launch free one-click website encryption". ZDNet. CBS Interactive.
  16. ^ a b c Fabian Scherschel (November 19, 2014). "Let's Encrypt: Mozilla und die EFF mischen den CA-Markt auf" (in German). heise.de.
  17. ^ Marvin, Rob (November 19, 2014). "EFF wants to make HTTPS the default protocol". Software Development Times. BZ Media. Archived from the original on June 17, 2016. Retrieved May 27, 2019.
  18. ^ Marier, Francois (January 1, 2015). "ITP: letsencrypt – Let's Encrypt client that can update Apache configurations". Debian Bug report logs.
  19. ^ "python-letsencrypt". Debian Package Tracker. May 27, 2015.
  20. ^ Barnes, Richard (April 30, 2015). "Deprecating Non-Secure HTTP". Mozilla Security Blog. Mozilla.
  21. ^ "Marking HTTP As Non-Secure". The Chromium Projects.
  22. ^ Moody, Glyn (November 25, 2014). "The Coming War on Encryption, Tor, and VPNs". Computerworld UK. IDG UK.
  23. ^ Vaughan-Nichols, Steven J. (April 9, 2015). "Securing the web once and for all: The Let's Encrypt Project". ZDNet. CBS Interactive.
  24. ^ Aas, Josh (March 13, 2018). "ACME v2 and Wildcard Certificate Support is Live". Let's Encrypt. Retrieved May 24, 2018.
  25. ^ "There's certs and certs – VeriSign badmouths rivals". www.theregister.com. Retrieved August 20, 2020.
  26. ^ Zorz, Zeljka (July 6, 2015). "Let's Encrypt CA releases transparency report before its first certificate". Help Net Security.
  27. ^ Joseph Tsidulko (November 18, 2014). "Let's Encrypt, A Free And Automated Certificate Authority, Comes Out Of Stealth Mode". crn.com. Retrieved August 26, 2015.
  28. ^ History for draft-barnes-acme
  29. ^ a b Reiko Kaps (June 5, 2015). "Let's Encrypt: Meilenstein zu kostenlosen SSL-Zertifikaten für alle" (in German). heise.de.
  30. ^ Josh Aas (June 16, 2015). "Let's Encrypt Launch Schedule". letsencrypt.org. Let's Encrypt. Retrieved June 19, 2015.
  31. ^ "Updated Let's Encrypt Launch Schedule". August 7, 2015.
  32. ^ Michael Mimoso. "First Let's Encrypt Free Certificate Goes Live". Threatpost.com, Kaspersky Labs. Retrieved September 16, 2015.
  33. ^ "Public Beta: December 3, 2015". November 12, 2015.
  34. ^ "Entering Public Beta - Let's Encrypt - Free SSL/TLS Certificates". Let's Encrypt. December 3, 2015. Retrieved January 6, 2016.
  35. ^ "Let's Encrypt Leaves Beta". LinuxFoundation.org. Archived from the original on April 15, 2016. Retrieved April 17, 2016.
  36. ^ Josh Aas; ISRG Executive Director. "Leaving Beta, New Sponsors". EFF. Retrieved April 12, 2016.
  37. ^ Catalin Cimpanu. "Let's Encrypt Launched Today, Currently Protects 3.8 Million Domains". Softpedia News. Retrieved April 12, 2016.
  38. ^ "Revoking certain certificates on March 4". March 3, 2020. Retrieved March 4, 2020.
  39. ^ Barrett, Brian (March 9, 2020). "The Internet Avoided a Minor Disaster Last Week". Wired. Conde Nast. Retrieved May 12, 2020.
  40. ^ Korzhitskii, Nikita; Carlsson, Niklas (2021). Revocation Statuses on the Internet. arXiv:2102.04288. {{cite book}}: |work= ignored (help)
  41. ^ Let's Encrypt, Jim Meyering, and Clarissa Lima Borges receive FSF's 2019 Free Software Awards Free Software Foundation, 2020
  42. ^ "Let's Encrypt Has Issued a Billion Certificates - Let's Encrypt - Free SSL/TLS Certificates". letsencrypt.org. Retrieved April 3, 2021.
  43. ^ "The Levchin Prize for Real-World Cryptography". Real World Crypto Symposium. International Association for Cryptologic Research. Retrieved April 9, 2024.
  44. ^ a b c d Aas, Josh (June 4, 2015). "Let's Encrypt Root and Intermediate Certificates". Let's Encrypt.
  45. ^ Reiko Kaps (June 17, 2015). "SSL-Zertifizierungsstelle Lets Encrypt will Mitte September 2015 öffnen" (in German). heise.de.
  46. ^ Gable, Aaron (September 17, 2020). "Let's Encrypt's New Root and Intermediate Certificates". Let's Encrypt. Retrieved September 22, 2020.
  47. ^ a b Brook, Chris (November 18, 2014). "EFF, Others Plan to Make Encrypting the Web Easier in 2015". Threatpost: The Kaspersky Lab Security News Service.
  48. ^ "Draft ACME specification". GitHub. May 6, 2020.
  49. ^ Barnes, Richard; Eckersley, Peter; Schoen, Seth; Halderman, Alex; Kasten, James (January 28, 2015). "Automatic Certificate Management Environment (ACME) draft-barnes-acme-01". Network Working Group.
  50. ^ "End of Life Plan for ACMEv1". Let's Encrypt Community Support. March 11, 2019. Retrieved August 20, 2020.
  51. ^ "End of Life Plan for ACMEv1 - API Announcements". Let's Encrypt Community Support. May 5, 2021. Retrieved May 12, 2021.
  52. ^ letsencrypt. "boulder/LICENSE.txt at master · letsencrypt/boulder · GitHub". Github.com. Retrieved January 6, 2016.
  53. ^ letsencrypt (November 23, 2015). "letsencrypt/LICENSE.txt at master · letsencrypt/letsencrypt · GitHub". Github.com. Retrieved January 6, 2016.
  54. ^ Sanders, James (November 25, 2014). "Let's Encrypt initiative to provide free encryption certificates". TechRepublic. CBS Interactive.
  55. ^ Aas, Josh (November 9, 2015). "Why ninety-day lifetimes for certificates?". Let's Encrypt. Retrieved June 26, 2016.
  56. ^ "ACME Client Implementations - Let's Encrypt - Free SSL/TLS Certificates". letsencrypt.org. Retrieved August 20, 2020.
[edit]
Wikimedia Commons has media related to Let's Encrypt.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Let%27s_Encrypt&oldid=1247852572"