Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-22 Thread Nick Kossifidis
I'm so sorry, something went terribly wrong with gmail/thunderbird :-( 2013/2/22 Nick Kossifidis mickfl...@gmail.com: Hello all, It's nice to see there is still discussion on the matter of using cpu timings for entropy. In general using cpu timings for gathering entropy is a nice idea but

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-21 Thread Phil Carmody
Apologies if this is misthreaded, I had to hand-craft the headers. The patch offers an entropy generator based on CPU timing jitter. The entropy collector has the following properties: * it does not maintain any state and therefore does not need any seed What is this pool if it's not

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-21 Thread Stephan Mueller
On 21.02.2013 15:07:12, +0100, Phil Carmody pc+l...@asdf.org wrote: Hi Phil, Apologies if this is misthreaded, I had to hand-craft the headers. The patch offers an entropy generator based on CPU timing jitter. The entropy collector has the following properties: * it does not maintain any

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-21 Thread Theodore Ts'o
On Thu, Feb 21, 2013 at 12:46:45PM -0500, Sandy Harris wrote: Also, in some designs it is possible to get very close to calculating entropy. The Turbid generator, for example, uses physical measurements of sound card properties plus arguments from standard circuit physics to prove a lower

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-10 Thread Sandy Harris
On Sun, Feb 10, 2013 at 1:50 PM, Theodore Ts'o ty...@mit.edu wrote: On Sun, Feb 10, 2013 at 01:46:18PM +0100, Stephan Mueller wrote: However, the CPU has timing jitter in the execution of instruction. And I try to harvest that jitter. The good thing is that this jitter is always present and

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-10 Thread Stephan Mueller
On 10.02.2013 19:50:02, +0100, Theodore Ts'o ty...@mit.edu wrote: Hi Ted, On Sun, Feb 10, 2013 at 01:46:18PM +0100, Stephan Mueller wrote: However, the CPU has timing jitter in the execution of instruction. And I try to harvest that jitter. The good thing is that this jitter is always present

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-10 Thread Sandy Harris
On Sun, Feb 10, 2013 at 2:32 PM, Stephan Mueller smuel...@chronox.de wrote: On 10.02.2013 19:50:02, +0100, Theodore Ts'o ty...@mit.edu wrote: Given all your doubts on the high-precision timer, how can you reasonably state that the Linux kernel RNG is good then? The data from

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-10 Thread Theodore Ts'o
On Sun, Feb 10, 2013 at 08:32:37PM +0100, Stephan Mueller wrote: Given all your doubts on the high-precision timer, how can you reasonably state that the Linux kernel RNG is good then? Because we're measuring intervals that are substantially larger than CPU jitter. (i.e., inputs from

Re: [RFC][PATCH] Entropy generator with 100 kB/s throughput

2013-02-09 Thread Jeff Epler
On Sat, Feb 09, 2013 at 01:06:29PM -0500, Theodore Ts'o wrote: For that reasons, what I would suggest doing first is generate a series of outputs of jitterentropy_get_nstime() followed by schedule(). Look and see if there is any pattern. That's the problem with the FIPS 140-2 tests. Passing