From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container/manager v3 0/2] add a deny-write option for device passthrough
Date: Mon, 9 Sep 2024 14:50:45 +0200 [thread overview]
Message-ID: <20240909125047.47720-1-f.schauer@proxmox.com> (raw)
Add the deny-write options for device passthrough, to restrict container
access to devices.
This allows for passing through a device in read-only mode without
giving the container full access to it.
Up until now a container with a device passed through to it was granted
full access to that device without an option to restrict that access as
pointed out by @Fiona.
Changes since v1:
* set default values for deny_read & deny_write
* remove the deny_read checkbox from the UI, since it is expected to
only have a very niche use case.
Changes since v2:
* remove the deny_read option due to a lack of use-cases
* rename deny_write to deny-write
pve-container:
Filip Schauer (1):
add deny-write option for device passthrough
src/PVE/LXC.pm | 7 ++++++-
src/PVE/LXC/Config.pm | 6 ++++++
2 files changed, 12 insertions(+), 1 deletion(-)
pve-manager:
Filip Schauer (1):
ui: lxc: add readonly option for device passthrough
www/manager6/lxc/DeviceEdit.js | 8 ++++++++
1 file changed, 8 insertions(+)
Summary over all repositories:
3 files changed, 20 insertions(+), 1 deletions(-)
--
Generated by git-murpp 0.6.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-09-09 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 12:50 Filip Schauer [this message]
2024-09-09 12:50 ` [pve-devel] [PATCH container v3 1/2] add " Filip Schauer
2024-09-10 14:36 ` [pve-devel] applied: " Thomas Lamprecht
2024-09-09 12:50 ` [pve-devel] [PATCH manager v3 2/2] ui: lxc: add readonly " Filip Schauer
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=20240909125047.47720-1-f.schauer@proxmox.com \
--to=f.schauer@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