Re: ldap_sasl_interactive_bind_s and LDAP_SASL_QUIET

2021-03-25 Thread Howard Chu
Jordan Brown wrote: > Any comments on this? No strong opinion. Generally, interact is only for prompts - messages that expect input from the user in response. Informational messages that don't require any response don't seem to apply. > On 3/4/2021 4:05 PM, Jordan Brown wrote: >> ldap_sasl_inte

Re: ldap_sasl_interactive_bind_s and LDAP_SASL_QUIET

2021-03-24 Thread Jordan Brown
Any comments on this? On 3/4/2021 4:05 PM, Jordan Brown wrote: > ldap_sasl_interactive_bind_s prints SASL-related messages on stderr by > default, unless you specify LDAP_SASL_QUIET. > > This seems wrong.  The whole point of the "interact" function is to > handle any required conversation with the

ldap_sasl_interactive_bind_s and LDAP_SASL_QUIET

2021-03-04 Thread Jordan Brown
ldap_sasl_interactive_bind_s prints SASL-related messages on stderr by default, unless you specify LDAP_SASL_QUIET. This seems wrong.  The whole point of the "interact" function is to handle any required conversation with the user.  In particular, in a GUI application these messages won't go to th