2024-04-03 01:30:03 +03:00
|
|
|
# $NetBSD: files.dev,v 1.10 2024/04/02 22:30:03 charlotte Exp $
|
2015-08-21 05:18:18 +03:00
|
|
|
|
|
|
|
|
file dev/bio.c bio needs-flag
|
|
|
|
|
file dev/ccd.c ccd
|
|
|
|
|
file dev/cgd.c cgd
|
|
|
|
|
file dev/cgd_crypto.c cgd
|
|
|
|
|
file dev/clock_subr.c kern # XXX
|
|
|
|
|
file dev/clockctl.c clockctl
|
2017-11-01 22:34:45 +03:00
|
|
|
file dev/dksubr.c cgd | xbd | ccd | raid | dm | ld | sd | cd | wd
|
2015-08-21 05:18:18 +03:00
|
|
|
file dev/dkwedge/dk.c kern # XXX
|
|
|
|
|
file dev/dkwedge/dkwedge_apple.c dkwedge_method_apple
|
|
|
|
|
file dev/dkwedge/dkwedge_bsdlabel.c dkwedge_method_bsdlabel
|
|
|
|
|
file dev/dkwedge/dkwedge_gpt.c dkwedge_method_gpt
|
|
|
|
|
file dev/dkwedge/dkwedge_mbr.c dkwedge_method_mbr
|
2017-02-26 14:56:49 +03:00
|
|
|
file dev/dkwedge/dkwedge_rdb.c dkwedge_method_rdb
|
2024-04-03 01:30:03 +03:00
|
|
|
file dev/dkwedge/dkwedge_tos.c dkwedge_method_tos
|
2015-08-21 05:18:18 +03:00
|
|
|
file dev/firmload.c firmload
|
|
|
|
|
file dev/fss.c fss
|
|
|
|
|
file dev/keylock.c keylock
|
|
|
|
|
file dev/lockstat.c lockstat needs-flag
|
|
|
|
|
file dev/md.c md
|
|
|
|
|
file dev/mm.c kern # XXX
|
|
|
|
|
file dev/nullcons_subr.c nullcons needs-flag
|
|
|
|
|
file dev/radio.c radio needs-flag
|
Rewrite entropy subsystem.
Primary goals:
1. Use cryptography primitives designed and vetted by cryptographers.
2. Be honest about entropy estimation.
3. Propagate full entropy as soon as possible.
4. Simplify the APIs.
5. Reduce overhead of rnd_add_data and cprng_strong.
6. Reduce side channels of HWRNG data and human input sources.
7. Improve visibility of operation with sysctl and event counters.
Caveat: rngtest is no longer used generically for RND_TYPE_RNG
rndsources. Hardware RNG devices should have hardware-specific
health tests. For example, checking for two repeated 256-bit outputs
works to detect AMD's 2019 RDRAND bug. Not all hardware RNGs are
necessarily designed to produce exactly uniform output.
ENTROPY POOL
- A Keccak sponge, with test vectors, replaces the old LFSR/SHA-1
kludge as the cryptographic primitive.
- `Entropy depletion' is available for testing purposes with a sysctl
knob kern.entropy.depletion; otherwise it is disabled, and once the
system reaches full entropy it is assumed to stay there as far as
modern cryptography is concerned.
- No `entropy estimation' based on sample values. Such `entropy
estimation' is a contradiction in terms, dishonest to users, and a
potential source of side channels. It is the responsibility of the
driver author to study the entropy of the process that generates
the samples.
- Per-CPU gathering pools avoid contention on a global queue.
- Entropy is occasionally consolidated into global pool -- as soon as
it's ready, if we've never reached full entropy, and with a rate
limit afterward. Operators can force consolidation now by running
sysctl -w kern.entropy.consolidate=1.
- rndsink(9) API has been replaced by an epoch counter which changes
whenever entropy is consolidated into the global pool.
. Usage: Cache entropy_epoch() when you seed. If entropy_epoch()
has changed when you're about to use whatever you seeded, reseed.
. Epoch is never zero, so initialize cache to 0 if you want to reseed
on first use.
. Epoch is -1 iff we have never reached full entropy -- in other
words, the old rnd_initial_entropy is (entropy_epoch() != -1) --
but it is better if you check for changes rather than for -1, so
that if the system estimated its own entropy incorrectly, entropy
consolidation has the opportunity to prevent future compromise.
- Sysctls and event counters provide operator visibility into what's
happening:
. kern.entropy.needed - bits of entropy short of full entropy
. kern.entropy.pending - bits known to be pending in per-CPU pools,
can be consolidated with sysctl -w kern.entropy.consolidate=1
. kern.entropy.epoch - number of times consolidation has happened,
never 0, and -1 iff we have never reached full entropy
CPRNG_STRONG
- A cprng_strong instance is now a collection of per-CPU NIST
Hash_DRBGs. There are only two in the system: user_cprng for
/dev/urandom and sysctl kern.?random, and kern_cprng for kernel
users which may need to operate in interrupt context up to IPL_VM.
(Calling cprng_strong in interrupt context does not strike me as a
particularly good idea, so I added an event counter to see whether
anything actually does.)
- Event counters provide operator visibility into when reseeding
happens.
INTEL RDRAND/RDSEED, VIA C3 RNG (CPU_RNG)
- Unwired for now; will be rewired in a subsequent commit.
2020-04-30 06:28:18 +03:00
|
|
|
file dev/random.c rnd needs-flag
|
2015-08-21 05:18:18 +03:00
|
|
|
file dev/video.c video needs-flag
|
|
|
|
|
file dev/vnd.c vnd
|
2018-12-25 14:56:13 +03:00
|
|
|
file dev/ipmi.c ipmi needs-flag
|
2021-07-22 02:16:08 +03:00
|
|
|
file dev/smbios.c smbios
|
2021-10-10 16:03:08 +03:00
|
|
|
|
|
|
|
|
defpseudo efi
|
|
|
|
|
file dev/efi.c efi needs-flag
|