On Tue 2019-03-05 18:48:11 +0100, Santiago Vila wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907191
ugh :(
> I'll take a look at the kernel feature to see if it's better than this.
fwiw, the change isn't in the kernel -- it's in how userspace talks to
the kernel to get its
Hi.
Incidentally, my current workaround for this and related issues
has been (for the last months) to bind-mount /dev/urandom on /dev/random
inside the chroot.
This has been working like a charm in most cases, the exception being
packages who insist on testing the hardware or the operating
On Thu 2019-01-24 15:12:24 -0500, Daniel Kahn Gillmor wrote:
> re: https://bugs.debian.org/841208 --
>
> entropy exhaustion should no longer be an issue on debian buster, since
> the gcrypt started using getrandom() as of gcrypt 1.8.4 (see upstream
> https://dev.gnupg.org/T3894)
I'm closing this
re: https://bugs.debian.org/841208 --
entropy exhaustion should no longer be an issue on debian buster, since
the gcrypt started using getrandom() as of gcrypt 1.8.4 (see upstream
https://dev.gnupg.org/T3894)
--dkg
signature.asc
Description: PGP signature
4 matches
Mail list logo
