On Sat, Jul 06, 2024 at 09:10:46PM -0000, Fredrik Wendt wrote:
> I just ran into this exact issue again with a fresh install of 24.04:
> Noble (and Jammy) can't connect to other Ubuntu nodes). What's the
> recommended approach - lift all nodes to one of the (in Ubuntu) broken
> libssl3 packages?
What application are you using in this context?
What are the version numbers for the libssl* packages in use on the various
nodes?
Off hand, I would expect that Jammy would be the only release whose
default Blowfish configuration is incompatible with the implementations
on the other releases. (That is, I would expect a Noble installation to
connect to earlier-than-Jammy instances without any problem.)
Nathan
p.s. Note that on any release using libssl3, if you are trying to Blowfish
encryption, you do need to enable the OpenSSL "legacy" provider. So
that step will be necessary on Noble, but is due to the general switch
to OpenSSL v3 rather than this specific bug in Jammy's libssl3 library.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1990216
Title:
backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
1.1 with blowfish in OFB or CFB modes" to Jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1990216/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
