OpenSSL 4.0 is going to land in April 2026. It is a major release with many significant changes, and we should start preparing for it.
Owners, do not implement this work until the FESCo vote has explicitly ended. The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.
REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.
Metadata Update from @alking: - Issue untagged with: system wide change - Issue tagged with: self contained change
Metadata Update from @alking: - Issue untagged with: self contained change
Metadata Update from @alking: - Issue tagged with: self contained change
I appreciate this being filed so far in advance.
I'm +1 to the change, but I am pretty sure we are going to need a openssl3 compat package(s) for a while.
Yeah, this is fine, but this is not a self-contained change. We will almost certainly require an openssl3 compat package to execute on, too.
openssl3
+1
+1, but System-Wide.
An SONAME change is planned, and a compat package will remain available. This sounds like a reasonable transition.
The proposal doesn't say this explicitly, but the compat package must include the devel headers to that we can keep compiling packages against openssl3. I'm mentioning this because in the previous openssl transitions there were ideas to do things in which things are dropped from the headers, making re-compilation impossible. We need to retain this ability for the duration of the release where the compat package is available, so that we can always recompile packages for updates.
Metadata Update from @humaton: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open) - Issue tagged with: pending announcement
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue tagged with: system wide change
Metadata Update from @zbyszek: - Issue untagged with: self contained change