WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH] [XEND] Xen-API support for ACM

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [XEND] Xen-API support for ACM
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Fri, 26 Jan 2007 10:56:42 -0500
Cc: Ewan Mellor <ewan@xxxxxxxxxxxxx>, ronpz@xxxxxxxxxx, sailer@xxxxxxxxxx
Delivery-date: Fri, 26 Jan 2007 07:54:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This patch is adding initial Xen-API support for the sHype access
control module so that functionality that can be reached via 'xm'
commands can also be reached using the Xen-API. 

This patch adds a security_label to the VM class, which is to be set
when ACM is enabled. Access control to the block interface is now
enforced in blkif.py and denied if the system's policy does not allow a
VM to access a block interface.

Future patches will extend this part of the Xen-API and lib-xen and
provide (latex) documentation.

The module is designed to also support other policies than ACM when they become 
available.

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Attachment: xend-xspolicy-xapi-main.diff
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>