Discussion:
0.9.4/0.9.9 CRAM-MD5 compatability problem?
(too old to reply)
Lars Kellogg-Stedman
2011-03-06 18:54:58 UTC
Permalink
I recently tried to get binkd 0.9.4 on my laptop talking to 0.9.9 on my
FreeBSD server. With CRAM-MD5 authentication enabled, I get an
"incorrect password" error... but if I modify the config on the calling
side to use only plaintext:

node 1:322/761 -nomd bbs.oddbit.com secret

Everything works fine. The *only* change I'm making is
enabling/disabling CRAM-MD5. The password matches on both systems.

Is this a known problem? Updating my laptop to 0.9.9 seems to have fixed
things, but is there a way to get 0.9.4 talking to 0.9.9 with CRAM-MD5?
I suspect this may have been some recent problems I had connecting to
my uplink.
Stas Degteff
2011-03-07 08:20:38 UTC
Permalink
Hello Lars.

06 Mar 11 21:54, you wrote to All:

LS> I recently tried to get binkd 0.9.4 on my laptop talking to 0.9.9 on
LS> my FreeBSD server. With CRAM-MD5 authentication enabled, I get
LS> an "incorrect password" error... but if I modify the config on the
LS> calling side to use only plaintext:

LS> node 1:322/761 -nomd bbs.oddbit.com secret

LS> Everything works fine. The *only* change I'm making is
LS> enabling/disabling CRAM-MD5. The password matches on both systems.

I don't remember similar bugreports. But the HISTORY file contains following
record:
=====
2004/10/18 13:29:35 1.0a-407 gul
md5b.c,2.8,2.9
Bugfix in MD_getChallenge(), thanks to Victor Levenets <***@takas.lt>
=====

If your copy of the binkd 0.9.4 is dated before 2004/10/18, this error was
showed at you, is possible.

And note.
You don't specifies the binkd full version information (not only version
number? but also date of build is needed!) In the future bug report messages
include a line of the version which the binkd started with the option "-v"
shows, please!

Stas
Jabber-ID: ***@grumbler.org
GPG key 0x72186DB9 (keyserver: hkp://wwwkeys.eu.pgp.net)
... Golded+, Husky & RNTrack maintainer, Binkd developer&webmaster
Loading...