From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Klaus Weidner <klaus@atsec.com>
Cc: dwalsh@redhat.com, sgrubb@redhat.com,
SELinux Mail List <selinux@tycho.nsa.gov>,
joe@nall.com
Subject: Re: MLS directory write constraints
Date: Fri, 24 Aug 2007 14:10:44 +0000 [thread overview]
Message-ID: <1187964644.13874.151.camel@gorn> (raw)
In-Reply-To: <20070823230519.GC23508@w-m-p.com>
On Thu, 2007-08-23 at 18:05 -0500, Klaus Weidner wrote:
> On Tue, Aug 21, 2007 at 09:10:23AM -0400, Christopher J. PeBenito
> wrote:
> > I see that the constraints are different in the 2.4.6-67 LSPP policy.
> > Is this the final one? I want to make sure that the LSPP policy changes
> > have been integrated upstream.
>
> selinux-policy-2.4.6-67.el5 is the evaluated version, that's the one that
> is known to match LSPP requirements. The version in the older thread that
> I linked to wasn't final yet, we had made some minor modifications last
> year to get to the final version. Please use the
> selinux-policy-2.4.6-67.el5 constraints for upstream if possible.
I have updated the refpolicy constraints with the above policy's
constraints.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
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.
next prev parent reply other threads:[~2007-08-24 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 12:34 MLS directory write constraints Christopher J. PeBenito
2007-08-20 20:52 ` Klaus Weidner
2007-08-21 13:10 ` Christopher J. PeBenito
2007-08-23 23:05 ` Klaus Weidner
2007-08-24 14:10 ` Christopher J. PeBenito [this message]
2007-08-20 21:02 ` Klaus Weidner
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=1187964644.13874.151.camel@gorn \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=joe@nall.com \
--cc=klaus@atsec.com \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@redhat.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.