From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH qemu-server] fix: api: fix permission check for cloudinit drive update
Date: Mon, 24 Jul 2023 13:46:10 +0200 [thread overview]
Message-ID: <fe06fbbe-e6d1-b857-9037-52f478d8b66b@proxmox.com> (raw)
In-Reply-To: <20230313125625.1060320-1-f.weber@proxmox.com>
ping (patch still applies)
On 13/03/2023 13:56, Friedrich Weber wrote:
> Trying to regenerate a cloudinit drive as a non-root user via the API
> currently throws a Perl error, as reported in the forum [1]. This is
> due to a type mismatch in the permission check, where a string is
> passed but an array is expected.
>
> [1] https://forum.proxmox.com/threads/regenerate-cloudinit-by-put-api-return-500.124099/
>
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
> To see if we have the same problem for other API endpoints, I ran:
> grep -r "['\"]perm['\"][^[]*]" .
> in my locally checked-out repos, but found only this single occurrence.
>
> PVE/API2/Qemu.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
> index 587bb22..0ea18eb 100644
> --- a/PVE/API2/Qemu.pm
> +++ b/PVE/API2/Qemu.pm
> @@ -1398,7 +1398,7 @@ __PACKAGE__->register_method({
> proxyto => 'node',
> description => "Regenerate and change cloudinit config drive.",
> permissions => {
> - check => ['perm', '/vms/{vmid}', 'VM.Config.Cloudinit'],
> + check => ['perm', '/vms/{vmid}', ['VM.Config.Cloudinit']],
> },
> parameters => {
> additionalProperties => 0,
next prev parent reply other threads:[~2023-07-24 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:56 Friedrich Weber
2023-07-24 11:46 ` Friedrich Weber [this message]
2023-07-25 15:23 ` [pve-devel] applied: " Thomas Lamprecht
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=fe06fbbe-e6d1-b857-9037-52f478d8b66b@proxmox.com \
--to=f.weber@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