[16491] 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: Tim Alsop <Tim@cybersafe.com>, Greg Hudson <ghudson@mit.edu>,
Sam Hartman
<hartmans@mit.edu>
Date: Fri, 19 Nov 2010 16:09:17 +0000
Message-ID: <C90C510C.27A0C%Tim.Alsop@CyberSafe.com>
In-Reply-To: <C90C5036.27A07%Tim.Alsop@CyberSafe.com>
Content-Language: en-US
MIME-Version: 1.0
Cc: Weijun Wang <weijun.wang@oracle.com>, "krbdev@MIT.EDU" <krbdev@mit.edu>
Content-Type: text/plain; charset="iso-8859-1"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
I am also trying to find out where the format of these configuration
entries is documented, if anywhere ?
For example, I see "fast_avail" in the entry issued by MS AD in our tests.
I assume this means that the realm supports FAST. Are there any other
values, such as fast_not_avail ?
Thanks,
Tim
On 19/11/2010 16:03, "Tim Alsop" <Tim@CyberSafe.com> wrote:
>So, is this name/realm specific to configuration data for FAST ? What
>happens if a vendor wants to store configuration data for some other
>reason, and not for FAST reasons ? Do they use different name/realm ?
>
>Thanks,
>Tim
>
>
>On 19/11/2010 16:00, "Greg Hudson" <ghudson@mit.edu> wrote:
>
>>On Fri, 2010-11-19 at 10:49 -0500, Sam Hartman wrote:
>>> Well, the patch was submitted to us by one of the Heimdal developers,
>>>so
>>> it is quite possible they will do something (or have done something)
>>> compatible.
>>
>>And in fact, looking at their code:
>>
>>commit 21af504e8a8bcdded12c88c2e5ff4bef418313f2
>>Author: Love Hörnquist Åstrand <lha@kth.se>
>>Date: Sat Jul 26 18:25:23 2008 +0000
>>
>> Add krb5_cc_[gs]et_config.
>>
>>(Initially Heimdal used the realm name of the ccache's default
>>principal, but then it changed to use the X-CACHECONF: realm as in our
>>code.)
>>
>>
>
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
