Bug 610104

Summary: krb5-auth-dialog spinning
Product: [Fedora] Fedora Reporter: Kevin L. Mitchell <klmitch>
Component: krb5-auth-dialogAssignee: Itamar Reis Peixoto <itamar>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: itamar, klmitch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 19:16:13 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:
Attachments:
Description Flags
Packet dump
none
Kerberos configuration none

Description Kevin L. Mitchell 2010-07-01 15:06:12 UTC
Created attachment 428465 [details]
Packet dump

Description of problem:

When my ticket expires or gets close to expiring, krb5-auth-dialog starts spinning, using up lots of CPU time and network bandwidth continuously re-acquiring both DNS responses for kerberos servers and successful TGS requests.

Version-Release number of selected component (if applicable):

krb5-auth-dialog-0.15-1.fc13.x86_64

How reproducible:

Very reproducible; it always happens when my credentials are just about to expire.

Steps to Reproduce:
1. Configure krb5-auth-dialog
2. Get credentials
3. Allow to expire
  
Actual results:

CPU time and network usage shoot up.

Expected results:

krb5-auth-dialog should only query one kerberos server once for a TGS--and it really should only do this *after* prompting me for a password, given that I could be away for hours and the credential it gets could have a massive time skew.

Additional info:

I will attach my krb5.conf and a text wireshark packet dump of a minute or two of traffic as generated by krb5-auth-dialog

Comment 1 Kevin L. Mitchell 2010-07-01 15:06:52 UTC
Created attachment 428466 [details]
Kerberos configuration

Comment 2 Bug Zapper 2011-06-01 15:02:34 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2011-06-27 19:16:13 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Thank you for reporting this bug and we are sorry it could not be fixed.