From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Shannon Sterz <s.sterz@proxmox.com>
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 [thread overview]
Message-ID: <179365936285.1979512.12902516793848419942.b4-ty@b4> (raw)
In-Reply-To: <20261023093717.99161-1-s.sterz@proxmox.com>
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
prev parent reply other threads:[~2026-11-02 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 9:37 [PATCH access-control/docs v3 0/2] Update default password hash function to yescrypt Shannon Sterz
2026-10-23 9:37 ` [PATCH access-control v3 1/2] pam/pve: use yescrypt for new password hashes Shannon Sterz
2026-10-23 9:37 ` [PATCH docs v3 2/2] pveum: document that the pve realm now uses yescrypt Shannon Sterz
2026-11-02 22:42 ` Thomas Lamprecht [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=179365936285.1979512.12902516793848419942.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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