linux-kernel - Re: [PATCH 1/2] random: Add support for architectural random hooks

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] [day] [month] [year] [list]

Message-ID: <CA+55aFzUeRd0fx79eepx98HLk3-EMWPyu2V-9VM1qtT60q-bVQ@mail.gmail.com>
Date:	Sat, 30 Jul 2011 18:33:38 -1000
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bryan Donlan <bdonlan@...il.com>
Cc:	George Spelvin <linux@...izon.com>, linux-kernel@...r.kernel.org,
	mpm@...enic.com, tytso@....edu
Subject: Re: [PATCH 1/2] random: Add support for architectural random hooks

On Sat, Jul 30, 2011 at 4:02 PM, Bryan Donlan <bdonlan@...il.com> wrote:
>
> In any case though, what about my suggestion - don't mess with urandom
> at all, and let udev replace the /dev/urandom device node with one
> directed to a fast hwrng device if one is detected?

Umm, user space is encouraged to do exactly that.

However, at no point does that mean "the kernel shouldn't do the best
it can". So it's a totally independent issue.

The kernel will want to use rdrand regardless of what user space does.
Both for legacy applications that don't know about rdrand, and for
scripts that don't want to bother. And for just its own use.

             Linus
--
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/