From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dimitry Golubovsky <golubovsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Ways to exit from kvm on behalf of the quest system?
Date: Wed, 1 Aug 2007 18:14:41 +0100 [thread overview]
Message-ID: <20070801171441.GK31282@redhat.com> (raw)
In-Reply-To: <bcba51a0708011006q3df19f99k7ae9df230c95487f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Aug 01, 2007 at 01:06:22PM -0400, Dimitry Golubovsky wrote:
> Daniel,
>
> On 8/1/07, Daniel P. Berrange <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>
> > Unless you whitelist which monitor commands it can run this would be a
> > significant security hole. eg a guest could run
> >
> > 'usb_add disk /some/path'
> >
> > To get access to arbitrary files & disks from the host.
> >
>
> If we assume that kvm runs under root, yes (and if kvm finds out it
> runs under root, it might disable such access to monitor). I have
> written a suid wrapper (very simple) that does whatever necessary
> under root, and then drops to user privileges, then execs kvm, so
> these actions will be limited by Linux multi-user mechanisms as usual.
> In my daily practice, I run kvm under my user privileges, and it works
> fine.
It can be a problem even if running as an unprivileged user, since the
guest can read/write any files owned by that user - for example other
guest disk images the user may have in their home dir.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-01 17:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 16:56 Ways to exit from kvm on behalf of the quest system? Dimitry Golubovsky
[not found] ` <bcba51a0707310956q41554dedn6b88f3819c37bb41-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-31 19:17 ` Amit Shah
[not found] ` <200708010047.36600.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-31 19:43 ` Dimitry Golubovsky
[not found] ` <bcba51a0707311243vf78d45bo9fcb61d0b972f37a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-01 16:40 ` Avi Kivity
[not found] ` <46B0B779.5050407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-01 16:48 ` Dimitry Golubovsky
[not found] ` <bcba51a0708010948t106be39dh81fccc10ebf0a676-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-01 16:53 ` Avi Kivity
2007-08-01 16:57 ` Daniel P. Berrange
[not found] ` <20070801165750.GH31282-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-08-01 17:06 ` Dimitry Golubovsky
[not found] ` <bcba51a0708011006q3df19f99k7ae9df230c95487f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-01 17:14 ` Daniel P. Berrange [this message]
2007-08-01 18:11 ` Anthony Liguori
[not found] ` <46B0CCC3.6010308-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-08-01 18:35 ` Dimitry Golubovsky
[not found] ` <bcba51a0708011135q109b9869qc8c563e6e3aeb004-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-01 21:28 ` Anthony Liguori
[not found] ` <46B0FAE2.4090906-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-08-01 21:43 ` Dimitry Golubovsky
[not found] ` <bcba51a0708011443o1d48779en94c724dc4fd0625-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-01 21:48 ` Anthony Liguori
2007-08-01 21:57 ` Anthony Liguori
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=20070801171441.GK31282@redhat.com \
--to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=golubovsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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