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

OpenSSL 3 support #203

Merged
merged 3 commits into from
Nov 21, 2023
Merged

OpenSSL 3 support #203

merged 3 commits into from
Nov 21, 2023

Conversation

quitschbo
Copy link
Member

@quitschbo quitschbo commented Aug 7, 2023

This reverts commit 6b38096. The CML layer is now compatible with OpenSSL 3. Thus, we can remove this backport and switch to the upstream OpenSSL recipe.

Needs: gyroidos/cml#392,
gyroidos/meta-trustx-intel#28,
gyroidos/gyroidos_build#108

@quitschbo
Copy link
Member Author

Hmm the kernel do_deploy() after initial ram-disk bundling produces a Segfault. with switching to the current openssl3 recipe. So do not merge, yet.

@quitschbo
Copy link
Member Author

sbsign was not supporting openssl 3. The PR gyroidos/meta-trustx-intel#28 fixes that by using more recent version of sbsigntool

This reverts commit 6b38096.
The CML layer is now compatible with OpenSSL 3. Thus, we can remove
this backport and switch to the upstream OpenSSL recipe.

Signed-off-by: Michael Weiß <[email protected]>
This recipe including some compile patches allows to build against
OpenSSL 3.

Signed-off-by: Michael Weiß <[email protected]>
We now set EXTERNALSRC similar to the cmld recipe, so changes in the
external trustme/build folder which contains the pki scripts would
be checked by bitbake. Further, the workaround for state cache
disabling is replaced by SSTATE_CACHE_SKIP variable. Also a proper
clean() task is provided.

Signed-off-by: Michael Weiß <[email protected]>
@quitschbo quitschbo merged commit 0871489 into gyroidos:kirkstone Nov 21, 2023
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

Successfully merging this pull request may close these issues.

2 participants