From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: selinux@tycho.nsa.gov
Subject: SELinux with initramfs
Date: Sat, 14 Jan 2012 15:20:02 +0100 [thread overview]
Message-ID: <20120114142001.GA5632@siphos.be> (raw)
Hi guys,
I'm trying to get a system to boot up with initramfs (without the initramfs
all things work just fine, but we need to get initramfs supported) with
SELinux running in enforcing mode, and without relying on unconfined
domains.
However, it looks to be quite challenging.
An initramfs' /init will run in the kernel_t domain (and unconfined until
load_policy is called ?) but does quite a lot of activities before it can
even call load_policy (get /dev in shape, including starting udev, mounting
root file system, etc.) because load_policy needs access to the policy.26
file on the root file system.
But because all of this, udev doesn't run in the proper domain (also in
kernel_t), device entries are wrongly labeled (and relabeling fails because
kernel_t does not have relabel privileges) and the system just doesn't want
to boot.
Is it correct to say that load_policy should occur as soon as possible (even
before udev starts)? If so, does that mean than a SELinux-supporting
initramfs should actually include the policy.26 file in the initramfs?
Wkr,
Sven Vermeulen
--
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 reply other threads:[~2012-01-14 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 14:20 Sven Vermeulen [this message]
2012-01-14 14:34 ` SELinux with initramfs Sven Vermeulen
2012-01-14 15:46 ` Chris PeBenito
2012-01-16 14:46 ` Daniel J Walsh
2012-01-21 19:24 ` Sven Vermeulen
2012-01-23 18:16 ` Daniel J Walsh
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=20120114142001.GA5632@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.