Bug 747653
Summary: | SELinux is preventing systemd-tty-ask from 'read' accesses on the file ask.lIE7zh. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul W. Frields <stickster> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | awilliam, dominick.grift, dwalsh, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:d2e195b2fe8a19ecc02d244f36b84d277e9a09baa3b35df50fc3d9a0564ac63e AcceptedBlocker | ||
Fixed In Version: | selinux-policy-3.10.0-45.1.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-10-25 03:34:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 713568 |
Description
Paul W. Frields
2011-10-20 15:59:38 UTC
Fixed in selinux-policy-3.10.0-45.fc16 Suggesting for blocker list even though it should be fixed forthwith. I agree. In that case, please submit an selinux-policy update with the fix included. What's the impact of this? We need to know that for blocker purposes. Also what triggers it? Would you see it simply by installing then booting F16? Ah, from http://paul.frields.org/2011/10/20/note-for-fedora-16-early-testers/ , I see the impact is on unlocking encrypted filesystems at boot. +1 blocker in that case. Criterion is "The installer must be able to complete an installation using the entire disk, existing free space, or existing Linux partitions methods, with or without encryption or LVM enabled " combined with "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention." Paul, in future, it helps when proposing a blocker if you can ensure there's a visible explanation of the actual practical consequence of the bug, and ideally if you can propose a criterion it infringes. Thanks! selinux-policy-3.10.0-45.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/FEDORA-2011-14618 -45 doesn't seem to fix this for me. I went straight from -40 to -45, rebooted, and got no passphrase entry dialog. Booting with enforcing=0 caused the dialog to pop up and boot to succeed. [ 9.606776] type=1400 audit(1319138147.125:3): avc: denied { write } for pid=873 comm="systemd-tty-ask" name="sck.17020271070667803910" dev=tmpfs ino=13422 scontext=system_u:system_r:systemd_passwd_agent_t:s0 tcontext=system_u:object_r:systemd_passwd_var_run_t:s0 tclass=sock_file that's with -45. I just checked in a fix for this. Fixed in selinux-policy-3.10.0-45.1.fc16 Confirmed, 45.1 fixes it. I edited the update with this release. re: Comment #5, my bad, sorry guys. The good news is 45.1 does fix the problem; I provided bodhi karma last night and it looked like the critpath update was approved. Discussed at 2011-10-21 blocker review meeting, accepted as a blocker per criterion mentioned in comment #5. Package selinux-policy-3.10.0-45.1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-45.1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14618 then log in and leave karma (feedback). selinux-policy-3.10.0-45.1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |