Devdas Bhagat wrote: > The problem with the current design of imapd is that it assumes that > SASL will be available locally in some form, ignoring that it may not > be available there. > Do the pwcheck daemons provide support for this? Yes. The pwcheck 'API' is this simple: - SASL sends username\0password\0 over a socket - The daemon sends back 'OK\0' or 'Incorrect password\0' How the daemon decides on what response to return is completely open. For instance, my pwcheck daemon contacts a MySQL server on a remote machine to check the credentials.
- Re: Re[2]: SASL re-entrancy crisis (was: OpenLDAP ... Jeremy Howard
- Re[4]: SASL re-entrancy crisis (was: OpenLDAP 2.0.... Kevin J. Menard, Jr.
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Devdas Bhagat
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... GOMBAS Gabor
- Re: Re[2]: SASL re-entrancy crisis (was: OpenLDAP ... GOMBAS Gabor
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Ken Murchison
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Julio Sanchez Fernandez
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Devdas Bhagat
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Devdas Bhagat
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Jules Agee
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Jeremy Howard
- Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x +... Walter Wong