Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
Reply-To: noloader@gmail.com
In-Reply-To: <20180718014344.1309-1-tytso@mit.edu>
References: <20180718014344.1309-1-tytso@mit.edu>
From:   Jeffrey Walton <noloader@gmail.com>
Date:   Wed, 18 Jul 2018 02:46:55 -0400
Message-ID: <CAH8yC8mG8PCd6zLK=oMWdvcAryvY42g1TprUrNg7ZGVyBenKjw@mail.gmail.com>
Subject: Re: [PATCH] random: add a config option to trust the CPU's hwrng
To:     "Theodore Ts'o" <tytso@mit.edu>
Cc:     Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
        Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
        Laura Abbott <labbott@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Jul 17, 2018 at 9:43 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> This gives the user building their own kernel (or a Linux
> distribution) the option of deciding whether or not to trust the CPU's
> hardware random number generator (e.g., RDRAND for x86 CPU's) as being
> correctly implemented and not having a back door introduced (perhaps
> courtesy of a Nation State's law enforcement or intelligence
> agencies).

+1.

Allowing the user to set local policy is a good idea. Thanks for that.