SELinux-Refpolicy Archive on lore.kernel.org
 help / Atom feed
From: "Sugar, David" <dsugar@tresys.com>
To: "selinux-refpolicy@vger.kernel.org"  <selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH 2/3] Changes to support plymouth working in enforcing
Date: Wed, 17 Apr 2019 02:51:38 +0000
Message-ID: <63c4a09b-5b6b-d364-9d7d-5de069c5b9c5@tresys.com> (raw)
In-Reply-To: <20190413075144.GA5901@brutus.lan>



On 4/13/19 3:51 AM, Dominick Grift wrote:
> 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.
> 
And even if I was able to get changes into plymouth, I'm not sure how 
long it would take to get those merged into RHEL.  Can this be merged as 
is or are there some suggestions to update this?

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

  reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 19:39 [PATCH 0/3] Resolve issues with plymouth " 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
2019-04-17  2:51           ` Sugar, David [this message]
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 publically 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=63c4a09b-5b6b-d364-9d7d-5de069c5b9c5@tresys.com \
    --to=dsugar@tresys.com \
    --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

SELinux-Refpolicy Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/selinux-refpolicy/0 selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ https://lore.kernel.org/selinux-refpolicy \
		selinux-refpolicy@vger.kernel.org selinux-refpolicy@archiver.kernel.org
	public-inbox-index selinux-refpolicy


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.selinux-refpolicy


AGPL code for this site: git clone https://public-inbox.org/ public-inbox