-
Notifications
You must be signed in to change notification settings - Fork 3k
32 Byte key derivation may fail with a 16 Byte ROT key #10516
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
32 Byte key derivation may fail with a 16 Byte ROT key #10516
Conversation
7bbb082
to
bf37b8b
Compare
bf37b8b
to
f74d545
Compare
@jeromecoutant, sorry to bother you but please take a look again cause I thought about it and find out the real correction is a bit different and therefore I have updated the file. |
@yossi2le, thank you for your changes. |
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.
LGTM.
ci started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
At least it now matches the function parameter defined in:
Though I'm still wondering a bit which function it used before? Do we have an overloaded version somewhere, which does not have the last |
The actual_size parameter has a default value of 0 and therefore no overload function is needed. |
Found it now, yep makes sense. |
Also in , both will be in 5.12.3 |
Description
When trying to derive 32 bytes key with a 16 bytes ROT key the process may fail cause the ROT returned buffer size from kvstore has been ignored.
This bug fix is influencing PR #10493 (STM32F303RE: Activate FLASHIAP) because the device key test is failing on that PR.
Pull request type
Reviewers
@JanneKiiskila, @jeromecoutant
Release Notes