From: Ivan Gyurdiev <ivg2@cornell.edu>
To: sds@tycho.nsa.gov
Cc: Joshua Brindle <jbrindle@tresys.com>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
Daniel J Walsh <dwalsh@redhat.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: The sort algorithm is broken by the second rule, We need a way to pin these rules to the top.
Date: Fri, 31 Mar 2006 14:03:24 -0500 [thread overview]
Message-ID: <442D7CFC.8060704@cornell.edu> (raw)
In-Reply-To: <1143831151.17469.13.camel@moss-spartans.epoch.ncsc.mil>
> Sorting is presently only
> happening in the policy build process via the
> refpolicy/support/fc_sort.c helper program, so it is only applied to the
> file_context file provided by the policy itself, not to any local
> entries (whether created via semanage or not).
>
My mistake, I thought sorting was moved into matchpathcon at some point...
In that case the patch I sent shouldn't be necessary.
--
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:[~2006-03-31 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 14:50 The sort algorithm is broken by the second rule, We need a way to pin these rules to the top Daniel J Walsh
2006-03-31 14:57 ` Joshua Brindle
2006-03-31 15:01 ` Daniel J Walsh
2006-03-31 15:17 ` Joshua Brindle
2006-03-31 16:01 ` Christopher Ashworth
2006-03-31 19:27 ` Stephen Smalley
2006-03-31 15:17 ` Stephen Smalley
2006-03-31 15:20 ` Stephen Smalley
2006-03-31 15:10 ` Stephen Smalley
2006-03-31 16:35 ` Ivan Gyurdiev
2006-03-31 17:26 ` Ivan Gyurdiev
2006-04-02 11:32 ` Ivan Gyurdiev
2006-03-31 18:52 ` Stephen Smalley
2006-03-31 19:03 ` Ivan Gyurdiev [this message]
2006-03-31 19:15 ` Stephen Smalley
2006-03-31 19:18 ` Joshua Brindle
2006-03-31 19:32 ` Stephen Smalley
2006-04-02 17:55 ` Joshua Brindle
2006-04-02 20:13 ` Ivan Gyurdiev
2006-04-02 20:31 ` Joshua Brindle
2006-03-31 22:17 ` Ivan Gyurdiev
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=442D7CFC.8060704@cornell.edu \
--to=ivg2@cornell.edu \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=sds@tycho.nsa.gov \
--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.