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

Actually fill fr_rand_pool.randrsl #5361

Closed

Conversation

jejones3141
Copy link
Contributor

@jejones3141 jejones3141 commented Jul 9, 2024

In fr_rand_init(), where /dev/urandom is available, the code as written would always read into the beginning of fr_rand_pool.randrsl, so that only the first max(read return value) bytes would be filled.

(Not associated with CID #1604611, but found while looking into it.)

In fr_rand_init(), where /dev/urandom is available, the code as
written would always read into the beginning of fr_rand_pool.randrsl,
so that only the first max(read returnh value) bytes would be filled.

(Not associated with CID #1604611, but found while looking into it.)
@alandekok
Copy link
Member

Nice! Is this also applicable to v3?

@jejones3141
Copy link
Contributor Author

Don't know; where can I find the v3 code?

@jejones3141
Copy link
Contributor Author

No need to be inconsistent with "fill the random pool" (d5276a8); will resubmit.

@jejones3141 jejones3141 deleted the fr_rand_init_read_overlap branch July 12, 2024 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants