From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Shannon Sterz <s.sterz@proxmox.com>
Subject: [pve-devel] applied:-series [PATCH manager/widget-toolkit/access-control 0/3] enforce minimum of 8 characters on new passwords
Date: Mon, 11 Nov 2024 23:11:21 +0100 [thread overview]
Message-ID: <e4d28c6e-0645-471c-961e-2604c97e6b16@proxmox.com> (raw)
In-Reply-To: <20241004133205.258755-1-s.sterz@proxmox.com>
Am 04.10.24 um 15:32 schrieb Shannon Sterz:
> this series pushes the minimum of 5 characters up to at least 8 for pve.
> this puts our password policy in line with NIST's latest recommendation
> [1].
>
> [1]: https://pages.nist.gov/800-63-4/sp800-63b.html#passwordver
>
> pve-manager:
>
> Shannon Sterz (1):
> ui: workspace/user view: change password minimum length to 8
>
> www/manager6/Workspace.js | 1 +
> www/manager6/dc/UserEdit.js | 2 +-
> www/manager6/dc/UserView.js | 1 +
> 3 files changed, 3 insertions(+), 1 deletion(-)
>
>
> proxmox-widget-toolkit:
>
> Shannon Sterz (1):
> password edit: add a minimum length parameter
>
> src/window/PasswordEdit.js | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
>
> pve-access-control:
>
> Shannon Sterz (1):
> api: enforce a minimum length of 8 on new passwords
>
> src/PVE/API2/AccessControl.pm | 2 +-
> src/PVE/API2/User.pm | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
> Summary over all repositories:
> 6 files changed, 12 insertions(+), 4 deletions(-)
>
> --
> Generated by git-murpp 0.5.0
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
applied the remaining two patches now too, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-11 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 13:32 [pve-devel] " Shannon Sterz
2024-10-04 13:32 ` [pve-devel] [PATCH manager 1/3] ui: workspace/user view: change password minimum length to 8 Shannon Sterz
2024-10-04 13:32 ` [pve-devel] [PATCH widget-toolkit 2/3] password edit: add a minimum length parameter Shannon Sterz
2024-11-11 20:38 ` [pve-devel] applied: " Thomas Lamprecht
2024-10-04 13:32 ` [pve-devel] [PATCH access-control 3/3] api: enforce a minimum length of 8 on new passwords Shannon Sterz
2024-11-11 22:11 ` 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=e4d28c6e-0645-471c-961e-2604c97e6b16@proxmox.com \
--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