Hi, I am trying to make the switch to binkp from binkd and for some reason I am getting CRAM-MD5 password mismatch errors on both of my main connections
Fidonet - runs Taurus
Fsxnet - runs mystic
I have tried
BinkpAllowPlainText=true
BinkpAllowPlainAuth=no
Michael Pierce wrote to All <=-
Hi, I am trying to make the switch to binkp from binkd and for some
reason I am getting CRAM-MD5 password mismatch errors on both of my
main connections
Fidonet - runs Taurus
Fsxnet - runs mystic
I have tried
BinkpAllowPlainText=true
BinkpAllowPlainAuth=no
what am I missing?
---
= Synchronet = fluxcap.dynv6.net:2323 * Portland, OR
Al wrote to Michael Pierce <=-
Re: binkp
By: Michael Pierce to All on Wed Aug 01 2018 07:43 am
Hi, I am trying to make the switch to binkp from binkd and for some reason I am getting CRAM-MD5 password mismatch errors on both of my main connections
BinkpAllowPlainText=true
BinkpAllowPlainAuth=no
Mystic doesn't support crypt BinkpAllowPlainText must be set to true
for Mystic and any mailer that doesn't support CRYPT. You already have that.
Mystic supports CRAM-MD5 but it defaults to offf in the mystic echomail node settings. Ask that node to set CRAM-MD5 to yes, or set BinkpAllowPlainAuth to true for that node.
I had the same problem with one of the Hubs serving echomails and that was the issue, They have to force their Node to serve me CRAM-MD5. also I had to set BinkpAllowPlainAuth true and the problem was gone.
Binkit will accept an inbound session in plain text with the above set to true but it will never send the password in plain text (as far as I know).
On 08-01-18 18:59, Rmh wrote to Al <=-
I had the same problem with one of the Hubs serving echomails and that
was the issue, They have to force their Node to serve me CRAM-MD5. also
I had to set BinkpAllowPlainAuth true and the problem was gone.
Binkit will accept an inbound session in plain text with the above set
to true but it will never send the password in plain text (as far as I
know).
When initiating a connection with a BinkP server that doesn't support CRAM-MD5, (and the linked node wasn't configured to require CRAM-MD5), BinkIT will send the password in plain text.
Hi, I am trying to make the switch to binkp from binkd and for some
reason I am getting CRAM-MD5 password mismatch errors on both of my
main connections
Re: Re: binkp
By: Rmh to Al on Wed Aug 01 2018 06:59 pm
Hi, I am trying to make the switch to binkp from binkd and for some
reason I am getting CRAM-MD5 password mismatch errors on both of my
main connections
I have just noticed, that if I poll the node, it works, but if they poll me, I get the CRAM-MD5 mismatch error
I have just noticed, that if I poll the node, it works, but if they poll me, I get the CRAM-MD5 mismatch error
On 08-02-18 12:54, Al wrote to Michael Pierce <=-
The only solution is to set BinkpAllowPlainAuth = true, or a better solution is to ask your link to set CRAM-MD5 to yes at their end.
I have just noticed, that if I poll the node, it works, but if they poll I get the CRAM-MD5 mismatch error
What mailer software (and version) is the other node using?
Re: Re: binkp
By: Digital Man to Michael Pierce on Wed Aug 01 2018 09:21 pm
I have just noticed, that if I poll the node, it works, but if they poll I get the CRAM-MD5 mismatch error
What mailer software (and version) is the other node using?
Aug 2 06:53:37 fluxcap synchronet: evnt Running timed event: BINKPOLL
Aug 2 06:53:37 fluxcap synchronet: evnt BINKPOLL BinkIT/2.6 invoked with options: -p
Aug 2 06:53:37 fluxcap synchronet: evnt BINKPOLL Attempting poll for node 21:2/100@fsxnet
Aug 2 06:53:37 fluxcap synchronet: evnt BINKPOLL JSBinkP/1.109 callout to 21:2/100@fsxnet started
Aug 2 06:53:37 fluxcap synchronet: evnt BINKPOLL Connecting to error404bbs.ddns.net:24555
Aug 2 06:53:38 fluxcap synchronet: evnt BINKPOLL Peer version: Mystic/1.12A39 binkp/1.0
Hi, I am trying to make the switch to binkp from binkd and for some
reason I am getting CRAM-MD5 password mismatch errors on both of my
main connections
Fidonet - runs Taurus
Fsxnet - runs mystic
I have tried
BinkpAllowPlainText=true
BinkpAllowPlainAuth=no
what am I missing?
My settings for ctrl/sbbsecho.ini:
mark lewis wrote to Rmh <=-
@TZ: 40f0
On 2018 Aug 01 18:56:00, you wrote to Michael Pierce:
Hi, I am trying to make the switch to binkp from binkd and for some
reason I am getting CRAM-MD5 password mismatch errors on both of my
main connections
Fidonet - runs Taurus
Fsxnet - runs mystic
I have tried
BinkpAllowPlainText=true
BinkpAllowPlainAuth=no
what am I missing?
My settings for ctrl/sbbsecho.ini:
ummm... the above is about mailer settings... not tosser settings ;)
My settings for ctrl/sbbsecho.ini:
ummm... the above is about mailer settings... not tosser settings ;)
The tosser (sbbsecho), also negotiates the connection with the Hub,
mark lewis wrote to Rmh <=-
@TZ: 40f0
On 2018 Aug 04 15:51:00, you wrote to me:
My settings for ctrl/sbbsecho.ini:
ummm... the above is about mailer settings... not tosser settings ;)
The tosser (sbbsecho), also negotiates the connection with the Hub,
sorry, no it doesn't... the tossers do not negotiate... those values
the tossers are concerned with are already negotiated and configured by the operators of each of the involved systems long before the tossers even come into play to toss or pack the mail ;)
My settings for ctrl/sbbsecho.ini:
ummm... the above is about mailer settings... not tosser settings
;)
The tosser (sbbsecho), also negotiates the connection with the Hub,
sorry, no it doesn't... the tossers do not negotiate... those values
the tossers are concerned with are already negotiated and configured
by the operators of each of the involved systems long before the
tossers even come into play to toss or pack the mail ;)
True all what you have said.
When I spoke I had in mind where Synchronet was holding the configurations, so that file, but I completely messed up with what I
said. In a way, also catching up with SYnchronet, I am too new to the software and getting familiar to quite a few things. Also re-learning
the ways again as I have forgotten so much, just apologies.
* MysticBBS v1.12A39 at least has an issue when the CRYPT
* option is included after the CRAM-MD5 challenge. It appends
* three NULs to the end of the challenge data.
Tell the linked node to upgrade his copy of Mystic as this bug has been fixe
actually, v1.12A39 *IS* the most current version - I just installed it - soo please, WHAT other options are there to get these 2 to connect???
Re: Re: binkp
By: Digital Man to Michael Pierce on Thu Aug 02 2018 11:52 pm
* MysticBBS v1.12A39 at least has an issue when the CRYPT
* option is included after the CRAM-MD5 challenge. It appends
* three NULs to the end of the challenge data.
Tell the linked node to upgrade his copy of Mystic as this bug has been fixe
actually, v1.12A39 *IS* the most current version - I just installed it - soo please, WHAT other options are there to get these 2 to connect???
On 08-08-18 06:58, Al wrote to Michael Pierce <=-
I connect with three mystic systems with binkit. I don't see any
problem here. I have BinkpAllowPlainText = true and BinkpAllowPlainAuth
= false but those nodes have CRAM-MD5 = yes at their end. If you are getting errors about CRAM-MD5 set BinkpAllowPlainAuth = true and I
think you'll be OK.
I connect with three mystic systems with binkit. I don't see any
problem here. I have BinkpAllowPlainText = true and
BinkpAllowPlainAuth = false but those nodes have CRAM-MD5 = yes at
their end. If you are getting errors about CRAM-MD5 set
BinkpAllowPlainAuth = true and I think you'll be OK.
I'd be one of them? :)
On 08-08-18 19:29, Al wrote to Tony Langdon <=-
I'd be one of them? :)
QWK-net yes, binkit no.. although we could do that.
I connect with three mystic systems with binkit. I don't see any problem here. I have BinkpAllowPlainText = true and BinkpAllowPlainAuth = false but those nodes have CRAM-MD5 = yes at their end. If you are getting errors about CRAM-MD5 set BinkpAllowPlainAuth = true and I think you'll
be OK.
Or is there a different problem?
It looks like there's also a work-around in binkit.js for the
broken-CRAM logic in Mystic:
It looks like there's also a work-around in binkit.js for the broken-CRAM logic in Mystic:
I thought I'd let you know that I did get it all sorted - was actually a couple of problems, turns out when I put my fsxnet node # I transposed the node #
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 08:14:59 |
Calls: | 508 |
Messages: | 219950 |