• 1
Please download selinux-policy-3.5.13-34.fc10 from koji to see if that solves your problem.

THe policy was not allowing staff_t->user_t transitions.

Thank you for your assistance. This weekend, I tried installing selinux-policy-3.5.13-34.fc10 and selinux-policy-targeted-3.5.13-34.fc10. It didn't change the behavior of sudo. It is still failing with the same errors when trying to transition from staff_t->user_t.

BTW, whether you successfully sudo with the same context or unsuccessfully sudo trying to transition from staff_t to user_t, the same four entries are in audit.log all with res=success. They are CRED_ACQ, USER_START, USER_END, and USER_CMD. There are no failures in audit.log

Looks like a bug in sudo, this does not work in permissive mode, if I remove the changing of the context it works.

The problem is sudo is changing the real and effective user id before it tries to set the terminal context, so it basically drops privs before running the SELinux code. And the user is not allowed to modify the attributes of the terminal.

Thank you very much. I'll keep an eye out for an update to sudo that fixes this. But, shouldn't it be trying to set the tty context to staff_u:object_r:user_tty_device_t instead of staff_u:user_r:user_t? Just curious.


it is trying to set the context to staff_u:object_r:user_tty_device_t. staff_u:user_r:user_t is the context of the process.

  • 1
?

Log in