Skip to contentSkip to conversation

strange problem

DISCUSSION Russell Coker 2 participants 3 messages Oct 31, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

avc: denied { execute_no_trans } for pid=11872 exe=/bin/bash path=/usr/bin/tr dev=09:03 ino=459224 scontext=system_u:system_r:crack_t tcontext=system_u:object_r:unlabeled_t tclass=file

root@test:~# ls --context /usr/bin/tr
-rwxr-xr-x  root     root     system_u:object_r:bin_t          /usr/bin/tr
root@test:~#

The above is a problem that's happened twice to me now. This time it happened with all the SE patches applied, the previous time it happened without.

When I run "tr" from the command line it works!

So why is it being denied when run from crack_t?

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.
#1 lore raw
Quoted 7 lines · Russell Coker

avc: denied { execute_no_trans } for pid=11872 exe=/bin/bash path=/usr/bin/tr dev=09:03 ino=459224 scontext=system_u:system_r:crack_t tcontext=system_u:object_r:unlabeled_t tclass=file

root@test:~# ls --context /usr/bin/tr
-rwxr-xr-x  root     root     system_u:object_r:bin_t          /usr/bin/tr
root@test:~#
Quoted 6 lines

The above is a problem that's happened twice to me now. This time it happened with all the SE patches applied, the previous time it happened without.

When I run "tr" from the command line it works!

So why is it being denied when run from crack_t?

This is expected without the separate SELinux patch due to a gap in LSM, but should be addressed by the separate SELinux patch. Please verify that this happens with the SELinux patch applied (and not your hacked version of the patch, but the original one). Is this 2.4.19 or 2.5.44?

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

#2 lore raw
Quoted 8 lines · Stephen Smalley
Quoted 3 lines

When I run "tr" from the command line it works!

So why is it being denied when run from crack_t?

This is expected without the separate SELinux patch due to a gap in LSM, but should be addressed by the separate SELinux patch. Please verify that this happens with the SELinux patch applied (and not your hacked version of the patch, but the original one). Is this 2.4.19 or 2.5.44?

It's 2.4.19.

I just realised that it's using the kernel without the extra SE patch, not the one with the patch.

I was watching TV at the time I was building the new kernel and didn't want to reboot my TV in the middle of a show. After the show ended I forgot to reboot with the new kernel... :(

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.