u-boot-stm32mp: Fix FIT signing process#106
Closed
bhstalel wants to merge 1 commit into
Closed
Conversation
u-boot-stm32mp resigns FIT configuration during do_deploy. The resiging process itself is not the issue, but the following: - it uses the image keyname for both images and configuration nodes, this will break the verification process at boot time. - it always signs the images node and Yocto sees that as optional using the FIT_SIGN_INDIVIDUAL variable This patch fixes both issues. Signed-off-by: Talel BELHAJ SALEM <bhstalel@gmail.com> Signed-off-by: Samar BEN ALI <samar.benali26@gmail.com>
Contributor
Author
|
I have just found out that there is a PR for this: #105 So, this PR can be closed |
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.
u-boot-stm32mp resigns FIT configuration during do_deploy.
The resiging process itself is not the issue, but the following:
This patch fixes both issues.