On Tue, Oct 14, 2003 at 12:57:44PM +0200, Szabo Nandor wrote:
> After some day of debugging, I realized the problem: the prefix
> of UserPassword attribute.
>
> I use {crypt} prefix, but more client (ldappasswd, sqwebmail,ldapbrowser)
> put {CRYPT}.
> auth_pop returns a "User record incorrect" error, then finds a {CRYPT}
> prefix.
>
> Other applications can authenticate both {crypt} or {CRYPT} prefix.
>
> So my questions:
> 1. Which is the correct (RFC standard) prefix?
> 2. Is it possible that auth_pop can work with both prefix, like other
> applications?
>
You seem to be using a old patch. Current auth_pop is using case_diff to
compare the prefixes in a case ignore way. So {crypt}, {CRYPT} and {CrYpT}
are all accepted. At least this is the desired behaviour.
--
:wq Claudio
