From: Oguz Bektas <o.bektas@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v1 access-control++ 0/5] SuperUser privilege
Date: Tue, 8 Feb 2022 14:10:06 +0100 [thread overview]
Message-ID: <20220208131011.752134-1-o.bektas@proxmox.com> (raw)
"SuperUser" (henceforth referred as SU) privilege allows to give
root-only permissions to API users, enabling them to perform privileged
actions on behalf of root@pam.
this privilege is enabled by default for "root@pam", and also mapped
inside "SuperAdministrator" (referred as SA)
changes from RFC (thanks for the review fabian g.!):
* manager: allow SAs to see/edit certain things on GUI
* qemu-server: also check the required non-root
VM privileges along with the SU priv
* pve-container: adapted error messages, changed variable name to
"is_superuser" for better clarity (in comparison to prev. "is_root"
which is a bit confusing)
* access-control: TFA permissions adaptation for SAs
access-control:
Oguz Bektas (2):
add "SuperAdministrator" role with the new "SuperUser" privilege
tfa: allow superusers to edit root@pam tfa
src/PVE/API2/TFA.pm | 7 +++++--
src/PVE/AccessControl.pm | 9 ++++++---
src/PVE/RPCEnvironment.pm | 2 +-
3 files changed, 12 insertions(+), 6 deletions(-)
container:
Oguz Bektas (1):
fix #2582: api: add checks for 'SuperUser' privilege for root-only
options
src/PVE/API2/LXC.pm | 13 ++++++-------
src/PVE/API2/LXC/Status.pm | 8 ++++++--
src/PVE/LXC.pm | 9 ++++++---
3 files changed, 18 insertions(+), 12 deletions(-)
manager:
Oguz Bektas (1):
change 'root@pam' checks with 'SuperUser' capability check
www/manager6/Utils.js | 3 ++-
www/manager6/dc/Config.js | 2 +-
www/manager6/dc/UserView.js | 2 +-
www/manager6/lxc/Options.js | 2 +-
www/manager6/lxc/Resources.js | 2 +-
www/manager6/node/Config.js | 2 +-
www/manager6/window/Migrate.js | 4 ++--
7 files changed, 9 insertions(+), 8 deletions(-)
qemu-server:
Oguz Bektas (1):
add SuperUser privilege checks for root-only options
PVE/API2/Qemu.pm | 119 +++++++++++++++++++++++++++++------------------
1 file changed, 73 insertions(+), 46 deletions(-)
--
2.30.2
next reply other threads:[~2022-02-08 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 13:10 Oguz Bektas [this message]
2022-02-08 13:10 ` [pve-devel] [PATCH v1 access-control 1/5] add default "SuperAdministrator" role with the new "SuperUser" privilege Oguz Bektas
2022-02-08 13:10 ` [pve-devel] [PATCH v1 access-control 2/5] tfa: allow superusers to edit root@pam tfa Oguz Bektas
[not found] ` <<20220208131011.752134-3-o.bektas@proxmox.com>
2022-02-10 15:30 ` Fabian Grünbichler
2022-02-08 13:10 ` [pve-devel] [PATCH v1 container 3/5] fix #2582: api: add checks for 'SuperUser' privilege for root-only options Oguz Bektas
[not found] ` <<20220208131011.752134-4-o.bektas@proxmox.com>
2022-02-10 15:30 ` Fabian Grünbichler
2022-02-08 13:10 ` [pve-devel] [PATCH v1 manager 4/5] change 'root@pam' checks with 'SuperUser' capability check Oguz Bektas
[not found] ` <<20220208131011.752134-5-o.bektas@proxmox.com>
2022-02-10 15:29 ` Fabian Grünbichler
2022-02-25 10:13 ` Dominik Csapak
2022-02-25 12:24 ` Thomas Lamprecht
2022-02-08 13:10 ` [pve-devel] [PATCH v1 qemu-server 5/5] add SuperUser privilege checks for root-only options Oguz Bektas
[not found] ` <<20220208131011.752134-6-o.bektas@proxmox.com>
2022-02-10 15:29 ` Fabian Grünbichler
2022-02-10 15:28 ` [pve-devel] [PATCH v1 access-control++ 0/5] SuperUser privilege Fabian Grünbichler
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=20220208131011.752134-1-o.bektas@proxmox.com \
--to=o.bektas@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