| Summary: | SELinux is preventing /bin/systemd-tty-ask-password-agent from read access on the fifo_file 136:1. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ian Pilcher <ipilcher> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | dwalsh, johannbg, lpoetter, metherid, mgrepl, mschmidt, notting, plautrba |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-31 19:55:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ian Pilcher
2011-03-15 14:21:55 UTC
I guess the question then is why didn't systemd label it correctly when it created the pipe? Or is this pipe created in the kernel? This is used by the tty and wall password agents to signal each other that where a tty agent is running a wall message doesn't need to be printed. Background: when a file system that needs to be decrypted needs a password we normally print a wall message to all logged in users informing them that the system is waiting for that, and he shall call a specific tool to enter it. However, while the user calls "systemctl" this tool will ask for the passwords anyway and hence it would be ugly if the wall message would be printed over the password prompt. We use the pipe which is named after the major/minor of the tty as flag file to communicate from systemctl (or more precisely the tty agent) to the wall agent that the tty doesn't need wall messages. We never actually send anything over the pipe. All we do is use the nice pipe behaviour that as long as nobody reads from a pipe writing to it will block/cause a failure as reliable lock. the tty agent process hence needs read access to those pipes, the wall agent write access, all though they never actually read or write to or from them. We just want the nice open() behaviour. Since these are now under /run I am going to close. |