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 E6EDA1FF0F5 for ; Mon, 02 Nov 2026 23:47:46 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 5B85D21740; Mon, 02 Nov 2026 23:47:44 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Shannon Sterz Subject: applied: [PATCH access-control/docs v3 0/2] Update default password hash function to yescrypt Date: Mon, 2 Nov 2026 23:42:53 +0100 Message-ID: <179365936285.1979512.12902516793848419942.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261023093717.99161-1-s.sterz@proxmox.com> References: <20261023093717.99161-1-s.sterz@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: 1793659659141 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.356 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: H7WJZ6ZWZOB5R3ZPSAMIWMZZ45YW76JW X-Message-ID-Hash: H7WJZ6ZWZOB5R3ZPSAMIWMZZ45YW76JW 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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 23 Oct 2026 11:37:15 +0200, Shannon Sterz wrote: > Also updates the password hash when a user logs in. > > Changelog > --------- > > * v2: https://lore.proxmox.com/pve-devel/DMALE6AFOB1U.1GWA9Q9EGVHZL@proxmox.com/ > > [...] Applied, with a follow-up for access control to upgrade legacy password hashes only on a best-effort basis to avoid locking one out on quorum loss (might be debatable if that's justified, but we don't do it now (for non-tfa), fwiw), thanks! [access-control] applied to git/pve-access-control.git (master) [1/1] pam/pve: use yescrypt for new password hashes commit: adbf5cbf2548e985404e21252f09e00591eacc98 [docs] applied to git/pve-docs.git (master) [1/1] pveum: document that the pve realm now uses yescrypt commit: 1bb3648463f63a393448f886728a310946957403