From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 783F11FF0DE for ; Thu, 19 Nov 2026 12:25:07 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 6720821703; Thu, 19 Nov 2026 12:25:06 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 19 Nov 2026 12:25:02 +0100 To: "Shannon Sterz" , Subject: Superseded: Re: [PATCH cluster 0/2] Refine setup_sshd_config() Message-Id: X-Mailer: aerc 0.20.0 References: <20261118142825.100797-1-s.sterz@proxmox.com> In-Reply-To: <20261118142825.100797-1-s.sterz@proxmox.com> From: "Shannon Sterz" X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795087502275 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.544 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: YDWW2SIKGMNTLAHEO6DOE6I7XMGZVFU2 X-Message-ID-Hash: YDWW2SIKGMNTLAHEO6DOE6I7XMGZVFU2 X-MailFrom: s.sterz@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Superseded-by: https://lore.proxmox.com/pve-devel/20261119112318.118471-1-s= .sterz@proxmox.com/T/#t On Wed Nov 18, 2026 at 3:28 PM CET, Shannon Sterz wrote: > these patches allow users to set their own permissions on the sshd > config and should pick up more cases in which a user may have adjusted > `PermitRootLogin` in a way that could break functionality. > > Shannon Sterz (2): > cluster: setup: keep file permissions for sshd config > cluster: setup: match PermitRootLogin option more precisely > > src/PVE/Cluster/Setup.pm | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > -- > 2.47.3