I'm still seeing a problem when binkit receives in inbound call from a mystic mailer using CRAM-MD5 passwords. It is working well with a node that sends the password in plain text.
Hello Digital Man,
I'm still seeing a problem when binkit receives in inbound call from a mystic mailer using CRAM-MD5 passwords. It is working well with a node that sends the password in plain text.
This is a new error but unrelated I think.
Mar 17 14:15:56 trmb synchronet: srvc 0052 BINKP !JavaScript /sbbs/exec/binkit .js line 862: TypeError: this.command is undefined
When binkout or binkpoll runs I get successful sessions.
For some reason fidoin.now and tickit.now are not being touched when I receive mail or files when an event is run (binkout or binkpoll). They are touched when the binkp service receives files in a successful session with irex or binkd.
Re: binkit <-> mystic
By: Al to Digital Man on Sat Mar 17 2018 02:47 pm
I'm still seeing a problem when binkit receives in inbound call from a mystic mailer using CRAM-MD5 passwords. It is working well with a node that sends the password in plain text.
I think I have all the log output going into one file now also.. :)
Re: binkit <-> mystic
By: Al to Digital Man on Sat Mar 17 2018 02:47 pm
I'm still seeing a problem when binkit receives in inbound call from a mystic mailer using CRAM-MD5 passwords. It is working well with a node that sends the password in plain text.
I think I have all the log output going into one file now also.. :)
Can you try an experiment for me?
I don't have any inbound Mystic/BINKP connections, so I can't test this just yet. Look in exec/load/binkp.js for this line:
this.wont_crypt = false;
and change it to:
this.wont_crypt = true;
Can you try an experiment for me?
I don't have any inbound Mystic/BINKP connections, so I can't test this just yet. Look in exec/load/binkp.js for this line:
this.wont_crypt = false;
and change it to:
this.wont_crypt = true;
Re: binkit <-> mystic
By: Digital Man to Al on Thu Mar 22 2018 02:38 pm
Can you try an experiment for me?
I don't have any inbound Mystic/BINKP connections, so I can't test this just yet. Look in exec/load/binkp.js for this line:
this.wont_crypt = false;
and change it to:
this.wont_crypt = true;
Success.. Here is the log..
Mar 23 19:09:11 trmb synchronet: srvc 0054 BINKP Sent M_NUL command args: OPT CRAM-MD5-d783a3ee954673499d64a9966e25c0b9
Mar 23 19:09:11 trmb synchronet: srvc 0054 BINKP Sent M_NUL command
args: OPT CRAM-MD5-d783a3ee954673499d64a9966e25c0b9
If we send another option keyword after that that CRAM-MD5 challenge (string of hex-chars), what they call [othropt] in http://ftsc.org/docs/fts-1027.001, then the Mystic BinkP mailer fails
to compute the CRAM-MD5 response correctly. It's a bug in Mystic.
Success.. Here is the log..
Okay, thanks. That's not good new for Mystic however. :-(
Here's the relevant lines:
Mar 23 19:09:11 trmb synchronet: srvc 0054 BINKP Sent M_NUL command
args: OPT CRAM-MD5-d783a3ee954673499d64a9966e25c0b9
If we send another option keyword after that that CRAM-MD5 challenge (string of hex-chars), what they call [othropt] in http://ftsc.org/docs/fts-1027.001, then the Mystic BinkP mailer fails to compute the CRAM-MD5 response correctly. It's a bug in Mystic.
On 2018 Mar 24 00:04:48, you wrote to Al:
Mar 23 19:09:11 trmb synchronet: srvc 0054 BINKP Sent M_NUL command
args: OPT CRAM-MD5-d783a3ee954673499d64a9966e25c0b9
If we send another option keyword after that that CRAM-MD5 challenge (string of hex-chars), what they call [othropt] in http://ftsc.org/docs/fts-1027.001, then the Mystic BinkP mailer fails to compute the CRAM-MD5 response correctly. It's a bug in Mystic.
considering that mystic is an alpha, it isn't surprising, really... that's not a slap at mystic! just a note that running alpha code can cut you... i tried, years back in the 1.10 or 1.11 alphas, to get mystic to have alpha and beta team members to do initial and basic testing... then have gamma releases like their current alpha stuff but it didn't go anywhere... i don't know why traditional development has foregone that methodology and preferrs to make everyone an alpha tester :(
Digital Man wrote to mark lewis <=-
It's pretty similar with Synchronet: we have "releases" and everything else is a "development" or "experimental" version. No alpha/beta tags anymore. We're all testers. :-)
not a slap at mystic! just a note that running alpha code can cut you... i tried, years back in the 1.10 or 1.11 alphas, to get mystic to have alpha and beta team members to do initial and basic testing... then have gamma releases like their current alpha stuff but it didn't go anywhere... i don't know why traditional development has foregone that methodology and preferrs to make everyone an alpha tester :(
considering that mystic is an alpha, it isn't surprising, really...
that's not a slap at mystic! just a note that running alpha code can cut you... i tried, years back in the 1.10 or 1.11 alphas, to get mystic to have alpha and beta team members to do initial and basic testing... then have gamma releases like their current alpha stuff but it didn't go anywhere... i don't know why traditional development has foregone that methodology and preferrs to make everyone an alpha tester :(
considering that mystic is an alpha, it isn't surprising, really...
that's not a slap at mystic! just a note that running alpha code can
cut you... i tried, years back in the 1.10 or 1.11 alphas, to get
mystic to have alpha and beta team members to do initial and basic
testing... then have gamma releases like their current alpha stuff but
it didn't go anywhere... i don't know why traditional development has
foregone that methodology and preferrs to make everyone an alpha
tester :(
It's pretty similar with Synchronet: we have "releases" and everything else is a "development" or "experimental" version. No alpha/beta tags anymore. We're all testers. :-)
If 90% of the (already small) user base had to wait a year between each time they get new features to play with, I believe most would lose interest.
I'm not even sure what the difference between alpha, beta, etc.
would be..
James Coyle wrote to mark lewis <=-
It really just comes down to the size of the user base and the fact
that tinkering with new stuff is really what keeps people interested in the hobby.
If 90% of the (already small) user base had to wait a year between each time they get new features to play with, I believe most would lose interest. Mystic does have an alpha-beta cycle, it just doesn't use
that exact terminology and it doesn't privatize the releases.
Really the difference is only that anyone can choose to participate in whatever cycle they want to, instead of me hand picking people and excluding others.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 07:15:38 |
Calls: | 510 |
Messages: | 220571 |