Subj : D'Bridge 3.99/SR10 available
To : Mark Hofmann
From : Alan Ianson
Date : Sun Jun 12 2016 03:50 pm
On 06/12/16, Mark Hofmann said the following...
MH> It seems the CRAM-MD5 setting in Mystic doesn't handshake properly with
MH> D'Bridge's BinkD. Not sure if that is because I'm running an older
MH> 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)
