From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Valdis.Kletnieks@vt.edu
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: list of permissions created by allow2audit: what do i do now?
Date: Tue, 18 May 2004 19:12:38 +0000 [thread overview]
Message-ID: <20040518191238.GO24917@lkcl.net> (raw)
In-Reply-To: <200405181625.i4IGPpIa012129@turing-police.cc.vt.edu>
On Tue, May 18, 2004 at 12:25:51PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 18 May 2004 13:02:44 -0000, Luke Kenneth Casson Leighton said:
>
> > given the number of errors i am seeing, and given that they won't
> > go away, perhaps there is some breakdown in communication between
> > the rules being in the policy.conf file and their application to
> > packages.
> >
> > for example, should i be doing a make relabel every time i add
> > some new rules?
>
> If you add new *rules* (allow foo_t bar_t...), you need to do a 'make reload'
> to get the new policy in place.
>
> If you add new file contexts, that requires a 'make relabel'.
>
> Remember : *.te changes -> make reload; *.fc changes -> make relabel.
ta.
> (If you're clever, you'll invoke setfiles by hand so you only relabel the
> file system(s) you need to - if all the stuff you need is on /usr, you don't
> need to redo all the other file systems...)
i'd noticed the technique employed by /etc/dpkg/postinst.d/selinux.
--
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:[~2004-05-18 19:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:40 list of permissions created by allow2audit: what do i do now? Luke Kenneth Casson Leighton
2004-05-18 12:40 ` Stephen Smalley
2004-05-18 13:02 ` Luke Kenneth Casson Leighton
2004-05-18 13:20 ` Stephen Smalley
2004-05-18 13:30 ` Stephen Smalley
2004-05-18 13:44 ` Stephen Smalley
2004-05-18 14:08 ` Luke Kenneth Casson Leighton
2004-05-18 15:11 ` Luke Kenneth Casson Leighton
2004-05-18 17:18 ` Stephen Smalley
2004-05-18 18:51 ` Luke Kenneth Casson Leighton
2004-05-18 19:54 ` Stephen Smalley
2004-05-18 20:18 ` Luke Kenneth Casson Leighton
2004-05-18 20:48 ` Russell Coker
2004-05-18 20:56 ` Luke Kenneth Casson Leighton
2004-05-18 19:51 ` Luke Kenneth Casson Leighton
2004-05-18 18:02 ` Russell Coker
2004-05-18 16:25 ` Valdis.Kletnieks
2004-05-18 19:12 ` Luke Kenneth Casson Leighton [this message]
2004-05-18 12:56 ` Luke Kenneth Casson Leighton
2004-05-18 13:14 ` Stephen Smalley
2004-05-18 15:19 ` Luke Kenneth Casson Leighton
2004-05-18 14:29 ` Russell Coker
2004-05-18 15:30 ` Luke Kenneth Casson Leighton
2004-05-18 14:01 ` Russell Coker
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=20040518191238.GO24917@lkcl.net \
--to=lkcl@lkcl.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=sds@epoch.ncsc.mil \
--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.