Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH alternative 2] dropbear: add support for custom arguments through config file
Date: Thu, 2 Jan 2014 15:07:26 +0100	[thread overview]
Message-ID: <20140102150726.3bc9af1f@skate> (raw)
In-Reply-To: <989a4f7aa922a740098b.1388666082@argentina>

Dear Thomas De Schampheleire,

On Thu, 02 Jan 2014 13:34:42 +0100, Thomas De Schampheleire wrote:
> The default port 22 used by dropbear for its SSH connections is not always
> desired. Dropbear accepts an option '-p' to set the port, but doing this was
> not possible from the buildroot-provided init script.
> 
> One way to fix this is by adding a custom S50dropbear in a project-specific
> rootfs overlay. However, this approach has the big disadvantage that bug
> fixes or improvements in the default init script (i.e. in newer buildroot
> releases) are not available (unless you manually port these changes each
> time you upgrade buildroot).
> 
> Another solution is to modify the default init script from a
> project-specific post-build script. However, this is fragile because you'd
> have to sed some line but this line may change in later buildroot releases.
> 
> Yet another solution is to change the default port at build time, by
> patching the options.h header file in the dropbear sources. This was
> proposed with a patch [1] before, but not accepted.
> 
> This patch implements another solution, hinted from the discussion in [1]:
> the default init script now sources a config file /etc/default/dropbear, in
> which the user can set the variable DROPBEAR_ARGS. This is similar to the
> S81named init script in the bind package. The config file would be added to
> a project-specific rootfs overlay, a custom skeleton, or created from a
> post-build script.
> This approach has the advantage of being simple and non-intrusive, without
> any code duplication or fragile script modifications.
> 
> [1] http://lists.busybox.net/pipermail/buildroot/2013-November/083165.html
> 
> 
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
> 
> ---
>  package/dropbear/S50dropbear |  10 ++++++++--
>  1 files changed, 8 insertions(+), 2 deletions(-)

Applied, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-01-02 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 12:34 [Buildroot] [PATCH alternative 2] dropbear: add support for custom arguments through config file Thomas De Schampheleire
2014-01-02 13:27 ` Yann E. MORIN
2014-01-02 14:07 ` Thomas Petazzoni [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=20140102150726.3bc9af1f@skate \
    --to=thomas.petazzoni@free-electrons.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