Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove OpenSSL engine support #5991

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

musicinmybrain
Copy link

The ENGINE API is deprecated in OpenSSL 3.0; the intended replacement is the Provider API.

See also #5356, for which this addresses one (but not all) of the reported deprecation warnings.

This is also motivated by F41 Change Proposal: OpenSSL Deprecate Engine (system-wide). OpenSSL ENGINE API support has not been removed from Fedora, but there is an effort to identify packages that require it and gradually fix them. A similar change appears in RHEL10.

Description of the Change

This simply removes each instance of #include <openssl/engine.h> and the one function call to OpenSSL’s ENGINE API, ENGINE_load_builtin_engines().

Alternate Designs

The call to ENGINE_load_builtin_engines() was added a very long time in 5ba9c00 as part of x.509 signature generation support. I’m making a guess in this PR that it can be removed without consequence, but it’s not immediately obvious to me how to test this properly. It’s possible that this breaks something important, and if that’s the case, then the Provider API in OpenSSL 3.0 is the intended replacement for the ENGINE API.

Release Notes

Removed support for deprecated OpenSSL engines.

musicinmybrain and others added 2 commits January 5, 2025 10:07
The ENGINE API is deprecated in OpenSSL 3.0; the intended replacement is
the Provider API.

See also BOINC#5356, for which this addresses one (but not all) of the
reported deprecation warnings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

Successfully merging this pull request may close these issues.

2 participants