Re: recent update and plain auth

2014-10-21 Thread Eric Abrahamsen
Evgeniy Berdnikov writes: > On Tue, Oct 21, 2014 at 06:00:17PM +0800, Eric Abrahamsen wrote: >> What I just noticed is that the authenticate string that isync is >> sending to dovecot: >> >> ZXJpY0BwYXBlci1yZXB1YmxpYy5vcmcAZXJpYwBQUndvcms= >> >> Which is being rejected, is the correct string *m

Re: recent update and plain auth

2014-10-21 Thread Evgeniy Berdnikov
On Tue, Oct 21, 2014 at 06:00:17PM +0800, Eric Abrahamsen wrote: > What I just noticed is that the authenticate string that isync is > sending to dovecot: > > ZXJpY0BwYXBlci1yZXB1YmxpYy5vcmcAZXJpYwBQUndvcms= > > Which is being rejected, is the correct string *minus* the null > characters. Ie isyn

Re: recent update and plain auth

2014-10-21 Thread Eric Abrahamsen
Evgeniy Berdnikov writes: > On Tue, Oct 21, 2014 at 05:26:57PM +0800, Eric Abrahamsen wrote: >> >> Before I go pester someone else, my last question: >> >> For this example account, the AUTHENTICATE string should, as I >> understand it, be derivable like this: >> >> $ pas=$(echo -en "\0e...@pa

Re: recent update and plain auth

2014-10-21 Thread Eric Abrahamsen
Evgeniy Berdnikov writes: > On Tue, Oct 21, 2014 at 05:26:57PM +0800, Eric Abrahamsen wrote: >> >> Before I go pester someone else, my last question: >> >> For this example account, the AUTHENTICATE string should, as I >> understand it, be derivable like this: >> >> $ pas=$(echo -en "\0e...@pa

Re: recent update and plain auth

2014-10-21 Thread Evgeniy Berdnikov
On Tue, Oct 21, 2014 at 05:26:57PM +0800, Eric Abrahamsen wrote: > > Before I go pester someone else, my last question: > > For this example account, the AUTHENTICATE string should, as I > understand it, be derivable like this: > > $ pas=$(echo -en "\[email protected]\0ThisIsMyPassword" |

Re: recent update and plain auth

2014-10-21 Thread Eric Abrahamsen
Oswald Buddenhagen writes: > On Tue, Oct 21, 2014 at 04:07:15PM +0800, Eric Abrahamsen wrote: >> I set AuthMech to LOGIN, and mbsync connected, but then got a >> UIDVALIDITY error for each mailbox. >> > this is seriously weird. the UIDVALIDITY can only change due to some > server-side event. mayb

Re: recent update and plain auth

2014-10-21 Thread Oswald Buddenhagen
On Tue, Oct 21, 2014 at 04:07:15PM +0800, Eric Abrahamsen wrote: > I set AuthMech to LOGIN, and mbsync connected, but then got a > UIDVALIDITY error for each mailbox. > this is seriously weird. the UIDVALIDITY can only change due to some server-side event. maybe it is somehow bound to the configura

Re: recent update and plain auth

2014-10-21 Thread Eric Abrahamsen
Oswald Buddenhagen writes: > On Tue, Oct 21, 2014 at 12:04:50PM +0800, Eric Abrahamsen wrote: >> I don't care that much about security on my local machine, so I'm using >> the PLAIN auth mechanism. This worked fine until today's update. >> > well, no. it didn't, because isync didn't support PLAIN

Re: recent update and plain auth

2014-10-21 Thread Oswald Buddenhagen
On Tue, Oct 21, 2014 at 12:04:50PM +0800, Eric Abrahamsen wrote: > I don't care that much about security on my local machine, so I'm using > the PLAIN auth mechanism. This worked fine until today's update. > well, no. it didn't, because isync didn't support PLAIN until now - it used the legacy LOGI

recent update and plain auth

2014-10-20 Thread Eric Abrahamsen
The isync-git package for Archlinux has already updated, and I'm having a bit of trouble with local authentication with my local dovecot server. I've looked at the recent commits, and made most of the changes, but am still getting stuck. Here's an account, with the old config directives commented o