From: Michael Kerrisk Date: Thu, 22 Jan 2015 20:36:04 +0000 (+0100) Subject: getrandom.2: Clarify sentence on getrandom() and partial GRND_RANDOM reads X-Git-Tag: man-pages-3.79~38 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=28ef3452e4b32b7ae270ed7141b679c57cc05e6c;p=thirdparty%2Fman-pages.git getrandom.2: Clarify sentence on getrandom() and partial GRND_RANDOM reads Signed-off-by: Michael Kerrisk --- diff --git a/man2/getrandom.2 b/man2/getrandom.2 index f302508dba..c5fdf15cb3 100644 --- a/man2/getrandom.2 +++ b/man2/getrandom.2 @@ -224,7 +224,7 @@ is not specified and .I buflen is less than or equal to 256, a return of fewer bytes than requested should never happen, -but the careful user-space code should check for this anyway! +but the careful programmer will check for this anyway! .SS Choice of random device Unless you are doing long-term key generation (and perhaps not even then), you probably shouldn't be using @@ -235,9 +235,11 @@ are quite conservative, and so should be sufficient for all purposes. The disadvantage of .B GRND_RANDOM is that it can block. -Furthermore, dealing with partially fulfilled +Furthermore, dealing with the partially fulfilled .BR getrandom () -requests increases code complexity. +requests that can occur when using +.B GRND_RANDOM +increases code complexity. .SS Emulating OpenBSD's getentropy() The .BR getentropy ()