Re: rawhide targeted vs. refpolicy rpm

[Ivan Gyurdiev <ivg2@cornell.edu>]

>
>> I am very confused..
>>
>> 1. The reason we designate a role as a "default" role is to get the 
>> labeling prefix. If we already have the labeling prefix, why do we still 
>> want to keep a "default" role around?
>>
>> 2. The labeling prefix has so far been tied to the user (map is 
>> seuser->user->(fixed) role -> labeing prefix). Now you're saying the 
>> login context should play a role in determining the labeling prefix? How 
>> would this work? Which login context from default_contexts should be used?
>>     
>
> Good point.   Let's just add a user->labelingprefix mapping and drop out
> defrole altogether then. 

One thing I am still not clear about is why we need a labeling prefix 
that's not related to a role.. how is targeted using the system role, 
and labeling things with the user prefix? Isn't the whole point of the 
labeling prefix to prevent that type of thing (cross-role communication).

Secondly, maybe we should look at the larger problem of why rbac doesn't 
work, and do something about it. Dan keeps telling me how rbac should be 
used to decide what programs users are allowed to run (depending on the 
role they're in). However, it doesn't work that way, because those 
programs store per-user files, and not per-role files. Selinux labels 
per-role files differently to prevent cross-role communication (at 
least, I assumed that's why), making the programs above not work. Is 
polyinstatiation going to address this problem? Ideas...



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.