From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/cpio: drop static random-seed
Date: Tue, 7 Jul 2015 14:28:09 +0300 [thread overview]
Message-ID: <20150707112809.GR3139@tarshish> (raw)
In-Reply-To: <87fv50nrz6.fsf@dell.be.48ers.dk>
Hi Peter,
On Tue, Jul 07, 2015 at 01:10:21PM +0200, Peter Korsgaard wrote:
> >>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>
> > Initializing the kernel entropy pool in initramfs from a seed file that never
> > changes doesn't make much sense. Not initializing the entropy pool at all is
> > better than initializing it from a known seed.
>
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>
> I agree, but why don't we simply drop our static /etc/random-seed from
> the default skeleton instead?
Good idea. /etc/random-seed is less harmful on persistent filesystems, as it
only affects the first boot. But it probably doesn't do any good either.
In addition to that I think it would also be better not to use
/etc/random-seed when the filesystem is read-only, even when that file exists.
Currently /etc/init.d/S20urandom reads /etc/random-seed from a read-only
filesystem, but doesn't write it, which seems just wrong.
What do you thing?
I'll send patches if everybody agree on the plan.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-07-07 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 10:01 [Buildroot] [PATCH] fs/cpio: drop static random-seed Baruch Siach
2015-07-07 11:10 ` Peter Korsgaard
2015-07-07 11:28 ` Baruch Siach [this message]
2015-07-07 12:38 ` Peter Korsgaard
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=20150707112809.GR3139@tarshish \
--to=baruch@tkos.co.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox