Fix unsound rand rustsec 2026 0097#831
Open
waxspin wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade rand 0.8 → 0.9 (mitigates RUSTSEC-2026-0097)
Bumps rand from 0.8.5 to 0.9.4 to resolve the advisory flagged in the previous commit. Adapts all call sites to the breaking API changes in rand 0.9.
API changes
rand::distributions::Open01rand::distr::Open01SeedableRng::from_entropy()SeedableRng::from_os_rng()rand::rngs::mock::StepRngMockRng(see below)from_os_rng() requires the os_rng feature in rand_core, exposed as rand's own os_rng feature — added to statime-linux's dependency.
MockRng
rand::rngs::mock::StepRng was deprecated in 0.9 without replacement. Rather than suppress the warning, a minimal MockRng(u64) implementing RngCore is added to the test module. The RNG is only used to produce timing jitter in delay
requests, so the specific values don't affect test correctness.
Test results
74 unit tests + 13 doctests pass with no warnings.