On Tue, Jul 22, 2014 at 11:49:52AM +0200, Hannes Frederic Sowa wrote: > > I think a lot of checks are of the type "if (getrandom() < 0)", so this > actually was the kind of programming errors I wanted to guard against. > Also, on some systems it is very likely that we return a short write to > user space, so it prevents this very common situation. Even if one would > like to extract 64 bytes randomness, one would often need two calls to > getrandom() on my virtualized systems. Would be great to know that in > blocking mode, either I get a -1 or the buffer is always filled and I > won't need to do pointer arithmetic to fill the rest of the buffer. But why would you need to use GRND_RANDOM in your scenario, and accept your application potentially getting stalled and stuck in amber for perhaps hours? If you are going to accept your application stalling like that, you can do the pointer arithmatic. It's really not hard, and someone who can't do that, again, shouldn't be allowd anywhere near crypto code in the first place (and if they are, they'll probably be making lots of other, equally fatal if not more so, newbie mistakes). - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
