-
Notifications
You must be signed in to change notification settings - Fork 3k
Allow Devicekey::generate_root_of_trust() to define key size. #12823
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
Conversation
@SeppoTakalo, thank you for your changes. |
CI started |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
Test run: FAILEDSummary: 1 of 6 test jobs failed Failed test jobs:
|
please review the failures in tests |
5287d88
to
289f6f8
Compare
289f6f8
to
0ba1d79
Compare
This is just nitpicking, but the inline docs is missing the return code for DEVICEKEY_INVALID_KEY_SIZE. |
By default, generate 16 byte keys, to be compatible with bootloader. But allow user to generate 32 byte keys as well.
0ba1d79
to
fc9e75b
Compare
Fixed. |
Test run: FAILEDSummary: 1 of 6 test jobs failed Failed test jobs:
|
Will need a new CI run, set to needs: CI |
CI started |
Test run: SUCCESSSummary: 6 of 6 test jobs passed |
Summary of changes
Allow
Devicekey::generate_root_of_trust()
to define key size.By default, generate 16 byte keys, to be compatible with bootloader.
But allow user to generate 32 byte keys as well.
This fixes #12821
Impact of changes
Default key, generated by
Devicekey::generate_root_of_trust()
is now 16 bytes,instead of 32 bytes.
Migration actions required
If you want to generate 32 byte keys with
Devicekey::generate_root_of_trust()
,you need to explicitly supply key size as a parameter.
Documentation
Documentation is in the Doxygen, and it is updated.
Pull request type
Test results
Reviewers