Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] move random-seed from /etc to /var/lib
Date: Fri, 13 Mar 2015 00:12:34 +0100	[thread overview]
Message-ID: <871tkthkt9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <55021C99.9070907@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 12 Mar 2015 20:09:13 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 > On 03/12/2015 08:01 PM, Peter Korsgaard wrote:
 >> But if rootfs is RO, so will /var/lib then?
 >> 
 >> I would rather get rid of the static random_seed file instead. Seeding
 >> all Buildroot based devices with a RO rootfs from the same 512 bytes of
 >> data can hardly be helpful for security.
 >> 
 >> For a R/W rootfs, why would /var/lib be any better than /etc?

 > I'm still planning to revap the random initscript and throw some infra
 > there.
 > Who says we can't use /etc/default + /etc/config for this? We can tell
 > where to write randomness if it's available that way.
 > On the project side we can choose if we'll use a per-project (build
 > time) random seed or nothing at all, after all we can't know every
 > scenario out there.

Ok, but simply doing a git rm system/skeleton/etc/random-seed would be a
good start (and shouldn't cause issues for any of those features).

-- 
Bye, Peter Korsgaard 

  reply	other threads:[~2015-03-12 23:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  0:20 [Buildroot] [PATCH] move random-seed from /etc to /var/lib Alex Suykov
2015-03-12 23:01 ` Peter Korsgaard
2015-03-12 23:09   ` Gustavo Zacarias
2015-03-12 23:12     ` Peter Korsgaard [this message]
2015-03-13  0:20   ` Alex Suykov
2015-03-13  6:20     ` 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=871tkthkt9.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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