From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14109 invoked from network); 26 Nov 2023 16:54:31 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 26 Nov 2023 16:54:31 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Sun Nov 26 11:50:29 -0500 2023 Received: from abbatoir (pool-108-6-24-2.nycmny.fios.verizon.net [108.6.24.2]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 6273b52b (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Sun, 26 Nov 2023 08:50:26 -0800 (PST) Message-ID: To: 9front@9front.org Date: Sun, 26 Nov 2023 11:50:25 -0500 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: virtualized private SSL hardware singleton Subject: Re: [9front] auth/rsagen: bump bits to 4096 Reply-To: 9front@9front.org Precedence: bulk Quoth Aaron Bieber : > 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?