linux-kernel - Re : [HW_RNG] How to use generic rng in kernel space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060804130030.90361.qmail@web25805.mail.ukl.yahoo.com>
Date:	Fri, 4 Aug 2006 13:00:30 +0000 (GMT)
From:	moreau francis <francis_moreau2000@...oo.fr>
To:	Michael Buesch <mb@...sch.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re : [HW_RNG] How to use generic rng in kernel space

Michael Buesch wrote:
> The dataflow is as follows:

> HW-RNG -> userspace RNGD (through /dev/hwrng) -> the daemon
> checks it for sanity and puts it back into the kernel through
> /dev/random -> Your driver gets the data from the /dev/random
> entropy pools.

Is that also true for embedded systems ? I mean we may not found
any rngd on these systems.

One other question now: suppose that others drivers need to use
random data during their inits. At this time userspace appli still not
have been started. How does it work ?

> This is very neccesary, because your HW-RNG may fail and
> so you may unintentionally use non-random data, if you use
> the random data from the RNG directly.
> The data _must_ go through userspace rngd, which does FIPS
> sanity checks on the data.

Well I'm working on a secure SOC which have a randown hardware
which is supposed to return true random data. I understand that 
some self tests on the random data are needed but doing them in 
userspace is suprising.

thanks

Francis

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/