From: Philipp Hufnagl <p.hufnagl@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] fix #474: allow transfer from container/vms
Date: Wed, 9 Aug 2023 16:20:42 +0200 [thread overview]
Message-ID: <22eba78f-dec2-42ff-9d75-3107aecdd981@proxmox.com> (raw)
In-Reply-To: <a3ea6ca3-9e48-9b93-7c9e-4ba137880275@proxmox.com>
On 8/9/23 13:32, Fiona Ebner wrote:
> The permission for the original pool should be checked here?! Or is
> that already done somewhere?
The permission of the original pool does not matter. The permission of
the VM is important
(maybe the original pool granting the user permission on the VM).
Hovever I tested it with granting the
user merely audit permissions on the VM and admin permissions on the
target pool and still got the
correct permission error so I don't think the permission checks have to
be modified at all
next prev parent reply other threads:[~2023-08-09 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:13 Philipp Hufnagl
2023-08-09 11:32 ` Fiona Ebner
2023-08-09 14:20 ` Philipp Hufnagl [this message]
2023-08-10 7:16 ` Fiona Ebner
2023-08-10 9:47 ` Philipp Hufnagl
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=22eba78f-dec2-42ff-9d75-3107aecdd981@proxmox.com \
--to=p.hufnagl@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox