From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-api 3/4] utils: user schema: explicitly forbid @ in user-names
Date: Wed, 26 Feb 2025 21:18:57 +0100 [thread overview]
Message-ID: <383ba771-7f87-49ef-992c-1cac58c7e1ea@proxmox.com> (raw)
In-Reply-To: <20250226191702.584119-4-s.ivanov@proxmox.com>
Am 26.02.25 um 20:17 schrieb Stoiko Ivanov:
> PMGs terms are:
> * 'userid' consists of 'username'@'realm'
>
> without this patch it was possible to create a user through the api,
> with @ in the username ('foo@bar@pmg'), and it got written to the
> user-conf.
> Reading that entry was not possible, as the verification on read was
> stricter.
>
> This patch forbids '@' in usernames, and additionally drops the
> maxLength of 64, as 60 are already enforced by the regex pattern match
> (leaving 4 as minimal length for '@pmg'/'@pam').
>
> Potential for regression should be minimal (the users could not be
> read-back from the config).
>
> Reported-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> src/PMG/Utils.pm | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/src/PMG/Utils.pm b/src/PMG/Utils.pm
> index 9a50de2..7e4b70b 100644
> --- a/src/PMG/Utils.pm
> +++ b/src/PMG/Utils.pm
> @@ -50,7 +50,7 @@ postgres_admin_cmd
> try_decode_utf8
> );
>
> -my $user_regex = qr![^\s:/]+!;
> +my $user_regex = qr![^\s:@/]+!;
>
> sub valid_pmg_realm_regex {
> my $cfg = PVE::INotify::read_file(PMG::Auth::Plugin::realm_conf_id());
context is now outdated so this needs rebasing
> @@ -110,7 +110,6 @@ PVE::JSONSchema::register_standard_option('username', {
> description => "Username (without realm)",
> type => 'string',
> pattern => '[^\s:\/\@]{1,60}',
> - maxLength => 64,
> });
>
> PVE::JSONSchema::register_standard_option('pmg-email-address', {
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next prev parent reply other threads:[~2025-02-26 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:16 [pmg-devel] [PATCH pmg-api 0/4] cleanups for OIDC patch-series Stoiko Ivanov
2025-02-26 19:16 ` [pmg-devel] [PATCH pmg-api 1/4] api: authrealm: create: add quarantine as reserved realm Stoiko Ivanov
2025-02-26 20:18 ` [pmg-devel] applied: " Thomas Lamprecht
2025-02-26 19:17 ` [pmg-devel] [PATCH pmg-api 2/4] utils: drop unused variable assignment Stoiko Ivanov
2025-02-26 20:18 ` Thomas Lamprecht
2025-02-26 19:17 ` [pmg-devel] [PATCH pmg-api 3/4] utils: user schema: explicitly forbid @ in user-names Stoiko Ivanov
2025-02-26 20:18 ` Thomas Lamprecht [this message]
2025-02-26 19:17 ` [pmg-devel] [PATCH pmg-api 4/4] api: users: rework userid validation Stoiko Ivanov
2025-02-26 20:19 ` [pmg-devel] applied: " Thomas Lamprecht
2025-02-26 19:32 ` [pmg-devel] [PATCH pmg-api 0/4] cleanups for OIDC patch-series Stoiko Ivanov
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=383ba771-7f87-49ef-992c-1cac58c7e1ea@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal