On 2020-07-08 10:50, Steve Dickson wrote:
I'm curious about these changes... since all krb5_free_string() does is call free()... where is the "strdup'd msg" coming from?
gssd_k5_err_msg() always returns a local strdup() of the error message. We shouldn't be using a Kerberos library method to free them. There's no guarantee that the library won't change, or even that the library was compiled with the same malloc library.
Doug
