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

Provide a mechanism for key ID handling (MCUBOOT_BUILTIN_KEY) #1935

Open
davidvincze opened this issue Apr 9, 2024 · 1 comment
Open

Provide a mechanism for key ID handling (MCUBOOT_BUILTIN_KEY) #1935

davidvincze opened this issue Apr 9, 2024 · 1 comment
Assignees

Comments

@davidvincze
Copy link
Collaborator

As an initial solution the responsibility of handling key IDs was delegated to the underlying crypto library. This is far from ideal, MCUBoot forced an initial mapping between the image index and key ID (image_index +1). Handling of the key IDs should be independent of the bootloader and crypto code to be able to provide more generic solutions. Proposed solutions are:

  1. add a new IMAGE_TLV_KEYID TLV type (this can be set as the EXPECTED_KEY_TLV),
  2. provide a HAL API to do the mapping: ~bootutil_get_keyid_from_img_index()
Copy link

github-actions bot commented Oct 7, 2024

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the stale label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant