All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: "Christopher J. PeBenito" <pebenito@ieee.org>,
	Rahul Sandhu <nvraxn@posteo.uk>,
	selinux-refpolicy@vger.kernel.org
Subject: Re: RFC: earlyinit_t
Date: Fri, 19 Jun 2026 17:38:47 +1000	[thread overview]
Message-ID: <2563044.CQOukoFCf9@dojacat> (raw)
In-Reply-To: <DJCKEOR9NQBQ.2GLS510LOWSDQ@posteo.uk>

On Friday, 19 June 2026 09:30:55 AEST Rahul Sandhu wrote:
> I think the concern is less that and moreso when policy is loaded. Off
> the top of my head, an example I can think of was one system I saw from
> a little while back which had the policy binary in the initramfs itself
> and hence loaded it midway through initramfs' setup and the switchroot.

Who does that nowadays?

https://etbe.coker.com.au/2008/07/24/se-linux-policy-loading/

I've written about my past tests with initrd policy and why I decided that was 
a bad idea.

> Once policy is loaded however, I'm not aware of any _processes_ that do
> persist beyond the initramfs. On my system, both journald and udev end
> up re-exec'd for example.

Great!

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/




  reply	other threads:[~2026-06-19  7:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 14:34 RFC: earlyinit_t Rahul Sandhu
2026-06-18 15:22 ` Russell Coker
2026-06-18 17:18   ` Rahul Sandhu
2026-06-18 21:04     ` Christopher J. PeBenito
2026-06-18 23:30       ` Rahul Sandhu
2026-06-19  7:38         ` Russell Coker [this message]
2026-06-19  7:29     ` Russell Coker

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=2563044.CQOukoFCf9@dojacat \
    --to=russell@coker.com.au \
    --cc=nvraxn@posteo.uk \
    --cc=pebenito@ieee.org \
    --cc=selinux-refpolicy@vger.kernel.org \
    /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.