[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xense-devel] [PATCH] ACM: adding C-support for policy translation and labeling support for domains
- To: Reiner Sailer <sailer@xxxxxxxxxx>
- From: David Palmer <dwpalmer.xense@xxxxxxxxx>
- Date: Wed, 31 Aug 2005 16:11:44 -0700
- Cc: Ray Valdez <rvaldez@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>, xense-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Wed, 31 Aug 2005 23:09:36 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=jsjK/M5vl4cqdOqU09ME8391voRWfepPIUKdggx8Apgs/GyAsaAokXEtxm3CDLuge/rnEIDCSQefaQ++jO1F5tx+vFRKhEcAj0Z5gVUcA1XCT/biLvL7QpPQkV+kGDwm0qtwLdoGu6hOo2Vu+wvnV0BO+ar/sht9c62RM0ukQFA=
- List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>
I'm not clear why the getssid() needs to be introduced. Isn't the
problem better solved by introducing new object
managers? With the getssid(), the code must know about the
specific policy, making the policy less amenable to adjustment as
problems are discovered. Wouldn't it be better for the
domains to provide object managers? This would allow the STE
policy to
make statements about those new objects. The code can be policy
neutral by strictly following the decisions of the security
server. Wouldn't this make it easier to revoke policies and
update them without having to change the code and patch?
Dave
On 8/18/05, Reiner Sailer <sailer@xxxxxxxxxx> wrote:
This patch:
* adds a C-based security policy translation
tool to Xen (secpol_xml2bin) and removes the current Java
security policy translator (Java dependencies).
The C-based tool integrates into the Xen source tree build
and install (using gnome libxml2 for
XML parsing). See install.txt.
* introduces security labels and related
tools. Users can now use semantic-rich label names to put security-tags
on domains. See example.txt, policy.txt.
* moves the security configuration (currently
ACM_USE_SECURITY_POLICY) from xen/Rules.mk
into a separate top-level Security.mk
file (it is needed by the tools/security and xen/acm).
Both xen/acm and tools/security are
built during the Xen build process only if ACM_USE_SECURITY_POLICY
is not ACM_NULL_POLICY (which is the
default setting).
Comments welcome!
Note: We are currently preparing a patch
that introduces a new ACM command (getssid) to retrieve the security types
of a running domain. This command is
enables domain-internal enforcement functions based on the ACM security
policy.
Thanks
Reiner
Signed-off-by Reiner Sailer <sailer@xxxxxxxxxx>
Signed-off by Stefan Berger <stefanb@xxxxxxxxxx>
Signed-off by Ray Valdez <rvaldez@xxxxxxxxxx>
_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel
_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel
|
