From: Shannon Sterz <s.sterz@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 0/3] implement a minimum length of 8 characters for new passwords
Date: Fri, 4 Oct 2024 15:40:51 +0200 [thread overview]
Message-ID: <20241004134054.263913-1-s.sterz@proxmox.com> (raw)
this patch series aims to implement a minimum length of 8 characters for
new passwords. this is more in line with NIST's current recommendations
[1].
the first patch in this series also ignores the `password` parameter in
the update user endpoint, as it is currently redundant. see the commit
for more info.
[1]: https://pages.nist.gov/800-63-4/sp800-63b.html#passwordver
Shannon Sterz (3):
api: ignore password parameter in the update_user endpoint
api: enforce minimum character limit of 8 on new passwords
ui: set min length for new passwords to 8
pbs-api-types/src/lib.rs | 2 +-
src/api2/access/mod.rs | 4 ++--
src/api2/access/user.rs | 32 +++++++++++---------------------
www/config/UserView.js | 1 +
www/window/UserEdit.js | 2 +-
5 files changed, 16 insertions(+), 25 deletions(-)
--
2.39.5
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2024-10-04 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 13:40 Shannon Sterz [this message]
2024-10-04 13:40 ` [pbs-devel] [PATCH proxmox-backup 1/3] api: ignore password parameter in the update_user endpoint Shannon Sterz
2024-10-04 13:40 ` [pbs-devel] [PATCH proxmox-backup 2/3] api: enforce minimum character limit of 8 on new passwords Shannon Sterz
2024-10-04 13:40 ` [pbs-devel] [PATCH proxmox-backup 3/3] ui: set min length for new passwords to 8 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=20241004134054.263913-1-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pbs-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