November 20th, 2024

Let's not Encrypt

The article critiques Let's Encrypt for creating a false sense of security, highlighting issues with certificate verification, automatic renewals, short validity, and concerns about its funding and long-term viability.

Read original articleLink Icon
Let's not Encrypt

The article critiques Let's Encrypt, an organization that provides free SSL certificates, arguing that it creates a false sense of security for website owners. The author highlights several issues, including the ease of certificate verification, which can be exploited by attackers, and the automatic renewal process that poses security risks. The author also points out that Let's Encrypt certificates are only valid for three months, leading to a burdensome renewal process that can disrupt website operations. Furthermore, the article suggests that the reliance on Let's Encrypt undermines the development of more robust security solutions and that the organization is funded by competitors, raising concerns about its long-term viability. The author concludes that the current system is flawed and that users are better off seeking alternative methods for securing their websites, as the existing model is unsustainable and potentially harmful.

- Let's Encrypt certificates may not provide the intended security against man-in-the-middle attacks.

- The automatic renewal process for Let's Encrypt certificates poses significant security risks.

- The short validity period of certificates leads to a cumbersome renewal process for website owners.

- The reliance on Let's Encrypt may hinder the development of better security solutions in the industry.

- The funding model of Let's Encrypt raises concerns about its independence and long-term sustainability.

Link Icon 4 comments
By @mrkeen - about 2 months
> what to do about it

> Not this time. The technical problems are easy to solve. For decades, users of SSH have had a system (save the certificate permanently the first time you connect, and warn if it ever changes) that is optimal in a sense

It's a fundamental problem, not easy to solve. And the Letsencrypt strategy already does things the SSH way: trust blindly on the first time (thus being vulnerable to MITM), and if you were not MITM'd the first time, then you're pretty safe during future connections.

Certbot just automates the "trust blindly" part because configuring a web server cert is a little more complicated than an invocation of ssh.

In fact, if we really did things the SSH way, it would be each user blindly trusting each website for the first visit.

By @zoezoezoezoe - about 2 months
The web is intrinsically a patch job, continually worsening year after year. Encryption solves more than just a MiTM attack, and I always thought it was to avoid snooping from bad actors, but realistically, if a bad actor is in a position where they can MiTM, you are fucked. Network snooping is largely eliminated however thanks to the way that public key encryption (aka what SSL is) works. The entirety of the web relies of the security of the few for the security of the many, and there's nothing you can do about it, and if you dont like it, that's a shame, nothing is going to compel google or microsoft to change anything.
By @keikobadthebad - about 2 months
> Update 2023-11-05 Yeah, I've got an LE cert now. And I don't want to talk about it.

You can still get paid certs, but the max validity period is shrinking, to 45 days in 2027 https://blog.nameshield.com/blog/2024/10/17/ssl-tls-certific...