public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	markus frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH container 1/1] fix #3748 changed regex-pattern to accept escape sequences on Comma
Date: Wed, 19 Jan 2022 14:52:05 +0100	[thread overview]
Message-ID: <9b33081c-78cc-66f5-a1c5-8b817d7cdaf2@proxmox.com> (raw)
In-Reply-To: <20220119120422.26517-1-m.frank@proxmox.com>

On 19.01.22 13:21, Markus Frank wrote:
> Correction: Patch for access-control and not for container
> 

also missing your SOB (sign-off).

side note: our webmailer is currently a bit broken on reply, i.e., it omits the
In-Reply-to header which in turn breaks threading for all with a sensible MUA.
Thus I'd appreciate it greatly if you'd use another MTA/MUA that avoids such
issues for now, e.g., thunderbird or claws if you prefer graphical or (neo)mutt
or aerc if you prefer terminal based ones. On the long run keeping up with our
and other opensource's projects development lists via webmail alone may get
cumbersome fast anyway ;-)


>> On 19.01.2022 13:04 markus frank <m.frank@proxmox.com> wrote:
>>
>>  
>> old-pattern: '\w+=[^,]+(,\s*\w+=[^,]+)*'

I mean, I can see that from the commit diff, so not really adding much here

>> the old pattern didn't allow LDAP base domain name to be like: dc=first\, second, dc=com

that is good info though, maybe add that commas in LDAP paths require
escaping and so we explicitly allow for a escaped comma only.

>> new-pattern: qr(\w+=([^,\\]|\\,)+(,\s*\w+=([^,\\]|\\,)+)*),

abobe again a bit redundant with the diff.

>> ---
>>  src/PVE/Auth/LDAP.pm | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/src/PVE/Auth/LDAP.pm b/src/PVE/Auth/LDAP.pm
>> index 97d0778..ad23cb2 100755
>> --- a/src/PVE/Auth/LDAP.pm
>> +++ b/src/PVE/Auth/LDAP.pm
>> @@ -19,7 +19,7 @@ sub properties {
>>  	base_dn => {
>>  	    description => "LDAP base domain name",
>>  	    type => 'string',
>> -	    pattern => '\w+=[^,]+(,\s*\w+=[^,]+)*',
>> +	    pattern => qr(\w+=([^,\\]|\\,)+(,\s*\w+=([^,\\]|\\,)+)*),

nit: we do not really use () for quoted regex operator, I'd rather prefer one
of qr// qr!! or qr@@ which all have some use in our code base, IIRC.

Further, this disallows now some values including a \ that where ok previous,
is that intended or what's the idea here? The commit message does not talks about
it.

>>  	    optional => 1,
>>  	    maxLength => 256,
>>  	},
>> @@ -33,7 +33,7 @@ sub properties {
>>  	bind_dn => {
>>  	    description => "LDAP bind domain name",
>>  	    type => 'string',
>> -	    pattern => '\w+=[^,]+(,\s*\w+=[^,]+)*',
>> +	    pattern => qr(\w+=([^,\\]|\\,)+(,\s*\w+=([^,\\]|\\,)+)*),
>>  	    optional => 1,
>>  	    maxLength => 256,
>>  	},
>> @@ -91,7 +91,7 @@ sub properties {
>>  	    description => "LDAP base domain name for group sync. If not set, the"
>>  		." base_dn will be used.",
>>  	    type => 'string',
>> -	    pattern => '\w+=[^,]+(,\s*\w+=[^,]+)*',
>> +	    pattern => qr(\w+=([^,\\]|\\,)+(,\s*\w+=([^,\\]|\\,)+)*),
>>  	    optional => 1,
>>  	    maxLength => 256,
>>  	},
>> -- 
>> 2.30.2
>>




      reply	other threads:[~2022-01-19 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 12:04 markus frank
2022-01-19 13:52 ` 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=9b33081c-78cc-66f5-a1c5-8b817d7cdaf2@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=m.frank@proxmox.com \
    --cc=pve-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal