-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs found by SELinux #5214
Comments
Can you paste full relevant messages? As for .pyc files, which exactly? I see those:
|
There are missing |
Presumably fixed by QubesOS/qubes-core-qrexec@0516ffc, closing. |
The change you linked is only at the dom0 side, so it's unlikely fixing any of those. |
This issue is being closed because:
If anyone believes that this issue should be reopened, please leave a comment saying so. |
Qubes OS version:
Qubes release 4.0 (R4.0)
Affected component(s) or functionality:
Probably multiple. Bugs have been found in qrexec, qubes-firewall, and others so far.
Steps to reproduce the behavior:
Run with SELinux in strict enforcing mode and start writing SELinux policies.
Expected or desired behavior:
qrexec-agent
doesn’t leak a Xen FD and a TTY FD to processes spawned by PAM.qubes-firewall
ships with.pyc
files in the RPM package.udevadm
is not run except usingsudo
.Actual behavior:
qrexec-agent
leaks a Xen FD and a TTY FD to processes spawned by PAM.qubes-firewall
doesn’t ship with.pyc
files in the RPM package.udevadm
is run withoutsudo
.General notes:
These show up as AVC denials. In the first case,
namespace_init_t
was passed FDs belonging to Xen and a TTY, which SELinux (correctly) blocked. In the second case,init_t
was trying to write compiled Python bytecode, which was also blocked. The third and forth cases are because on strict SELinux systems, administrative users such asuser
log in asstaff_u:staff_r:staff_t:s0-s0:c0.c1023
by default. This does not grant them permission to runudevadm
, but usingsudo
, they can transition tostaff_u:sysadm_r:sysadm_t:s0-s0:c0.c1023
, which does have the needed permissions.I have consulted the following relevant documentation:
I am aware of the following related, non-duplicate issues:
#4329, #4278, #4279
The text was updated successfully, but these errors were encountered: