Potential dovecot/pam issue in -current?
by avian from LinuxQuestions.org on (#5AFKY)
I noticed these lines in /var/log/secure the other day -
Code:Nov 17 17:21:49 xxx auth: gkr-pam: unable to locate daemon control file
Nov 17 17:21:49 xxx auth: gkr-pam: stashed password to try later in open session
Nov 17 17:22:58 xxx auth: gkr-pam: unable to locate daemon control file
Nov 17 17:22:58 xxx auth: gkr-pam: stashed password to try later in open sessionI traced it down to any auth attempt through dovecot (these are actually successful connections and authorisations).
Thinking it might just be something I've done in my set-up/config, I installed a new fully updated -current in a virtual machine. I created two self-signed certificates to make dovecot happy, but did not change a single thing in any dovecot configuration file. The result is the same lines appearing in /var/log/secure when connecting to dovecot.
I'm actually not even sure it is an *issue* per say, as everything appears to work regardless of the message. But any insights from the linux experts here would be appreciated. Particularly any fixes if there is a configuration issue within -current at the moment.
Code:Nov 17 17:21:49 xxx auth: gkr-pam: unable to locate daemon control file
Nov 17 17:21:49 xxx auth: gkr-pam: stashed password to try later in open session
Nov 17 17:22:58 xxx auth: gkr-pam: unable to locate daemon control file
Nov 17 17:22:58 xxx auth: gkr-pam: stashed password to try later in open sessionI traced it down to any auth attempt through dovecot (these are actually successful connections and authorisations).
Thinking it might just be something I've done in my set-up/config, I installed a new fully updated -current in a virtual machine. I created two self-signed certificates to make dovecot happy, but did not change a single thing in any dovecot configuration file. The result is the same lines appearing in /var/log/secure when connecting to dovecot.
I'm actually not even sure it is an *issue* per say, as everything appears to work regardless of the message. But any insights from the linux experts here would be appreciated. Particularly any fixes if there is a configuration issue within -current at the moment.