[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180102152758.GB4871@port70.net>
Date: Tue, 2 Jan 2018 16:27:59 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] Add getrandom syscall wrapper function
* Rich Felker <dalias@...c.org> [2018-01-01 21:14:03 -0500]:
> > > glibc does not have a fallback for this syscall there was a long
> > > discussion about this, see here: https://lwn.net/Articles/711013/
> > > As they never found a good solution for their fallback. I think musl
> > > should also not provide a fallback.
>
> Interesting that the biggest issue seems to have been about using file
> descriptors as the fallback. That's something I never considered using
> in musl since we have AT_RANDOM and sysctl on ancient kernels that
> lack it. There are a small number of kernels between when sysctl
> started spamming syslog with deprecation warnings and when AT_RANDOM
> was added but I don't really care about those; it still works anyway.
note that getrandom gives new entropy after fork
but AT_RANDOM is the same.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
