Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
rng-tools: 6.7 -> 6.8 #73007
Motivation for this change
Thanks! I looked at the individual patches and noticed that argp-standalone can now be used (nhorman/rng-tools@ddecdb5). It's needed when using musl because that doesn't include argp.
I don't know, however, how to build just this package with musl to verify that that works.
Would it be possible to change enableFeature withJitterEntropy to withFeature as well as enable it by default? This is the default in two other distributions, archlinux and fedora, and shouldn't harm entropy at all, only help it. Otherwise looks good. I tested this on my own branch (c0bw3b/nixpkgs@pkg/rngtools...kmcopper:rng-tools) and it works great. Additionally this will allow rngd to improve entropy on sandybridge systems.
Closure size (with my branch):
Since this v6.8 release
Upstream configure flag to add jitter source is
Entropy is more complicated than that. You can actually harm it with too many sources gathering too many data points from not-so-unpredictable events. See Dan J. Bernstein on this topic:
Sandy Bridge has RDRAND I believe? Plus it would help rngd only if you don't have any other sources available. On my test system with RDRAND and TPM sources available, the average "input channel speed" remains the same with or without jitter source.
Regarding closure size (
# standard build without jitterentropy: /nix/store/c00nxwcn3x3x1n87hidbgqgvln2xbwq8-rng-tools-6.8 80.0K 43.9M # rng-tools build WITH jitterentropy: /nix/store/xb347wd2bvqn1fh7p6db2b75lfdfm5i3-rng-tools-6.8 97.3K 43.9M