Bug 1667276
Summary: | Selinux - bunch of "avc: denied" messages in logs on rhel8. | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
Component: | rhosp-director | Assignee: | Cédric Jeanneret <cjeanner> |
Status: | CLOSED WORKSFORME | QA Contact: | Gurenko Alex <agurenko> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 15.0 (Stein) | CC: | cjeanner, dbecker, dprince, mburns, morazi, sasha |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-29 14:21:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexander Chuzhoy
2019-01-17 23:06:13 UTC
Hello! So, the relabelto will stay - it doesn't block the copy of the backup/config things, and allowing them is a security breach we don't want to see. The connectto might be OK, although I'd like to know a bit more about that: any idea of the container(s) wantin to connect? Apparently, some "sudo" command from within a container are issued.. ? The setexec might be OK, I think it might be accepted as an `openstack-selinux' patch Finally, the write from sss_cache needs some investigation in order to check what's going on in there (like the connectto). I'll check with the security team and openstack-selinux maintainers for patches, acceptable changes and the like. I agree with Cédric. Lets not let the container be able to relabel files. Quick update: the "net_broadcast" should be taken care in openstack-selinux with https://github.com/redhat-openstack/openstack-selinux/pull/22 Another quick update: the AVC regarding sss are known, and apparently fixed with selinux-policy-3.14.1-48.el8 (see https://bugzilla.redhat.com/show_bug.cgi?id=1651531) Also, this one is weird: type=AVC msg=audit(1547766061.463:5904): avc: denied { setexec } for pid=208019 comm="crond" scontext=system_u:system_r:container_t:s0:c560,c816 tcontext=system_u:system_r:container_t:s0:c560,c816 tclass=process permissive=0 According to https://github.com/containers/container-selinux/blob/master/container.te#L663 this is allowed... OK, container-selinux package is probably too old: https://github.com/containers/container-selinux/commit/de8020d4441bbd80e2f2c1646a34d60a15c3c270 I was the one adding this permission 3 months ago. You might still be using a pretty old podman as well, care to share its version (podman --version or, even better, podman --info)? podman version 0.10.1.3 Hey, As discussed: pretty old versions, we target podman 1.x on rhel8. There's just the "relabelto" which is "valid", but as stated, we won't add new policy for this one. It's tracked in LP https://bugs.launchpad.net/tripleo/+bug/1813313 (I'm still digging the reasons). It doesn't prevent the deploy or use. Cheers, C. |