Hide Forgot
SELinux is preventing /usr/libexec/telepathy-gabble from read, write access on the file /home/dzamirski/.cache/dconf/user. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that telepathy-gabble should be allowed read write access on the user file 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 telepathy-gabbl /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:telepathy_gabble_t:s0-s0 :c0.c1023 Target Context unconfined_u:object_r:cache_home_t:s0 Target Objects /home/dzamirski/.cache/dconf/user [ file ] Source telepathy-gabbl Source Path /usr/libexec/telepathy-gabble Port <Unknown> Host (removed) Source RPM Packages telepathy-gabble-0.12.0-1.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-18.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.4-20.fc15.x86_64 #1 SMP Thu Apr 28 23:32:48 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Fri 29 Apr 2011 09:41:57 AM EDT Last Seen Fri 29 Apr 2011 09:41:57 AM EDT Local ID e64384c0-58df-4038-b274-db9a00e79668 Raw Audit Messages type=AVC msg=audit(1304084517.369:66): avc: denied { read write } for pid=2313 comm="telepathy-gabbl" name="user" dev=dm-5 ino=28967620 scontext=unconfined_u:unconfined_r:telepathy_gabble_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:cache_home_t:s0 tclass=file type=SYSCALL msg=audit(1304084517.369:66): arch=x86_64 syscall=open success=no exit=EACCES a0=2065b50 a1=42 a2=180 a3=7fff552b3320 items=0 ppid=1 pid=2313 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=telepathy-gabbl exe=/usr/libexec/telepathy-gabble subj=unconfined_u:unconfined_r:telepathy_gabble_t:s0-s0:c0.c1023 key=(null) Hash: telepathy-gabbl,telepathy_gabble_t,cache_home_t,file,read,write audit2allow #============= telepathy_gabble_t ============== allow telepathy_gabble_t cache_home_t:file { read write }; audit2allow -R #============= telepathy_gabble_t ============== allow telepathy_gabble_t cache_home_t:file { read write };
Did everything work correctly, Other then the AVC showing up?
Well, I'm not sure if this is related but empathy does not persist account information - after every reboot I'm prompted to create account. Once I enter the account details, everything seems to work. The system was installed fresh but with /home partition left as is after Fedora 14. I have a two more such installations on my home PCs and none of them are having this issue. It's only just this particular PC.
Dominick Looks like telepathy apps need to write to ~/.cache/dconf/user?
(In reply to comment #2) > Well, I'm not sure if this is related but empathy does not persist account > information - after every reboot I'm prompted to create account. Once I enter > the account details, everything seems to work. The system was installed fresh > but with /home partition left as is after Fedora 14. I have a two more such > installations on my home PCs and none of them are having this issue. It's only > just this particular PC. Can you reproduce this? Do you use the proxy functionality?
Could you please apply the fix suggested in the report and see if that fixes your account problem as well? grep telepathy-gabbl /var/log/audit/audit.log | audit2allow -M mypol semodule -i mypol.pp After testing you can remove the "fix": semodule -r mypol.pp I doubt this is related and that this access is required but i am not positive. I have been told that gabble needs to interact with dconf for its new proxy functionality but that does not automatically mean it needs to read/write dconf cache files.
(In reply to comment #5) > Could you please apply the fix suggested in the report and see if that fixes > your account problem as well? > > grep telepathy-gabbl /var/log/audit/audit.log | audit2allow -M mypol > semodule -i mypol.pp > > After testing you can remove the "fix": > > semodule -r mypol.pp > > I doubt this is related and that this access is required but i am not positive. > > I have been told that gabble needs to interact with dconf for its new proxy > functionality but that does not automatically mean it needs to read/write dconf > cache files. Creating the custom policy module stopped the SELinux AVC but the accounts are still not persisted between sessions. I'm not using proxy at all.
ok please remove it: semodule -r mypol. It is not related to you account problem i suspect, and since you are only seeing this on your "problematic" system, it am not convinced (yet) that this should be allowed. You can silently deny this event of selinux blocking this access if you like: mkdir ~/mypol; cd ~/mypol; echo "policy_module(mypol, 1.0.0) gen_require(\` type telepathy_gabble_t, cache_home_t; ') dontaudit telepathy_gabble_t cache_home_t:file { read write };" > mypol.te; make -f /usr/share/selinux/devel/Makefile mypol.pp (sudo) semodule -i mypol.pp or you can just ignore it. I gather you were/are able to reproduce this issue (avc denial)? See if you are noticing any loss of functionality other than you account problem. I wonder what is causing your account problem. You might want to restore the context of your home directory just to be sure. Fedora 15 no longer has restorecond -u running in the background i believe, so it may well be a labelling issue? restorecon -R -v ~
Dominick, You can create a dontaudit policy module using audit2allow. audit2allow -D -i /var/log/audit/audit/log -M telepathdontaudit
I was not aware of that. Thanks for that information.
(In reply to comment #7) > ok please remove it: semodule -r mypol. It is not related to you account > problem i suspect, and since you are only seeing this on your "problematic" > system, it am not convinced (yet) that this should be allowed. > > You can silently deny this event of selinux blocking this access if you like: > > mkdir ~/mypol; cd ~/mypol; echo "policy_module(mypol, 1.0.0) gen_require(\` > type telepathy_gabble_t, cache_home_t; ') dontaudit telepathy_gabble_t > cache_home_t:file { read write };" > mypol.te; > > make -f /usr/share/selinux/devel/Makefile mypol.pp > (sudo) semodule -i mypol.pp > > or you can just ignore it. I gather you were/are able to reproduce this issue > (avc denial)? > > See if you are noticing any loss of functionality other than you account > problem. > > I wonder what is causing your account problem. > > You might want to restore the context of your home directory just to be sure. > Fedora 15 no longer has restorecond -u running in the background i believe, so > it may well be a labelling issue? > > restorecon -R -v ~ Ok, I have removed the custom policy and ran the restorecon on my home dir and now empathy picked up all the accounts configured after F14 installation and persists the settings. It restored a lot of stuff within ~/.mission_control directory. Many thanks for the help and tips.
Same problem. Apparently all works fine, but really empathy accounts that should to be active at boot, it doesn't instead. restorecon on my home dir doesn't work. Thanks.
Fixed in selinux-policy-3.9.16-21.fc15 The build is available from koji for now http://koji.fedoraproject.org/koji/buildinfo?buildID=242046
Hello, Just confirming that selinux-policy-3.9.16.-21.fc15 fixed the AVC for me.
Thank you. Could you update karma https://admin.fedoraproject.org/updates/selinux-policy-3.9.16-21.fc15 then log in and leave karma (feedback).
Ok, problem fixed for me too. Thanks
(In reply to comment #14) > Thank you. Could you update karma > > https://admin.fedoraproject.org/updates/selinux-policy-3.9.16-21.fc15 > > > then log in and leave karma (feedback). Done :-)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.