Hi Sebastian,

On 16/06/2026 23:22, Sebastian Andrzej Siewior wrote:
Package: release.debian.org
Control: affects -1 + src:openssl
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: transition
Severity: normal

Dear release team,

I aim for an OpenSSL transition :)

The so-version changes from 3 to 4 as a result of the ABI change.
The main changes are:
- The ENGINE API goes away. The "Provider mechanism" (available since
   3.0) is the replacement.
   There are three engines in tree:
   libengine-gost-openssl, libengine-pkcs11-openssl,
   libengine-tpm2-tss-openssl. The former two provide seem to provide a
   matching provider. The latter is probably replaced by tpm2-openssl.
   The build failure for non-engine code is the attempt to use a possibly
   available engine (which fails to link since the code is gone).

- ASN1_STRING has been made opaque. This seems to cause the most compile
   failures.

There is a blog post
        https://openssl-library.org/post/2026-04-14-openssl-40-final-release/

The longterm plan is to switwch to 4.0 and then to 4.2 which should be
released around April and will be LTS. So Forky would have an LTS
supported release, see
        https://openssl-library.org/post/2026-05-07-future-release/
We have thought about this and talked to other parties (such as the Security Team), and in the end we have decided to have this transition now and grant an exception for the 4.2 update during the freeze provided that there is no SONAME bump (our understanding is that there won't be one, please speak up if that is not the case).

I'm not acking the transition right now, we will do that as soon as a suitable transition slot opens up.

Regards,
Emilio

Reply via email to