From: Dominick Grift <dac.override@gmail.com>
To: Russell Coker <russell@coker.com.au>
Cc: "Sugar, David" <dsugar@tresys.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH 2/3] Changes to support plymouth working in enforcing
Date: Sat, 13 Apr 2019 09:51:44 +0200 [thread overview]
Message-ID: <20190413075144.GA5901@brutus.lan> (raw)
In-Reply-To: <10127256.WPnezCvjeA@xev>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
On Sat, Apr 13, 2019 at 02:24:45PM +1000, Russell Coker wrote:
> On Saturday, 13 April 2019 1:23:15 PM AEST Sugar, David wrote:
> > On 4/12/19 10:43 PM, Russell Coker wrote:
> >
> > > On Saturday, 13 April 2019 5:39:31 AM AEST Sugar, David wrote:
> > >
> > >> plymouth is started very early in the boot process. Looks
> > >> like before the SELinux policy is loaded so plymouthd is
> > >> running as kernel_t rather than plymouthd_t. Due to this
> > >> I needed to allow a few permissions on kernel_t to get
> > >> the system to boot.
> > >
> > >
> > > Could plymouth re-exec itself or do a dynamic domain transition to get
> > > the
> > > right domain?
> > >
> >
> >
> > I don't see a way in the plymouth.conf or other configuration file to
> > have plymouth re-exec.
>
> Probably need to hack the plymouth source.
Not sure if it is worth the trouble, plymouthd mainly runs in the initramfs.
There's a couple of left-overs when systemd loads policy but that is it AFAIK.
>
> --
> My Main Blog http://etbe.coker.com.au/
> My Documents Blog http://doc.coker.com.au/
>
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2019-04-13 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 19:39 [PATCH 0/3] Resolve issues with plymouth in enforcing Sugar, David
2019-04-12 19:39 ` [PATCH 1/3] Allow xdm (lightdm) execute plymouth Sugar, David
2019-04-17 2:49 ` Sugar, David
2019-04-23 22:31 ` Chris PeBenito
2019-04-12 19:39 ` [PATCH 2/3] Changes to support plymouth working in enforcing Sugar, David
2019-04-13 2:43 ` Russell Coker
2019-04-13 3:23 ` Sugar, David
2019-04-13 4:24 ` Russell Coker
2019-04-13 7:51 ` Dominick Grift [this message]
2019-04-17 2:51 ` Sugar, David
2019-04-23 22:31 ` Chris PeBenito
2019-04-12 19:39 ` [PATCH 3/3] Some items that seem they can be dontaudited for plymouthd Sugar, David
2019-04-13 2:33 ` Russell Coker
2019-04-13 3:26 ` Sugar, David
2019-04-13 4:24 ` Russell Coker
2019-04-13 7:54 ` Dominick Grift
2019-04-17 2:53 ` Sugar, David
2019-04-14 17:49 ` Chris PeBenito
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=20190413075144.GA5901@brutus.lan \
--to=dac.override@gmail.com \
--cc=dsugar@tresys.com \
--cc=russell@coker.com.au \
--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.