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 383501FF0B0 for ; Fri, 23 Oct 2026 11:37:24 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id E46EB2161C; Fri, 23 Oct 2026 11:37:23 +0200 (CEST) From: Shannon Sterz To: pve-devel@lists.proxmox.com Subject: [PATCH access-control/docs v3 0/2] Update default password hash function to yescrypt Date: Fri, 23 Oct 2026 11:37:15 +0200 Message-ID: <20261023093717.99161-1-s.sterz@proxmox.com> X-Mailer: git-send-email 2.47.3 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: 1792748240162 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.710 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: IPLDQON7KNVJOUNTAXK5D5232ORRWAAI X-Message-ID-Hash: IPLDQON7KNVJOUNTAXK5D5232ORRWAAI 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: Also updates the password hash when a user logs in. Changelog --------- * v2: https://lore.proxmox.com/pve-devel/DMALE6AFOB1U.1GWA9Q9EGVHZL@proxmox.com/ - changes since v2 (thanks @ Maximiliano Sandoval): + adjusted the commit message of the first patch to clarify why yescrypt should be used + updated documentation to use the proper `{pve}` shorthand * v1: https://lore.proxmox.com/pve-devel/20261009122729.178682-2-s.sterz@proxmox.com/ - changes since v1: + added a patch that actually opts in the pve and pam realm to yescrypt hashes and updates hashes on login access-control: Shannon Sterz (1): pam/pve: use yescrypt for new password hashes src/PVE/Auth/PAM.pm | 2 +- src/PVE/Auth/PVE.pm | 9 ++++++++- 2 files changed, 9 insertions(+), 2 deletions(-) docs: Shannon Sterz (1): pveum: document that the pve realm now uses yescrypt pveum.adoc | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) Summary over all repositories: 3 files changed, 21 insertions(+), 7 deletions(-) -- Generated by murpp 0.12.0