On Sat, Sep 14, 2019 at 9:35 AM Alexander E. Patrakov
Let me repeat: not -EINVAL, please. Please find some other error code,
so that the application could sensibly distinguish between this case
(low quality entropy is in the buffer) and the "kernel is too dumb" case
(and no entropy is in the buffer).
I'm not convinced we want applications to see that difference.
The fact is, every time an application thinks it cares, it has caused
problems. I can just see systemd saying "ok, the kernel didn't block,
so I'll just do
while (getrandom(x) == -ENOENTROPY)
instead. Which is still completely buggy garbage.
The fact is, we can't guarantee entropy in general. It's probably
there is practice, particularly with user space saving randomness from
last boot etc, but that kind of data may be real entropy, but the
kernel cannot *guarantee* that it is.
And people don't like us guaranteeing that rdrand/rdseed is "real
entropy" either, since they don't trust the CPU hw either.
Which means that we're all kinds of screwed. The whole "we guarantee
entropy" model is broken.
Description: Криптографическая подпись S/MIME