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] [patches] shype for xen / patches

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [patches] shype for xen / patches
From: Reiner Sailer <sailer@xxxxxxxxxx>
Date: Wed, 30 Mar 2005 00:11:41 -0500
Delivery-date: Thu, 31 Mar 2005 12:30:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Reply-to:
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Sensitivity:

Hi all,

For the past two months our team has worked to integrate the sHype security architecture into Xen. sHype was initially discussed on the Xen development emailing list in http://lists.xensource.com/archives/html/xen-devel/2005-01/msg00519.html and the implementation described here is based on the design published in http://www.research.ibm.com/secure_systems_department/projects/hypervisor.

We have attached the stable patches of our port for the group to evaluate. The code successfully enforces "sample" security policies and demonstrates the minimal impact sHype has on both the main Xen code base and on Xen's run-time performance.  (I post the patches here tonight, and will follow up by Thursday with a README and some examples.) The security enforcement hooks cover domain operations, event channels, and also --as far as available-- grant tables. These hooks will also cover save/restore/migrate once these operations are working and stable.

Please note that the default policy under these patches is a "NULL" policy.  This means that, even after the patches are applied, there will be *no* change to the user or administrator experience until a security policy is explicitly enabled.

The sHype port consists of three patches (tested on the xeno-unstable.bk  version from March 29 th):

1. shype_4_xeno-unstable.bk_v0.2_xen.diff .. patch that includes the security enforcement code and access control module, the heart of shype;

2. shype_4_xeno-unstable.bk_v0.2_sparse.diff .. kernel patch that includes an additional /proc/xen/policycmd interface using a new policy hypercall to communicate policies between xen and the policy management tool;

3. shype_4_xeno-unstable.bk_v0.2_tools.diff .. tools patch that includes support for a new parameter security subject identifier reference (ssidref) in the domain configuration, as well as a v-e-r-y simple policy tool to set binary policies in xen and to retrieve and dump enforced policies from xen (tools/policytool); in a future version, this tool will  read user-defined policies and compile them into the binary policies to be downloaded into xen.

If you install the patches, please start with a clean xeno-unstable.bk tree: make mrproper; make uninstall; >patch the code here<; make; ./install.sh. More instructions to follow.

Comments/feedback related to these patches are very welcome. Note that I will not be able to read my email from April 1st to 11th.  If anyone has any quick questions I will try to answer them before I leave; otherwise, please look through the code at your convenience and let us discuss details once I am back.  (Note that the code is still "under development" -- for example, work continues on save/restore support & on revoking resources to enable policy changes at run-time, as well as moving the enforced policy from a hard-coded parameter to a compile-time option).

Kindest Regards

Reiner

Signed-off-by: Reiner Sailer





__________________________________________________________
Reiner Sailer, Research Staff Member, Secure Systems Department
IBM T J Watson Research Ctr, 19 Skyline Drive, Hawthorne NY 10532
Phone: 914 784 6280  (t/l 863)  Fax: 914 784 6205, sailer@xxxxxxxxxx  
http://www.research.ibm.com/people/s/sailer/

Attachment: shype_4_xeno-unstable.bk_v0.2_xen.diff
Description: Binary data

Attachment: shype_4_xeno-unstable.bk_v0.2_tools.diff
Description: Binary data

Attachment: shype_4_xeno-unstable.bk_v0.2_sparse.diff
Description: Binary data

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