Re: [ SEMANAGE ] Install seusers, rename some files

[Joshua Brindle <jbrindle@tresys.com>]

Ivan Gyurdiev wrote:
> 
>>>>
>>>> Yes, the seusers from /etc/selinux/strict/seusers have to get in the 
>>>> sandbox somehow...
>>>> I'm not entirely sure how, but I think Tresys has indicated that 
>>>> should occur through the APIs, rather than by copying it in.
>>>>
>>>> This is only necessary for migration...
>>>
>>>
>>> So, the question of what should be done about this still stands - 
>>> Joshua? From the point of view of libsemanage, a commit with a 
>>> missing seusers file should fail, because the store should hold the 
>>> authoritative copy of this file, and it's an important file, so it 
>>> seems like lack of it should be considered fatal...there should at 
>>> least be a default entry?
>>>
>> This is really saying that libsemanage knows what libselinux needs, 
>> which I'm not sure is appropriate, because libselinux might not be 
>> looking in seuser at all for mappings, it could be looking in LDAP.
> 
> I think they should be looking in the same place for modifications to 
> the seuser database to work as expected...
> I'm not sure what the meaning of : selinux_usersconf_path is, if 
> libselinux is looking in LDAP.

If LDAP is in use it should be authoritative, thus no local file. 
Clearly libselinux has no support for this yet so how it would be 
configured is unclear but I'm pretty sure LDAP should be the only source 
of mapping if it is in use.
> 
>> I don't think this is a fatal error during commit.
> 
> That can be changed...
> 


--
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.