-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
v3.2: AVC with volumes #10522
Comments
@rhatdan PTAL |
It works with podman/test/system/030-run.bats Lines 602 to 604 in cbffddd
That test dates to 2021-01-21. I don't know why the test doesn't use |
This is also manifesting in a lot of the |
Problem is selinux-policy-34.9-1.fc34. Everything works fine with 34.8-1.fc34. Although this is not podman's fault, it's something we will need to deal with. |
This definitely looks like a valid error, and I have no idea why this worked in the past. We should definitely not allow users to mount random content into SELinux containers and have it work. Might be that the test systems previously did not have SELinux enabled, or had this /tmp/mypodman labeled correctly. I don't see this as a bug in podman, but with an error in the test. |
Some of these tests have exists and worked since 2020-01-16 (over a year). They worked until now, and broke with selinux-policy-34.9. I don't know why they worked or why they broke now. I'm just saying that we have a problem. Adding |
I think we fixed a security bug where podman containers were able to read user_tmp_t, so I think this is a good breakage, and we should fix the tests. |
Perhaps the older version had |
rpm -q --changelog selinux-policy
|
selinux-policy-34.9-1.fc34 breaks a behavior we've relied on since (at least) January 2020: - Revert "Add permission open to files_read_inherited_tmp_files() interface" That's probably the correct thing to do, but it breaks our existing tests. Solution: add ':Z' where needed. Tested on Ed's laptop, which has the offending selinux-policy as of 2021-05-31. Tests pass root and rootless. (I mention this because tests will obviously pass in CI, which has a much older selinux-policy). Also: add a 'podman rmi' for cleanup in one test, to avoid noise in test logs. Fixes: containers#10522 Signed-off-by: Ed Santiago <[email protected]>
This becomes a problem on hosts with upgraded policies. Ref: containers#10522 Also, made a small change to compose-test setup to reduce runtime. Signed-off-by: Chris Evich <[email protected]>
This becomes a problem on hosts with upgraded policies. Ref: containers#10522 Also, made a small change to compose-test setup to reduce runtime. Signed-off-by: Chris Evich <[email protected]>
Test
030-run.bats:podman run - check workdir
is failing in podman-3.2.0-0.2.rc3.fc34 under podman and podman-remote, root and rootless. It's an AVC. I don't know why CI didn't catch it.AVC is:
Easily reproduced on master @ cbffddd
container-selinux-2.162.1-3.fc34.noarch and also -2.162.2-1.fc34
The text was updated successfully, but these errors were encountered: