Bug 539987
| Summary: | SELinux is preventing /usr/sbin/abrtd "write" access on abrt. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jim Tourville <turbo> |
| Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | abarouri, abcd951234, achrisjo, akounga2000, alanmerriman, allesindtoren, amon.ra.ymond, ananta_u, anaselfathi, andrewwatty, antoniozamora76028, anton, artzfam, asrpavankumark, barryl123, bashon, best4ever.bharat, brucemartin10, bschwarzer, c69jay, carlos.tevez.20, Chungmunky, cyberpunk370, cyberpunk370, danilo.bogdanov, dan.king106, danschma, daryl.francis.thompson, deanroberts, dellerbadavide, devadatta.dev, dfediuck, draileanu, dvlasenk, dwalsh, dzickus, e_davis79, eddiet.sr, edowd, exsmalltalker1996, francico.87, ganesh.rajaiyan, giorgosfm, goodoldbook, griffij9, gustavocoutinho, hliuroc, hrobi88, im2061, inf.marcos, iprikryl, ironshack, jake, jasons1206, jdanbarnes, jemadux, jfcodelacruz, jmoskovc, jmoyad, j.t.anagnostopoulos, kklic, llbrunoll, l.uriel.mf, lynnevan, ma1t05, malazoj, mark.balmain, m.asgarikhah, matetiau, mgrepl, michkin_a, mido.mashakel.1, mmb.prog, mnowak, morirmorir, mukundkulkarni, mulligan.bob, n12367, nationjd, nobody+296696, npajkovs, oldjoet, omarberroteranlkf, omarcucci78, optimal_solution2000, pedro_magalhaes86, ranllb, rayharman, rhelbugzilla, rich010273, ricklee, rm-carneiro, rodrigo.sanchez, rplainfield, rpqmo65, sarrab1976, seedybeem, sellomohapi, seth.bladen, sgthrelfal, shobimathew, Soaringeagle424, ss4jbroly, taphm, terry.patrick, tmscanavan, travistrash, tremlex, turbo, twild1990, valdezfa, vasanthkumark, vold, vudintsev, will_z32, wushigung, xman-xavier, yakoob, zayzayats, zub07513 |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:25472fb419f61c13864f61244bf869c30fd5803e776d425e7d45b72027e73715 | ||
| Fixed In Version: | abrt-1.1.1-1.fc13 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-02 18:06:05 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
Jim Tourville
2009-11-21 20:53:33 UTC
Why is the abrt application modifying/creating pyhook.conf? I really don't know. I actually tried (after the SELinux alerts) to uninstall all of the abrt applications. But, this one kept coming up. (If you are asking me). When I did "rpm -q abrt" after I uninstalled the abrt apps I could not find a single one of them but abrt continued to try to modifying/create pyhook.conf. I am asking the abrt team. Sorry for the confusion. It's config file for ABRT python hook, is it a problem if abrtd changes a file in /etc/abrt ?? Jirka Well usually we like to stop a tool from changing it configuration. We can setup policy to allow it to write to /etc/abrt/pyhook.conf, but we would like it to be in a different directory if an admin is also going to edit this file. The goal of most apps is to think of /etc as a read only partition and if an app needs to write, it should put the content into /var/lib. (In reply to comment #5) > Well usually we like to stop a tool from changing it configuration. > > We can setup policy to allow it to write to /etc/abrt/pyhook.conf, but we would > like it to be in a different directory if an admin is also going to edit this > file. > > The goal of most apps is to think of /etc as a read only partition and if an > app needs to write, it should put the content into /var/lib. I can change the behavior of python hook, so it won't need this file, but our idea was to make the daemon configurable via the gui and make the daemon to read/write it's configuration to keep the code on one place(we can probably make it into a library). What would be the right solution for this? Create separate app like system-config-abrt and let the daemon just read the config file? I would separate out the function into two different programs. I changed the python hook to not require the /etc/abrt/pyhook.conf and the daemon shouldn't try to write in /etc/abrt anymore. Jirka abrt-1.0.1-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.1-1.fc12 abrt-1.0.1-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12994 abrt-1.1.1-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/abrt-1.1.1-1.fc13 abrt-1.1.1-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/abrt-1.1.1-1.fc13 abrt-1.1.1-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |