Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Creation of /etc/dropbear
Date: Thu, 06 Nov 2014 13:16:19 -0300	[thread overview]
Message-ID: <545B9ED3.7000802@zacarias.com.ar> (raw)
In-Reply-To: <CAAXf6LXOFHMjbFpEe5QF1v9KhfXtnzZUsPRs+Dy1kxy7mhcfWA@mail.gmail.com>

On 11/06/2014 12:29 PM, Thomas De Schampheleire wrote:

> In my case, the rootfs is also not persistent, but mounted read-write.
> In this case, I have an init script that restores the keys from
> persistent storage into /etc/dropbear and an exit script that saves
> the keys to persistent storage. All this after checking that the keys
> are valid using dropbearkey.
> 
> If you could mount your roofs as read-write, then the same approach
> could be taken, or alternatively the symlink could be created from an
> init script.
> 
> Of course, when mounting the rootfs truly read-only, neither approach works.

Overlayfs /etc, it won't matter if root is RO in that case.
(alternatively aufs or other implementation as well).
Also you could bind-mount /etc/dropbear if it's a directory (which it is
given what the package does) from some other rw directory of your choosing.
Regards.

  reply	other threads:[~2014-11-06 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 15:19 [Buildroot] Creation of /etc/dropbear Luca Ceresoli
2014-11-06 15:29 ` Thomas De Schampheleire
2014-11-06 16:16   ` Gustavo Zacarias [this message]
2014-11-07 13:31     ` Luca Ceresoli

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=545B9ED3.7000802@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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