librandom.rs(3): Randomness library for Rust #178

New Issue

emma · 2026-02-12T05:36:15-07:00

emma commented

2026-02-12 05:36:15 -07:00

How should randomness be implemented? I certainly want a wrapper around the C random functions because I’m not comfortable implementing randomness since it wouldn’t be cryptographically secure.

emma added the

enhancement

question

labels 2026-02-12 05:36:15 -07:00

emma self-assigned this 2026-02-12 05:36:15 -07:00

emma added a new dependency 2026-02-12 05:36:57 -07:00

#55 `mix(1)` – randomly sort inputs

trinity commented

2026-02-12 08:27:51 -07:00

Any cryptographically non-random library should be specifically labeled nonsecure or insecure to avoid StackOverflow-style problems (also known as the Microsoft method; where someone paid six figures to do something they don't understand uses the wrong tool for the job and blows a hole/backdoor in the building/server).

Any cryptographically non-random library should be specifically labeled `nonsecure` or `insecure` to avoid StackOverflow-style problems (also known as the Microsoft method; where someone paid six figures to do something they don't understand uses the wrong tool for the job and blows a hole/backdoor in the building/server).

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Blocks

#55 `mix(1)` – randomly sort inputs

bonsai/harakit

Reference: bonsai/harakit#178

librandom.rs(3): Randomness library for Rust #178

`librandom.rs(3)`: Randomness library for Rust #178