From: Dominik Csapak <d.csapak@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [PATCH datacenter-manager/proxmox v2 0/2] check privilege paths during compilation
Date: Mon, 31 Aug 2026 09:08:46 +0200 [thread overview]
Message-ID: <20260831070855.568455-1-d.csapak@proxmox.com> (raw)
This adds a check in proxmox-router to check the used parameter interpolations
in the privilege paths of api calls for existence.
Aside from the two use sites that fabian[0] already sent a patch for
it found another wrong usage of this (patch 2/2).
changes from rfc/v1:
* rebase on master
* require Resource.Audit on /resource/{remote} for each remote, filter out
where this isn't the case instead of requiring it on /resource
0: https://lore.proxmox.com/pdm-devel/e7fd6763-4c68-4669-a32a-c34c9ad08cbe@proxmox.com/T/#t
proxmox:
Dominik Csapak (1):
router: compile time check privilege path parameters for existence
proxmox-router/src/router.rs | 209 ++++++++++++++++++++++++++++++++++-
1 file changed, 208 insertions(+), 1 deletion(-)
proxmox-datacenter-manager:
Dominik Csapak (1):
server: api: pve firewall: fix permission check
server/src/api/pve/firewall.rs | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
Summary over all repositories:
2 files changed, 223 insertions(+), 4 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-08-31 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 7:08 Dominik Csapak [this message]
2026-08-31 7:08 ` [PATCH proxmox v2 1/2] router: compile time check privilege path parameters for existence Dominik Csapak
2026-08-31 7:08 ` [PATCH datacenter-manager v2 2/2] server: api: pve firewall: fix permission check Dominik Csapak
2026-08-31 7:58 ` partially-applied: " Lukas Wagner
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=20260831070855.568455-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pdm-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.