From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Kral <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] ui: cloudinit: disallow unprivileged users to regenerate images
Date: Mon, 4 Nov 2024 13:02:43 +0100 [thread overview]
Message-ID: <26371bea-2bd7-42d7-807a-21f2263073c4@proxmox.com> (raw)
In-Reply-To: <20241031140622.153169-1-d.kral@proxmox.com>
Am 31.10.24 um 15:06 schrieb Daniel Kral:
> Disables the "Regenerate image" button in the VM CloudInit tab for
> users, which lack the necessary permissions to do so, which are
> "VM.Config.CloudInit" and "VM.Config.CDROM". This is checked by the VM
> config update API endpoint in qemu-server, when ejecting and re-adding
> CloudInit drive images.
>
> This is consistent with the permissions restricting access to adding
> CloudInit drives in the Hardware tab.
>
> This is a cosmetic change as the VM config update API endpoint would
> fail because of insufficient permissions anyway.
>
Since those users can already use the cloudinit_update endpoint (just
not via UI) and thus effectively don't need "VM.Config.CDROM", I think
it's better to change the UI to use that endpoint as well.
The endpoint was added here [0] and the switch in the UI was already
proposed [1] as part of that but it seems never applied.
[0]:
https://lore.proxmox.com/pve-devel/20220622115206.3295425-1-aderumier@odiso.com/
[1]:
https://lore.proxmox.com/pve-devel/20220622141335.3616129-2-aderumier@odiso.com/
> Signed-off-by: Daniel Kral <d.kral@proxmox.com>
> ---
> I stumbled upon this while checking on BugZilla #3105 and trying to use
> the "Regenerate image" button with a user, that had only VM.Audit and
> VM.Config.CloudInit permissions. where the user missed the
> "VM.Config.CDROM" permission and the action couldn't be completed.
>
> www/manager6/qemu/CloudInit.js | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/www/manager6/qemu/CloudInit.js b/www/manager6/qemu/CloudInit.js
> index 49519726..aeef8c15 100644
> --- a/www/manager6/qemu/CloudInit.js
> +++ b/www/manager6/qemu/CloudInit.js
> @@ -142,7 +142,10 @@ Ext.define('PVE.qemu.CloudInit', {
> }
> });
>
> - me.down('#savebtn').setDisabled(!found);
> + let caps = Ext.state.Manager.get('GuiCap');
> + let canSaveImage = !!caps.vms['VM.Config.CDROM'] && !!caps.vms['VM.Config.Cloudinit'];
> + me.down('#savebtn').setDisabled(!found || !canSaveImage);
> +
> me.setDisabled(!found);
> if (!found) {
> me.getView().mask(gettext('No CloudInit Drive found'), ['pve-static-mask']);
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-04 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 14:06 Daniel Kral
2024-11-04 12:02 ` Fiona Ebner [this message]
2024-11-07 13:28 ` Daniel Kral
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=26371bea-2bd7-42d7-807a-21f2263073c4@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.kral@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