All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Ambrose <Vikram.Ambrose@windriver.com>
To: SELinux@tycho.nsa.gov
Subject: SELinux Bootstrap - without chroot
Date: Mon, 16 Jun 2008 12:49:14 -0400	[thread overview]
Message-ID: <4856998A.1020606@windriver.com> (raw)

Without a chroot environment, How does one go about building/installing, 
well basically the entire process including the bootstrap in a self 
contained build directory?

I have been playing with refpolicy. And from what I have learned, 
refpolicy allows you to define a LOCAL_ROOT but none of the selinux 
userspace tools allow you to make use of a folder other than 
/etc/selinux as that path is hard coded in all the source files.

In essence I want to know how to build a policy and tar it up, extract 
it into a target rootfs and simply call "load_policy" to use it.

thanks.

-- 
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 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 16:49 Vikram Ambrose [this message]
2008-06-16 17:57 ` SELinux Bootstrap - without chroot Stephen Smalley
2008-06-16 17:56   ` Vikram Ambrose
2008-06-16 18:19     ` Stephen Smalley
2008-06-16 21:35       ` Vikram Ambrose
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=4856998A.1020606@windriver.com \
    --to=vikram.ambrose@windriver.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.