Displaying 5 results from an estimated 5 matches for "nonblocking_pool".
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
...en the getrandom call will be
woken up when the input_pool received 128 bits. But those 128 bits are fed
from the input_pool to the blocking_pool based on the caller at the /dev/
random device. This implies that the reader for getrandom will NOT be able to
obtain data from the input_pool and the nonblocking_pool because the transfer
operation will not succeed. This implies that the nonblocking_pool remains
unseeded and yet getrandom returns data to the caller.
>
> That, however, is not the behavior I observed, which is that reading
> any amount from /dev/random will never block (since it is fed...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
...en the getrandom call will be
woken up when the input_pool received 128 bits. But those 128 bits are fed
from the input_pool to the blocking_pool based on the caller at the /dev/
random device. This implies that the reader for getrandom will NOT be able to
obtain data from the input_pool and the nonblocking_pool because the transfer
operation will not succeed. This implies that the nonblocking_pool remains
unseeded and yet getrandom returns data to the caller.
>
> That, however, is not the behavior I observed, which is that reading
> any amount from /dev/random will never block (since it is fed...
2016 Jul 29
0
getrandom waits for a long time when /dev/random is insufficiently read from
...call will be woken up when the input_pool received 128
> bits. But those 128 bits are fed from the input_pool to the
> blocking_pool based on the caller at the /dev/ random device. This
> implies that the reader for getrandom will NOT be able to obtain data
> from the input_pool and the nonblocking_pool because the transfer
> operation will not succeed. This implies that the nonblocking_pool
> remains unseeded and yet getrandom returns data to the caller.
I don't understand what this means. For my use case, hwrng is fed from
the host's urandom, so none of /dev/random, /dev/hwrng, /d...
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
Hi Alex,
> On Fri, 29 Jul 2016 12:24:27 +0200
>
> Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> > On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller
> >
> > <smueller at chronox.de> wrote:
> > > And finally, you have a coding error that is very very common but
> > > fatal
2016 Jul 29
2
getrandom waits for a long time when /dev/random is insufficiently read from
Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu:
Hi Alex,
> On Fri, 29 Jul 2016 12:24:27 +0200
>
> Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> > On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller
> >
> > <smueller at chronox.de> wrote:
> > > And finally, you have a coding error that is very very common but
> > > fatal