Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: sci.crypt
Subject: Re: Blowfish reliability
Date: Fri, 25 Jul 2025 18:15:16 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <1060hjk$21ebo$1@dont-email.me>
References: <20250715.155447.eeb4ce0a@yamn.paranoici.org> <1056h0u$a0n8$1@dont-email.me> <105trl7$pf43$1@dont-email.me> <105u3j6$qkjp$2@dont-email.me> <105vfc8$10f3u$1@dont-email.me>
Injection-Date: Fri, 25 Jul 2025 20:15:17 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="c9807ca2a9fcee6977e1f96300647e73";
	logging-data="2144632"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/9I8eI0+WpAFrxD0lDoIAg"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:P6K5OK7+6RP1Z59oGqPSJyA9F30=

Chax Plore <nznmrqmrxr@qazk.bet> wrote:
> On 2025-07-24 22:03, Rich wrote:
>> Chax Plore <nznmrqmrxr@qazk.bet> wrote:
>>>
>>> Someone rescaled Blowfish to 128-bit blocks:
>>>
>>> https://alexpukall.github.io/blowfish2/blowfish2-gcc.txt
>>>
>>> But the memory print of this version is monstrous.
>> 
>> Can you quantify "monstrous"?  Just how big is that?
> 
> In this particular case: 16912 bytes total of P-box and S-boxes onstants.

While that may very well be significantly larger than other algorithms, 
unless you are working in a very RAM constrained embedded system, ~16k 
of state is not likely to be significant for most systems.  And even if 
one were doing some kind of network server where each network link 
consumed that amount for 'state', 1GiB of RAM would still hold enough 
state blocks for 63,489 simultaneous network flows.  And any server 
meant for that much networking is likely going to have by far more than 
1GiB of RAM installed.