From: Willy Tarreau <w@1wt.eu>
To: "Theodore Ts'o" <tytso@mit.edu>, Ingo Molnar <mingo@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86-ml <x86@kernel.org>, "Jason A. Donenfeld" <Jason@zx2c4.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: early x86 unseeded randomness
Date: Tue, 15 Aug 2017 15:26:24 +0200 [thread overview]
Message-ID: <20170815132624.GA2688@1wt.eu> (raw)
In-Reply-To: <20170815120950.etl7wbxurziazi5o@thunk.org>
On Tue, Aug 15, 2017 at 08:09:50AM -0400, Theodore Ts'o wrote:
> On Tue, Aug 15, 2017 at 10:05:46AM +0200, Ingo Molnar wrote:
> > > > * Willy Tarreau <w@1wt.eu> wrote:
> > > > >
> > > > > Nowadays we could use similar methods using RDTSC providing more accurate
> > > > > counting. This doesn't provide a lot of entropy of course, given that a
> > > > > 2 GHz machine will at most count 31 bits there. But I tend to think that
> > > > > what matters during early boot is to transform something highly predictable
> > > > > into something unlikely to be predicted (ie: an exploit having to scan 2^31
> > > > > possible addresses will not be really usable). It's also possible to do the
> > > > > same with the PIT0 counter ticking at 18.2 Hz without any correlation with
> > > > > the RTC by the way, and roughly provide 25 more bits....
>
> All of this assumes that you have different clock crystals generating
> all of these different clock sources. Otherwise there can be a lot
> less entropy than you expected.
That's what's cool with the RTC, it definitely runs on its own 32kHz
crystal since it continues to beat when everything else is powered off.
Willy
next prev parent reply other threads:[~2017-08-15 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 17:35 early x86 unseeded randomness Borislav Petkov
2017-08-14 17:47 ` Linus Torvalds
2017-08-14 18:00 ` Borislav Petkov
2017-08-14 18:17 ` Linus Torvalds
2017-08-14 19:00 ` Borislav Petkov
2017-08-15 1:31 ` Theodore Ts'o
2017-08-15 6:44 ` Willy Tarreau
2017-08-15 7:42 ` Ingo Molnar
2017-08-15 8:01 ` Willy Tarreau
2017-08-15 8:05 ` Ingo Molnar
2017-08-15 12:09 ` Theodore Ts'o
2017-08-15 13:26 ` Willy Tarreau [this message]
2017-08-15 10:47 ` Thomas Gleixner
2017-08-15 13:45 ` Borislav Petkov
2017-08-15 13:48 ` Thomas Gleixner
2017-08-15 14:25 ` Theodore Ts'o
2017-08-15 14:42 ` Thomas Gleixner
2017-08-15 15:26 ` Borislav Petkov
2017-08-15 17:37 ` Thomas Gleixner
2017-08-16 3:35 ` Theodore Ts'o
2017-08-16 9:13 ` Thomas Gleixner
2017-08-16 9:56 ` Will Deacon
2017-08-16 3:21 ` Theodore Ts'o
2017-08-15 15:24 ` Borislav Petkov
2017-08-15 12:48 ` Michael Ellerman
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=20170815132624.GA2688@1wt.eu \
--to=w@1wt.eu \
--cc=Jason@zx2c4.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=x86@kernel.org \
/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