entropy
ClosedPublic
Actions

Authored by markj on Jul 3 2025, 5:39 PM.

Details

Reviewers

cse_cem_gmail_com
cem

Group Reviewers

csprng

Commits

rGfa8db724ae6e: random: Treat writes to /dev/random as separate from /entropy

Summary

RANDOM_CACHED is overloaded to refer both to entropy obtained from files
loaded by the boot loader, and entropy obtained via writes to
/dev/random. Introduce a new source, RANDOM_RANDOMDEV, to refer to the
latter. This is to enable treating RANDOM_CACHED as a special case in
the NIST health test implementation.

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

markj created this revision.Jul 3 2025, 5:39 PM

Herald added a subscriber: imp. · View Herald TranscriptJul 3 2025, 5:39 PM

markj requested review of this revision.Jul 3 2025, 5:39 PM

Herald added a subscriber: obrien. · View Herald TranscriptJul 3 2025, 5:39 PM

Harbormaster completed remote builds in B65197: Diff 157900.Jul 3 2025, 5:39 PM

markj added a parent revision: D51154: random: Add NIST SP 800-90B entropy source health test implementations.Jul 3 2025, 5:39 PM

Seems reasonable.

libexec/rc/rc.conf
697	I'm not totally sure I understand the mask change here, can you explain it?
sys/dev/random/random_harvestq.c
590–593	Does this have ABI implications for loadable modules?

markj added inline comments.Jul 4 2025, 2:13 AM

libexec/rc/rc.conf
697	I'll update the description later too, but: this setting disables all environmental sources except SWI, INTERRUPT, NET_NG, NET_TUN, MOUSE, KEYBOARD, ATTACH, CACHED. That corresponds to a mask of 0x1ff (511). To avoid changing any behaviour with this patch, I changed this to 0x11ff so that RANDOMDEV is included too.
sys/dev/random/random_harvestq.c
590–593	Yes, I should bump __FreeBSD_version for this change. I believe the userspace ABI is unaffected so long as we don't change the ordering of "environmental" sources. That's because `user_immutable_mask` in `random_check_uint_harvestmask()` disallows enabling or disabling non-environmental sources, and I don't think there are any other userspace-facing interfaces which are affected.