Received: from smtp3.stanford.edu (smtp3.Stanford.EDU [171.67.20.26]) by krbdev.mit.edu (8.9.3p2) with ESMTP id QAA16667; Wed, 6 Sep 2006 16:43:35 -0400 (EDT) Received: from smtp3.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 1ADC84C629 for ; Wed, 6 Sep 2006 13:43:30 -0700 (PDT) Received: from deus-ex.stanford.edu (tribes2.Stanford.EDU [171.64.19.81]) by smtp3.stanford.edu (Postfix) with ESMTP id 119794C1F5 for ; Wed, 6 Sep 2006 13:43:28 -0700 (PDT) Date: Wed, 06 Sep 2006 13:43:27 -0700 From: Quanah Gibson-Mount To: rt-comment@krbdev.mit.edu Subject: Re: [krbdev.mit.edu #4222] GSSAPI context being destroyed when ticket cache renewed Message-Id: In-Reply-To: References: X-Mailer: Mulberry/4.0.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 803 --On Friday, September 01, 2006 12:55 AM -0400 Sam Hartman via RT wrote: > I strongly suspect that the context is ending when it expires and that > SASL needs to do a better job of catching this error and reporting a > connection problem. 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. ;) --Quanah -- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html