[OpenAFS-devel] Re: [OpenAFS] New Windows AKLOG...
Ken Hornstein
kenh@cmf.nrl.navy.mil
Thu, 24 Jul 2003 17:00:35 -0400
>I've noticed a couple of strange anomalies in the original code. The first
>was related to the free'ing of the memory allocated by
>krb5_get_host_realm(). The krb5_xfree() call now causes a Debug assertion
>failure. I noticed what seems to be a new call krb5_free_host_realm(). I
>used that instead and it solved the problem. Was I correct in doing
>this? It is strange that on older compiles of the original code with older
>Krb5 versions the krb5_xfree() worked correctly.
krb5_xfree() was the way it "used" to work. The use of krb5_free_host_realm()
is the new "correct" way.
>>That's fine with me; the people who's aklog mine is based on didn't care,
>>and I certainly don't either.
>
>Ok, so you are saying there are no export restrictions on the code or binary?
Uh, _no_, I never said that. You'd need to ask a lawyer that question.
--Ken