<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Let&#x27;s Encrypt is announcing that they&#x27;ll support Merkle Tree Certificates:]]></title><description><![CDATA[<p>Let's Encrypt is announcing that they'll support Merkle Tree Certificates:</p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://letsencrypt.org/2026/06/03/pq-certs.html" title="A Post-Quantum Future for Let's Encrypt">
<img src="https://letsencrypt.org/images/LetsEncrypt-SocialShare.png" class="card-img-top not-responsive" style="max-height: 15rem;" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://letsencrypt.org/2026/06/03/pq-certs.html">
A Post-Quantum Future for Let's Encrypt
</a>
</h5>
<p class="card-text line-clamp-3">Let’s Encrypt is committed to a post-quantum-safe Web PKI. The path we’re planning to take is Merkle Tree Certificates (“MTCs”), a new approach that adds post-quantum authentication to the web without sacrificing the speed and reliability that have made TLS universal.
This post is about these plans and why we believe MTCs are worth pursuing as a key to a post-quantum future.
An increasingly urgent problem For much of the last several years, the conversation about post-quantum cryptography has been a conversation about encryption. The reasoning was straightforward: an attacker who records encrypted traffic today might be able to decrypt it years from now once quantum computers can break the underlying math. Authentication, the part of TLS that indicates a server is who it says it is, has been a less urgent problem. A quantum computer needs to forge a signature in real time, not retroactively, so threats to authentication hinge on the existence of a cryptographically relevant quantum computer (CRQC).
</p>
</div>
<a href="https://letsencrypt.org/2026/06/03/pq-certs.html" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://letsencrypt.org/favicon.ico" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />



<p class="d-inline-block text-truncate mb-0"> <span class="text-secondary">(letsencrypt.org)</span></p>
</a>
</div></p><p><a href="https://chaos.social/tags/TLS" rel="tag">#<span>TLS</span></a> <a href="https://chaos.social/tags/PostQuantumCryptography" rel="tag">#<span>PostQuantumCryptography</span></a> <a href="https://chaos.social/tags/PQC" rel="tag">#<span>PQC</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/c9f9af82-1154-47ce-88fa-1563458865e1/let-s-encrypt-is-announcing-that-they-ll-support-merkle-tree-certificates</link><generator>RSS for Node</generator><lastBuildDate>Fri, 05 Jun 2026 13:00:52 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/c9f9af82-1154-47ce-88fa-1563458865e1.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 03 Jun 2026 18:56:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Let&#x27;s Encrypt is announcing that they&#x27;ll support Merkle Tree Certificates: on Wed, 03 Jun 2026 22:54:10 GMT]]></title><description><![CDATA[<p><span><a href="/user/neverpanic%40chaos.social" rel="nofollow noopener">@<span>neverpanic</span></a></span> </p><p>Nice, we implemented that at the uni 10 years ago. Cool to see that the industry is catching up.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/13reak/statuses/116688633856152169</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/13reak/statuses/116688633856152169</guid><dc:creator><![CDATA[13reak@infosec.exchange]]></dc:creator><pubDate>Wed, 03 Jun 2026 22:54:10 GMT</pubDate></item></channel></rss>