9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Aaron Bieber <aaron@bolddaemon.com>
To: 9front@9front.org
Subject: Re: [9front] auth/rsagen: bump bits to 4096
Date: Sun, 26 Nov 2023 12:07:55 -0700	[thread overview]
Message-ID: <e0c8eeb2-0d34-4e72-9621-0fcb43b63f77@bolddaemon.com> (raw)
In-Reply-To: <A652DCFBDABA7DFFA055A38DCCDDC72D@eigenstate.org>



On 11/26/23 09:50, ori@eigenstate.org wrote:
> Quoth Aaron Bieber <aaron@bolddaemon.com>:
>> My reasoning is basically since we don't have alternative key types
>> (ed25519, ecdsa) for
>> general usage / ssh, bump the default to the highest available.
> why not DJB's post-quantum RSA proposal? I believe
> that the key size used there was 8796093022208 bits.
>
> Changing it isn't wrong, but there's no "highest
> available" size for RSA. Why 4096 specifically?
>
Ya, bad wording on my side. 4096 is the "max" supported by other tools,
gpg for example. So staying under that bar would allow for key-portability.
I am not married to it though.

  reply	other threads:[~2023-11-26 19:09 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 [this message]
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.
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=e0c8eeb2-0d34-4e72-9621-0fcb43b63f77@bolddaemon.com \
    --to=aaron@bolddaemon.com \
    --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).