Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dropbear: disable password logins for root.
Date: Sun, 21 Mar 2021 19:32:49 +0100	[thread overview]
Message-ID: <20210321183249.nZv8X4YYVlKNsoZwdqPtYmjHQtA2ry7M96nt9l41sU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29599@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/29599#issuecomment-803638008

Comment:
@mobinmob the issue here is that we'd be changing the service behavior on an update, and it's possible someone might miss it and get locked out after a reboot. Documenting that the default service allows root login might be the safest way forward (though I'd suggest keeping it disabled in your own services). 

Does dropbear work fine if you specify `-F` twice, as well? Otherwise someone with a `conf` file might have issues.

  parent reply	other threads:[~2021-03-21 18:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 18:51 [PR PATCH] " mobinmob
2021-03-21  4:28 ` ericonr
2021-03-21  4:37 ` ahesford
2021-03-21  7:51 ` Vaelatern
2021-03-21 18:04 ` mobinmob
2021-03-21 18:32 ` ericonr [this message]
2021-03-21 19:01 ` mobinmob
2021-03-21 19:02 ` mobinmob
2021-03-21 19:08 ` mobinmob
2021-03-22  0:11 ` Vaelatern
2021-03-22  0:12 ` Vaelatern
2021-03-22  9:39 ` mobinmob
2021-03-22  9:42 ` mobinmob
2021-03-22  9:55 ` mobinmob
2021-03-22 16:34 ` Piraty
2021-04-25 18:33 ` Piraty
2021-04-26  0:00 ` Vaelatern
2021-04-26  0:01 ` the-maldridge
2021-04-26  0:01 ` [PR PATCH] [Closed]: " the-maldridge
2021-04-26  6:53 ` Piraty
2021-04-26 14:26 ` Vaelatern

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=20210321183249.nZv8X4YYVlKNsoZwdqPtYmjHQtA2ry7M96nt9l41sU4@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).