Can I get you to make sure you have krb5-user installed, kinit -c KEYRING:blah <principal_name_goes_here> and start firefox with the KRB5CCNAME environment variable set to KEYRING:blah
(to confirm you're using the keyring cache, probably doing a kdestroy on your normal tickets would be good) What I'm trying to do here is to see if the performance is dependent on what type of credential cache is used. I'm suspecting that there is a locking problem in either MIT or Heimdal. Either MIT holds a lock too long, doesn't have fine grain locking somewhere, or Heimdal has a race condition and is not holding a lock that it needs. The keyring cache has a different locking path than the file based cache. So, it may perform differently. If it is faster, then that tells us something. If it is not, then we don't learn much. I don't have a test environment in which to reproduce this, although I am talking to upstream about the issue. I have not actually opened an upstream bug at this point; I've brought the issue up on the krbcore list. --Sam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
