Page MenuHomeFreeBSD

random: Have RANDOM_PURE_START be a cross-platform source
ClosedPublic

Authored by obrien on Oct 23 2025, 11:23 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 20, 3:00 AM
Unknown Object (File)
Fri, Nov 14, 5:23 PM
Unknown Object (File)
Fri, Nov 14, 7:47 AM
Unknown Object (File)
Fri, Nov 14, 5:09 AM
Unknown Object (File)
Tue, Nov 11, 4:58 AM
Unknown Object (File)
Sat, Nov 8, 11:02 AM
Unknown Object (File)
Tue, Nov 4, 5:29 PM
Unknown Object (File)
Mon, Nov 3, 4:04 PM
Subscribers

Details

Summary

and one that will be with us in the long-term future.
(this helps reduce diffs in the future and for
down-stream users that trim entropy sources)

Obtained from: Juniper Networks

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Let me give some motivation, since someone may ask "why" or "so what".
We're removing entropy sources from the enum at Juniper, (related to D53304) and I'm trying to reduce diffs to upstream. Since we're changing the order, why not semi-prefetch the 16.0 changes. RANDOM_PURE_START is currently pegged to RANDOM_PURE_SAFE which should go away for 16.0. Another way of looking at it - since I've already changed the 'enum entropy' twice in 16.0 (any KPI concerns), the reorder of RANDOM_PURE_TPM to re-peg RANDOM_PURE_START to make a smaller commit in the future for the removal of safe(4) should be non-contentious. Also, I hope to get this into 15.0-RELEASE so that RANDOM_PURE_START doesn't change in 15.x.

This revision is now accepted and ready to land.Fri, Nov 7, 10:19 PM