Skip to contentSkip to conversation

default context files

DISCUSSION Frank Mayer 2 participants 2 messages Jul 19, 2002 – Jul 22, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

Is there a reason why the cron_context file has a specific type (cron_context_t) and the default_context file has the generic etc_t type? We're trying to give a domain the ability to write both context files, and it seems excessive for it to have the ability to modify all files with etc_t type. Frank

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 5 lines · Frank Mayer

Is there a reason why the cron_context file has a specific type (cron_context_t) and the default_context file has the generic etc_t type? We're trying to give a domain the ability to write both context files, and it seems excessive for it to have the ability to modify all files with etc_t type. Frank

We haven't previously needed to grant selective write access to the default_context (or default_type) files, so it hasn't been necessary to have a separate type. MITRE defined a separate type for cron_context when they worked on the crond policy. Feel free to submit patches to the policy and file_contexts configurations to provide separate types for the default_context/type files.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.