Evgeniy Berdnikov <[email protected]> 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 "\[email protected]\0ThisIsMyPassword" | base64) >> >> If I telnet into my local dovecot server, and issue ", authenticate >> plain", together with the string from above, it logs in correctly. > > Are strings identical that you posted here and have entered by hands? > Run "base64 -d" to decode and compare. Their contents are different.
That's because I very cleverly (and totally pointlessly) changed the actual password in my example. The actual password, since it doesn't matter at all, is "PRwork". That's the password in my ~/.mbsyncrc file, and in my /etc/dovecot/passdb file, and it's the password that works when I log on to local dovecot via telnet. 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 isync is sending the results of echo -en "[email protected]" | base64 while what works with dovecot is: echo -en "\[email protected]\0PRwork" | base64 I don't know what TRT to do is, here. Eric ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
