On Fri, Sep 25, 2020 at 09:13:31AM +0100, doa379 wrote: > On 20-09-25 01:39:23, Oswald Buddenhagen wrote: > > On Thu, Sep 24, 2020 at 03:34:24PM +0100, doa379 wrote: > > > How come I can access this same account using isync-1.3.1 right now? > > > > > dunno. paste the full logs of mbsync -l -Dn for both versions. > > > Log from 1.3.3: > https://pastebin.com/KVUAFbZA > > > Log from 1.3.1: > https://pastebin.com/942Jr1fa > well, that's bizarre.
firstly, there is no discussion - the server *is* broken: it sends "ok" but acts as if the authentication had failed (subsequent commands that require authentication fail; also, it sends a second identical "hello", which seems a bit weird). the question is what triggers this bug ... the ip addresses are different in the logs, so you get routed to different servers in the cluster. try multiple runs each with the same version to rule out that the problem is actually a particular server. a more likely reason would be something that isn't visible in the log: ssl negotiation. try playing with sslversions, and/or see whether something sticks out of a wireshark log of the connection setup. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
