"Markus Moeller" writes:
> "Russ Allbery" wrote:

>>> const char *KRB5_CALLCONV error_message(long code) {
>>> char *msg=NULL;
>>> krb5_svc_get_msg(code,&msg);
>>> return msg;
>>> }

>> Ah. I think that part of your diff might not have been included. It

> Line 240 in the patch should have it.

Yeah, found it. Does krb5_svc_get_msg allocate new memory that then has
to be freed, or does it just set msg to a pointer to static space
somewhere? (If there's a krb5_svc_free_msg function, that would answer
this question.)

Russ Allbery (rra@stanford.edu)