unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: /dev/urandom
Date: Tue, 10 Jul 2018 14:43:23 -0400	[thread overview]
Message-ID: <87601nylro.fsf@netris.org> (raw)
In-Reply-To: <20180710182211.75442f8b@scratchpost.org> (Danny Milosavljevic's message of "Tue, 10 Jul 2018 18:22:11 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> writes:

> u-boot tools/sunxi-spl-image-builder.c reads from /dev/urandom .
>
> For reproducibility I'd like this to be a static file.  Do we already have one
> for this purpose?

I think it would be better to patch software as needed to avoid trying
to generate random numbers in specific places, mainly because it would
force us to always be aware of what the random numbers are being used
for, so that we can evaluate the potential security implications.

If we simply make /dev/urandom deterministic, then we will not be in the
position to know what the (non)random numbers are being used for, and we
run the risk of introducing serious security issues.

Note that it would not be sufficient to audit the software once to see
what the random numbers were being used for, because future versions of
the software might add additional uses for random numbers.  If that ever
happens, then the difference between the two approaches will become
important.

If we make /dev/urandom deterministic, then new uses for random numbers
introduced in future versions will be *automatically* made non-random,
and we might not notice.  On the other hand, if we patch out specific
uses of randomness, then new uses for randomness will be left intact
until we add patches for them.  This is as it should be, I think.

What do you think?

      Mark

  parent reply	other threads:[~2018-07-10 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 16:22 /dev/urandom Danny Milosavljevic
2018-07-10 18:28 ` /dev/urandom Leo Famulari
2018-07-10 18:58   ` /dev/urandom Danny Milosavljevic
2018-07-10 22:40     ` /dev/urandom Leo Famulari
2018-07-10 18:43 ` Mark H Weaver [this message]
2018-07-11 14:17   ` /dev/urandom Danny Milosavljevic
2018-07-11 15:07     ` /dev/urandom Vincent Legoll
2018-07-11 15:50       ` /dev/urandom Danny Milosavljevic
2018-07-11 16:34         ` /dev/urandom Vincent Legoll
2018-07-10 22:18 ` /dev/urandom Ludovic Courtès

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=87601nylro.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@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).