Re: /dev/random is hot garbage

[maya%netbsd.org@localhost]

On Sun, Jul 21, 2019 at 08:52:52PM +0200, Manuel Bouyer wrote:
> On Sun, Jul 21, 2019 at 06:43:04PM +0000, maya%netbsd.org@localhost wrote:
> > On Sun, Jul 21, 2019 at 11:55:23AM -0400, Greg Troxel wrote:
> > > Another approach, harder, is to create a xenrnd(4) pseudodevice and
> > > hypervisor call that gets bits from the host's /dev/random and injects
> > > them as if from a hardware rng.
> > > 
> > > 
> > 
> > That requires the ability coordinate "please run this backported patch"
> > to whoever does the package builds. Since we don't let anyone volunteer
> > for tasks and would rather have highly critical things rely on people
> > who stopped having NetBSD time about 5 years ago, that's not going to
> > happen.
> 
> no that's not the problem.
> Lots of nonsense has been written in this thread.
> /dev/randon actually works as documented and if rust wants /dev/urandom
> behavior it should use /dev/urandom. Also I'd like to get explained why
> a compiler needs that much random bits.
> 
> BTW, while talking about packages availability, when will the bootstrap
> kit for i386 be available ?

ftp://golden-delicious.urc.uninett.no/pub/rust/rust-std-1.35.0-i686-unknown-netbsd.tar.gz
?