Hide Forgot
Description of problem: When trying to log in to a vty I get logged in but before a shell prompt comes up I get a message: Cannot make/remove an entry for the specified session Version-Release number of selected component (if applicable): pam_krb5-2.4.8-1.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. Upgrade F19 to F20 2. Try to log in using a kerberos account 3. Actual results: Logged in but before getting a shell prompt you get: Cannot make/remove an entry for the specified session And then logged back out. Expected results: Logged in. Additional info: /var/log/secure reports: Dec 2 12:11:53 pc login: pam_krb5[29814]: TGT verified using key for 'host/pc.example.com@EXAMPLE' Dec 2 12:11:54 pc login: pam_krb5[29814]: authentication succeeds for 'brian' (brian@EXAMPLE) Dec 2 12:11:54 pc login: pam_krb5[29814]: error creating ccache using pattern "/tmp/krb5cc_1001" Dec 2 12:11:54 pc login: pam_krb5[29814]: error creating ccache for user "brian" Dec 2 12:11:54 pc login: Cannot make/remove an entry for the specified session Additionally (logged in via ssh and key so no kerberos authentication required): $ id uid=1001(brian) gid=1001(brian) $ /usr/lib64/security/pam_krb5/pam_krb5_cchelper -c /tmp/krb5cc_1001 1001 1001 $ echo $? 4 This appears to be where the login process comes to halt. I guess the question is why is pam_krb5_cchelper exiting with a 4 instead of doing it's work?
The template setting is expected to specify a cache type in addition to its location. If it's being explicitly configured, try prefixing it with "FILE:". If it's not being explicitly configured, then you're seeing a bug, and attaching a copy your krb5.conf should be useful in reproducing it. Thanks!
Ahhh. And there was the hint I needed. My F19 /etc/krb5.conf file had: default_ccache_name = /tmp/krb5cc_%{uid} without the cache type prefix. I guess that's being more strictly enforced in F20. I wonder how many others this will bite and if a missing cache type should default to FILE:.
We put so much effort to make sure that ccache goes into a better place than a file. We tried DIR cache but there were issues related to creating the root directory for cache so we ended up with a KEYRING one. Given these circumstances having file as the default cache type would be really something unfortunate.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.