From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60994) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNVKy-0001eL-Ro for qemu-devel@nongnu.org; Fri, 20 May 2011 15:26:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNVKx-000212-RS for qemu-devel@nongnu.org; Fri, 20 May 2011 15:26:16 -0400 Received: from mail-qw0-f45.google.com ([209.85.216.45]:61372) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNVKx-00020y-Nw for qemu-devel@nongnu.org; Fri, 20 May 2011 15:26:15 -0400 Received: by qwj8 with SMTP id 8so2357361qwj.4 for ; Fri, 20 May 2011 12:26:15 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4DD6B777.9020800@us.ibm.com> References: <4DD6B777.9020800@us.ibm.com> From: Blue Swirl Date: Fri, 20 May 2011 22:25:55 +0300 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH] Add support for fd: protocol List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Corey Bryant Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, Tyler C Hicks On Fri, May 20, 2011 at 9:48 PM, Corey Bryant wrote: > sVirt provides SELinux MAC isolation for Qemu guest processes and their > corresponding resources (image files). sVirt provides this support > by labeling guests and resources with security labels that are stored > in file system extended attributes. Some file systems, such as NFS, do > not support the extended attribute security namespace, which is needed > for image file isolation when using the sVirt SELinux security driver > in libvirt. > > The proposed solution entails a combination of Qemu, libvirt, and > SELinux patches that work together to isolate multiple guests' images > when they're stored in the same NFS mount. This results in an > environment where sVirt isolation and NFS image file isolation can both > be provided. Very nice. QEMU should use this to support privilege separation. We already have chroot and runas switches, a new switch should convert all file references to fd references internally for that process. If this can be made transparent, this should even be the default way of operation.