All private functions are compiled in Kerberos for Windows. However, not all private functions are exported from the DLLs.
The MIT Kerberos team does not want to have multiple versions of the Kerberos DLLs being distributed. It makes compatibility between applications and distributions very difficult if not impossible. For what reason do you need to have access to this function? Jeffrey Altman KFW Maintainer [EMAIL PROTECTED] wrote: > Hi All, > > I have tried to build up the MIT Krb-1.3.4 on Windows to export the private > interface "krb5_set_default_tgs_ktypes" declared in > \krb5-1.3.4\src\include\krb5.h. I have commented out the #if KRB5_PRIVATE directive > in this specifc header file and > added the compiled libraries into my VC6.0 project linker settings. Unfortunately, > it still gives me error such as "error LNK2001: unresolved external symbol > _krb5_set_default_tgs_ktypes". I am pretty sure that I have included the > libraries(comerr32.lib, gssapi32.lib, krb532.lib, xpprof32.lib) in my linker > settings but it still cannot work. Is there anything I missed out? I'd appreciate > your kind help a lot. Thanks. > > > Peter Yen -- ----------------- This e-mail account is not read on a regular basis. Please send private responses to jaltman at mit dot edu ________________________________________________ Kerberos mailing list [EMAIL PROTECTED] https://mailman.mit.edu/mailman/listinfo/kerberos
