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 5462F1FF0C0 for ; Wed, 21 Oct 2026 13:38:22 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 1BF6021645; Wed, 21 Oct 2026 13:38:15 +0200 (CEST) From: Shannon Sterz To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 2/2] pveum: document that the pve realm now uses yescrypt Date: Wed, 21 Oct 2026 13:38:08 +0200 Message-ID: <20261021113808.233146-3-s.sterz@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261021113808.233146-1-s.sterz@proxmox.com> References: <20261021113808.233146-1-s.sterz@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792582689784 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.740 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: VY2VHMGGYH6N26D3ZSEKCIUS2TIQPSWW X-Message-ID-Hash: VY2VHMGGYH6N26D3ZSEKCIUS2TIQPSWW 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: and document that passwords will be updated on login. Signed-off-by: Shannon Sterz --- Notes: we may want to implement a scheme similar to pbs and pdm where passwords are updated to the latest hashing scheme on log in, requiring less user interaction. pveum.adoc | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/pveum.adoc b/pveum.adoc index d089cb6..b970f1e 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -147,11 +147,18 @@ these users to log in via their system username and password. {pve} Authentication Server:: This is a Unix-like password store, which stores hashed passwords in -`/etc/pve/priv/shadow.cfg`. Passwords are hashed using the SHA-256 hashing -algorithm. This is the most convenient realm for small-scale (or even -mid-scale) installations, where users do not need access to anything outside of -{pve}. In this case, users are fully managed by {pve} and are able to change -their own passwords via the GUI. +`/etc/pve/priv/shadow.cfg`. Passwords are hashed and salted using the yescrypt +algorithm footnote:[yescrypt https://www.openwall.com/yescrypt/]. It provides +strong protections against offline password cracking attempts. This realm is the +most convenient realm for small-scale (or even mid-scale) installations, where +users do not need access to anything outside of {pve}. In this case, users are +fully managed by {pve} and are able to change their own passwords via the GUI. + +NOTE: Passwords created with older versions of Proxmox VE used a hashing scheme +based on SHA-256 that is now considered insecure. If the file +`/etc/pve/priv/shadow.cfg` shows a password hash starting with `$5$` for an +account that account still uses such a password. The hash will be updated on the +next login of that user or when a new password is set. LDAP:: -- 2.47.3