Bug 452861
| Summary: | SELinux is preventing gdb (xdm_t) "write" to ./rpm (rpm_var_lib_t). | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeff Moyer <jmoyer> |
| Component: | gdm | Assignee: | jmccann |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | cschalle, dwalsh, elzondriel, pgraner, rstrode |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-10 10:47:27 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
Jeff Moyer
2008-06-25 13:52:23 UTC
gdm should not be execing gdb *** Bug 452862 has been marked as a duplicate of this bug. *** It does it to get a reasonable backtrace (unlike execinfo.h functions) Now it shouldn't be crashing, but when it does crash, running gdb isn't a bug. Well then we need to figure out what access it actually needs to get a back trace. Giving it the ability to overwrite the rpm database is not a good idea. Yea, I'm not sure why gdb would be trying to do anything with /var/lib/rpm oh thinking about this more, gdb suggests to you which rpms to install to get debuginfo, so that's probably what's happening. Probably just need to give it read access to the db. I allow gdm to read rpm database in selinux-policy-3.3.1-73.fc9.noarch but I guess we need to cause gdm to crash to see if this is enough. I received this same message about SELinux preventing gdb from writing to .rpm. I am a relatively new Fedora user, and I am completely puzzled as to what this is referring to. I would appreciate any clarification as to what it means and what if anything I should do. Thank you. Dorothy McElrath Hi Dorothy, GDM is the the login screen you see when you first boot up the machine. gdb is a debugger that is run when the login screen (or part of the login screen) crashes. The debugger is able to add some information about why the crash happened. We don't ship all the packages necessary to get a complete view of that information by default since it can get big. gdb will try to figure out and report which packages it needs installed to work completely (in case a user is running it instead of a program running it). SELinux is a mechanism to secure a system from doing things it isn't supposed to do. Normally it wouldn't make sense for a debugger to look in /var/lib/rpm so selinux flagged it as suspicious and prevented it from performing the operation. Looking at /var/lib/rpm is how gdb discovers which packages it needs, though, so it's actually okay that it's looking there. That's why Dan fixed the selinux policy in comment 7. Dorothy what was the SELinux message that you saw? This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |