Re: Entropy error blocks lang/python38 installation

[Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost>]

Oh, the blocking was often permanent. If the system was otherwise idle then I would have to ssh in and run "ls -lR /" to get progress. I will admit that most of my experience with crypto is on Linux VMs. I've seen this enough that ssh and ls are just muscle memory for me now.

Maybe NetBSD is better than Linux at gathering entropy? Virtualisation definitely made Linux entropy gathering much worse.

Cheers,
Lloyd

On 17 June 2021 6:57:24 am NZST, "Greg A. Woods" <woods%planix.ca@localhost> wrote:

At Wed, 16 Jun 2021 11:18:02 +0200, Martin Husemann <martin%duskware.de@localhost> wrote:
Subject: Re: Entropy error blocks lang/python38 installation

 On Wed, Jun 16, 2021 at 11:10:34AM +0200, Joerg Sonnenberger wrote:
On Wed, Jun 16, 2021 at 06:13:23AM +0200, Martin Husemann wrote:
On Wed, Jun 16, 2021 at 03:42:35AM +0000, Thomas Mueller wrote:
I believe I must apply the fix/workaround every time.

 The entropy state gets stored on shutdown and reloaded on next boot.
 Fixing it once is enough.

 ...assuming that people actually use shutdown and don't just reboot.

 Kinda - but the instructions in the man page are quite explicit and
 ask you to save the entropy state at least once manually, which should
 avoid the blocking behaviour in all cases.

That's not an acceptable regression.

Previously no manual operations were ever necessary -- the blocking was
never permanent.

--
					Greg A. Woods <gwoods%acm.org@localhost>

Kelowna, BC     +1 250 762-7675           RoboHack <woods%robohack.ca@localhost>
Planix, Inc. <woods%planix.com@localhost>     Avoncote Farms <woods%avoncote.ca@localhost>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.