* Simo Sorce: > On Tue, 2025-09-09 at 16:37 +0200, Florian Weimer wrote: >> * Dmitry Belyavskiy: >> >> > OpenSSL upstream has started development of the version OpenSSL 4.0 It >> > will imply soname bump, removing ENGINE support, etc. As OpenSSL uses >> > time-based release planning, the release would happen in April 2026. >> >> Ugh. >> >> Will it at least be possible to load OpenSSL 4 and 3 into the same >> process? That's going to be difficult to get to work for dlsym-based >> FFI. > > Well dlsym should reference a dlopen() that was done against a specific > so file, so there should be no ambiguity about which symbol to load? I think there are cases of auto-discovery of sonames out there, to emulate what the native toolchain does when you write -lssl. Of course, this completely falls appart in the presence of such soname changes. > That said, I am not sure they are changing all symbol versions in the > new .so.4 file, perhaps they should reset all symbols versions to > 4.0.0? Yeah, if they don't do that, it's going to be really awkward. How set are they on the soname bump? Maybe they'd be open to a review how to avoid it on GNU/Linux? But that could mean they'll end up with different sonames on GNU and musl. Thanks, Florian -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
