Github messages for voidlinux
 help / color / mirror / Atom feed
From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dropbear: disable password logins for root.
Date: Sun, 21 Mar 2021 19:04:48 +0100	[thread overview]
Message-ID: <20210321180448.KVje3fDy2p7UTGvW5HrlKZaC_PxrNL3LaCiLd-RPluc@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: 719 bytes --]

New comment by mobinmob on void-packages repository

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

Comment:
@ericonr I will write an INSTALL.msg ;)
@ahesford Ι fully agree with getting -F out of $OPTS. I am using the same logic in the [66 services](https://github.com/mobinmob/void-66-services).  I think there are others runit services in the repo that can benefit from something similar - that is seperation of optional and mandatory switches.  Key generation is a part of all three ssh services in the repo (openssh, dropbear, tinyssh).
@Vaelatern It is ultimately a matter or policy. Disabling password login for root is a good practice. Users can rely on all sorts of things :)

  parent reply	other threads:[~2021-03-21 18:04 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 [this message]
2021-03-21 18:32 ` ericonr
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=20210321180448.KVje3fDy2p7UTGvW5HrlKZaC_PxrNL3LaCiLd-RPluc@z \
    --to=mobinmob@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).