Re: [pysieved] authentication problem

[Philippe Levan <levan at epix dot net>]

> Sebastian Ganschow <sebastian at ganschow dot name> writes:
> > The authentication request is build by the following pattern:
> > 	username\0username\0password
> > After changing the pattern to: (Diff attached)
> > 	\0username\0password
> > the authentication worked and I could store my sieve rules on the mail-server.

On Sat, 28 Jul 2007, Neale Pickett wrote:
> Has anybody else had a problem with this?

I can confirm that leaving the 1st field empty works
too, in my setup, although I can't see why the other
form doesn't work.
A quick look at the Dovecot 1.0.2 source code seems to
indicate that "username\0username\0pass" is supposed
to be handled just like "\0username\0pass" for PLAIN
authentication.
The question is : does "\0username\0pass" break
anybody else's setup ?

Remark : If I were ambitious enough, I'd revise the
code so that the whole authentication phase would be
a pass-through between the ManageSieve client and the
Dovecot authentication daemon. After all, all we need
in the end is a pass/fail decision and the username,
which Dovecot would pass back in its final
	OK <id> user=<username>
reply, so that everything else could be considered
opaque. Granted, right now the only advantage would
be to allow other mechanisms if available in Dovecot.
All the other plugins, including SASL via saslauthd,
are limited to PLAIN. Oh well, maybe some day...

		Philippe.

-- 
Philippe Levan - Frontier/epix Systems