diff options
| author | jirka-h <hladky.jiri@gmail.com> | 2022-03-31 15:53:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-31 15:53:36 +0200 |
| commit | 66323fb109e1d39ed06c2176a1ea4390f5feef30 (patch) | |
| tree | 3cac9f8c8c39fec8e3c420b2aacfa062f1d4ed1b | |
| parent | Update README.md (diff) | |
| download | haveged-66323fb109e1d39ed06c2176a1ea4390f5feef30.tar.xz haveged-66323fb109e1d39ed06c2176a1ea4390f5feef30.zip | |
Update README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -8,6 +8,8 @@ Starting from Linux kernel v5.6, the HAVEGED inspired algorithm has been include I'm happy that these changes made it into the mainline kernel. It's pleasing to see that the main idea behind HAVEGED has sustained time test - it was published already in 2003 [here.](https://www.irisa.fr/caps/projects/hipsor/publications/havege-tomacs.pdf) I'm also glad that the HAVEGE algorithm is being further explored and examined - see the [CPU Jitter Random Number Generator.](https://www.chronox.de/jent.html) +Please note that while the mainline Linux Kernel and HAVEGED are using the same concept to generate the entropy (utilizing the CPU jitter) the implementation is completely different. In this sense, HAVEGED can be viewed as another entropy source. + It means that HAVEGED **service** is now less relevant. However, it's still useful in the following situations, when you * need randomness early in the boot process, before the CRNG in the Linux kernel gets fully initialized. * want to deploy an additional entropy source. HAVEGED now inserts entropy into the kernel every 60 seconds, regardless of the entropy level reported by Linux Kernel. It does not affect the `/dev/random` read speed but it diversifies the entropy sources, making the Linux Kernel CRNG more robust. |