Description of problem: SELinux is preventing login from 'execute' accesses on the file /usr/bin/gnome-keyring-daemon. ***** Plugin catchall (100. confidence) suggests ************************** If cree que de manera predeterminada, login debería permitir acceso execute sobre gnome-keyring-daemon file. Then debería reportar esto como un error. Puede generar un módulo de política local para permitir este acceso. Do permita el acceso momentáneamente executando: # grep login /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:local_login_t:s0-s0:c0.c1023 Target Context system_u:object_r:gkeyringd_exec_t:s0 Target Objects /usr/bin/gnome-keyring-daemon [ file ] Source login Source Path login Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages gnome-keyring-3.18.3-1.fc23.x86_64 Policy RPM selinux-policy-3.13.1-157.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.2.7-300.fc23.x86_64 #1 SMP Wed Dec 9 22:28:30 UTC 2015 x86_64 x86_64 Alert Count 39 First Seen 2015-12-17 14:28:13 COT Last Seen 2015-12-21 12:45:59 COT Local ID 8c2265b8-88b4-49e3-b4c8-c8eec1f72b62 Raw Audit Messages type=AVC msg=audit(1450719959.874:469): avc: denied { execute } for pid=1313 comm="login" name="gnome-keyring-daemon" dev="sda4" ino=27624595 scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:object_r:gkeyringd_exec_t:s0 tclass=file permissive=0 Hash: login,local_login_t,gkeyringd_exec_t,file,execute Version-Release number of selected component: selinux-policy-3.13.1-157.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.7-300.fc23.x86_64 type: libreport Potential duplicate: bug 883627
Do you have pam_selinux in your pam stack?
Created attachment 1108664 [details] pam
Oh, I forgot to said that I added manually session optional pam_gnome_keyring.so auto_start auth optional pam_gnome_keyring.so journalctl displayed: gnome-keyring-daemon[1310]: couldn't access control socket: /run/user/1000/keyring/control So I tried to follow http://www.linuxquestions.org/questions/linux-desktop-74/openbox-autostart-gnome-keyring-daemon-message-4175547333-print/ (except for the line in /etc/pam.d/passwd, which was already present), no luck at all, with or without those lines gnome-keyring can't access to /run/user/1000/keyring/control (The file exist btw)
Looks like we would need policy rules to allow this behaviour. Easiest to allow it to execute, but I think you would end up with gnome-keyringd running as local_login_t. We could also allow gnome-keyring_exec_t to be an entrypoint into user domains including unconfined_t. Which might be the simplest thing to do.
I think that my pam stack is in Attachments
(In reply to Daniel Walsh from comment #1) > Do you have pam_selinux in your pam stack? Isn't my pam stack the one that is in attachments? if not please tell me the dir.
This bug makes Geary unusable
I think my pam stack is in attachments.
Can you still reproduce the issue?
Yes, i'm not using any key deposit because of that.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.
This problem is still happening on Fedora 33, how can it be reopened? type=AVC msg=audit(1608802896.534:784): avc: denied { execute } for pid=1986 comm="login" name="gnome-keyring-daemon" dev="dm-2" ino=1450729 scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:object_r:gkeyringd_exec_t:s0 tclass=file permissive=0
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 EOL if it remains open with a Fedora 'version' of '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.
This is a reminder that the bug is still present in Fedora 36 type=AVC msg=audit(1656951879.897:327): avc: denied { execute } for pid=2166 comm="login" name="gnome-keyring-daemon" dev="dm-2" ino=1459715 scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:object_r:gkeyringd_exec_t:s0 tclass=file permissive=0 For the last couple of Fedora releases I've worked around the issue using audit2allow, which suggests the following policy require { type gkeyringd_exec_t; type local_login_t; class file execute; } #============= local_login_t ============== allow local_login_t gkeyringd_exec_t:file execute;