All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Ambrose <Vikram.Ambrose@windriver.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux@tycho.nsa.gov,
	"Christopher J. PeBenito" <cpebenito@tresys.com>,
	Joshua Brindle <jbrindle@tresys.com>,
	Chad Sellers <csellers@tresys.com>,
	Eric Paris <eparis@parisplace.org>
Subject: Re: SELinux Bootstrap - without chroot
Date: Mon, 16 Jun 2008 17:35:15 -0400	[thread overview]
Message-ID: <4856DC93.5000909@windriver.com> (raw)
In-Reply-To: <1213640369.15523.152.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Mon, 2008-06-16 at 13:56 -0400, Vikram Ambrose wrote:
>   
>> Stephen Smalley wrote:
>>     
>>> Note that they get installed to $DESTDIR/usr/share/selinux/$SELINUXTYPE
>>> by make install.  In Fedora, they are packaged as such, then when you
>>> install the package on the target host, they are unpacked
>>> to /usr/share/selinux/$SELINUXTYPE by the package manager and then a %
>>> post scriptlet runs semodule on them to install them under /etc/selinux
>>> and load them.
>>>
>>>   
>>>       
>> In Fedora, does anaconda chroot into the sysroot and call semodule 
>> during installation?
>>     
>
> Some combination of anaconda and rpm, yes.  semodule runs from a %post
> scriptlet in the selinux-policy-targeted package at package install
> time.
>
>   
>>> Options for you might include:
>>> 1) Run semodule_link and semodule_expand at build time to link and
>>> expand the modules to a kernel policy up front.  Then you can just put
>>> the files into place without running semodule later.
>>>   
>>>       
>> I will investigate this option further, thank you.
>>     
>
> Ok.  You can see an example of it in the 'make validate' target,
> although that is just to check that they will link and expand
> successfully; it isn't used to install the policy normally and likely
> doesn't keep the final result around.
>
>   
I am getting a bit confused between "modular" and "monolithic", in both 
cases a policy.X file is needed to load the policy into the kernel, right?

and in the modular case, the policy.X file simply points to the various 
.pp files and in the monolithic case everything is in the policy.X file? 
Analogous to shared library and static library link (modular/monolithic)?


-- 
Vikram Ambrose | Linux Products Division | WindRiver Corporation


--
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:[~2008-06-16 21:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 16:49 SELinux Bootstrap - without chroot Vikram Ambrose
2008-06-16 17:57 ` Stephen Smalley
2008-06-16 17:56   ` Vikram Ambrose
2008-06-16 18:19     ` Stephen Smalley
2008-06-16 21:35       ` Vikram Ambrose [this message]
2008-06-17 12:38         ` Stephen Smalley
2008-06-17 13:52           ` Vikram Ambrose
2008-06-17 14:27             ` Stephen Smalley
2008-06-17 14:52               ` Vikram Ambrose
2008-06-17 16:43                 ` Stephen Smalley
2008-06-17 20:12                   ` Vikram Ambrose
2008-06-17 20:41                     ` Stephen Smalley

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=4856DC93.5000909@windriver.com \
    --to=vikram.ambrose@windriver.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=cpebenito@tresys.com \
    --cc=csellers@tresys.com \
    --cc=eparis@parisplace.org \
    --cc=jbrindle@tresys.com \
    --cc=sds@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.