Repository navigation
aktualizr: fix the build against OpenSSL 4.0 - #229
Merged
Merged
Conversation
OpenSSL 4.0 returns a const X509_NAME pointer from X509_get_subject_name() and removed the ENGINE API from libcrypto, so libaktualizr fails to compile and then to link: crypto.cc:625:45: error: invalid conversion from 'const X509_NAME*' to 'X509_NAME*' [-fpermissive] crypto.cc:149: undefined reference to 'ENGINE_load_private_key' Add the const fix submitted as uptane/aktualizr#138 and the patch submitted as uptane/aktualizr#139 that only compiles the engine-backed key loading with BUILD_P11. Builds without the hsm feature now link against OpenSSL 4.0; builds with it fail early at compile time until the PKCS#11 support is ported to OpenSSL providers. Assisted-by: Claude Code:claude-fable-5-1 Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
Collaborator
Author
|
This is a stop-gap until uptane/aktualizr#137 is fixed properly (migrating from engine to provider). |
ricardosalveti
added a commit
to ricardosalveti/meta-qcom
that referenced
this pull request
Sep 9, 2026
OE-Core moved to OpenSSL 4.0 and aktualizr from meta-updater no longer compiles, which breaks every qcom-distro-sota image. Carry the fix submitted as uptane/meta-updater#229 as a kas patch until it lands. Assisted-by: Claude Code:claude-fable-5-1 Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
quaresmajose
approved these changes
Sep 10, 2026
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenSSL 4.0 returns a const X509_NAME pointer from X509_get_subject_name() and removed the ENGINE API from libcrypto, so libaktualizr fails to compile and then to link:
crypto.cc:625:45: error: invalid conversion from 'const X509_NAME*'
to 'X509_NAME*' [-fpermissive]
crypto.cc:149: undefined reference to 'ENGINE_load_private_key'
Add the const fix submitted as uptane/aktualizr#138 and the patch submitted as uptane/aktualizr#139 that only compiles the engine-backed key loading with BUILD_P11. Builds without the hsm feature now link against OpenSSL 4.0; builds with it fail early at compile time until the PKCS#11 support is ported to OpenSSL providers.