Hi Axel, I didn't have the luxury of switching; I'm going to look at the aox code in the next few days as this has a knock on effect on a project I have so I need to fix it.
Thanks for confirming you'd had issues as it lets me know it's not just some quirk I have. Jim On 03/10/2014 12:52, Axel Rau wrote: > I have problems with DIGEST-MD5 since I remember, but never tracked it down > like you did. > We accept only SSL connections and so used plaintext password as workaround. > > Am 03.10.2014 um 12:33 schrieb NSS Ltd <[email protected]>: > > . . . > >> Oct 3 10:08:51 messaging Archiveopteryx: 7591/6/8/4/1 resp >> <<"9e5ee49ef8d07b875d7fff80274b8c73">> has length 34 (not 32) in >> DIGEST-MD5 response >> >> Which indicated the parsing of the MD5 auth response did not like the >> quoting of the response element - the quotes add 2 characters giving 34 >> instead of expected 32. >> >> As I had the source code to MailKit, I was able to alter the relevant >> section to remove the quotations, firstly from just the response element >> but that still failed. I then altered it so quoting was removed from >> qop, response and algorithm and then I could authenticate. (The >> benefits of open source!) >> >> However, this looks like an interoperability issue on the Archiveopteryx >> side. >> >> As I've been working on this other project and not had much time >> recently, it looks like I need to come back round to aox and look at >> that auth code as it should permit some additional quotation by the >> looks of things. >> >> Any thoughts/comments ? > Axel > --- > PGP-Key:29E99DD6 ☀ +49 151 2300 9283 ☀ computing @ chaos claudius >
