Ken ________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
Yes, I think allocating the storage and initializing it at most once
per context, delayed until the actual resolver usage, is the right
way to deal with this. Simply adding a pointer field to the context,
initialized to NULL, is probably the way to start....
- Re: Memory Leak problems with krb5_get_init_creds_password? Ken Raeburn
