From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IC3yV-0003dQ-OX
	for qemu-devel@nongnu.org; Fri, 20 Jul 2007 21:41:39 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IC3yU-0003cZ-VR
	for qemu-devel@nongnu.org; Fri, 20 Jul 2007 21:41:39 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IC3yU-0003cU-Qg
	for qemu-devel@nongnu.org; Fri, 20 Jul 2007 21:41:38 -0400
Received: from mail2.sea5.speakeasy.net ([69.17.117.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jmorris@namei.org>) id 1IC3yU-0003xP-BN
	for qemu-devel@nongnu.org; Fri, 20 Jul 2007 21:41:38 -0400
Date: Fri, 20 Jul 2007 21:41:31 -0400 (EDT)
From: James Morris <jmorris@namei.org>
In-Reply-To: <20070720235007.GA1595@redhat.com>
Message-ID: <Line.LNX.4.64.0707202138210.12822@d.namei>
References: <C2C68600.366D%dwindsor@tresys.com>
	<20070720201101.GC12218@redhat.com>
	<Line.LNX.4.64.0707201628150.9702@d.namei>
	<25a1d91b0707201457m6865a505maf93d22c5c28f0cc@mail.gmail.com>
	<20070720235007.GA1595@redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Qemu-devel] Re: [kvm-devel] [RFC][PATCH 00/01]qemu VM entrypoints
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: David Windsor <dwindsor@tresys.com>, kvm-devel <kvm-devel@lists.sourceforge.net>, qemu-devel <qemu-devel@nongnu.org>, selinux <selinux@tycho.nsa.gov>, Joshua Brindle <jbrindle@tresys.com>, David Windsor <dwindsor@gmail.com>

On Sat, 21 Jul 2007, Daniel P. Berrange wrote:

> obviously the UNIX user has a corresponding SELinux domain. In the remote 
> case, one could map x509 certificate IDs (the remote user's identify) to 
> appropriate local SELinux domains.

There is already a mechanism for conveying SELinux labels over the network 
via IPsec.


- James
-- 
James Morris
<jmorris@namei.org>