News for hackers. Stuff that matters.
Re:Letsencrypt will kill SMTP server auth following Chrome C... by londons_explore on Friday May 16, 2025 @09:07AM (#44005024)
I assume the reasoning for the policy change is that allowing a single certificate to be used for many different uses puts a greater risk of the certificate private key being leaked.

They don't want your insecure mail server software to put your secure web server at risk.

Re:Letsencrypt will kill SMTP server auth following Chrome C... by its-summertime on Friday May 16, 2025 @12:17PM (#44007204)
That's not whats happening, its the root certificates that the change applies to, e.g. lets encrypt, regardless of their views, can no longer use the same infrastructure to sign certs for anything other than TLS Server Authentication, lest they wish to see google's ire.
Re:Letsencrypt will kill SMTP server auth following Chrome C... by dandanio on Friday May 16, 2025 @09:55AM (#44005586)
If you can't secure your mail server, you certainly can't secure your web server. Letsencrypt, please rethink your decision!
Re:Letsencrypt will kill SMTP server auth following Chrome C... by arccy on Friday May 16, 2025 @10:56AM (#44006276)
most smtp servers don't use client certs, there's almost nothing that requires their clients to use client cert auth.

mail servers will continue working along just fine.

Re:Letsencrypt will kill SMTP server auth following Chrome C... by dlgeek on Friday May 16, 2025 @10:32AM (#44005985)
They don't have a choice - the decision comes from Chrome's root program and if they don't comply, LetsEncrypt would be distrusted by Chrome.
Re:Letsencrypt will kill SMTP server auth following Chrome C... by Attrecomet on Friday May 16, 2025 @10:35AM (#44006016)
Is it really that clear that Google has more power here? Whom would users blame if suddenly half their pages are falsely accused of being "untrusted"? Probably the browser, not LE, right?
Re:Letsencrypt will kill SMTP server auth following Chrome C... by phasmantistes on Friday May 16, 2025 @11:38AM (#44006741)
That's not leverage that a CA can use. If half the internet suddenly displays TLS warning interstitials, it doesn't make people mad at the CA, and it doesn't make people mad at their browser: it just _trains them to ignore such warnings_. That's a bad outcome all around, and one that a CA whose core purpose is improving security for end-users cannot condone.