Skip to contentSkip to conversation

deficiency in logging in enforcing mode

DISCUSSION Russell Coker 2 participants 2 messages May 29, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

It seems that messages such as the following are not logged in enforcing mode, only in permissive mode. So if I can't execute a program because it's got a domain_auto_trans rule specifying that it should transition to a domain that is not permitted for the role I'm in then it just doesn't get executed with no reason being logged!

This makes it difficult to determine why something is not working if you make a mistake in the role definitions, and limits the use of roles. Can this be fixed in the next version?

security_compute_sid: invalid context rjc:sysadm_r:apmd_t for scontext=rjc:sysadm_r:sysadm_t tcontext=system_u:object_r:apmd_exec_t tclass=process

Signature · 3 lines
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line

From field.

--
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 6 lines · Russell Coker

It seems that messages such as the following are not logged in enforcing mode, only in permissive mode. So if I can't execute a program because it's got a domain_auto_trans rule specifying that it should transition to a domain that is not permitted for the role I'm in then it just doesn't get executed with no reason being logged!

Quoted 7 lines

This makes it difficult to determine why something is not working if you make a mistake in the role definitions, and limits the use of roles. Can this be fixed in the next version?

security_compute_sid: invalid context rjc:sysadm_r:apmd_t for scontext=rjc:sysadm_r:sysadm_t tcontext=system_u:object_r:apmd_exec_t tclass=process

The only reason to log such a message is to help people in debugging policies, and permissive mode is suitable for that purpose. In contrast, the AVC auditing is useful both in debugging policies and in providing an audit log. The disabling of the security_compute_sid logging when in enforcing mode is intentional.

If we were to enable security_compute_sid logging in enforcing mode, we would also need to apply a rate limit mechanism, as with the AVC auditing, in order to guard against flooding.

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