[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9oOPyw_GFGQykt+quxeHV3jNMUx1P+Us1NhNrMPvKUrNg@mail.gmail.com>
Date: Thu, 8 Jun 2017 14:03:28 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Marcel Holtmann <marcel@...tmann.org>
Cc: "Theodore Ts'o" <tytso@....edu>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
kernel-hardening@...ts.openwall.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Biggers <ebiggers3@...il.com>,
"Gustavo F. Padovan" <gustavo@...ovan.org>,
Johan Hedberg <johan.hedberg@...il.com>
Subject: Re: [PATCH v4 12/13] bluetooth/smp: ensure RNG is properly seeded
before ECDH use
On Thu, Jun 8, 2017 at 7:04 AM, Marcel Holtmann <marcel@...tmann.org> wrote:
>> Do we need to do all of this? Bluetooth folks, is it fair to assume
>> that hci_power_on() has to be called before any bluetooth functions
>> can be done? If so, adding a wait_for_random_bytes() in
>> hci_power_on() might be all that is necessary.
Maybe, but that could hassle bluetooth users who don't want to use any
of the fancy bluetooth crypto and don't want to bother waiting for
their RNG to initialize.
Powered by blists - more mailing lists