Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #772712 +++
This issue is evident when krb5-auth-dialog is in use when the prompter is left there hanging for a long period.
When that happen krb5libs mistakenly record a great clock skew.
The effect is that at the next kinit this clock skew is applied and kinit/k-a-d may end up asking for a ticket in the past.
See upstream Ticket #7063
--- Additional comment from ssorce on 2012-01-09 13:01:25 EST ---
Upstream ticket URL:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=7063
--- Additional comment from ssorce on 2012-01-11 19:06:06 EST ---
Patch available here:
https://github.com/krb5/krb5-anonsvn/commit/2626c89efd8019853edab29c52bac951f5ba2794
Description of the bug.
prerequisite: a KDC that does not require preauth and with max tgt lifetime of 8-10 hours
Current situation:
1. make sure krb5_auth_dialog is running.
2. Take a short lived ticket
3. wait until it expire and let krb5_auth_dialog pop up
4. go home
5. when you get back next day enter your password
6. klist and see the ticket is valid but expires yesterday
7. run kinit
8. klist and notice how the ticket still expire in the past
9. run kinit again
10. klist and notice how the ticket now expire according to expected time
Correct behavior:
1. make sure krb5_auth_dialog is running.
2. Take a short lived ticket
3. wait until it expire and let krb5_auth_dialog pop up
4. go get lunch
5. when you get back enter your password
6. klist and see the ticket is valid but expires yesterday
7. run kinit
8. klist and see that ticket expire at the expected time
Comment 3RHEL Program Management
2012-07-10 08:16:30 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4RHEL Program Management
2012-07-10 23:59:48 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0319.html