Re: Bug with mupdatetest and CRAM-MD5
Etienne Goyer wrote:
Hi,
I have been getting this error lately when using mupdatetest :
[EMAIL PROTECTED] root]# mupdatetest -a mailadmin -u mailadmin mupdate
S: * AUTH "CRAM-MD5"
S: * PARTIAL-UPDATE
S: * OK MUPDATE "mupdate" "Cyrus Murder" "v2.2.6" "(master)"
C: A01 AUTHENTICATE "CRAM-MD5"{0+}
C:
S: A01 BAD "Extra arguments"
base64 decoding error
Authentication failed. generic failure
Security strength factor: 0
This is fixed in Cyrus 2.2.7+.
https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/cyrus/imtest/imtest.c.diff?r1=1.101&r2=1.102
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Bug with mupdatetest and CRAM-MD5
Hi,
I have been getting this error lately when using mupdatetest :
[EMAIL PROTECTED] root]# mupdatetest -a mailadmin -u mailadmin mupdate
S: * AUTH "CRAM-MD5"
S: * PARTIAL-UPDATE
S: * OK MUPDATE "mupdate" "Cyrus Murder" "v2.2.6" "(master)"
C: A01 AUTHENTICATE "CRAM-MD5"{0+}
C:
S: A01 BAD "Extra arguments"
base64 decoding error
Authentication failed. generic failure
Security strength factor: 0
Then, the connection idle there until I hit Ctrl-C. I guess the extra
argument is the {0+} on the AUTHENTICATE line, which seem redundant to
me. Is this a known problem ? If not, I am willing to make more test
to isolate the cause, if somebody can point me in the right direction.
Thanks all !
--
:wq
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
