Hi Jason!
I'd like to revive the topic of whether writes to /dev/urandom and /dev/random
should immediately reseed the CRNG, as I'm not sure that the past discussions on
this really resolved the issue. Currently, writes to /dev/{u,}random do *not*
reseed the CRNG, and thus the RNG's output isn't affected by preceding writes
until a reseed happens for an unrelated reason such as the periodic timer.
(Exception: if the state is CRNG_EMPTY, writes do immediately take effect.)
(Note, I'm *not* talking about whether entropy should be credited for writes to
/dev/{u,}random. It shouldn't be credited, and it isn't. That's a separate
topic, though it got somewhat conflated with this one in past discussions.)
As you know, the current behavior means that the "obvious" way of managing a
seed file, i.e. 'cat seed_file > /dev/urandom; cat /dev/urandom > seed_file',
may reduce the entropy of the seed file. Your suggested approach, SeedRNG
(https://git.zx2c4.com/seedrng) works around this by using hashing. Still, the
current behavior makes things difficult and surprising for users. The random(4)
man page still recommends the "wrong" way. Also, IIUC, even if you run SeedRNG,
if you then do something that uses the RNG like generating a cryptographic key,
it's possible that the seed file contributed nothing to it. The faster
reseeding schedule in v5.18+ does make this less likely, but it can happen.
This topic was discussed in early 2022 in the thread
"random: allow writes to /dev/urandom to influence fast init"
(https://lore.kernel.org/lkml/20220322191436.110963-1-Jason@xxxxxxxxx/T/#u).
Ultimately, it was decided not to change the current behavior.
I'm wondering if this should be revisited, for a couple reasons.
First, two months after that discussion, commit e85c0fc1d94c ("random: do not
pretend to handle premature next security model") was merged. I *think* that
eliminated the security reason to delay reseeding on writes to /dev/{u,}random,
as now "premature next" attacks are no longer under consideration.
Second, AFAICT, the current behavior actually hasn't always been the behavior,
contrary to previous statements/discussions which claimed that it's been the
behavior "forever". I did a bit of research, and whether writes to
/dev/{u,}random take effect immediately actually has a bit of history:
Starting in 1995 (v1.3.30, random.c created): writes take effect immediately
Starting in 1999 (v2.3.16, secondary pool added): writes don't take effect immediately
Starting in 2007 (v2.6.22, commit 7f397dcdb78d): writes take effect immediately
Starting in 2016 (v4.8, ChaCha20 CRNG added): writes don't take effect immediately
So the current "era" of behavior started in 2016, with 1999-2007 matching
current behavior too. However, the 1999-2007 era ended with commit 7f397dcdb78d
("random: fix seeding with zero entropy") that intentionally changed this
behavior. Interestingly, discussion of this patch does not appear in any
mailing list archive, though a bug report "Seeding /dev/random not working"
(https://lore.kernel.org/lkml/de6d2b4f0705290453kec2b050pb4d0bebc256b87a5@xxxxxxxxxxxxxx/T/#u)
can be found earlier in the same day the commit was made. Also, CVE-2007-2453
was allocated for this fix (though the CVE also covers a different RNG bug too).
This suggests that at the time, writes not taking effect immediately was
considered a security vulnerability that needed to be fixed immediately.
commit e192be9d9a30 ("random: replace non-blocking pool with a Chacha20-based
CRNG") then started the current "era" in 2016, returning to the behavior that
had been considered a vulnerability and fixed in 2007. In contrast to the 2007
change, it's not clear that the 2016 change in behavior was intentional. It
happened in the big commit that introduced ChaCha20 to the RNG. (And yes, even
2016 is still a long time ago in kernel terms, but it's not *that* long ago.)
Anyway, I'm wondering if the current behavior is really what we want, especially
considering that the "premature next" security model is no longer targetted.
Should we make writes to /dev/{u,}random immediately reseed the CRNG so that
users don't need to do the dance with hashing the old and new seeds together?
Anything I'm just completely missing? Performance concerns about reseeding?
Some attack that we're still trying to prevent by delaying the reseed?
This would be the potential change, BTW:
diff --git a/drivers/char/random.c b/drivers/char/random.c
index 3cb37760dfec2..97ea2938c715c 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -1420,6 +1420,7 @@ static ssize_t write_pool_user(struct iov_iter *iter)
cond_resched();
}
}
+ crng_reseed(NULL);
memzero_explicit(block, sizeof(block));
return ret ? ret : -EFAULT;
