From: Chris Koeritz <fred@gruntose.com>
Date: Sun, 27 Sep 2026 11:58:19 +0000 (-0400)
Subject: back to previously working blowfish key size
X-Git-Url: https://feistymeow.org/gitweb/?a=commitdiff_plain;h=93f8a824560fdf602d45d76ba47dff2119685031;p=feisty_meow.git

back to previously working blowfish key size

this reverts to a key size of 64 for borked blowfish, which was working
before with essentially the same code.  now, openssl is back to barfing
with any key size at all for blowfish, yet the twofish implementation
using the same openssl mechanisms is working flawlessly.  did openssl
really break blowfish completely, then fix it in the previous version of
their code, but then break it again in their most recent code???
---

diff --git a/nucleus/library/crypto/borked_blowfish_crypto.h b/nucleus/library/crypto/borked_blowfish_crypto.h
index 470e7691..cf66b4c2 100644
--- a/nucleus/library/crypto/borked_blowfish_crypto.h
+++ b/nucleus/library/crypto/borked_blowfish_crypto.h
@@ -57,7 +57,7 @@ public:
   // blowfish relevant values for appropriate key sizes.
   virtual int minimum_key_size_in_bits() const { return static_minimum_key_size_in_bits(); }
   virtual int maximum_key_size_in_bits() const { return static_maximum_key_size_in_bits(); }
-  static int static_minimum_key_size_in_bits() { return 128; }
+  static int static_minimum_key_size_in_bits() { return 64; }
     // officially, this is 32.  but openssl fails occasionally with less than 64 bits.
   static int static_maximum_key_size_in_bits() { return 448; }
 };