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

Usage of deprecated openssl "ENGINE API" #1038

Open
gobenji opened this issue Nov 28, 2024 · 0 comments
Open

Usage of deprecated openssl "ENGINE API" #1038

gobenji opened this issue Nov 28, 2024 · 0 comments

Comments

@gobenji
Copy link

gobenji commented Nov 28, 2024

mstflint currently uses an openssl api that was deprecated since version 3.0, the "engine api":
https://github.com/openssl/openssl/blob/af33b200da8040c78dbfd8405878190980727171/README-ENGINES.md

This was pointed out by Red Hat employees in a private ticket (https://issues.redhat.com/browse/RHEL-58081). In RHEL-10, the next major release of RHEL, openssl is built without support for "engines".

In that case, trying to compile mstflint leads to errors starting with:

mlxsign_openssl_engine.cpp:86:5: error: 'ENGINE_load_builtin_engines' was not declared in this scope
   86 |     ENGINE_load_builtin_engines();
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~

As a result, mstflint is built without openssl and thus without mstfwmanager in RHEL-10. From mstflint.spec:

* Fri May 24 2024 Kamal Heib <[email protected]> - 4.26.0-4
- Disable openssl

Since mstfwmanager is the most convenient way to upgrade firmware, it would be nice to be able to have it in RHEL-10. Can you remove usage of the deprecated engine api in mstflint?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant