632d1127df
We're a far cry from the good old days when we just read from /dev/urandom without any fuss... In particular, the threading logic is slightly non-trivial and probably worth some basic sanity checks. Also write a fork-safety test, and test the fork-unsafe-buffering path. The last one is less useful right now, since fork-unsafe-buffering is a no-op with RDRAND enabled (although we do have an SDE bot...), but it's probably worth exercising the code in https://boringssl-review.googlesource.com/c/boringssl/+/31564. Change-Id: I14b1fc5216f2a93183286aa9b35f5f2309107fb2 Reviewed-on: https://boringssl-review.googlesource.com/31684 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
|---|---|---|
| .. | ||
| bot | ||
| fipstools | ||
| 32-bit-toolchain.cmake | ||
| all_tests.go | ||
| all_tests.json | ||
| BUILD.toplevel | ||
| check_filenames.go | ||
| check_imported_libraries.go | ||
| convert_comments.go | ||
| convert_wycheproof.go | ||
| diff_asm.go | ||
| doc.config | ||
| doc.css | ||
| doc.go | ||
| embed_test_data.go | ||
| generate_build_files.py | ||
| generate-asm-lcov.py | ||
| generate-coverage.sh | ||
| make_errors.go | ||
| make_prefix_headers.go | ||
| run_android_tests.go | ||
| whitespace.txt | ||