Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93A6DC10F11 for ; Sat, 13 Apr 2019 04:24:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6090F21721 for ; Sat, 13 Apr 2019 04:24:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=coker.com.au header.i=@coker.com.au header.b="vio2XxnC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725776AbfDMEYv (ORCPT ); Sat, 13 Apr 2019 00:24:51 -0400 Received: from smtp.sws.net.au ([46.4.88.250]:57732 "EHLO smtp.sws.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725766AbfDMEYv (ORCPT ); Sat, 13 Apr 2019 00:24:51 -0400 Received: from xev.coker.com.au (localhost [127.0.0.1]) by smtp.sws.net.au (Postfix) with ESMTP id D2E46ED83; Sat, 13 Apr 2019 14:24:49 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coker.com.au; s=2008; t=1555129490; bh=dJPwosbGdQX46cWN904HA/DgdHTmm8SSyVSAqEOD89o=; l=822; h=From:To:Reply-To:Cc:Subject:Date:In-Reply-To:References:From; b=vio2XxnCgyb7dwMju6z3Dz3CIFnwPCsxIXn1yZC4DNG/p7eA6IYuVL6Sq0p5OF+r7 2NNj74IC0mZ/92G1pZGenQN12uj0553Jy3RObsNJyVS8eU0cwWTOzn0eq5QWt/pfWH nK5Psvj2vNK+u3MDgVk87rOEKge3SwDR8T8c/HFI= Received: by xev.coker.com.au (Postfix, from userid 1001) id 50F6CD0E775; Sat, 13 Apr 2019 14:24:45 +1000 (AEST) From: Russell Coker To: "Sugar, David" Reply-To: russell@coker.com.au Cc: "selinux-refpolicy@vger.kernel.org" Subject: Re: [PATCH 2/3] Changes to support plymouth working in enforcing Date: Sat, 13 Apr 2019 14:24:45 +1000 Message-ID: <10127256.WPnezCvjeA@xev> In-Reply-To: <3a5203d1-da92-4549-9a71-0055691e92be@tresys.com> References: <20190412193917.23886-1-dsugar@tresys.com> <2123404.RoTncvGGnz@liv> <3a5203d1-da92-4549-9a71-0055691e92be@tresys.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: selinux-refpolicy-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org 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. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/