From: Shannon Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH cluster 2/2] cluster: setup: match PermitRootLogin option more precisely
Date: Wed, 18 Nov 2026 15:28:25 +0100 [thread overview]
Message-ID: <20261118142825.100797-3-s.sterz@proxmox.com> (raw)
In-Reply-To: <20261118142825.100797-1-s.sterz@proxmox.com>
`setup_sshd_config()` tries to find a line relating to the setting
`PermitRootLogin` in the sshd config. the previous regex did not match
certain cases (e.g., " PermitRootLogin yes"; " # PermitRootLogin no").
if nothing is matched the function adds a "PermitRootLogin yes" line
to the end of the file.
this would allow for cases where " PermitRootLogin no" and
"PermitRootLogin yes" are present in the same file. sshd applies the
first option it finds, so root login would be disabled. without
"PermitRootLogin yes" set any cluster join and certain functionality,
such as zfs replication, would break.
adjust the regex so that the "PermitRootLogin" option is picked up in
those cases too. also match case insensitively and allow statements
such as `permitrootlogin=yes` as OpenSSH also accepts them.
further, the early return is extended to only care about the first
occurrence of the `PermitRootLogin` option as that's the one OpenSSH
cares about.
Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
Notes:
note that by default on our installs the setting is "PermitRootLogin
yes". so this scenario could only happen if a user manually adjusts
it. however, setting "PermitRootLogin no" is often recommended so
someone accidentally adding a space infront of that line is not
impossible.
src/PVE/Cluster/Setup.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/PVE/Cluster/Setup.pm b/src/PVE/Cluster/Setup.pm
index 2550f70..b446059 100644
--- a/src/PVE/Cluster/Setup.pm
+++ b/src/PVE/Cluster/Setup.pm
@@ -150,9 +150,9 @@ sub setup_sshd_config {
my $conf = PVE::Tools::file_get_contents($ssh_system_server_config);
- return if $conf =~ m/^PermitRootLogin\s+yes\s*$/m;
+ return if $conf =~ m/^\h*PermitRootLogin(?:\h*=\h*|\h+)(\S+)/mi && lc($1) eq 'yes';
- if ($conf !~ s/^#?PermitRootLogin.*$/PermitRootLogin yes/m) {
+ if ($conf !~ s/^(?:\h*#)*\h*PermitRootLogin.*$/PermitRootLogin yes/mi) {
chomp $conf;
$conf .= "\nPermitRootLogin yes\n";
}
--
2.47.3
next prev parent reply other threads:[~2026-11-18 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:28 [PATCH cluster 0/2] Refine setup_sshd_config() Shannon Sterz
2026-11-18 14:28 ` [PATCH cluster 1/2] cluster: setup: keep file permissions for sshd config Shannon Sterz
2026-11-18 14:28 ` Shannon Sterz [this message]
2026-11-19 11:25 ` Superseded: Re: [PATCH cluster 0/2] Refine setup_sshd_config() Shannon Sterz
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=20261118142825.100797-3-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pve-devel@lists.proxmox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox