<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mthiim</author><text>That algorithm was never chosen as a final candidate, unlike Dilithium and Kyber. Nevertheless, it remains intriguing because it advanced significantly in the competition until this vulnerability was identified, which allows for it to be cracked in just a few minutes on a standard computer. This underscores the inherent risk of rapidly introducing new algorithms, whether quantum or not. While RSA might become vulnerable to future quantum computers, its resilience since its public introduction in 1977 (aside from the need to increase key sizes) is quite an achievement. This is why new algorithms should always be paired with trusted classical algorithms to get the best of both worlds: if the new post-quantum component is flawed, at least you&amp;#x27;re not worse off than if you had used classical algorithms. On the other hand, if quantum computers capable of breaking practical sizes of RSA or ECC emerge, there&amp;#x27;s still the hope that the post-quantum element remains intact.</text><parent_chain><item><author>cbeach</author><text>I&amp;#x27;ve probably missed an important detail here, but if the post-quantum algo can be broken on classical computers, what use is it, vs. a combination of classical and quantum computers?</text></item><item><author>timenova</author><text>It seems that&amp;#x27;s exactly what the community is doing.&lt;p&gt;Cloudflare recently enabled post-quantum cryptography, in which they&amp;#x27;re using X25519+Kyber [0]. Similarly, Signal&amp;#x27;s post-quantum cryptography also uses the same [1].&lt;p&gt;I&amp;#x27;m guessing this spawned from the fact that a post-quantum algorithm was broken on classical computers a few years ago [2].&lt;p&gt;So now any attacker would have to break both the classical algorithm and the post-quantum algorithm.&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;post-quantum-to-origins&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;post-quantum-to-origins&amp;#x2F;&lt;/a&gt;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;signal.org&amp;#x2F;blog&amp;#x2F;pqxdh&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;signal.org&amp;#x2F;blog&amp;#x2F;pqxdh&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.quantamagazine.org&amp;#x2F;post-quantum-cryptography-scheme-is-cracked-on-a-laptop-20220824&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.quantamagazine.org&amp;#x2F;post-quantum-cryptography-sch...&lt;/a&gt;</text></item><item><author>rany_</author><text>Is it a good idea to use quantum resistant crypto algorithm on-top of more established&amp;#x2F;widespread algorithms like RSA&amp;#x2F;ECDSA? I don&amp;#x27;t feel comfortable using quantum resistant crypto due to how cutting edge it all is.</text></item></parent_chain></comment><story><title>Java implementation of a quantum computing resistant cryptographic algorithm</title><url>https://github.com/mthiim/dilithium-java</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>insanitybit</author><text>At this point quantum computers aren&amp;#x27;t breaking anything. Adding protections against them is nice because we&amp;#x27;re theoretically safe in the future. We don&amp;#x27;t want to compromise our safety &lt;i&gt;now&lt;/i&gt; by choosing algorithms that are less battle tested though, so it&amp;#x27;s best to layer them.&lt;p&gt;If it turns out that both the classical and quantum hard algorithms are weak we&amp;#x27;re just screwed, yes. That said, at this point it&amp;#x27;s not even clear, as far as I know, that many classical algorithms are event going to be broken under QC.</text><parent_chain><item><author>cbeach</author><text>I&amp;#x27;ve probably missed an important detail here, but if the post-quantum algo can be broken on classical computers, what use is it, vs. a combination of classical and quantum computers?</text></item><item><author>timenova</author><text>It seems that&amp;#x27;s exactly what the community is doing.&lt;p&gt;Cloudflare recently enabled post-quantum cryptography, in which they&amp;#x27;re using X25519+Kyber [0]. Similarly, Signal&amp;#x27;s post-quantum cryptography also uses the same [1].&lt;p&gt;I&amp;#x27;m guessing this spawned from the fact that a post-quantum algorithm was broken on classical computers a few years ago [2].&lt;p&gt;So now any attacker would have to break both the classical algorithm and the post-quantum algorithm.&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;post-quantum-to-origins&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;post-quantum-to-origins&amp;#x2F;&lt;/a&gt;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;signal.org&amp;#x2F;blog&amp;#x2F;pqxdh&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;signal.org&amp;#x2F;blog&amp;#x2F;pqxdh&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.quantamagazine.org&amp;#x2F;post-quantum-cryptography-scheme-is-cracked-on-a-laptop-20220824&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.quantamagazine.org&amp;#x2F;post-quantum-cryptography-sch...&lt;/a&gt;</text></item><item><author>rany_</author><text>Is it a good idea to use quantum resistant crypto algorithm on-top of more established&amp;#x2F;widespread algorithms like RSA&amp;#x2F;ECDSA? I don&amp;#x27;t feel comfortable using quantum resistant crypto due to how cutting edge it all is.</text></item></parent_chain></comment><story><title>Java implementation of a quantum computing resistant cryptographic algorithm</title><url>https://github.com/mthiim/dilithium-java</url></story>