From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: raingloom <raingloom@riseup.net>
Cc: 44808@debbugs.gnu.org
Subject: bug#44808: Default to allowing password authentication on leaves users vulnerable
Date: Mon, 23 Nov 2020 11:15:18 -0500 [thread overview]
Message-ID: <87r1ok2go9.fsf@dustycloud.org> (raw)
In-Reply-To: <20201123044615.13cc0898@riseup.net>
raingloom writes:
> On Mon, 23 Nov 2020 03:32:08 +0100
> Taylan Kammer <taylan.kammer@gmail.com> wrote:
>
>> On 23.11.2020 00:20, Christopher Lemmer Webber wrote:
>> > Okay, I just realized I left a friend vulnerable by guiding them
>> > through a Guix graphical install and telling them it would give
>> > them a decent setup. They turned on openssh support.
>> >
>> > Then I realized their config had password-authentication? on.
>> >
>> > That's unacceptable. We need to change this default. This is
>> > known to leave users open to attack, and selecting a password
>> > secure enough against brute forcing is fairly difficult, much more
>> > difficult than only allowing entry by keys. Plus, few
>> > distributions do what we're doing anymore, precisely because of
>> > wanting to be secure by default.
>> >
>> > Yes, I know some people want password authentication on as part of a
>> > bootstrapping process. Fine... those users know to put it on.
>> > Let's not leave our users open to attack by default though.
>> >
>> > Happy to produce a patch and change the documentation, but I'd like
>> > to hear that we have consensus to make this change. But we should,
>> > because otherwise else I think we're going to hurt users.
>>
>> I think most ideal would be if the user is asked the following two
>> questions, with a short explanation of what each means:
>>
>> - Allow root login via SSH?
>>
>> - Allow password authentication in SSH?
>>
>> (I think Debian does this.)
>>
>> Because as you say, on one hand password authentication in SSH can be
>> a security risk. But on the other hand many machines never have
>> their SSH port exposed to the Internet, and the intranet is assumed
>> to be safe. In those cases it would be an annoyance to have to enable
>> it manually.
>>
>> Both points apply to direct root login as well I think.
>>
>> Allowing password authentication but disabling root login might also
>> be considered safe enough on machines exposed to the Internet,
>> because the attacker needs to guess the username as well. Only
>> presents a small increase in complexity for the attacker though.
>>
>>
>> - Taylan
>>
>>
>>
>
> Most people won't know why allowing password authentication is
> unsecure. Either it should be worded differently, have a warning, or
> not be an option.
>
> Same goes doubly so for allowing root login.
Agreed on both counts.
next prev parent reply other threads:[~2020-11-23 16:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 23:20 bug#44808: Default to allowing password authentication on leaves users vulnerable Christopher Lemmer Webber
2020-11-23 2:32 ` Taylan Kammer
2020-11-23 3:46 ` raingloom
2020-11-23 16:15 ` Christopher Lemmer Webber [this message]
2020-11-23 3:57 ` Carlo Zancanaro
2020-11-23 16:17 ` Christopher Lemmer Webber
2020-11-30 3:58 ` Maxim Cournoyer
2020-12-05 15:14 ` Ludovic Courtès
2020-12-05 18:22 ` Christopher Lemmer Webber
2020-12-07 11:51 ` Ludovic Courtès
2020-12-07 12:56 ` Dr. Arne Babenhauserheide
2020-12-07 16:48 ` Christopher Lemmer Webber
2020-12-07 19:53 ` Dr. Arne Babenhauserheide
2020-12-07 22:57 ` Mark H Weaver
2020-12-08 10:36 ` Ludovic Courtès
2020-12-09 1:31 ` Mark H Weaver
2020-12-10 8:17 ` Ludovic Courtès
2020-12-11 1:43 ` Mark H Weaver
2020-12-11 18:10 ` Ludovic Courtès
2020-12-08 13:48 ` Christopher Lemmer Webber
2020-12-07 19:40 ` Leo Famulari
2020-12-07 21:38 ` Christopher Lemmer Webber
2021-02-11 7:46 ` raid5atemyhomework via Bug reports for GNU Guix
2021-02-11 20:36 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1ok2go9.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=44808@debbugs.gnu.org \
--cc=raingloom@riseup.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).