From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES storage/manager/container/qemu-server] improve check_volume_access
Date: Mon, 21 Mar 2022 14:06:25 +0100 [thread overview]
Message-ID: <20220321130633.62086-1-f.ebner@proxmox.com> (raw)
The first patch is in preparation for the import-from API, allowing
users with VM.Config.Disk to list images of their VMs.
The rest of the series introduces a content type parameter to
check_volume_access() for future-proofing.
Dependency bumps for storage are needed for the parameter to actually
have an effect.
storage:
Fabian Ebner (4):
check volume access: allow if user has VM.Config.Disk
check volume accesss: add content type parameter
pvesm: extract config: add content type check
api: file restore: use check_volume_access to restrict content type
PVE/API2/Storage/FileRestore.pm | 12 ++++--------
PVE/CLI/pvesm.pm | 9 ++++++++-
PVE/Storage.pm | 9 ++++++++-
3 files changed, 20 insertions(+), 10 deletions(-)
manager:
Fabian Ebner (2):
pveam: remove: add content type check
api: vzdump: extract config: add content type check
PVE/API2/VZDump.pm | 9 ++++++++-
PVE/CLI/pveam.pm | 2 +-
2 files changed, 9 insertions(+), 2 deletions(-)
container:
Fabian Ebner (1):
api: create/modify: add content type checks
src/PVE/API2/LXC.pm | 10 +++++++++-
src/PVE/LXC.pm | 9 ++++++++-
2 files changed, 17 insertions(+), 2 deletions(-)
qemu-server
Fabian Ebner (1):
api: create/modify: add content type checks
PVE/API2/Qemu.pm | 27 ++++++++++++++++++++++++---
1 file changed, 24 insertions(+), 3 deletions(-)
--
2.30.2
next reply other threads:[~2022-03-21 13:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:06 Fabian Ebner [this message]
2022-03-21 13:06 ` [pve-devel] [PATCH storage 1/4] check volume access: allow if user has VM.Config.Disk Fabian Ebner
2022-03-22 8:31 ` Fabian Ebner
2022-03-22 9:31 ` Fabian Ebner
2022-03-24 8:18 ` Fabian Grünbichler
2022-03-28 9:07 ` Fabian Ebner
2022-03-28 11:36 ` Fabian Grünbichler
2022-03-29 7:48 ` Fabian Ebner
2022-03-29 12:33 ` Fabian Grünbichler
2022-03-21 13:06 ` [pve-devel] [PATCH storage 2/4] check volume accesss: add content type parameter Fabian Ebner
2022-03-21 13:06 ` [pve-devel] [PATCH storage 3/4] pvesm: extract config: add content type check Fabian Ebner
2022-03-21 13:06 ` [pve-devel] [PATCH storage 4/4] api: file restore: use check_volume_access to restrict content type Fabian Ebner
2022-03-21 13:06 ` [pve-devel] [PATCH manager 1/2] pveam: remove: add content type check Fabian Ebner
2022-03-21 13:06 ` [pve-devel] [PATCH manager 2/2] api: vzdump: extract config: " Fabian Ebner
2022-03-21 13:06 ` [pve-devel] [PATCH container 1/1] api: create/modify: add content type checks Fabian Ebner
2022-03-21 13:06 ` [pve-devel] [PATCH qemu-server " Fabian Ebner
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=20220321130633.62086-1-f.ebner@proxmox.com \
--to=f.ebner@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 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.