All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Palmer <dwpalmer.xense@gmail.com>
To: Reiner Sailer <sailer@us.ibm.com>
Cc: Ray Valdez <rvaldez@us.ibm.com>,
	xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>,
	xense-devel@lists.xensource.com
Subject: Re: [Xense-devel] [PATCH] ACM: adding C-support for policy translation and labeling support for domains
Date: Wed, 31 Aug 2005 16:11:44 -0700	[thread overview]
Message-ID: <7d415b2805083116114dd152@mail.gmail.com> (raw)
In-Reply-To: <OF5D657B66.09315CCE-ON85257061.006EDD5B-85257061.00739A25@us.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 2225 bytes --]

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@us.ibm.com> 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 <http://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@us.ibm.com> 
> Signed-off by Stefan Berger <stefanb@us.ibm.com> 
> Signed-off by Ray Valdez <rvaldez@us.ibm.com> 
> 
> 
> _______________________________________________
> Xense-devel mailing list
> Xense-devel@lists.xensource.com
> http://lists.xensource.com/xense-devel
> 
> 
> 
>

[-- Attachment #1.2: Type: text/html, Size: 3975 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2005-08-31 23:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 21:02 [PATCH] ACM: adding C-support for policy translation and labeling support for domains Reiner Sailer
2005-08-31 23:11 ` David Palmer [this message]
2005-09-01  1:10   ` [Xense-devel] " Reiner Sailer
2005-09-01 18:34     ` David Palmer
2005-09-02  0:53       ` Reiner Sailer
     [not found] <7d415b2805090208471f99f452@mail.gmail.com>
2005-09-03  0:56 ` Reiner Sailer

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=7d415b2805083116114dd152@mail.gmail.com \
    --to=dwpalmer.xense@gmail.com \
    --cc=rvaldez@us.ibm.com \
    --cc=sailer@us.ibm.com \
    --cc=stefanb@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xense-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.