Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/mhoye/statuses/114518058342998577">mhoye (mhoye@mastodon.social)'s status on Friday, 16-May-2025 23:49:10 JST</a><a href="https://mastodon.social/@mhoye" title="mhoye@mastodon.social"><img src="https://gnusocial.jp/avatar/9256-48-20240425145904.webp" width="48" height="48" alt="mhoye" style="position: absolute; left: 0; top: 0;">mhoye</a></section><article><p>As much as I admire the work of the LetsEncrypt team, making a policy change that effectively raises the cost of competitive and independent agency at the behest of a browser team that's at risk of being split off from their corporate sponsors specifically because of anticompetitive behavior in the domain of that agency... this might be technically justifiable,  but it's not the right decision for an organization being run for the public's benefit. </p><p><a href="https://letsencrypt.org/2025/05/14/ending-tls-client-authentication/" rel="nofollow">https://letsencrypt.org/2025/05/14/ending-tls-client-authentication/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/5063100#notice-9927100">In conversation</a><time datetime="2025-05-16T23:49:10+09:00" title="Friday, 16-May-2025 23:49:10 JST">about 21 hours ago</time> <span>from <span><a href="https://mastodon.social/@mhoye/114518058342998577" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@mhoye/114518058342998577">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: letsencrypt.org</div><h5><a href="https://letsencrypt.org/2025/05/14/ending-tls-client-authentication/">Ending TLS Client Authentication Certificate Support in 2026</a></h5><div></div></header><div>Let’s Encrypt will no longer include the “TLS Client Authentication” Extended Key Usage (EKU) in our certificates beginning in 2026. Most users who use Let’s Encrypt to secure websites won’t be affected and won’t need to take any action. However, if you use Let’s Encrypt certificates as client certificates to authenticate to a server, this change may impact you.
To minimize disruption, Let’s Encrypt will roll this change out in multiple stages, using ACME Profiles:</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
mhoye (mhoye@mastodon.social)'s status on Friday, 16-May-2025 23:49:10 JST mhoye
As much as I admire the work of the LetsEncrypt team, making a policy change that effectively raises the cost of competitive and independent agency at the behest of a browser team that's at risk of being split off from their corporate sponsors specifically because of anticompetitive behavior in the domain of that agency... this might be technically justifiable, but it's not the right decision for an organization being run for the public's benefit.
https://letsencrypt.org/2025/05/14/ending-tls-client-authentication/
In conversationabout 21 hours ago from mastodon.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: letsencrypt.org
  Ending TLS Client Authentication Certificate Support in 2026
  Let’s Encrypt will no longer include the “TLS Client Authentication” Extended Key Usage (EKU) in our certificates beginning in 2026. Most users who use Let’s Encrypt to secure websites won’t be affected and won’t need to take any action. However, if you use Let’s Encrypt certificates as client certificates to authenticate to a server, this change may impact you. To minimize disruption, Let’s Encrypt will roll this change out in multiple stages, using ACME Profiles:

Public

Embed Notice

HTML Code

Corresponding Notice