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
 
   
 

xense-devel

[Xense-devel] Xen/sHype Access Control

To: <xense-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xense-devel] Xen/sHype Access Control
From: "Myong H. Kang" <mkang@xxxxxxxxxxxxxxxx>
Date: Thu, 19 Jan 2006 17:19:44 -0500
Delivery-date: Thu, 19 Jan 2006 22:28:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xense-devel-request@lists.xensource.com?subject=help>
List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>
List-post: <mailto:xense-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: mkang@xxxxxxxxxxxxxxxx
Sender: xense-devel-bounces@xxxxxxxxxxxxxxxxxxx
Xen 3.0/sHype provides a way to control access between domains. Simple types
can be associated with a domain that can be the basis for enforcing an
access control policy.

Controlling access to physical devices is another important area because
many of covert channels stem from sharing resources (physical devices in
this case). Also such mechanism may provide an opportunity to simplify
assurance arguments. For example, if we create a mechanism to associate
simple types to a physical device, sHype ACM can enforce an access control
policy.

I would like to hear your comments on the above idea and the feasibility of
implementing the idea.

Myong  




_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel

<Prev in Thread] Current Thread [Next in Thread>