On 05/27/15 13:05 -0700, Jordan Brown wrote:
I'm sorry, I'm sure this is documented somewhere but I'm just not
finding it.
When a SASL server application calls
result = sasl_server_init(NULL, "myserver");
the library reads configuration options from /usr/lib/sasl2/myserver.conf.
When a SASL client application calls
result = sasl_client_init(NULL);
there's no program name specified, so what file does it read?
I cannot find it documented either. The code indicates that a NULL
parameter is acceptible. My assumption would be that libsasl would function
as if there were a missing config file and use the defaults.
(I know that the caller can supply a getopt callback and supply custom
settings, but the particular caller that I'm interested in - OpenLDAP's
client - passes in NULL.)
