Hi Sam, I was browsing the docs when I found auth_sasl initializes *authtype_ret and *authdata_ret. They will be set to a malloc(3)-ed buffers that can be directly passed as arguments to auth_generic(3). It is the application's responsibility to free(3) these buffers when it's done with them.
If that function lives in a so library, freeing buffers can become erratic. In facts, you cannot control what malloc library is your client code linking with. I'd put e.g. auth_sasl_free_buffers(char *authtype_ret, char *authdata_ret) into the same .so for calling the corresponding free. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
