qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
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>
Subject: [Qemu-devel] Re: [kvm-devel] [RFC][PATCH 00/01]qemu VM entrypoints
Date: Fri, 20 Jul 2007 21:41:31 -0400 (EDT)	[thread overview]
Message-ID: <Line.LNX.4.64.0707202138210.12822@d.namei> (raw)
In-Reply-To: <20070720235007.GA1595@redhat.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>

      reply	other threads:[~2007-07-21  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C2C68600.366D%dwindsor@tresys.com>
2007-07-20 21:50 ` [Qemu-devel] [RFC][PATCH 00/01]qemu VM entrypoints David Windsor
     [not found] ` <46A1151F.7020502@codemonkey.ws>
2007-07-20 21:55   ` [Qemu-devel] Re: [kvm-devel] " David Windsor
2007-07-20 22:19     ` Anthony Liguori
     [not found] ` <20070720201101.GC12218@redhat.com>
     [not found]   ` <Line.LNX.4.64.0707201628150.9702@d.namei>
2007-07-20 21:57     ` David Windsor
2007-07-20 23:50       ` Daniel P. Berrange
2007-07-21  1:41         ` James Morris [this message]

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=Line.LNX.4.64.0707202138210.12822@d.namei \
    --to=jmorris@namei.org \
    --cc=berrange@redhat.com \
    --cc=dwindsor@gmail.com \
    --cc=dwindsor@tresys.com \
    --cc=jbrindle@tresys.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=selinux@tycho.nsa.gov \
    /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).