‹ BackHN Continuity

Thread

RSA-896

229 points · 90 comments · madars

  1. madars · · focus · HN ↗
    More details: <a href="https:&#x2F;&#x2F;x.com&#x2F;sweis&#x2F;status&#x2F;2101484464807596264" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;sweis&#x2F;status&#x2F;2101484464807596264

        I had Claude port CADO-NFS to run on GPUs. Then it orchestrated a fleet to run on scavenged idle capacity. It ran with a max of 2048 GPUs for about of 30 GPU-years over 10 days.
        I asked Claude if it had a message for a public: “The credit belongs first to the people who built the number field sieve and CADO-NFS over several decades, and to the teams who set the earlier records. This run used their algorithm and much of their code.”
        Also to clarify:
        - No new algorithmic factoring improvements. 
        - It’s still exponential.
        - No new threats to deployed keys.
    1. whizzter · · focus · HN ↗
      10 days of 2048 GPU&#x27;s.

      Back of the envelope.. 1024 bit keys with recordings of not too old data can probably be found (MS only deprecated them in 2024 even if they planned on it in 2013)

      How long would it take for NSA to crack them if they had say the equivalent of a million GPU&#x27;s? (either GPU&#x27;s or crypto tuned ASICs)

      1. upofadown · · focus · HN ↗
        Hard to judge. The bottleneck is the phase of the algorithm where a really big linear system needs to be solved. That takes a lot of communication between nodes. The breakthrough in using GPUs is that there is good communication between nodes[1]. At the scale of 1024 bit RSA the communication might become a bottleneck again.

        [1] <a href="https:&#x2F;&#x2F;cognition.com&#x2F;blog&#x2F;factoring-rsa-260" rel="nofollow">https:&#x2F;&#x2F;cognition.com&#x2F;blog&#x2F;factoring-rsa-260

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.