From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Erich Schubert <erich@debian.org>
Cc: sds@tycho.nsa.gov, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: How can modular policy ever have worked? [patch]
Date: Mon, 27 Mar 2006 10:48:00 -0500 [thread overview]
Message-ID: <1143474480.3962.110.camel@sgc> (raw)
In-Reply-To: <1143331040.6084.15.camel@wintermute.xmldesign.de>
On Sun, 2006-03-26 at 00:57 +0100, Erich Schubert wrote:
> Monolithic builds are broken AFAICT now, by the removal of the module
> name from the optional_policy statement... that way, the only optional
> policy you could maybe still build is the one containing all modules.
> When I downgrade policy/support/loadable_module.spt to the version with
> my original patch only, and downgrade to my latest version prior to the
> optional_policy $1 removal, I can build a monolithic policy.
I committed a fix for Rules.monolithic to fix this; disabled modules
interfaces were not being expanded.
--
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:[~2006-03-27 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 14:20 How can modular policy ever have worked? [patch] Erich Schubert
2006-03-20 14:39 ` Stephen Smalley
2006-03-20 15:16 ` Erich Schubert
2006-03-20 16:00 ` Stephen Smalley
2006-03-25 23:57 ` Erich Schubert
2006-03-26 3:27 ` Joshua Brindle
2006-03-27 15:48 ` Christopher J. PeBenito [this message]
2006-03-20 16:57 ` Christopher J. PeBenito
2006-03-21 16:21 ` Christopher J. PeBenito
2006-03-23 20:12 ` Stephen Smalley
2006-03-20 15:25 ` 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=1143474480.3962.110.camel@sgc \
--to=cpebenito@tresys.com \
--cc=erich@debian.org \
--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.