Bug 523271
Summary: | setroubleshoot: SELinux is preventing /usr/bin/kdm "execute" access on /sbin/grub. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Trenholme <PTrenholme> |
Component: | kdebase-workspace | Assignee: | Than Ngo <than> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | dwalsh, fedora, fedora, jkubin, jreznik, kevin, lorenzo, ltinkl, mgrepl, rdieter, smparrish, than |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:73767704a83813da10ec4a7e755d06c8e353f532ea91b235a2cc27e59fd0e665 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-15 16:17:12 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: |
Description
Peter Trenholme
2009-09-14 17:15:10 UTC
This, and two additional messages are generated, I believe, because KDE/KDM has a feature in the "Reboot" selection when quitting to, after specifying the boot loader, select the OS into which to reboot. Implementation of this feature require that KDE (or KDM) read and parse the boot configuration file and, when a reboot target is selected, that the process modify the boot loader. If this supposition is correct, the SELinux policy will need to permit (I'd guess) KDM rw access to both the GRUB and LILO boot configuration files. This may, of course, be an unacceptable security risk, in which case I suppose that the "reboot target selection" feature should be disabled when SELinux in in "Enforcing" mode. Just because an app allows a Dumb idea, and a potential security flaw does not mean that SELinux has to allow it. If you want to allow the login program to manipulate the /etc/grub file, then you need to add custom policy to allow this. I will not support it. That's what I thought too. Could/Should this "bug" be moved to the KDM/KDE people? Since (I believe) KDM will access this "feature" whenever a user selects the "Reboot" option in the "Leave" pop-up, you're going to get a lot of "access denied" reports cluttering up your in-box when F12 goes live, and disgruntled people telling everyone the SELinux is not worth the trouble. It should be fairly trivial for them to change the KDE "Leave" pop-up application to disable the "Select reboot target" feature when SELinux is active. (They could even ask the user if they really want to use the feature, and warn them of the consequences of so doing.) I would prefer to remove the feature altogether. patches welcome, otherwise users are still welcome to continue to modify/customize kdm to use this feature as well as create custom/local policy to allow it. Hey, I use that line all the time. :^) We aren't going to remove upstream features. We disable it by default, that's as far as we're willing to go. Oh, and FYI:
> Since (I believe) KDM will access this "feature" whenever a user selects the
> "Reboot" option in the "Leave" pop-up
No, it will not, as the default configuration is "no bootloader" (i.e. no bootloader integration). Only if you enable GRUB integration manually in System Settings, you'll trigger the SELinux denial.
Sounds ok to me. If you Change the default settings of an application sometimes you have to adjust the SELinux, which can be done by creating a selinux module. |