From: James Morris <jmorris@namei.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
SELinux <selinux@tycho.nsa.gov>,
"David P. Quigley" <dpquigl@tycho.nsa.gov>
Subject: Re: [PATCH 1/1] selinux: add support for installing a dummy policy
Date: Sat, 23 Aug 2008 08:56:35 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.1.10.0808230852320.24779@tundra.namei.org> (raw)
In-Reply-To: <20080822193413.GA8401@us.ibm.com>
On Fri, 22 Aug 2008, Serge E. Hallyn wrote:
> In August 2006 I posted a patch to the selinux list generating a minimal
> SELinux policy. This week, David P. Quigley posted an updated version
> of that as a patch against the kernel. In addition to some fixes, also
> had nice logic for auto-installing the policy.
>
> I've gone ahead and hooked it into the kernel Makefile logic. The way I
> have it here, doing 'make scripts' ends up compiling 'mdp', after which
> you must
> cd scripts/selinux
> sh install_policy.sh
>
> That isn't as nice as being able to do
> make selinux_install
> the way David had it, but it avoids mucking with the top-level
> Makefile. Which is preferred?
I think leaving out of the top level makefile is preferred, as there are
no other subsystem targets there.
Please make sure 'make distclean' cleans up properly. These are
currently left behind:
# scripts/selinux/mdp/file_contexts
# scripts/selinux/mdp/policy.23
# scripts/selinux/mdp/policy.conf
Please also provide documentation on how to boot the system up with this
policy.
> + echo "no file contests file. Please run"
ITYM contexts :-)
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-08-22 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 19:34 Serge E. Hallyn
2008-08-22 22:56 ` James Morris [this message]
2008-08-23 2:38 ` Serge E. Hallyn
2008-08-25 9:12 ` James Morris
2008-08-25 12:16 ` Stephen Smalley
2008-08-25 12:10 ` Stephen Smalley
2008-08-26 19:16 ` Serge E. Hallyn
2008-08-25 14:56 ` David P. Quigley
2008-08-26 15:04 ` Daniel J Walsh
2008-08-26 15:54 ` David P. Quigley
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=alpine.LRH.1.10.0808230852320.24779@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dpquigl@tycho.nsa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
--cc=serue@us.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®