On Tue, Sep 9, 2025 at 6:29 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > On 09. 09. 25 11:59, Dmitry Belyavskiy wrote: > > Dear colleagues, > > > > 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. > > > > It's too early to write a System-wide proposal change as of now - if I'm not > > mistaken, this change could land only in Fedora 45, but I think it's worth > > considering the transition already. > > Suggestion: Submit a change proposal for Fedora 45. It's not too early. > I concur: something this important would definitely benefit from the early notification that the Change process can enable. > > We definitely would need an openssl3-compat package(s) including the one with > > engine support but I would better avoid being a primary maintainer of it. Also, for upstreams that rely on OpenSSL, is there a good way to start testing early against OpenSSL 4.0, short of building it manually? For example, I maintain a tool[1] that generates certificates using libcrypto. I'd like to be able to include an upstream CI test to build regularly against the OpenSSL development branch to catch issues early. (Spoiler: if the answer to this is "yes", that's information that should go into the Change Proposal too.) [1] https://github.com/sgallagher/sscg -- _______________________________________________ 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
