From: Jason Cooper <jason@lakedaemon.net>
To: Amit Shah <amit.shah@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Virtualization List <virtualization@lists.linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
herbert@gondor.apana.org.au, keescook@chromium.org,
stable@vger.kernel.org
Subject: Re: [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init"
Date: Fri, 11 Jul 2014 11:44:07 -0400 [thread overview]
Message-ID: <20140711154407.GD13108@titan.lakedaemon.net> (raw)
In-Reply-To: <20140711132626.GB17415@grmbl.mre>
On Fri, Jul 11, 2014 at 06:56:26PM +0530, Amit Shah wrote:
> On (Wed) 09 Jul 2014 [12:07:25], Jason Cooper wrote:
> > Amit, Kees,
>
> (snip)
>
> > I'm cooling to the idea of the init function for virtio-rng, and it
> > might be best just to admit that there's no way to seed the entropy pool
> > from the virtio-rng at probe time. After all, once userspace is up, the
> > system should take advantage of /dev/hwrng for the generation of
> > long-term keys. Either via rngd feeding /dev/random, or directly.
> >
> > As for the follow-on patch you asked about, I think that's fine. More
> > entropy can't hurt.
> >
> > The below patch might be worth considering so that the user of a system
> > with only virtio-rng can kick the entropy pool as they see fit. It's
> > probably not too kosher as is, but if the idea is liked, I could clean
> > it up and submit.
> >
> > The advantage is that users don't need to have rngd installed and
> > running on the system in order to jump-start the entropy pool.
>
> ... so a udev rule that looks for the new sysfs file, and asks the
> kernel to do its thing?
Or, as simple as:
[ -e /sys/.../rng_seed_kernel ] && echo "0" >/sys/.../rng_seed_kernel
in the initrd. It needs to run *before* any init scripts which may create
keys.
> And maybe even a patch to rngd that looks for this file and does a
> similar thing?
I'm not opposed to that, but it doesn't fit the problem I'm trying to
solve. Basically, average systems, not trying to be Ft Knox-secure, but
needing to generate long-term keys at first boot. These systems won't
have an hwrng installed, but should use one if available. eg
virtio-rng, or any of the on-die SoC hwrngs.
> There's also the option to use a delayed workqueue item, that will
> succeed if probe has finished. This method doesn't have userspace
> dependencies.
Hmm, I like that idea better. No ABI change to maintain, no userspace
changes... You obviously know virtio-rng better than I do, care to take
a crack at it?
thx,
Jason.
next prev parent reply other threads:[~2014-07-11 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1404538109.git.amit.shah@redhat.com>
2014-07-05 5:34 ` [PATCH v2 1/2] hwrng: fetch randomness only after device init Amit Shah
2014-07-07 4:41 ` Kees Cook
2014-07-07 5:53 ` Amit Shah
2014-07-07 6:04 ` Amit Shah
2014-07-07 6:39 ` Amit Shah
2014-07-09 11:53 ` Jason Cooper
2014-07-09 13:08 ` Amit Shah
2014-07-09 13:17 ` Jason Cooper
2014-07-09 13:25 ` Amit Shah
2014-07-09 16:07 ` [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init" Jason Cooper
2014-07-11 13:26 ` Amit Shah
2014-07-11 15:44 ` Jason Cooper [this message]
2014-07-14 21:50 ` Kees Cook
2014-07-05 5:34 ` [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe Amit Shah
2014-07-07 4:38 ` Kees Cook
2014-07-07 5:51 ` Amit Shah
2014-07-07 6:09 ` Kees Cook
2014-07-07 6:34 ` Amit Shah
2014-07-09 12:08 ` Jason Cooper
2014-07-09 13:15 ` Amit Shah
2014-07-09 16:18 ` Jason Cooper
2014-07-10 8:45 ` Herbert Xu
2014-07-10 9:53 ` Amit Shah
2014-07-10 8:52 ` Amit Shah
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=20140711154407.GD13108@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=amit.shah@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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