Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] openssh: replace individual ssh-keygen calls with a single call
Date: Tue, 5 Aug 2014 22:22:51 +0300	[thread overview]
Message-ID: <20140805192251.GL2322@tarshish> (raw)
In-Reply-To: <CANxTyt65uANp54R7hjpQg07Kf==RNQsJQQ6vX+3NGRTFeJZ9Nw@mail.gmail.com>

Hi Danomi,

On Mon, Aug 04, 2014 at 10:28:08AM -0400, Danomi Manchego wrote:
> On Mon, Aug 4, 2014 at 4:24 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > On Sun, 3 Aug 2014 09:25:13 -0400, Danomi Manchego wrote:
> >> I think this issue is not limited to openssh - there's other things
> >> that want to occasionally save stuff to /etc, /var, even /root (e.g.
> >> gstreamer plugins cache).  I suppose that efforts could be made to try
> >> to patch/configure these locations to all be in one place (/var ?),
> >> but that still assumes a writable directory.  So, unless we direct all
> >> attempts to save state to a tmpfs, I think it always come back to
> >> being the user's responsibility.
> >>
> >> So for now I'm content to keep openssh as it is, rather than hunt down
> >> all the places that might try to write to etc (, var, $HOME, ...).
> >
> > Buildroot is normally supposed to support a read-only root filesystem,
> > and there are already several things being done to make this possible:
> >
> >  * /etc/resolv.conf is a symbolic link to /tmp/resolv.conf
> >  * Most of the /var/<foo> directories are symbolic links to /tmp.
> >    Only /var/lib is not.
> >  * /tmp is mounted as tmpfs, so that it's read/write even if the rootfs
> >    is read only.
> 
> So - should the openssh.mk be making symlinks of all the key files to
> /tmp/$FILE?  That re-introduces the maintenance burden, but I'll make
> a patch along those lines if there's interest.

I don't think so. SSH keys should be stored in a writeable AND persistent over 
reboot location. Storing them under /tmp (ephemeral tmpfs by default) would 
make the keys regenerate on every boot, which would defeat the whole purpose 
of having host keys in the first place.

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 -

  reply	other threads:[~2014-08-05 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03  1:21 [Buildroot] [PATCH 1/1] openssh: replace individual ssh-keygen calls with a single call Danomi Manchego
2014-08-03  7:37 ` Yann E. MORIN
2014-08-03 13:25   ` Danomi Manchego
2014-08-04  8:24     ` Thomas Petazzoni
2014-08-04  9:17       ` Waldemar Brodkorb
2014-08-08 20:03         ` Peter Korsgaard
2014-08-09 15:23           ` Thomas Petazzoni
2014-08-04 14:28       ` Danomi Manchego
2014-08-05 19:22         ` Baruch Siach [this message]
2014-08-03  8:36 ` Thomas Petazzoni

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=20140805192251.GL2322@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