[please followup to tech-userlevel@ to keep discussion in one place]
Traditionally NetBSD has implemented three ways to get unpredictable
independent uniform random bytes out of the kernel's entropy pool:
- /dev/urandom -- never blocks, uses whatever is in the entropy pool,
returns short reads
On Fri, May 01, 2020 at 07:19:09PM +, Taylor R Campbell wrote:
> I propose that we additionally adopt getrandom and getentropy, two C
> APIs the world is converging on. For getentropy, this can be a simple
> userland wrapper in libc; for getrandom, this requires a new path into
> the kernel, a
> nia@ wrote the getentropy patch (probably needs a set list update too,
> and could use an automatic test); I wrote the getrandom patch.
> Feedback welcome!
My arguments for getentropy can be roughly summarized:
- It's just providing access to functionality already exposed to
userspace, but ma
