This very minor "hotfix" release brings the Windows version of BinkD to
the 1.1a-27 build-level with native IPV6 connectivity support... along
with some minor things I wrote over the past few months.

Once things settle down with getting nodes online in WWIVnet-FTN, I will upgrade things over here. Still learning some little things that need to be adjusted for compatability between systems.

It seems the CRAM-MD5 setting in Mystic doesn't handshake properly with D'Bridge's BinkD. Not sure if that is because I'm running an older version of BinkD or not.

I will test that out later once things settle down.

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (1:261/1304.0)

Installed a little while ago and everything is okay so far.

█████████████████████████████████████████████████████████████
█════█ █════█ █════█ █════█ █════█ █════█
█ █════█ █════█ █════█ █════█ █════█ █
█════█ █════█ █════█ █════█ █════█ █════█
█ █════█ █════█ █
█════█ █════█
█ D'Bridge EMAIL System █
Copyright (c) by Nick J. Andre, Ltd.

[...]

D'Bridge should now be 100% IPV6-capable and ready...

Great! Now some of us have to get our ISPs to enable it.

[...]

NOTE: Refer to the revised README file to install D'Bridge on Windows 10.

Done and working well.

NOTE: The structure of the Echomail database file DBRIDGE.ADF has been changed in this release. Refer to TECHSPEC.TXT.

- Random problems with "Error: Invalid parameter 'U', reverting back to previous configuration" and related weird nonsense from BinkD is fixed.

- An option has been added for saving the kludge-lines in archived messages, on a per-echo basis, in Editor - Echo areas. This question
works in conjunction with DBUTIL PURGE. So now, you can have your choice
of having some areas with the kludges archived, and some without... you
get the idea.

That was a greqt idea! Many thanks.

[...]

- Two additional security checks are done as part of the mailer's much
more comprehensive "baseline check" against mail-bombs, invalid packets
and so on that was introduced from before.

- DBUTIL QNAME just reports the Queue name... Duhhhhhhhh.

LOL!


Regards,

Roger

--- DB 3.99 + Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna (1:3828/7)

On 06/12/16, Mark Hofmann said the following...

It seems the CRAM-MD5 setting in Mystic doesn't handshake properly with D'Bridge's BinkD. Not sure if that is because I'm running an older version of BinkD or not.

It does handshake OK with Mystic. Here is a log snippit of a session we had
not long ago..

Jun 12 14:54:05 0 Connect: 69.251.83.134 (c-69-251-83-134.hsd1.md.comcast.net) Jun 12 14:54:05 1 Recv: NUL SYS Weather Station Hub
Jun 12 14:54:05 1 Authorization State: 0 HH:1 NH:0
Jun 12 14:54:05 1 SYS Weather Station Hub
Jun 12 14:54:05 1 Sent: NUL OPT CRAM-MD5-d9d3b2e95635d7389a3cfcdb17b2019d
Jun 12 14:54:05 1 Recv: NUL ZYZ Mark Hofmann
Jun 12 14:54:05 1 Authorization State: 1 HH:1 NH:0
Jun 12 14:54:05 1 ZYZ Mark Hofmann
Jun 12 14:54:05 1 Sent: NUL SYS The Rusty MailBox
Jun 12 14:54:05 1 Sent: NUL ZYZ Alan Ianson
Jun 12 14:54:05 1 Sent: NUL VER Mystic/1.12A18 binkp/1.0
Jun 12 14:54:05 1 Sent: ADR 1:153/757@fidonet 9:91/21@survnet 21:1/110@fsxnet 4:240/1@sportnet 24:240/0@sportnet 24:240/2@sportnet 40:100/36@cybernet 44:250/ @dorenet 46:1/161@agoranet 454:1/757@ilink 618:500/18@micronet 11:1/201@wwivftn Jun 12 14:54:05 1 Recv: NUL LOC Bel Air, Maryland/USA
Jun 12 14:54:05 1 Authorization State: 3 HH:1 NH:0
Jun 12 14:54:05 1 LOC Bel Air, Maryland/USA
Jun 12 14:54:05 1 Recv: NUL NDL 9600,TCP,BINKP
Jun 12 14:54:05 1 NDL 9600,TCP,BINKP
Jun 12 14:54:05 1 Recv: NUL TIME Sun, 12 Jun 2016 17:54:05 -0400
Jun 12 14:54:05 1 TIME Sun, 12 Jun 2016 17:54:05 -0400
Jun 12 14:54:05 1 Recv: NUL VER binkd/1.0a-521/Win32 binkp/1.1
Jun 12 14:54:05 1 VER binkd/1.0a-521/Win32 binkp/1.1
Jun 12 14:54:05 1 Recv: ADR 1:261/1@fidonet 1:261/0@fidonet 11:1/100@wwivftn 1:1/131@fsxnet 33:1/4@dovenet 44:443/0@dorenet 46:1/163@agoranet 618:100/13@mic onet
Jun 12 14:54:05 1 ADR 1:261/1@fidonet 1:261/0@fidonet 11:1/100@wwivftn 21:1/13 @fsxnet 33:1/4@dovenet 44:443/0@dorenet 46:1/163@agoranet 618:100/13@micronet Jun 12 14:54:05 1 Recv: NUL OPT NDA EXTCMD CRYPT
Jun 12 14:54:05 1 Authorization State: 4 HH:1 NH:0
Jun 12 14:54:05 1 OPT NDA EXTCMD CRYPT
Jun 12 14:54:05 1 Received challenge (d9d3b2e95635d7389a3cfcdb17b2019d)
Jun 12 14:54:05 1 Authorization State: 4 HH:0 NH:1
Jun 12 14:54:06 1 Recv: NUL TRF 0 409
Jun 12 14:54:06 1 Authorization State: 4 HH:1 NH:0
Jun 12 14:54:06 1 TRF 0 409
Jun 12 14:54:06 1 Recv: PWD CRAM-MD5-527e3235c5518bb50339325ba3681aa8
Jun 12 14:54:06 1 Received PWD frame
Jun 12 14:54:06 1 Remote: MD5=1 AKA= 1:261/1@fidonet 1:261/0@fidonet 11:1/100@w ivftn 21:1/131@fsxnet 33:1/4@dovenet 44:443/0@dorenet 46:1/163@agoranet 618:100 13@micronet
Jun 12 14:54:06 1 Looking for matching AKA in EchoNodes
Jun 12 14:54:06 1 Authenticating 11:1/100@wwivftn by CRAM-MD5
Jun 12 14:54:06 1 Password accepted
Jun 12 14:54:06 1 Sent: OK secure
Jun 12 14:54:06 1 Queuing for 11:1/100@wwivftn by CRAM-MD5
Jun 12 14:54:06 1 Password accepted
Jun 12 14:54:06 1 Queued 0 files for 11:1/100
Jun 12 14:54:06 1 State RxS:1 TxS:1 HH:0 NH:1
Jun 12 14:54:06 1 Sent: EOB
Jun 12 14:54:06 1 Recv: FILE 0000FF9B.SU0 409 1465768321 0
Jun 12 14:54:06 1 State RxS:1 TxS:4 HH:1 NH:0
Jun 12 14:54:06 1 Receiving 0000FF9B.SU0 (409 bytes)
Jun 12 14:54:06 1 State RxS:2 TxS:4 HH:0 NH:1
Jun 12 14:54:06 1 Recv: Data 409/409
Jun 12 14:54:06 1 State RxS:2 TxS:4 HH:1 NH:0
Jun 12 14:54:06 1 Received Rx Data 409
Jun 12 14:54:06 1 Sent: GOT 0000FF9B.SU0 409 1465768321
Jun 12 14:54:06 1 State RxS:1 TxS:4 HH:0 NH:1
Jun 12 14:54:06 1 Recv: EOB
Jun 12 14:54:06 1 State RxS:1 TxS:4 HH:1 NH:0
Jun 12 14:54:06 1 Session complete (0 sent, 1 rcvd, 0 skip)

So I think you are OK to use MD5 with Mystic. It will work without it the password will be sent in plain text, but as you can see from the above.. MD5 does work with Mystic.. :)

Ttyl :-),
Al

--- Mystic BBS v1.12 A18 (Linux)
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

VERSION 3.99 SERVICE RELEASE 10 - JUNE 11 2016

So far so good on the point system! ;)

Shawn

--- TimEd and D'Bridge
* Origin: Tiny's Trailer (1:229/452.1)

So I think you are OK to use MD5 with Mystic. It will work without it the password will be sent in plain text, but as you can see from the above.. MD5 does work with Mystic.. :)

Fantastic, thanks for validating. Now the only question is why at least (3) Mystic systems had to disable CRAM-MD5 for our connection to work.

Maybe running different versions of Mystic or some other configuration thing?

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (1:261/1304.0)

14 Jun 16 10:59, you wrote to Alan Ianson:

So I think you are OK to use MD5 with Mystic. It will work without it
the password will be sent in plain text, but as you can see from the
above.. MD5 does work with Mystic.. :)

Fantastic, thanks for validating. Now the only question is why at
least (3) Mystic systems had to disable CRAM-MD5 for our connection to work.

mystic has/had two places to enable CRAM-MD5... one setting is to force CRAM-MD5 on all connections and the other is to enable/disable it for each individual system... the first one requires all connections to be secure so non-secure sessions will fail...

)\/(ark

Always Mount a Scratch Monkey

... "God is dead." - Nietzche.... "Nietzche is dead." - God
---
* Origin: (1:3634/12.73)