Re: dietlibc broken on i386 since Feb 2018?
Frank Bergmann <[email protected]> Tue, 8 Oct 2019 21:04:21 +0200
| Newsgroups | gmane.linux.lib.dietlibc |
|---|---|
| Message-ID | <[email protected]> |
Reject due to wrong sender address, repeating... On Tue, Oct 08, 2019 at 08:29:00PM +0200, Frank Bergmann wrote: > On Thu, Oct 03, 2019 at 09:08:00PM +0200, Felix von Leitner wrote: > > to be compiled with support for it, or not. This means doing additional > > stuff in the startup code, namely initialize one variable to a random > > value, and it has to be real randomness for security reasons. > > Got it. > > > The way dietlibc does this is take the randomness the kernel hands it, > > and there really is no other good way to do it, that is why this is > > turned on by default. The alternative is to read from /dev/urandom, but > > that can fail in chroot environments or if the file table is full. What > > then? Abort the binary? That is clearly also bad. > > > > The only recommendable fix is to tell people to use a kernel which > > supports passing randomness. > > Sure, I got it. > > > Newer kernels also have a system call to get randomness, but that was > > added even later so it does not help with this problem. > > > > > > 2.6.18 was released in 2006. > > > > If that is not ancient then what is? > > > haha... I thought that sysenter was introduced even long before that - and > > > this is still configurable in dietfeatures. ;-) > > > > So is this feature. > > > > What is your point? > > Kidding, just kidding, Felix. :-) -- EDV Frank Bergmann Tel. +49-5221-9249753 LPIC-3 Linux Professional Fax +49-5221-9249754 Pödinghauser Str. 5 email [email protected] D-32051 Herford USt-IdNr DE237314606