public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-ve-rs 1/1] partial fix #6226: macros: add LDAP_UDP macro
Date: Wed, 19 Mar 2025 09:56:51 +0100	[thread overview]
Message-ID: <9b243910-e88e-4aa3-a592-0d732bcdcc78@proxmox.com> (raw)
In-Reply-To: <D8K44D12DN35.N2ED1JKP8ROD@proxmox.com>



On 3/19/25 09:50, Christoph Heiss wrote:
> On Tue Mar 18, 2025 at 4:38 PM CET, Stefan Hanreich wrote:
>> Add LDAP_UDP macro to the firewall to support LDAP implementations
>> that use UDP as well, such as Windows AD [1]
>>
>> [1] https://learn.microsoft.com/de-de/troubleshoot/windows-server/active-directory/config-firewall-for-ad-domains-and-trusts
>> [..]
>> --- a/proxmox-ve-config/resources/macros.json
>> +++ b/proxmox-ve-config/resources/macros.json
>> @@ -377,6 +377,15 @@
>>      ],
>>      "desc": "Lightweight Directory Access Protocol traffic"
>>    },
>> +  "LDAP_UDP": {
> 
> What about naming it "AD" instead and including both the TCP and UDP
> rule instead? I.e. making it completely separate from the "normal" LDAP
> rule.

The idea was to not suddenly open up a port for users that are using
that macro currently (and it works fine for them).

> Naming it "LDAP_UDP" could be confusing to users, in that it might be
> required for actual, compliant LDAP servers as well, not just AD.

Agreed, that the name might not be optimal, I'm open to suggestions.

>> +    "code": [
>> +      {
>> +        "dport": "389",
>> +        "proto": "udp"
>> +      }
>> +    ],
>> +    "desc": "Lightweight Directory Access Protocol traffic via UDP"
>> +  },
>>    "LDAPS": {
>>      "code": [
>>        {
> 



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-03-19  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 15:38 Stefan Hanreich
2025-03-18 15:38 ` [pve-devel] [PATCH pve-firewall " Stefan Hanreich
2025-03-19  8:50 ` [pve-devel] [PATCH proxmox-ve-rs " Christoph Heiss
2025-03-19  8:56   ` Stefan Hanreich [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=9b243910-e88e-4aa3-a592-0d732bcdcc78@proxmox.com \
    --to=s.hanreich@proxmox.com \
    --cc=c.heiss@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