Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] openssh: add option to allow login as root
Date: Wed, 20 Mar 2019 09:58:11 +0100	[thread overview]
Message-ID: <87imwdexcs.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <f11c03b3-7edd-5c55-7287-61684f2c9a64@mind.be> (Arnout Vandecappelle's message of "Wed, 20 Mar 2019 01:23:42 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >> We discussed it tonight on IRC and didn't really get to a good compromise.
 >> 
 >> On one hand, we prefer to stick with upstream defaults (especially when
 >> security is involved)

 >  This patch doesn't change the defaults.

No, but the discussion on IRC included talking about if there should be
an option or if we should unconditionally allow/disallow root logins.

 >> We prefer to not add configuration options for these kind of
 >> detailed policy decisions,

 >  *That* is the crux of the matter. We normally only have configurability of
 > compile-time options, and assume that anything else is handled in post-build
 > scripts. The (only?) exception to that principle is the system menu.

 >  So *maybe* something global in the system menu could work, and then dropbear
 > and openssh and whatnot would do whatever is needed to permit/disallow root
 > login for that particular package. But I'm not exactly ecstatic about that option.

Me neither.


 >> as openssh has a LOT of other configuration
 >> options

 >  True, but permitting root login is clearly one that is a lot more
 > important/relevant than all the others. Currently, the typical user will naively
 > enable openssh, then try to ssh into the device, and fail...

Correct. It will also fail for dropbear as the root user by default does
not have a password set.


 >> So all in all, this kind of policy tweaks are better done in a post
 >> build script.

 >  In the few projects where I've seen openssh used, it was always with a custom
 > config file. Otherwise, there's not much reason to use openssh instead of
 > dropbear I guess.

Indeed. I always use dropbear as well.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-03-20  8:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 11:41 [Buildroot] [RFC] openssh: add option to allow login as root Esben Haabendal
2019-03-19 15:23 ` Grant Edwards
2019-03-19 22:42 ` Peter Korsgaard
2019-03-20  0:23   ` Arnout Vandecappelle
2019-03-20  8:58     ` Peter Korsgaard [this message]
2019-03-20  9:05       ` James Hilliard
2019-03-20  9:23         ` Arnout Vandecappelle
2019-03-20  9:26         ` Yann E. MORIN
2019-03-20  9:32           ` James Hilliard
2019-03-20 16:25     ` Carlos Santos

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=87imwdexcs.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