-
Notifications
You must be signed in to change notification settings - Fork 3k
Add TRNG checkup in devicekey #9302
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
Add TRNG checkup in devicekey #9302
Conversation
Actually I believe when such a case happens, the TRNG itself is broken. When it fails, but still returns success, the TRNG itself has a very big bug. But nonetheless, adding such a check can be quite useful when a bug in the hal layer occurs. |
@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.
19b2a9c
to
29c9123
Compare
@yossi2le Please remove the second commit in this branch by rebasing this branch instead of merging the read-only reference into this one. I have no idea what kind of problems trying to bring this into 5.11.2 would cause with that commit, but I would wager it wouldn't be pretty. |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
…py func. this should enable as to eliminate some rare cases when the trng fail but still return success.
29c9123
to
2adf5db
Compare
CI started |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
Description
To eliminate the case in which TRNG return success but actually fail and did nothing I have added a check that test if the device key buffer has changed after calling entropy function.
This checkup is not a bulletproof mechanism but we believe that it should decrease the chances for such an error in substantially.
This PR is dependant on #9278
Pull request type
Reviewers