On Tue, 2006-12-05 at 14:07 +0100, Jan Glauber wrote:
> Yes, if an attacker knows the initial clock value a brute-force attack
> would be feasible to predict the output. But I don't know if the
> hardware completely relies on the clock values or if there is any
> internal state which is not visible
On Thu, 2006-12-07 at 19:43 +0100, Arnd Bergmann wrote:
> On Thursday 07 December 2006 16:19, Jan Glauber wrote:
> > Hm, why is /dev/urandom implemented in the kernel?
> >
> > It could be done completely in user-space (like libica already does)
> > but I think having a device node where you can re
On Thursday 07 December 2006 16:19, Jan Glauber wrote:
> Hm, why is /dev/urandom implemented in the kernel?
>
> It could be done completely in user-space (like libica already does)
> but I think having a device node where you can read from is the simplest
> implementation. Also, if we can solve th
On Thu, 2006-12-07 at 16:06 +0100, Arnd Bergmann wrote:
> On Friday 01 December 2006 14:19, Jan Glauber wrote:
> > I've chosen the char driver since it allows the user to decide which
> > pseudo-random
> > numbers he wants to use. That means there is a new interface for the s390
> > PRNG, called /
On Friday 01 December 2006 14:19, Jan Glauber wrote:
> I've chosen the char driver since it allows the user to decide which
> pseudo-random
> numbers he wants to use. That means there is a new interface for the s390
> PRNG, called /dev/prandom.
>
> I would like to know if there are any objections
On Mon, 2006-12-04 at 11:15 -0500, [EMAIL PROTECTED] wrote:
> On Fri, 01 Dec 2006 14:19:15 +0100, Jan Glauber said:
> > New s390 machines have hardware support for the generation of pseudo-random
> > numbers. This patch implements a simple char driver that exports this
> > numbers
> > to user-spac
On Fri, 01 Dec 2006 14:19:15 +0100, Jan Glauber said:
> New s390 machines have hardware support for the generation of pseudo-random
> numbers. This patch implements a simple char driver that exports this numbers
> to user-space. Other possible implementations would have been:
> + for (i = 0; i
Alan <[EMAIL PROTECTED]> wrote:
> On Fri, 01 Dec 2006 16:20:46 +0100
> Jan Glauber <[EMAIL PROTECTED]> wrote:
>> Yes, a user can just symlink urandom to prandom and will have a faster
>> generator.
>
>
> More usefully they can use it as an entropy source with an entropy
> daemon to feed it into
On Fri, 01 Dec 2006 16:20:46 +0100
Jan Glauber <[EMAIL PROTECTED]> wrote:
> Yes, a user can just symlink urandom to prandom and will have a faster
> generator.
More usefully they can use it as an entropy source with an entropy
daemon to feed it into the standard urandom/random.
-
To unsubscribe f
On Fri, 2006-12-01 at 13:39 +, Alan wrote:
> > * merging the s390 PRNG with the random pool implementation
> > PRO: no new interface, random numbers can be read through /dev/urandom
> > CON: complex implementation, could only use traditional /dev/urandom
> > algorithm
> > or hardware-acce
> * merging the s390 PRNG with the random pool implementation
> PRO: no new interface, random numbers can be read through /dev/urandom
> CON: complex implementation, could only use traditional /dev/urandom algorithm
> or hardware-accelerated implementation
Also PRO: Can be verified by non-IBM
New s390 machines have hardware support for the generation of pseudo-random
numbers. This patch implements a simple char driver that exports this numbers
to user-space. Other possible implementations would have been:
* using the new hwrandom number generator API
PRO: reuse of an existing interface
12 matches
Mail list logo
