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 6FC391FF0C0 for ; Wed, 21 Oct 2026 15:57:48 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id B54C1215ED; Wed, 21 Oct 2026 15:57:44 +0200 (CEST) From: Maximiliano Sandoval To: Shannon Sterz Subject: Re: [PATCH docs v2 2/2] pveum: document that the pve realm now uses yescrypt In-Reply-To: <20261021113808.233146-3-s.sterz@proxmox.com> (Shannon Sterz's message of "Wed, 21 Oct 2026 13:38:08 +0200") References: <20261021113808.233146-1-s.sterz@proxmox.com> <20261021113808.233146-3-s.sterz@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Wed, 21 Oct 2026 15:57:37 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792591057323 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.613 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) POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes 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: 6BEGP7MMXHKJWXDM6UR4Y4HSCS6NRSQZ X-Message-ID-Hash: 6BEGP7MMXHKJWXDM6UR4Y4HSCS6NRSQZ X-MailFrom: m.sandoval@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 CC: pve-devel@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Comments below. Shannon Sterz writes: > 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 nit: Perhaps /protections/protection/? > +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 nit: This should be '{pve}' rather than 'Proxmox VE '. > +based on SHA-256 that is now considered insecure. If the file nit: By whom? Is there any good source to link here? > +`/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:: -- Maximiliano