All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Lange <nolange79@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/haveged: Change service file to run early
Date: Tue, 30 Jun 2020 09:54:39 +0200	[thread overview]
Message-ID: <CADYdroOxd6_bLu8BNE2=KN_KYBawLk2-ZeXgCmvCwAyxMXs79A@mail.gmail.com> (raw)
In-Reply-To: <CADYdroO=qn7v5_VdQup-0Fja++NY0Qa1b040oP_kH5XhrkyMkA@mail.gmail.com>

> >
> > > > > I am not up to speed with FIPS tests, but from a really really long way back
> > > > > it wasn't a big issue to pass most tests with the Mersenne Twister and a few
> > > > > bits of true entropy.
> > > > >
> > > > > Basically it feeds PRNG back to kernel and lets it account as entropy source.
> > > >
> > > > I could not find any backup for that claim.  If I understood
> > > > correctly, haveged does not read from the kernel PRNG.
> > >
> > > The kernel has an entropy pool, it taps alot sources (inkl jitter, see
> > > https://lwn.net/Articles/642166/).
> >
> > Yes, but according to Stephan M?ller, the author of the
> > jitterentropy-rng, the kernel uses the CPU timing jitter internally
> > only in the crypto subsystem, that's not fed to the pool /dev/random
> > uses [1].  There's a patch series for a redesigned random number
> > subsystem by him, which would make that possible, but that never got
> > merged.

Forgot adding the kernel uses "timings of events such as hardware
interrupts as inputs",
that's basically the same entropy source that causes your "jitters".
"CPU effects" like cache evictions, pipeline flushes are just an
effect of that and could
be deterministically recreated if the IRQs happen in the same fashion again.

Norbert

  reply	other threads:[~2020-06-30  7:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 22:41 [Buildroot] (no subject) Norbert Lange
2020-06-09 22:41 ` [Buildroot] [PATCH v2 1/2] package/haveged: Change service file to run early Norbert Lange
2020-06-25 22:39   ` Norbert Lange
2020-06-29  7:31     ` Jérémy ROSEN
2020-06-29  8:29       ` Norbert Lange
2020-06-29  9:30         ` Alexander Dahl
2020-06-29  9:55           ` Norbert Lange
2020-06-29 12:41             ` Alexander Dahl
2020-06-29 15:17               ` Norbert Lange
2020-06-29 21:37                 ` Alexander Dahl
2020-06-30  7:46                   ` Norbert Lange
2020-06-30  7:54                     ` Norbert Lange [this message]
2020-06-30  8:14                     ` Alexander Dahl
2020-06-29 12:03         ` Jérémy ROSEN
2020-06-29 15:08           ` Norbert Lange
2020-09-13 13:27   ` Thomas Petazzoni
2020-09-14  7:00     ` Jérémy ROSEN
2020-06-09 22:41 ` [Buildroot] [PATCH v2 2/2] package/haveged: bump to version 1.9.9 Norbert Lange
2020-06-10 20:57   ` Thomas Petazzoni

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='CADYdroOxd6_bLu8BNE2=KN_KYBawLk2-ZeXgCmvCwAyxMXs79A@mail.gmail.com' \
    --to=nolange79@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.