MIT Kerberos for Windows failing with Windows 10 update 1803?

[Ruurd Beerstra]

Thanks very much, that clarifies my problems.
I must have clicked on "Make default", and it has the API settings in 
the registry.
I can't find any button to undo that - If I've changed something in 
krb.ini, click "Make default", then afterwards I'm stuck with those 
settings until I manually edit the registry?
Odd.

But If I use the API settings, all is well and logging in with GSSAPI or 
Kerberized telnet works the way it should.
I'll update my docs to reflect that in case my users run into this problem.

Thanks again for the help,

     Ruurd

Op 19-6-2018 om 22:25 schreef Greg Hudson:
> On 06/19/2018 03:51 PM, Ruurd Beerstra wrote:
>> OK, I'm confused now....
>> 2 days ago I tried FILE: by editing krb5.ini and setting 
>> default_cc_name to FILE:c:/tmp/krb5cc_${uid}
>> I saw it uses the SID for my user as part of the filename in c:/tmp.
>> I SAW the file being made, and it STILL refused to work the way it 
>> should. The ticket manager showed "FILE:.." in the "Credential cache" 
>> column.
> I'm not sure if I can completely explain this, but it's [libdefaults] 
> default_ccache_name, not default_cc_name.
>
>> Start the "MIT kerberos.exe", get a TGT: The Credential cache" still 
>> shows "API: Initial default ccache". Huh? Why does it not go back to 
>> MSLSA?
>
> Three's a registry value HKCU\Software\MIT\Kerberos5 ccname, which the 
> ticket manager sets if you click "make default".
>