Michael Stone dixit:
> So that's basically just the --rng-entropy argument? If we switch rng-tools5
> to
/usr/lib/stunnel/arngc-slrd | runtunnel | \
rngd -f -r /proc/self/fd/0 -H 0.99 -B 2 \
-s 32 -W "$threshold" -t 300 -T 60
I just had the idea of “castling”¹, to avoid going through pu:
I’d upload src:rng-tools-debian (to unstable, but with the
intention of letting it transition to testing/buster) but
providing the rng-tools binary package, with NEWS suggesting
a move to rng-tools5. We’ll scrap the rng-tools-debian package
for now, and post-buster re-evaluate whether the missing flags
can be added to rng-tools5 (in which case we’ll start a tran‐
sition of whole Debian to it) or not (in which case we’ll keep
it but, perhaps, under a new name).
Sorry still not caught up with all mails yet, but this is the
best I think we can do, with the release coming up so soon.
The rng-tools-debian source package contains the well-tested
code users can, at the moment, expect, plus a massively better
initscript, so letting it take over the rng-tools binary package
has no cost and minor benefit to users (but allows us to go
without p-u, and to RM src:rng-tools entirely). This also allows
users some time for the transition (and two years to complain to
us if they *do*, for some reason, need the old rng-tools), if it’s
announced in buster that we plan to remove it for bullseye.
bye,
//mirabilos
① inspired from rereading the Launchpad bug discussion
