From: Shannon Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/2] pveum: note that passwords set with old versions may use insecure hashes
Date: Fri, 9 Oct 2026 14:27:30 +0200 [thread overview]
Message-ID: <20261009122729.178682-4-s.sterz@proxmox.com> (raw)
In-Reply-To: <20261009122729.178682-2-s.sterz@proxmox.com>
and describe how to remidiate that issue.
Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
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 | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/pveum.adoc b/pveum.adoc
index 53cb992..f3b68c2 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -154,6 +154,13 @@ 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 versions of Proxmox VE that used a
+libpve-common-perl version older than 8.3.1 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, setting a new password
+for that account is recommended. The new password will then be stored using
+yescrypt (the hash will start with `$y$`).
+
LDAP::
LDAP (Lightweight Directory Access Protocol) is an open, cross-platform protocol
--
2.47.3
prev parent reply other threads:[~2026-10-09 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 12:27 [PATCH docs 0/2] update documentation to show that yescrypt is used Shannon Sterz
2026-10-09 12:27 ` [PATCH docs 1/2] pveum: document that the pve realm now uses yescrypt Shannon Sterz
2026-10-09 12:27 ` Shannon Sterz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261009122729.178682-4-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox