From: Serge Hallyn <serge.hallyn@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: targeted policy patch
Date: Thu, 19 May 2005 10:54:53 -0500 [thread overview]
Message-ID: <46ce702f05051908547025fbeb@mail.gmail.com> (raw)
In-Reply-To: <1116516582.7682.70.camel@moss-spartans.epoch.ncsc.mil>
Ah, ok, thanks.
What about the strict policy? Should I use that out of fc as well?
thanks,
-serge
On 5/19/05, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> On Thu, 2005-05-19 at 10:11 -0500, Serge Hallyn wrote:
> > Hi,
> >
> > In order to compile the sf.net targeted policy on a gentoo system with
> > the sf.net checkpolicy, I needed the following patch. It does several
> > small things, the last of which I expect is actually wrong, but at
> > least gets me a compiling policy:
> >
> > 1. preserves kernel.te to get its type declaration.
> > 2. fixes what i assume is a type, 'rm -rf domains/misc/used' instead of unused
> > 3. deletes setfiles.fc, since setfiles_exec_t is not declared in the policy
> > 4. adds the unrestricted attribute to the insmod_t domain. This stops
> > a conflict with the neverallow rule for ~signal -> unconfined_t.
>
> I'd advise using the targeted policy spec file from the Fedora Core CVS
> tree instead; we only update our spec files occasionally (e.g. prior to
> an updated release on nsa.gov) and they are only intended as examples.
> FC4 targeted policy includes many more domains.
>
> --
> Stephen Smalley
> National Security Agency
>
>
--
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:[~2005-05-19 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 15:11 targeted policy patch Serge Hallyn
2005-05-19 15:29 ` Stephen Smalley
2005-05-19 15:54 ` Serge Hallyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 12:42 Russell Coker
2006-12-08 13:39 ` Christopher J. PeBenito
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=46ce702f05051908547025fbeb@mail.gmail.com \
--to=serge.hallyn@gmail.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.