From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] dropbear: add extra build customization options
Date: Tue, 3 Feb 2015 15:04:37 +0100 [thread overview]
Message-ID: <20150203150437.7d27225c@free-electrons.com> (raw)
In-Reply-To: <1410450212-30718-1-git-send-email-bos@je-eigen-domein.nl>
Dear Floris Bos,
On Thu, 11 Sep 2014 17:43:31 +0200, Floris Bos wrote:
> - Option to disable password authentication,
> to only allow public key authentication instead
This can be done at runtime using the -s option, and presumably
disabling it at build time doesn't give much space savings, so we'd
rather not have a Config.in option for this.
> - Option to disable TCP forwarding.
> Defaults to y, as most legitimate users are not using it,
> and the feature is very popular with spammers that scan
> for devices with weak passwords and use them to relay spam.
This can be done at runtime using the -j and -k options, so same logic
as for the password authentication disabling.
We'd however be open to merge the option to install or not the clients,
but we do have some comments/questions below.
> +ifeq ($(BR2_PACKAGE_DROPBEAR_CLIENT),y)
> DROPBEAR_TARGET_BINS = dbclient dropbearkey dropbearconvert scp ssh
> DROPBEAR_MAKE = $(MAKE) MULTI=1 SCPPROGRESS=1 \
> PROGRAMS="dropbear dbclient dropbearkey dropbearconvert scp"
> -
> -DROPBEAR_LICENSE = MIT, BSD-2c-like, BSD-2c
> -DROPBEAR_LICENSE_FILES = LICENSE
> +else
> +DROPBEAR_TARGET_BINS = dropbearkey dropbearconvert scp
> +DROPBEAR_MAKE = $(MAKE) MULTI=1 SCPPROGRESS=1 \
> + PROGRAMS="dropbear dropbearkey dropbearconvert scp"
> +endif
Why is scp part of the server-only installation?
Also, can you make this a bit smarter to avoid duplication. For example:
DROPBEAR_TARGET_BINS = dropbearkey dropbearconvert scp
ifeq ($(BR2_PACKAGE_DROPBEAR_CLIENT),y)
DROPBEAR_TARGET_BINS += ssh dbclient
endif
And then use:
PROGRAMS="dropbear $(DROPBEAR_TARGET_BINS)"
When doing the $(MAKE) call.
We'll mark your patch as 'Changes Requested' in patchwork, so can you
resend an updated version that takes into account those comments?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-02-03 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:43 [Buildroot] [PATCH 1/1] dropbear: add extra build customization options Floris Bos
2014-09-11 15:43 ` [Buildroot] [PATCH 1/1] sqlite: add option to disable fsync Floris Bos
2014-09-11 21:53 ` Thomas Petazzoni
2014-09-13 21:51 ` Peter Korsgaard
2015-02-03 14:04 ` Thomas Petazzoni [this message]
2015-02-03 17:53 ` [Buildroot] [PATCH 1/1] dropbear: add extra build customization options Floris Bos
2015-02-03 19:30 ` Thomas Petazzoni
2015-02-04 15:35 ` Floris Bos
2015-02-04 15:40 ` 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=20150203150437.7d27225c@free-electrons.com \
--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