From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dropbear: add help text about key creation
Date: Tue, 12 Jan 2016 23:35:20 +0100 [thread overview]
Message-ID: <8737u277fb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1452302153-9304-1-git-send-email-arnout@mind.be> (Arnout Vandecappelle's message of "Sat, 9 Jan 2016 02:15:53 +0100")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
> Commit e7d04dd2d replaced /etc/dropbear with a symlink to /var/run and
> updated the start scripts to replace it with a real directory, so the
> keys would be persistent. However, it turns out that this is pretty
> confusing even for expert users, who don't know how to make the keys
> really persistent now.
> Update the help text explaining what the issue is, and telling the user
> to replace the /etc/dropbear symlink with a symlink to a persistent
> directory. Also mention the possiblity of unionfs.
> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2016-01-12 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 1:15 [Buildroot] [PATCH] dropbear: add help text about key creation Arnout Vandecappelle
2016-01-12 22:35 ` Peter Korsgaard [this message]
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=8737u277fb.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