SELinux is preventing /usr/bin/boinc_client from using the 'execmem' accesses on a process. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that boinc_client should be allowed execmem access on processes labeled boinc_t by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep /usr/bin/boinc_client /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:boinc_t:s0 Target Context system_u:system_r:boinc_t:s0 Target Objects Unknown [ process ] Source boinc_client Source Path /usr/bin/boinc_client Port <Neznámé> Host (removed) Source RPM Packages boinc-client-6.10.45-2.r21128svn.fc14 Target RPM Packages Policy RPM selinux-policy-3.9.7-18.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.35.10-72.fc14.i686 #1 SMP Mon Dec 20 22:05:49 UTC 2010 i686 i686 Alert Count 1 First Seen Čt 23. prosinec 2010, 20:53:37 CET Last Seen Čt 23. prosinec 2010, 20:53:37 CET Local ID 4c0e2a21-4451-489e-88c9-a63d597553f4 Raw Audit Messages type=AVC msg=audit(1293134017.871:24727): avc: denied { execmem } for pid=1521 comm="boinc_client" scontext=system_u:system_r:boinc_t:s0 tcontext=system_u:system_r:boinc_t:s0 tclass=process boinc_client,boinc_t,boinc_t,process,execmem type=SYSCALL msg=audit(1293134017.871:24727): arch=i386 syscall=mmap2 success=yes exit=118026240 a0=0 a1=801000 a2=7 a3=20022 items=0 ppid=1 pid=1521 auid=4294967295 uid=492 gid=487 euid=492 suid=492 fsuid=492 egid=487 sgid=487 fsgid=487 tty=(none) ses=4294967295 comm=boinc_client exe=/usr/bin/boinc_client subj=system_u:system_r:boinc_t:s0 key=(null) boinc_client,boinc_t,boinc_t,process,execmem #============= boinc_t ============== allow boinc_t self:process execmem;
Adding a "me too" here. It looks like this is a regression that's cropped up before: https://bugzilla.redhat.com/show_bug.cgi?id=468358 On F14 x86_64 for me.
*** Bug 665545 has been marked as a duplicate of this bug. ***
We have these access (execstack, execmem) for boinc_project_t domain in policy which covers boinc projects. But boinc-client should not need this priv. The following explains the access. http://www.akkadia.org/drepper/selinux-mem.html
*** Bug 666101 has been marked as a duplicate of this bug. ***
I have this problem too, but the bug report xml is very messed up and I don't know how to make it readable
(In reply to comment #3) > We have these access (execstack, execmem) for boinc_project_t domain in policy > which covers boinc projects. > > But boinc-client should not need this priv. > > The following explains the access. > > http://www.akkadia.org/drepper/selinux-mem.html Thank you for the explanation (although it's over my head), but what is the "fix"? I would rather not have to disable selinux in order to run this program.
You can add the access for now by executing # grep boinc_t /var/log/audit/audit.log | audit2allow -M myboinc # semodule -i myboinc.pp In the meantime the boinc developers/packagers should explain why it needs this access or fix it so it does not. If boinc used java,mono or some similar tool it might really need the access.
Just for the record: I'm still waiting for an explanation on this from upstream: http://boinc.berkeley.edu/trac/ticket/1043
(In reply to comment #8) > Just for the record: I'm still waiting for an explanation on this from > upstream: > http://boinc.berkeley.edu/trac/ticket/1043 any news?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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