openssh unix dev - Mar 2023 - ChaCha20 Rekey Frequency

Hi Damien,
>This is what I'm playing with at the moment:
if you?re playing with this currently anyway, shouldn?t?
>+	/*
>+	 * Otherwise, use the RFC4344 s3.2 recommendation of 2**(L/4) blocks
>+	 * before rekeying where L is the blocksize in bits.
>+	 * Most other ciphers have a 128 bit blocksize, so this equates to
>+	 * 2**32 blocks / 64GB data.
>+	 */
>+	return (uint64_t)1 << (c->block_size * 2);
? this get an upper bound? This is UB for 256-bit blocksizes
at least?

bye,
//mirabilos
-- 
Infrastrukturexperte ? tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn ? http://www.tarent.de/
Telephon +49 228 54881-393 ? Fax: +49 228 54881-235
HRB AG Bonn 5168 ? USt-ID (VAT): DE122264941
Gesch?ftsf?hrer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

                        ****************************************************
/?\ The UTF-8 Ribbon
??? Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
??? HTML eMail! Also,     https://www.tarent.de/newsletter
??? header encryption!
                        ****************************************************

On Wed, 29 Mar 2023, Thorsten Glaser wrote:
> Hi Damien,
> 
> >This is what I'm playing with at the moment:
> 
> if you?re playing with this currently anyway, shouldn?t?
> 
> >+	/*
> >+	 * Otherwise, use the RFC4344 s3.2 recommendation of 2**(L/4) blocks
> >+	 * before rekeying where L is the blocksize in bits.
> >+	 * Most other ciphers have a 128 bit blocksize, so this equates to
> >+	 * 2**32 blocks / 64GB data.
> >+	 */
> >+	return (uint64_t)1 << (c->block_size * 2);
> 
> ? this get an upper bound? This is UB for 256-bit blocksizes
> at least?
block sizes in struct sshcipher are in bytes, not bits