From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Seeding the Linux RNG at first boot
Date: Thu, 7 Dec 2017 18:47:49 -0500 [thread overview]
Message-ID: <20171207234749.GA22844@jasmine.lan> (raw)
In-Reply-To: <87indickmd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Thu, Dec 07, 2017 at 10:07:38PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> > On the guest side, we would extend urandom-seed-service to also draw on
> > /dev/hwrng, which is where virtio-rng-pci makes the data from the host
> > available.
>
> Maybe ‘virtualized-operating-system’ in (gnu system vm) could
> automatically customize ‘rngd-service-type’ (or add it)?
Yes, we could do that, although I don't think it's necessary to run a
daemon continuously. It is enough to seed the RNG once.
At the same time we handle the random seed, we could also try reading
from /dev/hwrng and, if the read is successful, copy some bytes into
/dev/urandom. We'd have to try reading and handle failure since we
always create /dev/hwrng regardless of whether the Linux kernel module
is loaded or not.
> > I have an idea for another improvement: to add an argument like
> > "--entropy-seed=" to `guix system` that could place the value in
> > '/var/lib/random-seed', where it would be used on first boot.
>
> We could do that, though I very much prefer the idea of a “backdoor” à
> la virtio-rng-pci, because it allows to stick to bit-reproducible images
> (well, they’re not bit-reproducible yet I suppose, but let’s not add to
> it.)
I think it would be most useful for disk images, for which there is no
host.
If one always passes the same value to --entropy-seed, it will not
negatively affect the reproducibility of the image ;)
This would not be something we do for the official release image, but
merely an optional tool.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-07 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171203003126.GA353@jasmine.lan>
[not found] ` <f238b944-2f7d-5063-2996-d234647a97a9@tobias.gr>
[not found] ` <20171204184558.GF30970@jasmine.lan>
[not found] ` <87wp20ydlj.fsf@fastmail.com>
2017-12-06 18:27 ` Seeding the Linux RNG at first boot Leo Famulari
2017-12-07 21:07 ` Ludovic Courtès
2017-12-07 23:47 ` Leo Famulari [this message]
2017-12-11 9:16 ` Ludovic Courtès
2017-12-11 16:08 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171207234749.GA22844@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).