From: "M. Mohan Kumar" <mohan@in.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [V3 PATCH 0/8] virtio-9p: Use chroot to safely access files in passthrough model
Date: Tue, 18 Jan 2011 11:53:19 +0530 [thread overview]
Message-ID: <1295331799-23856-1-git-send-email-mohan@in.ibm.com> (raw)
In passthrough security model, following symbolic links in the server
side could result in TOCTTOU vulnerabilities.
This patchset resolves this issue by creating a dedicated process which
chroots into the share path and all file object access is done in the
chroot environment.
This patchset implements chroot enviroment, provides necessary functions
that can be used by the passthrough function calls.
Changes from version V2
* Treat socket IO errors as fatal, ie qemu will exit
* Split patchset based on chroot side (server) and qemu side(client)
functionalities
This patchset is tested with fsstress, connectathon, Tuxera POSIX test suite
and LTP FS testcases for all three security models.
M. Mohan Kumar (8):
Implement qemu_read_full
Provide chroot environment server side interfaces
Add client side interfaces for chroot environment
Add support to open a file in chroot environment
Create support in chroot environment
Support for creating special files
Move file post creation changes to none security model
Chroot environment for other functions
Makefile.objs | 1 +
hw/9pfs/virtio-9p-chroot.c | 414 ++++++++++++++++++++++++++++++++++++++++
hw/9pfs/virtio-9p-chroot.h | 42 ++++
hw/9pfs/virtio-9p-local.c | 456 ++++++++++++++++++++++++++++++++++++--------
hw/9pfs/virtio-9p.c | 23 +++
hw/file-op-9p.h | 2 +
osdep.c | 32 +++
qemu-common.h | 2 +
8 files changed, 891 insertions(+), 81 deletions(-)
create mode 100644 hw/9pfs/virtio-9p-chroot.c
create mode 100644 hw/9pfs/virtio-9p-chroot.h
--
1.7.3.4
next reply other threads:[~2011-01-18 6:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 6:23 M. Mohan Kumar [this message]
2011-01-18 6:25 ` [Qemu-devel] [V3 PATCH 1/8] virtio-9p: Implement qemu_read_full M. Mohan Kumar
2011-01-18 6:25 ` [Qemu-devel] [V3 PATCH 2/8] virtio-9p: Provide chroot environment server side interfaces M. Mohan Kumar
2011-01-18 17:03 ` Blue Swirl
2011-01-18 6:25 ` [Qemu-devel] [V3 PATCH 3/8] virtio-9p: Add client side interfaces for chroot environment M. Mohan Kumar
2011-01-18 6:25 ` [Qemu-devel] [V3 PATCH 4/8] virtio-9p: Add support to open a file in " M. Mohan Kumar
2011-01-18 6:25 ` [Qemu-devel] [V3 PATCH 5/8] virtio-9p: Create support " M. Mohan Kumar
2011-01-18 17:08 ` Blue Swirl
2011-01-19 11:08 ` M. Mohan Kumar
2011-01-18 6:26 ` [Qemu-devel] [V3 PATCH 6/8] virtio-9p: Support for creating special files M. Mohan Kumar
2011-01-18 17:11 ` Blue Swirl
2011-01-18 6:26 ` [Qemu-devel] [V3 PATCH 8/8] virtio-9p: Chroot environment for other functions M. Mohan Kumar
2011-01-18 8:24 ` [Qemu-devel] [V3 PATCH 7/8] virtio-9p: Move file post creation changes to none security model M. Mohan Kumar
2011-01-20 8:59 ` Stefan Hajnoczi
2011-01-20 14:41 ` M. Mohan Kumar
2011-01-20 14:48 ` Daniel P. Berrange
2011-01-20 21:15 ` Stefan Hajnoczi
2011-01-20 21:15 ` Venkateswararao Jujjuri (JV)
2011-01-20 21:45 ` Stefan Hajnoczi
2011-01-21 6:55 ` Venkateswararao Jujjuri (JV)
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=1295331799-23856-1-git-send-email-mohan@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).