From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 44808@debbugs.gnu.org
Subject: bug#44808: Default to allowing password authentication on leaves users vulnerable
Date: Mon, 07 Dec 2020 12:51:54 +0100 [thread overview]
Message-ID: <87sg8hzvdx.fsf@gnu.org> (raw)
In-Reply-To: <87k0twkt9c.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Sat, 05 Dec 2020 13:22:23 -0500")
Hi Chris,
Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
> Ludovic Courtès writes:
[...]
>> Agreed. There are several ways to do that:
>>
>> 1. Have the installer emit an ‘openssh-configuration’ that explicitly
>> disables password authentication.
>>
>> 2. Change the default value of the relevant field in
>> <openssh-configuration>.
>>
>> #2 is more thorough but also more risky: people could find themselves
>> locked out of their server after reconfiguration, though this could be
>> mitigated by a news entry.
>>
>> Thoughts?
>>
>> Ludo’.
>
> We could also do a combination of the above, as a transitional plan:
> do #1 for now, but try to advertise that in the future, the default will
> be changing... please explicitly set password access to #t if you need
> this! Then in the *following* release, change the default.
>
> This seems like a reasonable transition plan, kind of akin to a
> deprecation process?
Sounds like a plan. I went ahead and pushed
aecd2a13cbd8301d0fdeafcacbf69e12cc3f6138 which does this.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-12-07 11:54 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
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 [this message]
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=87sg8hzvdx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44808@debbugs.gnu.org \
--cc=cwebber@dustycloud.org \
--cc=maxim.cournoyer@gmail.com \
/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).