From mboxrd@z Thu Jan 1 00:00:00 1970 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=-19.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1, USER_IN_DEF_DKIM_WL 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 D2F6EC433DB for ; Tue, 12 Jan 2021 14:19:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7FAB22311C for ; Tue, 12 Jan 2021 14:19:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729278AbhALOTY (ORCPT ); Tue, 12 Jan 2021 09:19:24 -0500 Received: from linux.microsoft.com ([13.77.154.182]:60978 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729199AbhALOTY (ORCPT ); Tue, 12 Jan 2021 09:19:24 -0500 Received: from localhost.localdomain (c-73-172-233-15.hsd1.md.comcast.net [73.172.233.15]) by linux.microsoft.com (Postfix) with ESMTPSA id BE55420B6C40; Tue, 12 Jan 2021 06:18:43 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com BE55420B6C40 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1610461124; bh=NQwzfXWDD/Yy8D3qtWBuuQZhjGxL8VBB6pV71ekoDrU=; h=Subject:From:To:References:Date:In-Reply-To:From; b=XdTGL7vEXxlguYAh2/+e4UMqifKt6hgjDKiQdH303QH0ENEQ5Ex2055F9bHNQrTJU wwOmUc95M8j6DTdcADKrTWVTYZlPysBQoqUDjsyseu0Bb22AHH9PSN8Xt4lY79jMsY huP4jxwhtsz2Ij5HmvZNnnssPAGkZe4+UCLZR9BY= Subject: Re: [PATCH] strict patches From: Daniel Burgener To: Russell Coker , selinux-refpolicy@vger.kernel.org References: <40e12eb0-782d-2a73-3cd9-a2e2cca2d916@linux.microsoft.com> Message-ID: <9e38ca3b-cc76-2b52-dcd5-01c661cdcfcd@linux.microsoft.com> Date: Tue, 12 Jan 2021 09:18:42 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <40e12eb0-782d-2a73-3cd9-a2e2cca2d916@linux.microsoft.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org On 1/12/21 9:15 AM, Daniel Burgener wrote: > On 1/12/21 5:31 AM, Russell Coker wrote: >> Also remove the systemd_analyze_t domain which >> does no good. > > I proposed this same change on github: > https://github.com/SELinuxProject/refpolicy/pull/321 > > The consensus there was that having a separate domain for this access > would add value and the better direction would be to flesh out the > permissions it needs.  We have a bit of a starting point locally on > that.  I'm not sure what shape it's in with regard to upstreaming, but > I'll talk to the developer who worked on it. > > -Daniel My mistake - looks like we ended up granting the needed permissions to the parent domain in our environment, so I don't have any systemd-analyze policy available for upstream.  I still might try developing some, but I don't expect that I'm likely to get to it soon. -Daniel