Received-SPF: pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: Are we on the wrong track?
To:     bauen1 <j2468h@googlemail.com>
Cc:     selinux-refpolicy@vger.kernel.org
References: <3243717.6S2XvbbdUs@liv>
 <578d7c7c-cb41-b224-2758-144aa9b5c1ad@ieee.org> <2469682.qIgoumM3a6@liv>
 <ca477891-8d50-2681-d17e-7a358146dde9@gmail.com>
 <f8f1e127-bab5-b67a-32c7-4f4d3abe2efc@ieee.org>
 <03249797-9067-34f1-c4ec-39f163fb9042@gmail.com>
From:   Chris PeBenito <pebenito@ieee.org>
Message-ID: <63612ad4-967b-18b0-2667-1f6b74c19e5d@ieee.org>
Date:   Tue, 21 Jul 2020 10:22:46 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <03249797-9067-34f1-c4ec-39f163fb9042@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: selinux-refpolicy-owner@vger.kernel.org
Precedence: bulk

On 7/19/20 3:29 PM, bauen1 wrote:
> On 7/16/20 4:09 PM, Chris PeBenito wrote:
>> This behavior depends on the type of the file. If you end up with a staff_u:object_r:etc_t context, the user separations don't apply since this is not a user file.
> 
> I'll have to take another look at it then.
> 
>> We used to have role based separations but it was encoded into the TE rules and generated an enormous amount of rule duplication.  There are some remaining examples of this, e.g. in the su and sudo policies (staff_su_t, sysadm_su_t).
> 
> There are cases where these will still be necessary, mainly when type transitions to the user type are required, but some could be eliminated.

Right, there will always be needs like this. Which ones could be eliminated? I 
can't immediately think of an example.


>> When the default_* statements were implemented I started to reimplement the role-based separations using the role, but then I lost the work before I finished.  I don't think it is too involved, since it may be as simple copying the UBAC infrastructure and tweaking it to work on roles.
> 
> I've also worked on implementing RBAC and RBACSEP for refpolicy (A bit messy: https://github.com/bauen1/refpolicy/tree/rbac) . If this becomes a goal to implement, perhaps https://github.com/SELinuxProject/refpolicy/pull/203 could be merged first.

It's a goal, but it hasn't been a high enough priority for someone invest the 
time in it.

-- 
Chris PeBenito