Hi, On Wed, Jul 23, 2014, at 00:59, Theodore Ts'o wrote: > 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).
I favored the idea of having a non-failing non-partial-read getrandom syscall. But I am with you if it often causes long stalls that we should stick to the old semantics. Thanks, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
