Subject: Re: [PATCH 3/3] Some items that seem they can be dontaudited for
 plymouthd
To:     Russell Coker <russell@coker.com.au>,
        "Sugar, David" <dsugar@tresys.com>
Cc:     "selinux-refpolicy@vger.kernel.org" 
        <selinux-refpolicy@vger.kernel.org>
References: <20190412193917.23886-1-dsugar@tresys.com>
 <20190412193917.23886-4-dsugar@tresys.com> <2319520.MOiGnKPAe5@liv>
From:   Chris PeBenito <pebenito@ieee.org>
Message-ID: <290b6376-a0c7-5dee-faff-4e5c9bb4a22d@ieee.org>
Date:   Sun, 14 Apr 2019 13:49:06 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <2319520.MOiGnKPAe5@liv>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: selinux-refpolicy-owner@vger.kernel.org
Precedence: bulk

On 4/12/19 10:33 PM, Russell Coker wrote:
> What is netlink_kobject_uevent_socket?  Do we have a place we can document
> this sort of thing to make it easier to determine whether access is required
> and what the implications of such access are?

The object class/perms list should be the place.  Right now its at 
https://selinuxproject.org/page/ObjectClassesPerms, though arguably it 
could move back to the refpolicy wiki not that it's on SELinux project 
GitHub.

-- 
Chris PeBenito