Received: from serrano.cc.columbia.edu (IDENT:cu41754@serrano.cc.columbia.edu [128.59.29.6]) by krbdev.mit.edu (8.9.3p2) with ESMTP id RAA16712; Wed, 6 Sep 2006 17:45:07 -0400 (EDT)
Received: from [192.168.1.13] (cpe-68-175-91-105.nyc.res.rr.com [68.175.91.105]) (user=jaltman mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id k86Lj4q5029929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rt@krbdev.mit.edu>; Wed, 6 Sep 2006 17:45:06 -0400 (EDT)
Message-Id: <44FF41E5.2050101@mit.edu>
Date: Wed, 06 Sep 2006 17:47:17 -0400
From: Jeffrey Altman <jaltman@mit.edu>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #4222] GSSAPI context being destroyed when ticket cache renewed
References: <rt-4222-18546.14.8966709623526@krbdev.mit.edu>
In-Reply-To: <rt-4222-18546.14.8966709623526@krbdev.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-BY: MIMEDefang 2.48 on 128.59.29.6
RT-Send-Cc: 
X-RT-Original-Encoding: iso-8859-1
Content-Length: 519

Russ Allbery via RT wrote:

>> Just to be clear, the problem happens when the ticket cache is
>> refreshed. I.e., the tickets for the existing SASL/GSSAPI connection
>> hadn't actually yet expired, just the ticket cache was refreshed with
>> new tickets.  I can understand why the SASL/GSSAPI context would be
>> closed out on *expiration* but I think a refresh shouldn't have this
>> effect. ;)

If it is possible, can you post a stack trace at the point the context
is deemed to be invalid?

That would help a lot.