This bug is used to track the readiness of dotnet3.1 with OpenSSL 3.0.0. Currently the build fails to build with OpenSSL 3.0.0 with the following logs https://koji.fedoraproject.org/koji/taskinfo?taskID=78020162 Kindly fix them to ensure this package builds with OpenSSL 3.0.0 You can treat the deprecated warnings not as errors if you want to continue to use deprecated functions, but it is encouraged to use the new APIs, and this migration could be done sooner than later. To not treat deprecated warnings as errors, you may use -Wno-error=deprecated-declarations To port to new APIs, kindly refer to the OpenSSL upstream migration guide: https://www.openssl.org/docs/manmaster/man7/migration_guide.html Thank you
The new/about-to-be-release upstream version of .NET (.NET 6) has OpenSSL 3.0 support already: https://github.com/dotnet/runtime/issues/46526 Supporting OpenSSL 3.1 (which goes EOL in about a year) involves a large amount of fairly invasive changes: https://github.com/dotnet/corefx/pull/43078 I am considering EOL'ing dotnet3.1 in Fedora rather than risk breaking security in .NET.
Porting .NET Core 3.1 to OpenSSL 3.1 is quite difficult to verify and there is a significant risk of accidentally breaking some important security feature. New versions of .NET, such as .NET 6 are compatible with OpenSSL 3.0 and will work fine. It's likely .NET Core 3.1 will be EOL before Fedora removes OpenSSL 1.1. I am closing this bug as WONTFIX.