the new default_contexts file
The idea of having key-value pairs where the key is the partial context of the daemon is good.
However only being able to specify an order is not good.
I would like to be able to have two users, user "a" gets user_r:user_t by default while user "b" gets second_r:second_t by default even though both users are authorised for both roles.
Signature · 10 lines
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 8 lines · Russell Coker
The idea of having key-value pairs where the key is the partial context of the daemon is good.
However only being able to specify an order is not good.
I would like to be able to have two users, user "a" gets user_r:user_t by default while user "b" gets second_r:second_t by default even though both users are authorised for both roles.
This can be customized on a per-user basis by the user via a $HOME/.default_contexts file. Same syntax as the main configuration file, and it takes precedence.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 6 lines · Stephen Smalley
Quoted 5 lines · Russell Coker
The idea of having key-value pairs where the key is the partial context of the daemon is good.
However only being able to specify an order is not good.
Quoted 7 lines
Quoted 3 lines
I would like to be able to have two users, user "a" gets user_r:user_t by default while user "b" gets second_r:second_t by default even though both users are authorised for both roles.
This can be customized on a per-user basis by the user via a $HOME/.default_contexts file. Same syntax as the main configuration file, and it takes precedence.
OK. Should we define a new type for the default_contexts file then and allow the various login programs read access?
Signature · 10 lines
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.