virtiofsd: add net and pid namespace sandboxing
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | virtiofsd: move to an empty network namespacecontrib/ | +14 | 1 reply | |
| 2/2 | virtiofsd: move to a new pid namespacecontrib/ | +72 | 5 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Dr. David Alan Gilbert |
|---|---|
| 1/2 | R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] virtiofsd: add net and pid namespace sandboxing
These patches are based on gitlab.com/virtio-fs/qemu.git virtio-fs-dev.
virtiofsd is sandboxed so that it does not have access to the system in the event that the process is compromised. At the moment we use seccomp and mount namespaces to restrict the list of allowed syscalls and only give access to the shared directory.
This patch series enhances sandboxing by putting virtiofsd into an empty network and pid namespace. If the process is compromised it will be unable to perform network activity, even to localhost services running on the host. It will also be unable to see other processes running on the system since it runs as pid 1 in a new pid namespace.
These enhancements are inspired by the Crosvm virtio-fs device's jail configuration.
Stefan Hajnoczi (2):
virtiofsd: move to an empty network namespace
virtiofsd: move to a new pid namespace
contrib/virtiofsd/passthrough_ll.c | 109 +++++++++++++++++++++++------ 1 file changed, 86 insertions(+), 23 deletions(-)
Signature · 1 line
2.21.0