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  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]
Date:	Thu, 17 Jul 2014 14:39:42 +0200
From:	Daniel Borkmann <>
To:	"H. Peter Anvin" <>
CC:	Andy Lutomirski <>,
	kvm list <>,
	"Theodore Ts'o" <>,
	"" <>,
	Kees Cook <>, X86 ML <>,
	Srivatsa Vaddagiri <>,
	Raghavendra K T <>,
	Gleb Natapov <>,
	Paolo Bonzini <>,
	Bandan Das <>,
Subject: Re: [PATCH v3 2/5] random,x86: Add arch_get_slow_rng_u64

On 07/17/2014 12:59 AM, H. Peter Anvin wrote:
> On 07/16/2014 03:40 PM, Andy Lutomirski wrote:
>> On Wed, Jul 16, 2014 at 3:13 PM, Andy Lutomirski <> wrote:
>>> My personal preference is to defer this until some user shows up.  I
>>> think that even this would be too complicated for KASLR, which is the
>>> only extremely early-boot user that I found.
>>> Hmm.  Does the prandom stuff want to use this?
>> prandom isn't even using rdrand.  I'd suggest fixing this separately,
>> or even just waiting until someone goes and deletes prandom.
> prandom is exactly the opposite; it is designed for when we need
> possibly low quality random numbers very quickly.  RDRAND is actually
> too slow.

Yep, prandom() is quite heavily used in the network stack where it's
traded for speed.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists