From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 330091FF0E5 for ; Wed, 15 Jul 2026 19:47:32 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 91857213E3; Wed, 15 Jul 2026 19:47:31 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Shan Shaji Subject: applied: [PATCH datacenter-manager v2] fix: api: allow non-pam users to access shell Date: Wed, 15 Jul 2026 19:47:20 +0200 Message-ID: <178413762881.348724.1790302036088615634.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260623120314.305942-1-s.shaji@proxmox.com> References: <20260623120314.305942-1-s.shaji@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1784137629283 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.288 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_LOW -0.7 Sender listed at https://www.dnswl.org/, low 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: RHPLT3OQD5NOTSRB6LLTQMESKE6CWUQB X-Message-ID-Hash: RHPLT3OQD5NOTSRB6LLTQMESKE6CWUQB X-MailFrom: t.lamprecht@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 Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 23 Jun 2026 14:03:14 +0200, Shan Shaji wrote: > Remove the explicit restriction that only pam users can access the > shell. This is safe to do, as all users that are not root@pam will > be shown with a login shell. So they need to have some (PAM) login > credentials available. > > This changes is useful for setups where a host integrates with central > authentication systems (e.g. LDAP or Active Directory) either as a PDM > realm or as a PAM plugin. It also allows environments that favor > non-pam users for PDM by default, but still want to keep PAM > accounts available for admnistrators. > > [...] Applied, thanks! [1/1] fix: api: allow non-pam users to access shell commit: f3eecedf7cafbe59a1e309df9882784b9c9b5460