Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1463415

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

From Stephan Mueller <smueller@chronox.de>
Newsgroups linux.kernel
Subject Re: [PATCH v6 0/5] /dev/random - a new approach
Date 2016-08-16 07:50 +0200
Message-ID <s6Fqa-7v0-7@gated-at.bofh.it> (permalink)
References <s4Xhw-3LZ-17@gated-at.bofh.it> <s6wZA-1Wr-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Am Montag, 15. August 2016, 13:42:54 CEST schrieb H. Peter Anvin:

Hi H,

> On 08/11/16 05:24, Stephan Mueller wrote:
> > * prevent fast noise sources from dominating slow noise sources
> > 
> >   in case of /dev/random
> 
> Can someone please explain if and why this is actually desirable, and if
> this assessment has been passed to someone who has actual experience
> with cryptography at the professional level?

There are two motivations for that:

- the current /dev/random is compliant to NTG.1 from AIS 20/31 which requires 
(in brief words) that entropy comes from auditible noise sources. Currently in 
my LRNG only RDRAND is a fast noise source which is not auditible (and it is 
designed to cause a VM exit making it even harder to assess it). To make the 
LRNG to comply with NTG.1, RDRAND can provide entropy but must not become the 
sole entropy provider which is the case now with that change.

- the current /dev/random implementation follows the same concept with the 
exception of 3.15 and 3.16 where RDRAND was not rate-limited. In later 
versions, this was changed.

Ciao
Stephan

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v6 0/5] /dev/random - a new approach Stephan Mueller <smueller@chronox.de> - 2016-08-11 14:30 +0200
  Re: [PATCH v6 0/5] /dev/random - a new approach Theodore Ts'o <tytso@mit.edu> - 2016-08-11 23:40 +0200
    Re: [PATCH v6 0/5] /dev/random - a new approach Stephan Mueller <smueller@chronox.de> - 2016-08-12 11:40 +0200
      Re: [PATCH v6 0/5] /dev/random - a new approach Theodore Ts'o <tytso@mit.edu> - 2016-08-12 21:30 +0200
        Re: [PATCH v6 0/5] /dev/random - a new approach Stephan Mueller <smueller@chronox.de> - 2016-08-15 08:20 +0200
          Re: [PATCH v6 0/5] /dev/random - a new approach Theodore Ts'o <tytso@mit.edu> - 2016-08-15 17:10 +0200
    Re: [PATCH v6 0/5] /dev/random - a new approach Pavel Machek <pavel@ucw.cz> - 2016-08-17 23:50 +0200
      Re: [PATCH v6 0/5] /dev/random - a new approach Theodore Ts'o <tytso@mit.edu> - 2016-08-19 03:20 +0200
        Re: [PATCH v6 0/5] /dev/random - a new approach Pavel Machek <pavel@ucw.cz> - 2016-08-19 03:30 +0200
          Re: [PATCH v6 0/5] /dev/random - a new approach Theodore Ts'o <tytso@mit.edu> - 2016-08-19 05:20 +0200
            Re: [PATCH v6 0/5] /dev/random - a new approach Herbert Xu <herbert@gondor.apana.org.au> - 2016-08-19 08:00 +0200
              Re: [PATCH v6 0/5] /dev/random - a new approach "H. Peter Anvin" <hpa@linux.intel.com> - 2016-08-19 19:30 +0200
                Re: [PATCH v6 0/5] /dev/random - a new approach Herbert Xu <herbert@gondor.apana.org.au> - 2016-08-21 05:20 +0200
            Re: [PATCH v6 0/5] /dev/random - a new approach Pavel Machek <pavel@ucw.cz> - 2016-08-19 09:50 +0200
  Re: [PATCH v6 0/5] /dev/random - a new approach "H. Peter Anvin" <hpa@linux.intel.com> - 2016-08-15 22:50 +0200
    Re: [PATCH v6 0/5] /dev/random - a new approach Stephan Mueller <smueller@chronox.de> - 2016-08-16 07:50 +0200
      Re: [PATCH v6 0/5] /dev/random - a new approach "H. Peter Anvin" <hpa@linux.intel.com> - 2016-08-17 00:30 +0200
        Re: [PATCH v6 0/5] /dev/random - a new approach "H. Peter Anvin" <hpa@linux.intel.com> - 2016-08-17 00:50 +0200
        Re: [PATCH v6 0/5] /dev/random - a new approach Stephan Mueller <smueller@chronox.de> - 2016-08-17 07:30 +0200

csiph-web