From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] move random-seed from /etc to /var/lib
Date: Fri, 13 Mar 2015 02:20:17 +0200 [thread overview]
Message-ID: <20150313002017.GA11581@vostro> (raw)
In-Reply-To: <8761a5hlbr.fsf@dell.be.48ers.dk>
Fri, Mar 13, 2015 at 12:01:28AM +0100, Peter Korsgaard wrote:
> >>>>> "Alex" == Alex Suykov <alex.suykov@gmail.com> writes:
>
> > In case / is mounted read-only, /etc is likely to be read-only
> > as well, so the seed will not be saved.
>
> But if rootfs is RO, so will /var/lib then?
Common (I think?) setup is to have ro / and rw /var on some
kind of persistent storage. This way /etc typically remains
a part of read-only root.
Buildroot does not support such layout at present but with /etc/mtab
and /etc/resolv.conf already out of /etc, it's one step away.
> 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.
Agreed. Currently the initial file is only used to check for rw filesystem.
That's not necessary, and easy to fix. Sending a patch.
next prev parent reply other threads:[~2015-03-13 0:20 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
2015-03-13 0:20 ` Alex Suykov [this message]
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=20150313002017.GA11581@vostro \
--to=alex.suykov@gmail.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