This is a log from a different mystic mailer. In this case the mailer is presenting the password in plain text and it does match what I have in my binkit.ini and I do have "AllowPlainPassword=true" in there also. For some reason it is also considered an unsecure session.
Mar 12 13:18:52 trmb synchronet: srvc 0054 BINKP Sent M_OK command args: non-secure
Mar 12 13:18:52 trmb synchronet: srvc 0054 BINKP Sent M_OK command
args: non-secure
This indicates that the password for the link has either been unconfigured, configured as blank, or just '-'. Is any of that possible?
Re: Binkit <-> Mystic
By: Digital Man to Al on Mon Mar 12 2018 02:42 pm
Mar 12 13:18:52 trmb synchronet: srvc 0054 BINKP Sent M_OK command
args: non-secure
This indicates that the password for the link has either been unconfigured, configured as blank, or just '-'. Is any of that possible?
No, that mailer sent the password correctly in plain text, I obfuscated it.
Mar 12 13:18:52 trmb synchronet: srvc 0054 BINKP Got M_PWD command args: XXXXXX XX
When I get mail/files from that node the session is non-secure (even though the password is correct) and files arrive in my unsecure inbound. When sbbsecho runs the incoming pkts are renamed to bad and I have to move them to the secure inbound directory and rename them back to pkt and retoss them.
Sessions with this node, and other mystic nodes work well when run from a binkout or binkpoll event.
This a log from a binkpoll event with the same node, it is a secure session and mail is received in my secure inbound.
Did the M_PWD args begin with "CRAM-MD5-"?
If you could update both binkp.js and binkit.js from CVS and capture another inbound session and paste the output here, that'd be helpful.
If you could update both binkp.js and binkit.js from CVS and capture another inbound session and paste the output here, that'd be helpful.
Re: Binkit <-> Mystic
By: Digital Man to Al on Tue Mar 13 2018 02:44 pm
If you could update both binkp.js and binkit.js from CVS and capture another inbound session and paste the output here, that'd be helpful.
Updated and this is a fresh capture from the same node with plain text password.
Unfortunately the log output you pasted is *only* the debug level log output. There are other (non-debug level) log messages which help to provide context and will be required to resolve this issue. Can you provide me the log output of the session with *all* the log messages?
Mar 14 11:40:42 trmb synchronet: srvc 0054 BINKP CRAM-MD5 required (and not pro vided) by 316:36/1@whispnet
This is that nodes entry in binkit.ini
[316:36/1]
Host=vintagebbsing.com
Password=XXXXXXXX
Poll=true
AllowPlainPassword=true
AllowUnencrypted=true
Okay, I think I just committed a fix for that problem. Please cvs update and try again.
Also, the inter-mixed (all log-level) log output is the most helpful - for the future.
Re: Binkit <-> Mystic
By: Digital Man to Al on Wed Mar 14 2018 03:02 pm
Okay, I think I just committed a fix for that problem. Please cvs update and try again.
It looks like it is working now. Thank you for working on this.
Also, the inter-mixed (all log-level) log output is the most helpful - for the future.
That would be better. I have never changed the log settings in sbbs.ini from the defaults because I don't know what would be better.
Would setting LogFacility=Local1 result in an intermixed log?
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 06:46:17 |
Calls: | 510 |
Messages: | 220571 |