[16492] in Kerberos_V5_Development
Re: X-CACHECONF in cache type 0504
daemon@ATHENA.MIT.EDU (Tim Alsop)
Fri Nov 19 13:37:29 2010
From: Tim Alsop <Tim@cybersafe.com>
To: Greg Hudson <ghudson@mit.edu>, Tim Alsop <Tim@cybersafe.com>
Date: Fri, 19 Nov 2010 16:50:44 +0000
Message-ID: <C90C5B23.27A31%Tim.Alsop@CyberSafe.com>
In-Reply-To: <1290184998.2633.1275.camel@ray>
Content-Language: en-US
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
Ok, thanks.
Next I am going to capture data between MIT 1.8.1 kinit and MS AD, to find
out why this cache entry is being written, when KDC does not support FAST
Tim
On 19/11/2010 16:43, "Greg Hudson" <ghudson@mit.edu> wrote:
>On Fri, 2010-11-19 at 11:27 -0500, Tim Alsop wrote:
>> Ok, so we can use krb5_ccache_conf_data at the start with the
>>X-CACHECONF:
>> as realm, but the data between these two elements can be anything we
>>want.
>>
>> e.g. This is valid and acceptable if found in a cache:
>> krb5_ccache_conf_data/foo/bar/hello/world@X-CACHECONF:
>
>Well, any service principal is valid and acceptable according to the
>cache format.
>
>To work with the Heimdal/MIT krb5_cc_get_config API, the principal must
>have three components: "krb5_ccache_conf_data", the config key, and the
>unparsed name of the cache's default client principal.
>
>
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
