Skip to contentSkip to conversation

Security Context of nscd_socket

DISCUSSION Carsten Grohmann 2 participants 2 messages Apr 30, 2002 – May 1, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

Hi!

Yesterday I rebuild the file security context and after this the nscd did not work, because the security context of the file /var/run/.nscd_socket was set to var_run_t and not to nscd_var_run_t. The policy denied the unlink of this file.
A solution is to add follow line in the file file_context
/var/run/.nscd_socket system_u:object_r:nscd_var_run_t.

Could anybody add this to the source code?

Carsten

--
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 8 lines · Carsten Grohmann

Yesterday I rebuild the file security context and after this the nscd did not work, because the security context of the file /var/run/.nscd_socket was set to var_run_t and not to nscd_var_run_t. The policy denied the unlink of this file.
A solution is to add follow line in the file file_context
/var/run/.nscd_socket system_u:object_r:nscd_var_run_t.

Could anybody add this to the source code?

I'd suggest using <<none>> rather than a particular context for this type of object in file_contexts, since the socket file should be recreated each time by the daemon. Notice that such an entry exists for the pid 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.