On Wed, 2010-08-04 at 11:49 -0500, C. Bensend wrote:
> >> > username NUL username NUL password
> >>
> >> It's username then password.
> >
> > What about the NUL characters in the middle? Those are important.
>
> U... I wrote a quick perl script to decrypt the string and
> print it out... I'l
>> > username NUL username NUL password
>>
>> It's username then password.
>
> What about the NUL characters in the middle? Those are important.
U... I wrote a quick perl script to decrypt the string and
print it out... I'll have to look at how to tell if there are
NUL chars in there.
>>
On Wed, 2010-08-04 at 11:07 -0500, C. Bensend wrote:
> > So it's either
> >
> > NUL username NUL password
> >
> > or
> >
> > username NUL username NUL password
>
> It's username then password.
What about the NUL characters in the middle? Those are important.
> Should I try the straight dovecot p
> So it's either
>
> NUL username NUL password
>
> or
>
> username NUL username NUL password
It's username then password.
> Wonder if it has to do with a single process doing multiple lookups.
> That's the main difference compared to SSH and pretty much everything
> else.
I upgraded the server
On Tue, 2010-08-03 at 21:18 -0500, C. Bensend wrote:
>Well, I cranked the debug back up all the way and captured the
> password. After whipping up a quick perl script to decode it,
> it gives me my username and password, end-to-end, no delimiter.
> Both the username and password are correct, a
> Did you check with auth_debug_passwords=yes what the password is? v1.2
> doesn't seem to log it clearly, but by base64 decoding resp= value you
> could see it.
Hi Timo,
Well, I cranked the debug back up all the way and captured the
password. After whipping up a quick perl script to decode
>> And sure enough, there it is:
>>
>>
>> Aug 3 12:15:23 fusion dovecot: auth(default): client in: AUTH 1
>> PLAIN service=imapsecured lip=127.0.0.1 rip=127.0.0.1
>> lport=143
>> rport=19068 resp=
>> Aug 3 12:15:23 fusion dovecot: auth(default): bsdauth(benny,127.0.0.1):
>> loo
On Tue, 2010-08-03 at 12:43 -0500, C. Bensend wrote:
> And sure enough, there it is:
>
>
> Aug 3 12:15:23 fusion dovecot: auth(default): client in: AUTH 1
> PLAIN service=imapsecured lip=127.0.0.1 rip=127.0.0.1 lport=143
> rport=19068 resp=
> Aug 3 12:15:23 fusion dov
>>The only error I get in the mail log is:
>>
>> Aug 3 11:00:09 fusion dovecot: imap-login: Aborted login (auth failed,
>> 1
>> attempts): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1,
>> secured
>
> Get it to log more with auth_verbose=yes, and perhaps even
> auth_debug_passwords=yes.
On Tue, 2010-08-03 at 11:10 -0500, C. Bensend wrote:
>The only error I get in the mail log is:
>
> Aug 3 11:00:09 fusion dovecot: imap-login: Aborted login (auth failed, 1
> attempts): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1,
> secured
Get it to log more with auth_verbose=yes, and
Hey folks,
I recently upgraded my mail server from an older OpenBSD -CURRENT
snapshot to the latest (Aug 1). As part of this upgrade, I updated
all of my packages to their latest versions.
Since this upgrade, dovecot has begun failing to authenticate
intermittently. I use it primarily fo
11 matches
Mail list logo
