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

Document that random must be "at least" as good as a CSPRNG. #30

Merged
merged 1 commit into from
Jun 1, 2023

Conversation

sunfishcode
Copy link
Member

Document that the random API doesn't necessarily need to be a CSPRNG; it need only be at least as good as a CSPRNG in both security and performance. This theoretically allows hardware random devices to be used directly, provided they're able to produce cryptographically-secure data with sufficient performance.

Fixes #28.

Document that the random API doesn't necessarily need to be a CSPRNG;
it need only be at least as good as a CSPRNG in both security and
performance. This theoretically allows hardware random devices to be
used directly, provided they're able to produce cryptographically-secure
data with sufficient performance.

Fixes #28.
@sunfishcode sunfishcode merged commit 77178f3 into main Jun 1, 2023
1 check failed
@sunfishcode sunfishcode deleted the sunfishcode/at-least branch June 1, 2023 13:33
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.

Clarify that a fast hardware entropy device could be a valid implementation
1 participant