----- Forwarded message from coderman <coderman@gmail.com> ----- Date: Mon, 14 Oct 2013 18:07:57 -0700 From: coderman <coderman@gmail.com> To: David Johnston <dj@deadhat.com> Cc: Cryptography List <cryptography@metzdowd.com>, Discussion of cryptography and related <cryptography@randombit.net> Subject: Re: [cryptography] /dev/random is not robust Message-ID: <CAJVRA1SEmBgfr46BuGbjpj=+ZjKHKz7dLUcTkYCKA4ikaHY1_Q@mail.gmail.com> On Mon, Oct 14, 2013 at 5:35 PM, <dj@deadhat.com> wrote:

http://eprint.iacr.org/2013/338.pdf

"...it remains unclear if these attacks lead to actual exploitable vulnerabilities in practice." in my mtrngd for XSTORE i not only fed /dev/random when it became write-able (entropy less than full) but also fed it at regular intervals, specifically to keep the pool fresh. in the standard rng-tools rngd, you specify this parameter with the timeout parameter, "Interval written to random-device when the entropy pool is full, in seconds (default: 60)" i am pleased to see this made it into the stock rngd source! best regards, _______________________________________________ cryptography mailing list cryptography@randombit.net http://lists.randombit.net/mailman/listinfo/cryptography ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://ativel.com http://postbiota.org AC894EC5: 38A5 5F46 A4FF 59B8 336B 47EE F46E 3489 AC89 4EC5