[16467] in Kerberos_V5_Development
Re: X-CACHECONF in cache type 0504
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Nov 18 13:15:46 2010
From: Greg Hudson <ghudson@mit.edu>
To: Tim Alsop <Tim@cybersafe.com>
In-Reply-To: <C90AE14D.2764A%Tim.Alsop@CyberSafe.com>
Date: Thu, 18 Nov 2010 13:15:41 -0500
Message-ID: <1290104141.2633.1197.camel@ray>
Mime-Version: 1.0
Cc: "krbdev@MIT.EDU" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Thu, 2010-11-18 at 08:57 -0500, Tim Alsop wrote:
> Why was 0504 cache type format changed, thus breaking interoperability
> with other code which uses same cache type ?
The cache format was not changed incompatibly. The additional
information is encoded as credential entries for oddly-named server
principals.
> Basically if MIT code is used to create the cache, the Java 1.6 code
> cannot recognise the TGT unless the cache entries are renewed to
> remove the extra information added by MIT.
If so, I would expect that to reflect a bug in the Java 1.6 code; it
should see a config entry as just another credential for a service it
doesn't care about. Obviously, had we been aware of such a bug at the
time we added the cache config support, we would have attempted to work
around it.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
