random: Have RANDOM_PURE_START be a cross-platform source
ClosedPublic
Actions

Authored by obrien on Oct 23 2025, 11:23 PM.

Details

Reviewers

Group Reviewers

Commits

rG0339b24f8d30: random: Have RANDOM_PURE_START be a cross-platform source
rGe224f2c1b98b: random: Have RANDOM_PURE_START be a cross-platform source
rG068fea0aa15b: random: Have RANDOM_PURE_START be a cross-platform source

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

obrien created this revision.Oct 23 2025, 11:23 PM

Herald added a subscriber: imp. · View Herald TranscriptOct 23 2025, 11:23 PM

obrien requested review of this revision.Oct 23 2025, 11:23 PM

Harbormaster completed remote builds in B68065: Diff 164919.Oct 23 2025, 11:23 PM

obrien added a reviewer: csprng.Fri, Oct 31, 5:05 AM

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.