From: doncatnip <gnopap@gmail.com>
To: guix-devel@gnu.org
Subject: Fwd: Re: /dev/urandom
Date: Wed, 11 Jul 2018 17:40:40 +0200 [thread overview]
Message-ID: <ea03dab6-d241-c873-01da-a464a644ee7e@gmail.com> (raw)
In-Reply-To: <ca2801d7-c55b-4a5c-40a8-e0e251b3451e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Of course, I forgot the CC.
-------- Forwarded Message --------
Subject: Re: /dev/urandom
Date: Wed, 11 Jul 2018 09:58:14 +0100
From: Steffen Schulz <gnopap@gmail.com>
To: Leo Famulari <leo@famulari.name>
I probably got it wrong.
but it seems the programs purpose is to build images (boot loaders). I
then wonder why it needs to do this during installation. If image
building is the programs purpose, it should happen during execution
after installation, no ?
Users would *most likely* prefer it's actual purpose (proper Images,
including optimization) instead of reproducibility.
On 10.07.2018 23:40, Leo Famulari wrote:
> On Tue, Jul 10, 2018 at 08:58:43PM +0200, Danny Milosavljevic wrote:
>> It writes an image file. Since that image is later written to flash storage
>> (by the user), the program randomizes the data in order to increase longevity.
>> Then it stores the random data used as well.
> I see. Like Ludo and Mark, I think we should avoid doing tricky things
> with urandom.
>
> Could /dev/zero work here? Does it use urandom once, to get a seed, or
> does it read urandom repeatedly, expecting different values each time?
>
> Also, I wonder if Guix users would want reproducibility here instead of
> longer-lived NAND storage.
[-- Attachment #2: Type: text/html, Size: 2390 bytes --]
next parent reply other threads:[~2018-07-11 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ca2801d7-c55b-4a5c-40a8-e0e251b3451e@gmail.com>
2018-07-11 15:40 ` doncatnip [this message]
[not found] <cfbb12ea-f059-d1a1-b2d5-6c6b140c3c06@gmail.com>
2018-07-11 15:41 ` Fwd: Re: /dev/urandom doncatnip
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=ea03dab6-d241-c873-01da-a464a644ee7e@gmail.com \
--to=gnopap@gmail.com \
--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).