All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Ron Kuris <rk@unify.com>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: file context ordering
Date: Fri, 29 Jul 2005 14:02:03 -0400	[thread overview]
Message-ID: <1122660123.20983.58.camel@sgc> (raw)
In-Reply-To: <42E946ED.2050705@unify.com>

On Thu, 2005-07-28 at 13:58 -0700, Ron Kuris wrote:
> My suggestion:
> 
> Use M4 diversions to raise the priority of the more important rules.
> M4 will output diverted text at the end of the script, and you can
> prioritize each section this way.
> 
> This worked perfectly for me when I had a similar problem:
> 
> divert(3)
> [ insert selinux rules here ]
> divert(0)
> 
> The rules between the diverts will be output at the end, in order by
> the diversion number (in this case, 3).

Well this is definitely an interesting solution.  The problem is that it
doesn't apply to the loadable policy modules, since the file contexts in
a module don't have m4.  Preserving m4 into the modules, and having
semodule run m4 to reconstruct file_contexts is probably a bad idea.
Adding a weight to specs, which is what Steve suggested, would be more
general than leveraging m4.

-- 
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.

  reply	other threads:[~2005-07-29 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 19:16 file context ordering Christopher J. PeBenito
2005-07-28 20:58 ` Ron Kuris
2005-07-29 18:02   ` Christopher J. PeBenito [this message]
2005-07-29 18:53     ` Ron Kuris
2005-07-29 19:26       ` Christopher J. PeBenito
2005-07-29 10:26 ` Daniel J Walsh
2005-07-29 19:30   ` Christopher J. PeBenito
2005-07-29 12:44 ` Stephen Smalley
2005-07-29 20:09   ` 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=1122660123.20983.58.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=rk@unify.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.