← Entropy Atlas
Reproducible randomness
Fuzzing
A fuzzer mutates inputs to find crashes, hangs, and security bugs.
Evaluation card
What “plenty” means here.
- Required property
- Efficient exploration, coverage feedback, and durable recording of any crashing input.
- If it fails
- The campaign repeats shallow mutations or loses the exact input and environment that triggered a bug.
- Relevant attacker
- The fuzzer acts like an attacker; unpredictability of the random stream is rarely the security property.
- The Plenty Line
- Scale corpus quality, coverage, workers, and time; record seeds but treat discovered inputs as the primary replay artifact.
- Why more is not automatically better
- A cryptographically stronger stream does not automatically explore code more intelligently.
Where it appears
Recognize the pattern.
- 01parser fuzzing
- 02protocol fuzzing
- 03compiler fuzzing
The Plentropy rule
Protect the requirement, then stop.
Scale corpus quality, coverage, workers, and time; record seeds but treat discovered inputs as the primary replay artifact.
Once that claim has comfortable evidence and margin, improve the next limiting factor instead of worshipping a larger entropy number.