9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] auth/rsagen: bump bits to 4096
Date: Sun, 26 Nov 2023 20:43:27 +0100	[thread overview]
Message-ID: <7D815659CDA544149A6CA4CB32684F2C@felloff.net> (raw)
In-Reply-To: <f43fd147-e07c-40b5-a343-b5e26afe577e@bolddaemon.com>

> It's some logic you just made up :P - I never said I wouldn't propose 
> changing it if we had EC kex. I probably would have not picked 4096 though.

my point was that i do not see the connection between them.
what has the availability of ec todo with the rsa key size?
the only place where i see a connection is if you would want to "nudge"
users into not using rsa and for that you sabotage it beyond
any reason. but this would be pretty nasty thing todo no?

> I haven't hit any issues - and I am on some pretty shitty internet. I 
> haven't tested extensively though. That said, IMO if people need speed
> they can still  generate smaller keys...

common, just quantify it. whats the actual timing differences?
like make a test program i can run on my raspberry pi...
do SOMETHING usefull that helps quantifying the impact.

--
cinap

  reply	other threads:[~2023-11-26 19:46 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 [this message]
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=7D815659CDA544149A6CA4CB32684F2C@felloff.net \
    --to=cinap_lenrek@felloff.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).