I did update the NET 2 HUB which is running Win/64 bit to

v1.12 A46 Windows/64 Compiled 2020/03/01 15:37:21

When I try to poll 1/100 from 2/100 I see this in the 2/100 logging

-------------------- POLL v1.12 A46 2020/03/01 Mon, Mar 02 2020 (loglevel
2)
+ 2020.03.02 02:23:25 Poll BINKP node via address lookup: 21:1/100
+ 2020.03.02 02:23:25 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.02 02:23:25 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.02 02:23:25 1-Connected by IPV4 to 219.89.83.33
+ 2020.03.02 02:23:28 1-Connection lost
+ 2020.03.02 02:23:28 1-Authorization failed
+ 2020.03.02 02:23:29 Polled 1 systems

--------------------- POLL v1.12 A46 2020/03/01 Mon, Mar 02 2020
(loglevel 2)
+ 2020.03.02 02:25:39 Poll BINKP node via address lookup: 21:1/100
+ 2020.03.02 02:25:39 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.02 02:25:39 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.02 02:25:39 1-Connected by IPV4 to 219.89.83.33
+ 2020.03.02 02:25:40 1-Error receiving data (Msg=RB Socket read buffer
result -1 10054 Size=5/5379) (Res=-1)
+ 2020.03.02 02:25:40 1-Connection lost
+ 2020.03.02 02:25:40 1-Authorization failed
+ 2020.03.02 02:25:41 Polled 1 systems


and at 1/100 I see this in the MIS logs

+ 2020.03.02 20:23:22 BINKP Received connection; Negotiating (for up to 30 seconds)
+ 2020.03.02 20:23:24 BINKP Cannot activate (Client sent obsolete handshake for the insecure SSLv2 protocol)

and

+ 2020.03.02 20:25:35 BINKP Received connection; Negotiating (for up to 30 seconds)
+ 2020.03.02 20:25:36 BINKP Cannot activate (Client sent obsolete handshake for the insecure SSLv2 protocol)

I can see there is a copy of CL64.DLL that is version 3.4.3.0

I'll try to update this to the one I am running at 1/100

[time passes]

Nope that didn't work

--------------------- POLL v1.12 A46 2020/03/01 Mon, Mar 02 2020 (loglevel 2) + 2020.03.02 02:31:58 Poll BINKP node via address lookup: 21:1/100
+ 2020.03.02 02:31:58 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.02 02:31:58 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.02 02:31:58 1-Connected by IPV4 to 219.89.83.33
+ 2020.03.02 02:32:03 1-Connection lost
+ 2020.03.02 02:32:03 1-Authorization failed
+ 2020.03.02 02:32:04 Polled 1 systems

and at 1/100

+ 2020.03.02 20:31:57 BINKP Received connection; Negotiating (for up to 30 sec + 2020.03.02 20:31:59 BINKP Cannot activate (Client sent obsolete handshake fo

The avove tests were using cl64.dll 3.4.4.1

I then tried cl32.dll 3.4.4.1 and also no joy (I expected it not to, as it is
a 64 bit version of Mystic NET 2 is using)

Here's where it got interesting.

I was stating port 24553 in the BinkP Hostname and SSL was set to yes.

Then I removed the port from the BinkP Hostname and kept SSL to yes and tested again with the new c164.dll 3.4.4.1 and it worked.

--------------------- POLL v1.12 A46 2020/03/01 Mon, Mar 02 2020 (loglevel 2) + 2020.03.02 02:46:13 Poll BINKP node via address lookup: 21:1/100
+ 2020.03.02 02:46:13 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.02 02:46:13 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.02 02:46:15 1-Connected by IPV4 SSL to 219.89.83.33
+ 2020.03.02 02:46:15 1-System fsxHUB Risa [NET1]
+ 2020.03.02 02:46:15 1-SysOp Avon
+ 2020.03.02 02:46:15 1-Info TIME Mon, 02 Mar 2020 20:46:11 +1300
+ 2020.03.02 02:46:15 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.03.02 02:46:15 1-Info BUILD 2020/03/01 15:36:07 Windows/32
+ 2020.03.02 02:46:16 1-Remote Queue: 1 files 8,745 bytes
+ 2020.03.02 02:46:16 1-Receiving: ffff0000.mod (8,745 bytes)
+ 2020.03.02 02:46:18 1-Session ended (0 sent, 1 rcvd, 0 skip)
+ 2020.03.02 02:46:18 Polled 1 systems

So there is something in this code that precludes a successful BinkP SSL session if the port is stated, but if it is not then the very same port
(24553) does work when polling 1/100

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

So there is something in this code that precludes a successful BinkP SSL session if the port is stated, but if it is not then the very same port (24553) does work when polling 1/100

I was able to find the issue and I have fixed it. I am uploading a new prealpha build now which will include this fix.

It also changes the "Crash Errors" tracker to reset to 0 every time it authenticates to an outbound BINKP connection. So its now officially the number of failed attempts since the last good attempt that is being tracked.

And it adds the SSL connection message as per requested!

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 02 Mar 2020 at 03:24p, g00r00 pondered and said...

I was able to find the issue and I have fixed it. I am uploading a new prealpha build now which will include this fix.

I will test tonight when I get home - thanks!

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)