From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bb0Jg-0001M9-N0 for qemu-devel@nongnu.org; Thu, 17 Jun 2004 13:04:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bb0Je-0001Hg-TW for qemu-devel@nongnu.org; Thu, 17 Jun 2004 13:04:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bb0Je-0001HO-Ob for qemu-devel@nongnu.org; Thu, 17 Jun 2004 13:04:42 -0400 Received: from [195.121.6.14] (helo=smtp18.wxs.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Bb0I8-0003dE-02 for qemu-devel@nongnu.org; Thu, 17 Jun 2004 13:03:08 -0400 Received: from ip503ca58d.speed.planet.nl (ip503ca58d.speed.planet.nl [80.60.165.141]) by smtp18.wxs.nl (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0HZG0077EQ16WP@smtp18.wxs.nl> for qemu-devel@nongnu.org; Thu, 17 Jun 2004 19:03:07 +0200 (CEST) Date: Thu, 17 Jun 2004 19:03:21 +0200 From: Sander Nagtegaal Subject: Re: [Qemu-devel] [PATCH] Security house-cleaning In-reply-to: <20040617163740.GB20148@sentinelchicken.org> Message-id: <200406171903.21342.trunks-carracho@planet.nl> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline References: <20040617043838.GA1938@sentinelchicken.org> <20040617151418.GD27872@cs.unibo.it> <20040617163740.GB20148@sentinelchicken.org> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org *nothing to do with security* On thing wich would also be a good thing to add ( I'm not sure QEMU has it ) , is drag and drop from the guest OS to the emulator. If anyone of you are familiair with virtual PC then you'll know what I'll mean. Op donderdag 17 juni 2004 6:37 pm, schreef Tim: > > One of the main pros of Qemu (among the others) it that it has been > > designed NOT to run SUID. > > The only piece of code that need root access is tuntap networking. > > This problem can be circunvented by: > > - using sudo for tuntap > > - using user net (a.k.a slirp) > > - using vde. > > Other future considerations: > - PCI Proxy support (if it is ever offically supported) > How will the host OS allow access by QEMU guest in this case? > - Other bus (USB, firewire, etc) direct access to real hardware > > > Not trying to be alarmist. Just being conservative with code > quality/security. > > tim > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel