Bug 196587

Summary: pam_setcred changes in kcheckpass from #191049
Product: [Fedora] Fedora Reporter: Kostas Georgiou <k.georgiou>
Component: kdebaseAssignee: Than Ngo <than>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: fc5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-23 15:25:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kostas Georgiou 2006-06-25 13:08:52 UTC 
It seems that kcheckpass now tries pam_setcred with PAM_REFRESH_CRED instead of
PAM_ESTABLISH_CRED which isn't a bad idea. But unfortunately if the renewal time
of your kerberos ticket has expired it will not grab a new ticket for you. I
don't know enough about pam but it would be nice (if pam_setcred returns an
error) to detect this and retry with PAM_ESTABLISH_CRED so the user always has a
valid ticket.

Unfortunately #191049 is closed so I have no idea what the reasoning behind the
change is.
Comment 1 Rex Dieter 2006-08-23 14:31:23 UTC 
> Unfortunately #191049 is closed 
puzzling statement since *this* bug is #191049.  (: Did you mean to refer to a
different one?
Comment 2 Kostas Georgiou 2006-08-23 15:25:35 UTC 
*This* bug is #196587 :)

In any case this bug seems to be fixed now, I do get new tickets every time I
unlock my screen. I haven't checked what has changed but I can login to my
desktop every morning (since my home is nfs4 with kerberos, I do notice right
away if I don't have a ticket.)