9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] auth/rsagen: bump bits to 4096
Date: Sun, 26 Nov 2023 20:26:16 -0500	[thread overview]
Message-ID: <f6c2229d-3df9-42b9-95e6-1df565425522@fjrhome.net> (raw)
In-Reply-To: <7B7270387AB3072AE5507DD342C3F31A@eigenstate.org>

This is the recommendation from NIST:

https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf

A 2048-bit RSA key has a "security strength" of 112 bits (page 54).

NIST considers encryption with a security strength of 112 bits to be 
acceptable protection through 2030 but not beyond that (page 59).


See also: 
https://www.gradenegger.eu/en/which-key-sizes-should-be-used-for-certification-bodies-and-certificates/

That document indicates that a German government security organization 
considers less than 3000 bits with RSA to be unacceptable even now.


Of course, RSA is known to be vulnerable to an algorithm which could be 
implemented on a sufficiently large quantum computer; while such a 
computer is currently believed to be over a decade away, there have been 
known cases of full encrypted exchanges being captured and stored for 
longer periods of time than that to be decrypted after the technology 
improves to be able to crack the data.  Depending on the sensitivity of 
the information, this could be a factor for some.


There are groups making various efforts to develop new algorithms 
designed to be safe against quantum computers:

https://en.wikipedia.org/wiki/Post-quantum_cryptography



On 11/26/23 19:42, ori@eigenstate.org wrote:
> Quoth Frank D. Engel, Jr. <fde101@fjrhome.net>:
>> Presumably 2048-bit RSA is good until 2030 - but that is less than 7
>> years away and keys created today may still be in use long past that time.
> This is getting closer to a useful description of why,
> but can you explain *how* you concluded that these keys
> are good until 2030?
>
>
>


  reply	other threads:[~2023-11-27  1:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26  4:33 Aaron Bieber
2023-11-26 12:48 ` cinap_lenrek
2023-11-26 14:46   ` Aaron Bieber
2023-11-26 16:50     ` ori
2023-11-26 19:07       ` Aaron Bieber
2023-11-26 17:06     ` cinap_lenrek
2023-11-26 19:15       ` Aaron Bieber
2023-11-26 19:43         ` cinap_lenrek
2023-11-27  0:33           ` Frank D. Engel, Jr.
2023-11-27  0:42             ` ori
2023-11-27  1:26               ` Frank D. Engel, Jr. [this message]
2023-11-27  9:50                 ` hiro
2023-11-27 12:22                   ` Frank D. Engel, Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f6c2229d-3df9-42b9-95e6-1df565425522@fjrhome.net \
    --to=fde101@fjrhome.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).