From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH access-control/docs v2 0/2] Update default password hash function to yescrypt
Date: Wed, 21 Oct 2026 16:04:00 +0200 [thread overview]
Message-ID: <s8oecdjtajz.fsf@toolbox> (raw)
In-Reply-To: <20261021113808.233146-1-s.sterz@proxmox.com> (Shannon Sterz's message of "Wed, 21 Oct 2026 13:38:06 +0200")
Shannon Sterz <s.sterz@proxmox.com> writes:
> Also updates the password hash when a user logs in.
>
> Changelog
> ---------
>
> * 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:
>
> [...]
>
> docs:
>
> [...]
Modulo some very small comments regarding documentation (see reply to
commit), the series looks good to me.
Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
--
Maximiliano
next prev parent reply other threads:[~2026-10-21 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 11:38 [PATCH access-control/docs v2 0/2] Update default password hash function to yescrypt Shannon Sterz
2026-10-21 11:38 ` [PATCH access-control v2 1/2] pam/pve: use yescrypt for new password hashes Shannon Sterz
2026-10-21 11:38 ` [PATCH docs v2 2/2] pveum: document that the pve realm now uses yescrypt Shannon Sterz
2026-10-21 13:57 ` Maximiliano Sandoval
2026-10-21 14:39 ` Shannon Sterz
2026-10-21 14:04 ` Maximiliano Sandoval [this message]
2026-10-21 14:39 ` [PATCH access-control/docs v2 0/2] Update default password hash function to yescrypt Shannon Sterz
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=s8oecdjtajz.fsf@toolbox \
--to=m.sandoval@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