From ad5973028c42d947440cdae5e4f106152c3dda28 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 8 Jun 2022 17:53:50 +0000 Subject: Prepare for 2.6.0.0; delete s6-fillurandompool; add rngseed Signed-off-by: Laurent Bercot --- doc/s6-fillurandompool.html | 74 --------------------------------------------- 1 file changed, 74 deletions(-) delete mode 100644 doc/s6-fillurandompool.html (limited to 'doc/s6-fillurandompool.html') diff --git a/doc/s6-fillurandompool.html b/doc/s6-fillurandompool.html deleted file mode 100644 index c07b0f4..0000000 --- a/doc/s6-fillurandompool.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - s6-linux-utils: the s6-fillurandompool program - - - - - - -

-s6-linux-utils
-Software
-skarnet.org -

- -

The s6-fillurandompool program

- -

-s6-fillurandompool blocks until the machine's -/dev/urandom entropy pool is filled up. Then it exits. -

- -

Interface

- -
-     s6-fillurandompool
-
- -

Rationale

- -

- For some reason, Linux has two separate entropy pools: one for -/dev/random and one for /dev/urandom. -

- -

- Reading from /dev/random blocks when its entropy pool is -not full enough, so it will never return weak random data. (Reading -from /dev/random is overkill anyway, and -you -should not be doing it.) -

- -

- However, reading from /dev/urandom (which -you should be doing) -will not block, even though the entropy pool may not have been -initialized yet. That's the only insecure thing about it: at boot time, -/dev/urandom may return weak random data, until its entropy -pool has filled up. -

- -

- s6-fillurandompool is meant to address this issue. Call it once -early on in your boot scripts, before you need any serious random data; -when it exits, the /dev/urandom pool has been properly initialized, -and it is now safe to read from /dev/urandom every time you need -random data, until the machine shuts down. -

- -

Notes

- - - - - -- cgit v1.2.3