Re: [PATCH v4 0/5] /dev/random - a new approach

2016-06-18 Thread Stephan Mueller
Am Samstag, 18. Juni 2016, 10:44:08 schrieb Theodore Ts'o: Hi Theodore, > > At the end of the day, with these devices you really badly need a > hardware RNG. We can't generate randomness out of thin air. The only > thing you really can do requires user space help, which is to generate > keys l

Re: [PATCH v4 0/5] /dev/random - a new approach

2016-06-18 Thread Theodore Ts'o
On Fri, Jun 17, 2016 at 03:56:13PM +0200, David Jaša wrote: > I was thinking along the lines that "almost every important package > supports FreeBSD as well where they have to handle the condition so > option to switch to Rather Break Than Generate Weak Keys would be nice" > - but I didn't expect t

Re: [PATCH v4 0/5] /dev/random - a new approach

2016-06-18 Thread Stephan Mueller
Am Freitag, 17. Juni 2016, 11:26:23 schrieb Sandy Harris: Hi Sandy, > David Jaša wrote: > > BTW when looking at an old BSI's issue with Linux urandom that Jarod > > Wilson tried to solve with this series: > > https://www.spinics.net/lists/linux-crypto/msg06113.html > > I was thinking: > > 1) wou

Re: [PATCH v4 0/5] /dev/random - a new approach

2016-06-18 Thread Stephan Mueller
Am Freitag, 17. Juni 2016, 15:56:13 schrieb David Jaša: Hi David, > Hi Stephan, > > thank you for your thorough reply, > > On St, 2016-06-15 at 18:58 +0200, Stephan Mueller wrote: > > Am Mittwoch, 15. Juni 2016, 18:17:43 schrieb David Jaša: > > > > Hi David, > > > > > Hello Stephan, > > > >

Re: [PATCH] crypto: use timespec64 for jent_get_nstime

2016-06-18 Thread Stephan Mueller
Am Freitag, 17. Juni 2016, 17:59:41 schrieb Arnd Bergmann: Hi Arnd, > The jent_get_nstime() function uses __getnstimeofday() to get > something similar to a 64-bit nanosecond counter. As we want > to get rid of struct timespec to fix the y2038 overflow, > this patch changes the code to use __getn