NIM plug-in loading question
Kevin Koch
kpkoch at MIT.EDU
Mon Mar 31 09:17:59 EDT 2008
Removing the plugin from the plugins page worked.
Can you confirm that the Krb4Cred Plugin and MITKrb4 Module are the only
registry deletions needed in the installers?
Kevin
-----Original Message-----
From: Jeffrey Altman [mailto:jaltman at secure-endpoints.com]
Sent: Sunday, March 30, 2008 10:21 PM
To: kpkoch at MIT.EDU
Subject: Re: NIM plug-in loading question
Go to the plugins page in NIM and disable it or remove it.
Kevin Koch wrote:
> A KRB4 provider is probably the problem. By registered, do you mean a
> Krb4Cred entry in
HKLM/Software/MIT/Kerberos/NetIDMgr/PluginManager/Plugins?
>
> The release notes don't mention the HKLM/.../PluginManager/Modules
entries.
> Would I want to delete the MITKrb4 entry as well?
>
> -----Original Message-----
> From: Jeffrey Altman [mailto:jaltman at secure-endpoints.com]
> Sent: Sunday, March 30, 2008 10:32 AM
> To: kpkoch at mit.edu
> Cc: kfwdev at mit.edu
> Subject: Re: NIM plug-in loading question
>
> Kevin Koch wrote:
>> Good point. For now, I'll continue trying to get it to work without any
>> KRB4 support. Later I'll turn the compile time condition into a run time
>> condition.
>>
>> With the changes in dynimport.c, NetIdMgr starts but one of the three
>> kmmint_plugin_broker threads calls krb4_cb which leads to an exception in
>> khm_krb4_set_def_tkt_string. Is another NO_KRB4 / No-KRB4-support
> condition
>> needed somewhere?
>>
>> Kevin
> Look at the #ifndef _WIN64 code blocks. It will be one of those.
>
> Although krb4_cb should not be called unless you are loading the krb4
> provider. Make sure you don't have a krb4 provider registered on your
> system
More information about the kfwdev
mailing list