Jump to content

Let's Encrypt: Difference between revisions

Coordinates: 37°48′01″N 122°27′00″W / 37.800322°N 122.449951°W / 37.800322; -122.449951
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Rescuing 0 sources and tagging 1 as dead. #IABot (v2.0beta10ehf1)
Line 241: Line 241:
<ref name="transparency report">{{cite web |first=Zeljka |last=Zorz |website=Help Net Security |date=July 6, 2015 |url=//www.helpnetsecurity.com/2015/07/06/lets-encrypt-ca-releases-transparency-report-before-its-first-certificate/ |title=Let's Encrypt CA releases transparency report before its first certificate }}</ref>
<ref name="transparency report">{{cite web |first=Zeljka |last=Zorz |website=Help Net Security |date=July 6, 2015 |url=//www.helpnetsecurity.com/2015/07/06/lets-encrypt-ca-releases-transparency-report-before-its-first-certificate/ |title=Let's Encrypt CA releases transparency report before its first certificate }}</ref>


<ref name="ISRG-LF">{{cite web |first=Sean Michael |last=Kerner |website=eWeek |date=April 9, 2015 |url=//www.eweek.com/security/lets-encrypt-becomes-linux-foundation-collaborative-project.html |title=Let's Encrypt Becomes Linux Foundation Collaborative Project |publisher=QuinStreet Enterprise }}</ref>
<ref name="ISRG-LF">{{cite web |first=Sean Michael |last=Kerner |website=eWeek |date=April 9, 2015 |url=//www.eweek.com/security/lets-encrypt-becomes-linux-foundation-collaborative-project.html |title=Let's Encrypt Becomes Linux Foundation Collaborative Project |publisher=QuinStreet Enterprise }}{{Dead link|date=December 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>


<ref name="ZDNet20150409">{{cite web |first=Steven J. |last=Vaughan-Nichols |website=ZDNet |date=April 9, 2015 |url=//www.zdnet.com/article/securing-the-web-once-and-for-all-the-open-encryption-project/ |title=Securing the web once and for all: The Let's Encrypt Project |publisher=CBS Interactive }}</ref>
<ref name="ZDNet20150409">{{cite web |first=Steven J. |last=Vaughan-Nichols |website=ZDNet |date=April 9, 2015 |url=//www.zdnet.com/article/securing-the-web-once-and-for-all-the-open-encryption-project/ |title=Securing the web once and for all: The Let's Encrypt Project |publisher=CBS Interactive }}</ref>

Revision as of 14:00, 12 December 2018

Let's Encrypt
FormationNovember 18, 2014; 10 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
BudgetUS$2.91 million[1] (in 2017)
Staff8[1] (in 2016)
Websiteletsencrypt.org Edit this at Wikidata

Let's Encrypt is a certificate authority that provides X.509 certificates for Transport Layer Security (TLS) encryption at no charge. The certificate is valid for 90 days, during which renewal can take place at anytime. The offer is accompanied by an automated process designed to overcome manual creation, validation, signing, installation, and renewal of certificates for secure websites.[2][3] It launched on April 12, 2016.[4][5]

The project claims to make encrypted connections to World Wide Web servers ubiquitous.[6] 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.[7] On a Linux web server, execution of only two commands is sufficient to set up HTTPS encryption and acquire and install certificates.[8][9]

To that end, a software package was included into the official Debian and Ubuntu software repositories.[10][11] Current initiatives of major browser developers such as Mozilla and Google to deprecate unencrypted HTTP are counting on the availability of Let's Encrypt.[12][13] The project is acknowledged to have the potential to accomplish encrypted connections as the default case for the entire web.[14]

Only domain-validated certificates are being issued, since they can be fully automated. Organization Validation and Extended Validation Certificates are not available.[15]

By being as transparent as possible, they hope to both protect their own trustworthiness and guard against attacks and manipulation attempts. For that purpose they regularly publish transparency reports,[16] publicly log all ACME transactions (e.g. by using Certificate Transparency), and use open standards and free software as much as possible.[8]

Support of ACME v2 and wildcard certificates was added in March 2018.[17]

Involved parties

Let's Encrypt is a service provided by the Internet Security Research Group (ISRG), a public benefit organization. Major sponsors are the Electronic Frontier Foundation (EFF), the Mozilla Foundation, OVH, Akamai, and Cisco Systems. Other partners include the certificate authority IdenTrust, the University of Michigan (U-M), the Stanford Law School, the Linux Foundation[18] as well as Stephen Kent from Raytheon/BBN Technologies and Alex Polvi from CoreOS.[8]

Technical Advisory Board

Technology

In June 2015, Let's Encrypt announced the generation of their first RSA root certificate, ISRG Root X1.[19] The root certificate was used to sign two intermediate certificates[19], which are also cross-signed by the certificate authority IdenTrust.[20][21] 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.[19] Because the IdenTrust certificate is preinstalled in major web browsers, Let's Encrypt certificates can normally be validated and are accepted upon installation[22] even before browser vendors include the ISRG root certificate as a trust anchor.

The Let's Encrypt developers planned to generate an ECDSA root certificate as well later in 2015,[19] which was pushed back to early 2016, and again to 2018.[23][24][25]

Protocol

The challenge–response protocol used to automate enrolling with this new certificate authority is called Automated Certificate Management Environment (ACME). It involves various requests to the web server on the domain that is covered by the certificate. Based on whether the resulting responses match the expectations, control of the enrollee over the domain is assured (domain validation). In order to do that, the ACME client software sets up a special TLS server on the server system that gets queried by the ACME certificate authority server with special requests using Server Name Indication (Domain Validation using Server Name Indication, DVSNI).

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

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

Software implementation

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).[29] It provides a RESTful API that can be accessed over a TLS-encrypted channel.

An Apache-licensed[30] 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.[8][31] 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.[26] 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.[32] The official certbot client and most of the third-party clients allow automation of the certificate renewal.

Example of a website with Let's Encrypt certificate

Several third-party client implementations in several languages were created by the community.[33]

History

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.[34]

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

On January 28, 2015, the ACME protocol was officially submitted to the IETF for standardisation.[36] On April 9, 2015, the ISRG and the Linux Foundation declared their collaboration.[18] The root and intermediate certificates were generated in the beginning of June.[22] 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.[37] 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.[38] The cross-signature from IdenTrust is planned to be available when Let's Encrypt opens for the public.[21]

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.[39]

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.[20]

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.[40] The public beta ran from December 3, 2015[41] to April 12, 2016.[42]

Certificates issued

Date Certificates issued
March 8, 2016 1 million[43]
April 21, 2016 2 million[44]
June 3, 2016 4 million[45]
June 22, 2016 5 million[*][46]
September 9, 2016 10 million[47]
November 27, 2016 20 million[48]
December 12, 2016 24 million[49]
June 28, 2017 100 million[50]
August 6, 2018 115 million[51]
September 14, 2018 380 million[52]

[*] Of which 3.8 million are unexpired and unrevoked. Their active certificates cover more than 7 million unique domains, in part due to support by large hosting companies.

See also

Further reading

  • Barnes, R.; Hoffman-Andrews, J.; Kasten, J. (June 21, 2017). Automatic Certificate Management Environment (ACME) draft-ietf-acme-acme-07. IETF. I-D draft-ietf-acme-acme-07. Retrieved September 17, 2017.

References

  1. ^ a b Aas, Josh (September 20, 2016). "What It Costs to Run Let's Encrypt". Let's Encrypt. Retrieved December 12, 2017.
  2. ^ Kerner, Sean Michael (November 18, 2014). "Let's Encrypt Effort Aims to Improve Internet Security". eWeek.com. Quinstreet Enterprise. Retrieved February 27, 2015.
  3. ^ Eckersley, Peter (November 18, 2014). "Launching in 2015: A Certificate Authority to Encrypt the Entire Web". Electronic Frontier Foundation. Retrieved February 27, 2015.
  4. ^ Josh Aas; ISRG Executive Director. "Leaving Beta, New Sponsors". EFF. Retrieved April 12, 2016.
  5. ^ Catalin Cimpanu. "Let's Encrypt Launched Today, Currently Protects 3.8 Million Domains". Softpedia News. Retrieved April 12, 2016.
  6. ^ "How It Works". Let's Encrypt. Retrieved July 9, 2016.
  7. ^ Tung, Liam (November 19, 2014). "EFF, Mozilla to launch free one-click website encryption". ZDNet. CBS Interactive.
  8. ^ a b c d Fabian Scherschel (November 19, 2014). "Let's Encrypt: Mozilla und die EFF mischen den CA-Markt auf" (in German). heise.de.
  9. ^ Marvin, Rob (November 19, 2014). "EFF wants to make HTTPS the default protocol". Software Development Times. BZ Media LLC. Archived from the original on June 17, 2016. {{cite web}}: Unknown parameter |dead-url= ignored (|url-status= suggested) (help)
  10. ^ Marier, Francois (January 1, 2015). "ITP: letsencrypt – Let's Encrypt client that can update Apache configurations". Debian Bug report logs.
  11. ^ "python-letsencrypt". Debian Package Tracker. May 27, 2015.
  12. ^ Barnes, Richard (April 30, 2015). "Deprecating Non-Secure HTTP". Mozilla Security Blog. Mozilla.
  13. ^ "Marking HTTP As Non-Secure". The Chromium Projects.
  14. ^ Moody, Glyn (November 25, 2014). "The Coming War on Encryption, Tor, and VPNs". Computerworld UK. IDG UK.
  15. ^ Vaughan-Nichols, Steven J. (April 9, 2015). "Securing the web once and for all: The Let's Encrypt Project". ZDNet. CBS Interactive.
  16. ^ Zorz, Zeljka (July 6, 2015). "Let's Encrypt CA releases transparency report before its first certificate". Help Net Security.
  17. ^ Aas, Josh (March 13, 2018). "ACME v2 and Wildcard Certificate Support is Live". Let's Encrypt. Retrieved May 24, 2018.
  18. ^ a b Kerner, Sean Michael (April 9, 2015). "Let's Encrypt Becomes Linux Foundation Collaborative Project". eWeek. QuinStreet Enterprise.[permanent dead link‍]
  19. ^ a b c d Aas, Josh (June 4, 2015). "Let's Encrypt Root and Intermediate Certificates". Let's Encrypt.
  20. ^ a b Aas, Josh (October 19, 2015). "Let's Encrypt is Trusted".
  21. ^ a b Reiko Kaps (June 17, 2015). "SSL-Zertifizierungsstelle Lets Encrypt will Mitte September 2015 öffnen" (in German). heise.de.
  22. ^ a b Reiko Kaps (June 5, 2015). "Let's Encrypt: Meilenstein zu kostenlosen SSL-Zertifikaten für alle" (in German). heise.de.
  23. ^ "Certificates". Let's Encrypt. Archived from the original on December 3, 2015.
  24. ^ Aas, Josh (August 13, 2015). "Elliptic Curve Cryptography (ECC) Support". Let's Encrypt. Archived from the original on December 12, 2015. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  25. ^ "Certificates". Let's Encrypt. Archived from the original on October 9, 2017.
  26. ^ 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.
  27. ^ "Draft ACME specification". GitHub.
  28. ^ 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.
  29. ^ letsencrypt. "boulder/LICENSE.txt at master · letsencrypt/boulder · GitHub". Github.com. Retrieved January 6, 2016.
  30. ^ letsencrypt (November 23, 2015). "letsencrypt/LICENSE.txt at master · letsencrypt/letsencrypt · GitHub". Github.com. Retrieved January 6, 2016.
  31. ^ Sanders, James (November 25, 2014). "Let's Encrypt initiative to provide free encryption certificates". TechRepublic. CBS Interactive.
  32. ^ Aas, Josh (November 9, 2015). "Why ninety-day lifetimes for certificates?". Let's Encrypt. Retrieved June 26, 2016.
  33. ^ "Let's Encrypt - Documentation".
  34. ^ Aas, Josh (November 18, 2014). "Let's Encrypt | Boom Swagger Boom". Boomswaggerboom.wordpress.com. Retrieved January 6, 2016.
  35. ^ 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.
  36. ^ History for draft-barnes-acme
  37. ^ Josh Aas (June 16, 2015). "Let's Encrypt Launch Schedule". letsencrypt.org. Let's Encrypt. Retrieved June 19, 2015.
  38. ^ "Updated Let's Encrypt Launch Schedule". August 7, 2015.
  39. ^ Michael Mimoso. "First Let's Encrypt Free Certificate Goes Live". Threatpost.com, Kaspersky Labs. Retrieved September 16, 2015.
  40. ^ "Public Beta: December 3, 2015". November 12, 2015.
  41. ^ "Entering Public Beta - Let's Encrypt - Free SSL/TLS Certificates". Let's Encrypt. December 3, 2015. Retrieved January 6, 2016.
  42. ^ "Let's Encrypt Leaves Beta". LinuxFoundation.org. Archived from the original on April 15, 2016. Retrieved April 17, 2016. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  43. ^ Aas, Josh (March 8, 2016). "Our Millionth Certificate - Let's Encrypt - Free SSL/TLS Certificates". letsencrypt.org. Retrieved March 15, 2016.
  44. ^ "Let's Encrypt Reaches 2,000,000 Certificates". April 22, 2016. Retrieved September 24, 2016.
  45. ^ "Let's Encrypt Stats". letsencrypt.org. June 5, 2016. Retrieved June 5, 2016.
  46. ^ "Progress Towards 100% HTTPS, June 2016". letsencrypt.org. June 24, 2016. Retrieved June 22, 2016.
  47. ^ Let's Encrypt [@letsencrypt] (September 9, 2016). "We've now issued more than 10 million certificates" (Tweet). Retrieved September 24, 2016 – via Twitter.
  48. ^ Let's Encrypt [@letsencrypt] (November 27, 2016). "We've issued 20M+ certificates!" (Tweet). Retrieved November 27, 2016 – via Twitter.
  49. ^ Let's Encrypt [@letsencrypt] (December 12, 2016). "Just over 1 year ago, we issued our first cert. Today, 24M+ and climbing!" (Tweet). Retrieved January 18, 2017 – via Twitter.
  50. ^ "Milestone: 100 Million Certificates Issued - Let's Encrypt - Free SSL/TLS Certificates". letsencrypt.org. Retrieved July 2, 2017.
  51. ^ "Let's Encrypt Root Trusted By All Major Root Programs". letsencrypt.org. Retrieved September 11, 2018.
  52. ^ "Let's Encrypt on Twitter". Twitter. Retrieved September 16, 2018.
Wikimedia Commons has media related to Let's Encrypt.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Let%27s_Encrypt&oldid=873325522"