Received: from smtp1.stanford.edu (smtp1.Stanford.EDU [171.67.22.28]) by krbdev.mit.edu (8.9.3p2) with ESMTP id BAA12398; Fri, 1 Sep 2006 01:08:14 -0400 (EDT) Received: from smtp1.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 489364BEBF for ; Thu, 31 Aug 2006 22:08:13 -0700 (PDT) Received: from SW-90-717-287-3.stanford.edu (SW-90-717-287-3.Stanford.EDU [171.66.155.86]) by smtp1.stanford.edu (Postfix) with ESMTP id 2CE024BDF1 for ; Thu, 31 Aug 2006 22:08:13 -0700 (PDT) Date: Thu, 31 Aug 2006 22:08:12 -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: <20EB5477F90FDE7DC3CE16E3@SW-90-717-287-3.stanford.edu> 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: 678 --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. Well, this is very different than how Heimdal's behavior operates, and quite frankly I prefer what Heimdal does. I see no reason to make an *already* established & encrypted connection break just because the context has ended. --Quanah -- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html