-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix bug in K64F trng_api.c #5550
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
Thanks for spotting and fixing this! @0xc0170 Could you also add @mazimkhan as a reviewer, please? |
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
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
/morph build |
Build : SUCCESSBuild number : 590 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 202 |
Test : FAILUREBuild number : 403 |
/morph test |
Test : SUCCESSBuild number : 413 |
Description
K64F
trng_get_byte
function assumed memory for byte was zero initialized.That means that this line would OR random data with data existing in memory. All values will eventually reach 255 if called many times.
Steps to test or reproduce
Use this test program to replicate the issue: