Received: from jalapeno.cc.columbia.edu (IDENT:cu41754@jalapeno.cc.columbia.edu [128.59.29.5]) by krbdev.mit.edu (8.9.3p2) with ESMTP id SAA16746; Wed, 6 Sep 2006 18:16:42 -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 jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id k86MGgKl016693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rt@krbdev.mit.edu>; Wed, 6 Sep 2006 18:16:42 -0400 (EDT)
Message-Id: <44FF494A.1030908@mit.edu>
Date: Wed, 06 Sep 2006 18:18:50 -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-18548.19.1623282477208@krbdev.mit.edu>
In-Reply-To: <rt-4222-18548.19.1623282477208@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.5
RT-Send-Cc: 
X-RT-Original-Encoding: iso-8859-1
Content-Length: 385

Quanah Gibson-Mount via RT wrote:
> I can get in contact with the user who reported the issue, and see what 
> additional data they can gather, if you like.

We need to know exactly what is wrong if we are going to have a chance
of improving the behavior.  I don't see any place in the code that the
credential cache would be examined once the context is established.

Jeffrey Altman