I am trying to connect two of my systems via binkp. On the synchronet side, I am running binkit. On the other, the linux binkd server. When the sbbs system polls the binkd system, the binkd side reports bad password, with the string being shown as "CRAM-MD5-blahblah". I have tried setting the following in my sbbsecho.ini file:
BinkpAllowPlainAuth=true
BinkpAllowPlainText=true
I have also tried '-nomd' on the binkd side. It is still either sending that CRAM string where binkd is expecting to find the password, or that string contains the encrypted password and it thinks it does not match.
I have checked the configs on both sides... it matches, although it is in all CAPS on both sides.
Anyone seen this before? Is there a way to get binkit to stop sending that CRAM-MD5 string all together since neither side is requiring CRAM?
BinkpAllowPlainAuth=true
BinkpAllowPlainText=true
I have also tried '-nomd' on the binkd side. It is still either sending that CRAM string where binkd is expecting to find the password, or that string contains the encrypted password and it thinks it does not match.
I have checked the configs on both sides... it matches, although it is in all CAPS on both sides.
I'm not sure why you are experiencing these failures. A space in your config file maybe, or an AKA typo?
I have checked the configs on both sides... it matches, although it is in >DW> all CAPS on both sides.I'm not sure why you are experiencing these failures. A space in your config file maybe, or an AKA typo?
I have checked the configs on both sides... it matches, although it is in >DW> all CAPS on both sides.I'm not sure why you are experiencing these failures. A space in your config file maybe, or an AKA typo?
Here is what the entry on the binkd side looks like... sbbs to follow...
node 1:2320/105.0@fidonet capitolcityonline.net:24554 PASSWORD
I included the port number, even though it is default, because on this machine the service entry is set up for the non-default port.
I am trying to connect two of my systems via binkp. On the synchronet side, I am running binkit. On the other, the linux binkd server. When the sbbs system polls the binkd system, the binkd side reports bad password, with the string being shown as "CRAM-MD5-blahblah". I have tried setting the following in my sbbsecho.ini file:
BinkpAllowPlainAuth=true
BinkpAllowPlainText=true
I have also tried '-nomd' on the binkd side. It is still either sending that CRAM string where binkd is expecting to find the password, or that string contains the encrypted password and it thinks it does not match.
I have checked the configs on both sides... it matches, although it is in all CAPS on both sides.
Anyone seen this before? Is there a way to get binkit to stop sending that CRAM-MD5 string all together since neither side is requiring CRAM?
Since I have never run binkd before, I am not sure if that CRAM-MD5 string that it says is an incorrect password contains the encrypted password, or if it is receiving that string where it expects a password.
On another note, for whatever reason, the binkd side (107) does not make the outgoing call to the binkit (105) machine. It will try to if something is waiting, but I do not see any evidence on the sbbs (105) machine of an inbound call ever being received.
There is no space in the "SessionPwd=" entry, but there also is not forany
of the other entries that were created when I ran the binkit command to merge the binkit.ini file into the sbbsecho.ini file.
The domain also needs to match.. @fidonet or @fsxnet etc.
or I?? another one that gets me recently is "rn" and "m"...
try this... set the password on both ends as "xxxxxxxx"... yes, eight lower case x... recycle both sides and then try again... if it still fails, the only other thing i can think of is maybe the clocks are too
far out of sync... they should be within a second or two of each
other...
Can you paste a log of the actual protocol transaction?
If the client (BinkD) side is sending the CRAM-MD5-blahblah and you're
not expecting that, then it sounds like it's the BinkD side that needs reconfiguration. No?
try this... set the password on both ends as "xxxxxxxx"... yes, eight lower case x... recycle both sides and then try again... if it still fails, the only other thing i can think of is maybe the clocks are too
far out of sync... they should be within a second or two of each
other...
I shall try that. The Binkd side does not have a trailing space for
sure, and both are in all caps and spelled right. I will check the
binkit config in a minute, though.
I tried that. Also made sure all of my akas on the binkit side had matching domain entries at the bottom of my sbbsecho.ini. Even with
the 8 x's, it still is giving me an incorrect password error.
My binkd installation reports as version 1.0.5-pre5. That is the
version that debian stretch stable has in its repository for 32-bit
linux machines. Maybe I should try to find a newer version?
I tried that. Also made sure all of my akas on the binkit side had matching domain entries at the bottom of my sbbsecho.ini. Even with
the 8 x's, it still is giving me an incorrect password error.
wow...
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 28 |
Nodes: | 8 (0 / 8) |
Uptime: | 189:14:55 |
Calls: | 2,004 |
Calls today: | 1 |
Files: | 11,114 |
Messages: | 942,265 |