Skip to content

u-boot-stm32mp: Fix FIT signing process#106

Closed
bhstalel wants to merge 1 commit into
STMicroelectronics:scarthgapfrom
bhstalel:fix-u-boot-fit
Closed

u-boot-stm32mp: Fix FIT signing process#106
bhstalel wants to merge 1 commit into
STMicroelectronics:scarthgapfrom
bhstalel:fix-u-boot-fit

Conversation

@bhstalel

Copy link
Copy Markdown
Contributor

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.

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>
@bhstalel

Copy link
Copy Markdown
Contributor Author

I have just found out that there is a PR for this: #105

So, this PR can be closed

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.

1 participant