All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Klaus Weidner <klaus@atsec.com>,
	Chad Hanson <chanson@TrustedCS.com>,
	Darrel Goeddel <dgoeddel@TrustedCS.com>,
	selinux@tycho.nsa.gov
Subject: Re: MLS policy constraints verification
Date: Fri, 17 Nov 2006 13:47:25 -0500	[thread overview]
Message-ID: <455E03BD.6020501@redhat.com> (raw)
In-Reply-To: <1163426567.18181.104.camel@sgc.columbia.tresys.com>

Christopher J. PeBenito wrote:
> On Sat, 2006-11-11 at 12:37 -0600, Klaus Weidner wrote:
>   
>> in the ongoing LSPP evaluation project, a review of the constraints
>> defined in "policy/mls" in the refpolicy turned up some suspicious
>> entries.
>>
>> Could people who wrote the policy or have opinions on what it's supposed
>> to be please comment?
>>     
>
> The constraints are almost all from the old example policy and were
> written by TCS since they did the enhanced MLS support.  Since I'm not
> familiar with the LSPP requirements, I can't speak to whether or not the
> MLS is strict enough to meet the requirements.  Chad, Darrel?
>
>   
Klous do you have a patch that you want applied to modify the constraints?

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2006-11-17 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 18:37 MLS policy constraints verification Klaus Weidner
2006-11-13 14:02 ` Christopher J. PeBenito
2006-11-17 18:47   ` Daniel J Walsh [this message]
2006-11-21 22:27 ` Darrel Goeddel

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=455E03BD.6020501@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=chanson@TrustedCS.com \
    --cc=cpebenito@tresys.com \
    --cc=dgoeddel@TrustedCS.com \
    --cc=klaus@atsec.com \
    --cc=selinux@tycho.nsa.gov \
    /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.