From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: delayed "random: get_random_bytes" line in dmesg
Date: Sun, 26 Jan 2020 16:26:19 -0500 [thread overview]
Message-ID: <20200126212619.GA13716@mit.edu> (raw)
In-Reply-To: <a4d06aa4-30df-4333-6b94-46fa95e32129@gmx.de>
On Sun, Jan 26, 2020 at 03:41:24PM +0100, Toralf Förster wrote:
> I do wonder a little bit about the timestamp of the "random: get_random_bytes" near the end b/c it is way delayed, or?
The get_random_bytes call in setup_net is used to initialize value
returned by net_hash_mix() for the root net namespace. So if that's
not super random, an attacker might be able to use that to leverage
kernel level attacks. It's at least not being used for a
cryptographic purpose, though.
> Linux mr-fox 5.4.15 #6 SMP Sun Jan 26 10:07:17 CET 2020 x86_64 Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz GenuineIntel GNU/Linux
The E5-1650 is a (roughly) eight year old chip with the Sandy Bridge
architecture, and that was the last architecture _not_ to support
RDRAND.
- Ted
prev parent reply other threads:[~2020-01-26 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 14:41 delayed "random: get_random_bytes" line in dmesg Toralf Förster
2020-01-26 21:26 ` Theodore Y. Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200126212619.GA13716@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).