The Call of the Open Sidewalk

From a place slightly to the side of the more popular path

User Tools

Site Tools


pgpfan:2048

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
pgpfan:2048 [2020/12/31 22:43] – Typo b.walzerpgpfan:2048 [2023/10/04 13:07] (current) – link to new, improved article b.walzer
Line 1: Line 1:
 ======2048 Bit RSA Keys====== ======2048 Bit RSA Keys======
  
-If you generate a public/private keypair with a recent version of [[https://gnupg.org/|GnuPG]] you get a 2048 bit RSA key by default. That fact generates a surprising amount of angst.+Since the creation of this article, there is now a much more detailed discussion of these issues available: 
 + 
 +[[em:20482030]] 
 + 
 +If you generate a public/private keypair with a recent version of [[https://gnupg.org/|GnuPG]] you get a 2048 bit RSA key by default ((The versions of GnuPG that are showing up in distributions are now (2021) defaulting to 3072 bit RSA. Nothing else has changed so this article is still otherwise relevant.)). That fact generates a surprising amount of angst.
  
 Currently (2020) the largest RSA key ever actually broken is 829 bits long(([[wp>RSA_Factoring_Challenge]])). Using a random cost off the net for AWS compute capacity the cost works out to around one million USD. Currently (2020) the largest RSA key ever actually broken is 829 bits long(([[wp>RSA_Factoring_Challenge]])). Using a random cost off the net for AWS compute capacity the cost works out to around one million USD.
pgpfan/2048.1609454600.txt.gz · Last modified: 2020/12/31 22:43 by b.walzer