Re: getrandom and getentropy

[maya%NetBSD.org@localhost]

For the previous discussion about it:
http://mail-index.netbsd.org/tech-crypto/2018/06/21/msg000763.html

This discussion calls for only having one interface, the
getrandom(...,0) one, which is the path other operating systems
took with their /dev/{,u}random.


The getrandom interface intentionally traps people to make questionable
design choices.
We might immediately take https://www.2uo.de/myths-about-urandom/

And re-write bits about /dev/random as being about getrandom(...,GRND_RANDOM).

Calling it "/dev/random" behaviour is ambiguous. Didn't you fix
/dev/random to not have this limitation, and be more like
getrandom(...,0)?


Having compat shims in libc is as good as having compat shims in syscall
because it isn't possible to share raw syscall code between NetBSD and
other operating systems -- our calling convention is different.