<?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[Last year, my position was that we still had time to design PQ authentication mechanisms.]]></title><description><![CDATA[<p>Last year, my position was that we still had time to design PQ authentication mechanisms.</p><p>Now, based on the pace of progress and on statements like Google's, I believe:</p><p>1. we need to finish rolling out PQ key exchange yesterday<br />2. we need to start rolling out PQ auth now<br />3. it's too late to ship any new non-PQ design or system</p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/" title="Quantum frontiers may be closer than they appear">
<img src="https://storage.googleapis.com/gweb-uniblog-publish-prod/images/post-quantum_cryptography_migration_social.width-1300.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://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/">
Quantum frontiers may be closer than they appear
</a>
</h5>
<p class="card-text line-clamp-3">An overview of how Google is accelerating its timeline for post-quantum cryptography migration.</p>
</div>
<a href="https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://blog.google/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">Google <span class="text-secondary">(blog.google)</span></p>
</a>
</div></p>]]></description><link>https://board.circlewithadot.net/topic/a0f3f8c9-962e-4aef-91bd-44a36cd03f7c/last-year-my-position-was-that-we-still-had-time-to-design-pq-authentication-mechanisms.</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Apr 2026 11:46:38 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/a0f3f8c9-962e-4aef-91bd-44a36cd03f7c.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 26 Mar 2026 15:43:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Last year, my position was that we still had time to design PQ authentication mechanisms. on Mon, 06 Apr 2026 17:46:42 GMT]]></title><description><![CDATA[<p><span><a href="/user/filippo%40abyssdomain.expert">@<span>filippo</span></a></span> <span><a href="/user/cryptohagen%40social.data.coop">@<span>cryptohagen</span></a></span> are you following this? <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.unwi.re/ap/users/115637003872401174/statuses/116359010848386452</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.unwi.re/ap/users/115637003872401174/statuses/116359010848386452</guid><dc:creator><![CDATA[flux@mastodon.unwi.re]]></dc:creator><pubDate>Mon, 06 Apr 2026 17:46:42 GMT</pubDate></item><item><title><![CDATA[Reply to Last year, my position was that we still had time to design PQ authentication mechanisms. on Thu, 26 Mar 2026 16:32:58 GMT]]></title><description><![CDATA[<p><span><a href="/user/freddy%40social.security.plumbing">@<span>freddy</span></a></span> <span><a href="/user/filippo%40abyssdomain.expert">@<span>filippo</span></a></span> </p><p>Scott Aaronson writes:</p><p>"I’m going to close this post with a warning. When Frisch and Peierls wrote their now-famous memo in March 1940, estimating the mass of Uranium-235 that would be needed for a fission bomb, they didn’t publish it in a journal, but communicated the result through military channels only. As recently as February 1939, Frisch and Meitner had published in Nature their theoretical explanation of recent experiments, showing that the uranium nucleus could fission when bombarded by neutrons. But by 1940, Frisch and Peierls realized that the time for open publication of these matters had passed.</p><p>"Similarly, at some point, the people doing detailed estimates of how many physical qubits and gates it’ll take to break actually deployed cryptosystems using Shor’s algorithm are going to stop publishing those estimates, if for no other reason than the risk of giving too much information to adversaries. Indeed, for all we know, that point may have been passed already. This is the clearest warning that I can offer in public right now about the urgency of migrating to post-quantum cryptosystems, a process that I’m grateful is already underway."</p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://scottaaronson.blog/?p=9425" title="More on whether useful quantum computing is “imminent”">
<img src="http://img.youtube.com/vi/0_7SH3Eons0/0.jpg" 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://scottaaronson.blog/?p=9425">
More on whether useful quantum computing is “imminent”
</a>
</h5>
<p class="card-text line-clamp-3">These days, the most common question I get goes something like this: A decade ago, you told people that scalable quantum computing wasn't imminent. Now, though, you claim it plausibly is imminent. Why have you reversed yourself?? I appreciated the friend of mine who paraphrased this as follows: "A decade ago you said you were…</p>
</div>
<a href="https://scottaaronson.blog/?p=9425" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://scottaaronson.blog/wp-content/uploads/2021/10/cropped-Jacket-32x32.gif" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />







<p class="d-inline-block text-truncate mb-0">Shtetl-Optimized <span class="text-secondary">(scottaaronson.blog)</span></p>
</a>
</div></p>]]></description><link>https://board.circlewithadot.net/post/https://mathstodon.xyz/users/4raylee/statuses/116296435542009881</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mathstodon.xyz/users/4raylee/statuses/116296435542009881</guid><dc:creator><![CDATA[4raylee@mathstodon.xyz]]></dc:creator><pubDate>Thu, 26 Mar 2026 16:32:58 GMT</pubDate></item><item><title><![CDATA[Reply to Last year, my position was that we still had time to design PQ authentication mechanisms. on Thu, 26 Mar 2026 16:21:12 GMT]]></title><description><![CDATA[<p><span><a href="/user/filippo%40abyssdomain.expert">@<span>filippo</span></a></span> You got me interested to know what it would look like in authorized_keys, and can it be this short! Looks neat.</p><p>ssh-mldsa44-ed25519 434f4d505349472d4d4c44534134342d456432353531392d534841353132</p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://datatracker.ietf.org/doc/draft-sun-ssh-composite-sigs/02/" title="Composite ML-DSA Signatures for SSH">
<img src="https://static.ietf.org/dt/12.61.0/ietf/images/ietf-logo-nor-white.svg" 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://datatracker.ietf.org/doc/draft-sun-ssh-composite-sigs/02/">
Composite ML-DSA Signatures for SSH
</a>
</h5>
<p class="card-text line-clamp-3">Composite ML-DSA Signatures for SSH </p>
</div>
<a href="https://datatracker.ietf.org/doc/draft-sun-ssh-composite-sigs/02/" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://static.ietf.org/dt/12.61.0/ietf/images/ietf-logo-nor-32.png" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />







<p class="d-inline-block text-truncate mb-0">IETF Datatracker <span class="text-secondary">(datatracker.ietf.org)</span></p>
</a>
</div></p>]]></description><link>https://board.circlewithadot.net/post/https://twit.social/users/Ciantic/statuses/116296389280679191</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://twit.social/users/Ciantic/statuses/116296389280679191</guid><dc:creator><![CDATA[ciantic@twit.social]]></dc:creator><pubDate>Thu, 26 Mar 2026 16:21:12 GMT</pubDate></item><item><title><![CDATA[Reply to Last year, my position was that we still had time to design PQ authentication mechanisms. on Thu, 26 Mar 2026 16:20:54 GMT]]></title><description><![CDATA[<p><span><a href="/user/freddy%40social.security.plumbing">@<span>freddy</span></a></span> <span><a href="/user/filippo%40abyssdomain.expert">@<span>filippo</span></a></span> as far as I can tell that timeline is because that is the timeline that has been set by NSA / NIST.  Google is probably just trying to protect its access to sell devices / services to the government.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/relishthecracker/statuses/116296388072004477</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/relishthecracker/statuses/116296388072004477</guid><dc:creator><![CDATA[relishthecracker@infosec.exchange]]></dc:creator><pubDate>Thu, 26 Mar 2026 16:20:54 GMT</pubDate></item><item><title><![CDATA[Reply to Last year, my position was that we still had time to design PQ authentication mechanisms. on Thu, 26 Mar 2026 16:07:47 GMT]]></title><description><![CDATA[<p><span><a href="/user/filippo%40abyssdomain.expert">@<span>filippo</span></a></span> Interesting, I just cam across <a href="https://infosec.exchange/@mttaggart/116163107290977793" rel="nofollow noopener"><span>https://</span><span>infosec.exchange/@mttaggart/11</span><span>6163107290977793</span></a> the other day, basically saying that it won't be feasible any time soon.</p>]]></description><link>https://board.circlewithadot.net/post/https://ipv6.social/users/ikke/statuses/116296336510640467</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ipv6.social/users/ikke/statuses/116296336510640467</guid><dc:creator><![CDATA[ikke@ipv6.social]]></dc:creator><pubDate>Thu, 26 Mar 2026 16:07:47 GMT</pubDate></item><item><title><![CDATA[Reply to Last year, my position was that we still had time to design PQ authentication mechanisms. on Thu, 26 Mar 2026 15:46:36 GMT]]></title><description><![CDATA[<p><span><a href="/user/filippo%40abyssdomain.expert">@<span>filippo</span></a></span> I like their aggressive timeline, but I'm not sure there's any specific argument or reason that explains why it should be expedited. Am I missing something?</p>]]></description><link>https://board.circlewithadot.net/post/https://social.security.plumbing/users/freddy/statuses/116296253199853882</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://social.security.plumbing/users/freddy/statuses/116296253199853882</guid><dc:creator><![CDATA[freddy@social.security.plumbing]]></dc:creator><pubDate>Thu, 26 Mar 2026 15:46:36 GMT</pubDate></item></channel></rss>