From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5138] New: Add dropbear config option to allow blank passwords
Date: Fri, 27 Apr 2012 16:35:06 +0200 [thread overview]
Message-ID: <20120427163506.4e0a7ba2@skate> (raw)
In-Reply-To: <jn9jsk$fob$1@dough.gmane.org>
Le Wed, 25 Apr 2012 19:39:02 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :
> > this is a security issue
>
> Only if you set it (it defaults to "n") and the device in question is
> on an accessible network.
>
> > I prefer to add an option to add a default ssh public key
>
> That doesn't do the same thing.
>
> > I've a patch somewhere
>
> I've no objection to having an option for a default key, but I don't
> think it's buildroot's place to try to decide and enforce security
> policies. Those decisions belong to the person specifying and
> designing the embedded system.
>
> [Not allowing blank passwords in dropbear seems especially silly when
> blank passwords are allowed by telnetd, login and openssh.]
Agreed. I think both the "Allow blank passwords" option and the "Add
default ssh public key" options make sense, and they both should be
added.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-04-27 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 13:38 [Buildroot] [Bug 5138] New: Add dropbear config option to allow blank passwords bugzilla at busybox.net
2012-04-25 14:18 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-25 19:39 ` Grant Edwards
2012-04-27 14:35 ` Thomas Petazzoni [this message]
2013-05-26 8:46 ` [Buildroot] [Bug 5138] " bugzilla at busybox.net
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=20120427163506.4e0a7ba2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.