From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] superseded: [PATCH storage/guest-common/qemu-server 0/3] harden import of file-based volumes
Date: Mon, 04 Nov 2024 11:43:37 +0100 [thread overview]
Message-ID: <1730716945.dyx5boopr1.astroid@yuna.none> (raw)
In-Reply-To: <20240809112234.1572295-1-f.gruenbichler@proxmox.com>
v2 sent: https://lore.proxmox.com/pve-devel/20241104104221.228730-1-f.gruenbichler@proxmox.com
On August 9, 2024 1:22 pm, Fabian Grünbichler wrote:
> this series of patches implements additional hardening when copying
> potentially untrusted image files:
> - extend file_size_info helper which already does most of the work
> - add call to check imported volume in remote migration
> - add/adapt calls for `import-from` handling in Qemu
>
> these are not problematic at the moment, and these patches just serve as
> additional hardening:
> - remote migration requires a special privilege, the source must already
> be trusted
> - import-from only allows importing volumes already on the storage,
> which are not untrusted but created by PVE itself, or by a user with
> root privileges
>
> the functionality in PVE::Storage should also be used for future
> additions where untrusted image files are processed:
> - Dominik's OVA import patch series
> - arbitrary disk image upload/download features
>
> where not doing such checks might pose a security risk.
>
> pve-guest-common:
>
> Fabian Grünbichler (1):
> storage tunnel: check just-imported image files
>
> src/PVE/StorageTunnel.pm | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> pve-storage:
>
> Fabian Grünbichler (1):
> file_size_info: implement untrusted mode
>
> src/PVE/Storage.pm | 4 ++--
> src/PVE/Storage/Plugin.pm | 35 ++++++++++++++++++++++++++++++-----
> 2 files changed, 32 insertions(+), 7 deletions(-)
>
> qemu-server:
>
> Fabian Grünbichler (1):
> disk import: add additional safeguards for imported image files
>
> PVE/API2/Qemu.pm | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> --
> 2.39.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-04 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 11:22 [pve-devel] " Fabian Grünbichler
2024-08-09 11:22 ` [pve-devel] [PATCH guest-common 1/1] storage tunnel: check just-imported image files Fabian Grünbichler
2024-09-10 11:33 ` Fiona Ebner
2024-08-09 11:22 ` [pve-devel] [PATCH storage 1/1] file_size_info: implement untrusted mode Fabian Grünbichler
2024-09-10 11:33 ` Fiona Ebner
2024-08-09 11:22 ` [pve-devel] [PATCH qemu-server 1/1] disk import: add additional safeguards for imported image files Fabian Grünbichler
2024-09-10 11:33 ` Fiona Ebner
2024-11-04 10:43 ` Fabian Grünbichler [this message]
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=1730716945.dyx5boopr1.astroid@yuna.none \
--to=f.gruenbichler@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