Hi All,

Hub 4 has been upgraded to the newest pre-alpha of Mystic.

v1.12 A46 Windows/32 Compiled 2020/03/01 15:35:57

I also have port 24553 set up if anyone would like to try to use BINKPS.


---

Black Panther(RCS)
aka Dan Richter
Sysop - Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/32)
* Origin: fsxHUB Niba [NET4] (21:4/100)

Hello Black,

I also have port 24553 set up if anyone would like to try to use
BINKPS.

I'm going to poll you here in the next little bit with the options g00r00 suggested. If it works I'll keep on doing that. I'm not sure if that will work or not.

If you like you can send stuff to my binkps port, 24553. I have not heard of anyone having a successfull poll or not aside from 1 link using binkd so I'm not sure that will work.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 01 Mar 2020, Al said the following...

If you like you can send stuff to my binkps port, 24553. I have not
heard of anyone having a successfull poll or not aside from 1 link using binkd so I'm not sure that will work.

12:43:41 Poll BINKP node via address lookup: 21:4/106
12:43:41 1-Polling 21:4/106 on slot 1 via BINKP
12:43:41 1-Connecting to trmb.ca on port 24553
12:43:42 1-Connected by IPV4 SSL to 172.105.21.200
12:43:42 1-System The Rusty MailBox
12:43:42 1-SysOp Alan Ianson
12:43:42 1-Location Penticton, BC Canada
12:43:42 1-Info NDL 115200,CM,XW,IBN
12:43:42 1-Info TIME Sun, 1 Mar 2020 11:43:40 -0800
12:43:42 1-Mailer binkd/1.1a-101/Linux binkp/1.1
12:43:42 1-Info TRF 0 0
12:43:42 1-Session ended (0 sent, 0 rcvd, 0 skip)
12:43:43 Polled 1 systems

Looks like it worked from this end. :)


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Hello Black,

12:43:41 Poll BINKP node via address lookup: 21:4/106
12:43:41 1-Polling 21:4/106 on slot 1 via BINKP
12:43:41 1-Connecting to trmb.ca on port 24553
12:43:42 1-Connected by IPV4 SSL to 172.105.21.200
12:43:42 1-System The Rusty MailBox
12:43:42 1-SysOp Alan Ianson
12:43:42 1-Location Penticton, BC Canada
12:43:42 1-Info NDL 115200,CM,XW,IBN
12:43:42 1-Info TIME Sun, 1 Mar 2020 11:43:40 -0800
12:43:42 1-Mailer binkd/1.1a-101/Linux binkp/1.1
12:43:42 1-Info TRF 0 0
12:43:42 1-Session ended (0 sent, 0 rcvd, 0 skip)
12:43:43 Polled 1 systems

Looks like it worked from this end. :)

It did! We are good to go for binkps. Real headway. :)

Here's my poll to your node..


=== Cut ===
+ 01 Mar 11:50:32 [2195] call to 21:4/100@fsxnet
+ 01 Mar 11:50:32 [2195] External command 'openssl s_client -quiet -alpn binkp -cipher ALL:@SECLEVEL=0 -connect bbs.castlerockbbs.com:24553' started, pid 2196
01 Mar 11:50:32 [2195] connected
+ 01 Mar 11:50:32 [2195] outgoing session with bbs.castlerockbbs.com:24553
- 01 Mar 11:50:35 [2195] OPT CRAM-MD5-59b8f43506c5a21bd0f072306635af79
+ 01 Mar 11:50:35 [2195] Remote requests MD mode
- 01 Mar 11:50:35 [2195] SYS fsxHUB Niba [NET4]
- 01 Mar 11:50:35 [2195] ZYZ Black Panther
- 01 Mar 11:50:35 [2195] TIME Sun, 01 Mar 2020 12:50:36 -0700
- 01 Mar 11:50:35 [2195] VER Mystic/1.12A46 binkp/1.0
- 01 Mar 11:50:35 [2195] BUILD 2020/03/01 15:36:07 Windows/32
+ 01 Mar 11:50:35 [2195] addr: 21:4/100@fsxnet
+ 01 Mar 11:50:35 [2195] addr: 21:4/0@fsxnet
- 01 Mar 11:50:35 [31320] incoming from 127.0.0.1 (47410)

And here is the start of an incoming poll from your node. The 127.0.0.1 tells me the poll was answered by my webserver on port 24553 and was passed to my running binkd.

+ 01 Mar 11:50:35 [2197] incoming session with localhost [127.0.0.1]
+ 01 Mar 11:50:35 [2195] pwd protected session (MD5)
- 01 Mar 11:50:35 [2195] QSIZE 0 files 0 bytes
+ 01 Mar 11:50:35 [2195] done (to 21:4/100@fsxnet, OK, S/R: 0/0 (0/0 bytes))
01 Mar 11:50:35 [2195] session closed, quitting...
01 Mar 11:50:35 [2195] rc(2196)=0
01 Mar 11:50:35 [2194] rc(2195)=0
01 Mar 11:50:35 [2194] the queue is empty, quitting...
- 01 Mar 11:50:35 [2197] SYS fsxHUB Niba [NET4]
- 01 Mar 11:50:35 [2197] ZYZ Black Panther
- 01 Mar 11:50:35 [2197] TIME Sun, 01 Mar 2020 12:50:36 -0700
- 01 Mar 11:50:35 [2197] VER Mystic/1.12A46 binkp/1.0
- 01 Mar 11:50:35 [2197] BUILD 2020/03/01 15:36:07 Windows/32
+ 01 Mar 11:50:35 [2197] addr: 21:4/100@fsxnet
+ 01 Mar 11:50:35 [2197] addr: 21:4/0@fsxnet
+ 01 Mar 11:50:35 [2197] pwd protected session (MD5)
- 01 Mar 11:50:36 [2197] QSIZE 1 files 1,135 bytes
- 01 Mar 11:50:36 [2197] receiving 0000fffa.su9 (1135 byte(s), off 0)
+ 01 Mar 11:50:36 [2197] 0000fffa.su9 -> /usr/local/fido/inbound/0000fffa.su9
01 Mar 11:50:36 [2197] got *.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z], delayed starting /usr/local/bin/hpt-incoming.sh
+ 01 Mar 11:50:36 [2197] rcvd: 0000fffa.su9 (1135, 1135.00 CPS, 21:4/100@fsxnet)
+ 01 Mar 11:50:36 [2197] done (from 21:4/100@fsxnet, OK, S/R: 0/1 (0/1135 bytes))
01 Mar 11:50:36 [2197] Running /usr/local/bin/hpt-incoming.sh
- 01 Mar 11:50:36 [2197] executing `/usr/local/bin/hpt-incoming.sh'
- 01 Mar 11:50:36 [2197] rc=0
=== Cut ===

If I'm not mistaken we have binkps working between us. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 01 Mar 2020, Al said the following...

If I'm not mistaken we have binkps working between us. :)

It sure looks like it. I am also able to use binkds between hub 4 and hubs 1 and 3. Hub 2 is getting an unable to connect yet...


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Hello Black,

If I'm not mistaken we have binkps working between us. :)

It sure looks like it. I am also able to use binkds between hub 4 and
hubs 1 and 3. Hub 2 is getting an unable to connect yet...

I have connected binkps to hub 1 also but am having a problem with hub 3 and I'm unsure of just why that is. Hub 2 might need an upgrade.

I have found with binkd adding -cipher ALL:@SECLEVEL=1 works well. I see no difference between a binkp or binkps poll. SECLEVEL=0 succeeds also but it takes time to negotiate. SECLEVEL=2 fails.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 01 Mar 2020 at 12:12p, Al pondered and said...

If I'm not mistaken we have binkps working between us. :)

How cool is that :)

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

On 01 Mar 2020 at 01:50p, Black Panther pondered and said...

It sure looks like it. I am also able to use binkds between hub 4 and
hubs 1 and 3. Hub 2 is getting an unable to connect yet...

Are you using MIS POLL SEND now Dan for mailin / mailout? It's fast.

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

Hello Avon,

If I'm not mistaken we have binkps working between us. :)

How cool is that :)

+----------Coolness-O-Meter----------+
| Meh | Uh Huh | OK | Sure | Whammo! |
+------------------------------------+
| | | | | XXXXX |
+------------------------------------+


I think we are in a pretty good place now and getting better as we go. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

It did! We are good to go for binkps. Real headway. :)
+ 01 Mar 11:50:32 [2195] External command 'openssl s_client -quiet -alpn binkp -cipher ALL:@SECLEVEL=0 -connect bbs.castlerockbbs.com:24553'

Awesome progress!

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

I have found with binkd adding -cipher ALL:@SECLEVEL=1 works well. I see no difference between a binkp or binkps poll. SECLEVEL=0 succeeds also
but it takes time to negotiate. SECLEVEL=2 fails.

This sounds about right. SECLEVEL=1 means 1024 bit key minimum which Mystic used (and now uses 2048 assuming it doesn't create issues). If memory serves me I believe I made my key 1024 to match what Synchronet was using for compatibility back then so it should fix it for Synchronet connections too.

Seems like until somewhat recently SECLEVEL=1 was the default for OpenSSL so it wasn't needed on the command line.

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

On 02 Mar 2020, Avon said the following...

It sure looks like it. I am also able to use binkds between hub 4 and hubs 1 and 3. Hub 2 is getting an unable to connect yet...

Are you using MIS POLL SEND now Dan for mailin / mailout? It's fast.

Yes, it is a huge time saver! I'm loving it! ;)

Great job, g00r00! :)


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Hello g00r00!

On 02 Mar 2020, g00r00 said the following...

This sounds about right. SECLEVEL=1 means 1024 bit key minimum which Mystic used (and now uses 2048 assuming it doesn't create issues). If

Does that mean that the very very latest prealpha (probably later than the
one I installed yesterday morning) auto-creates a 2048-bit SSL key/certificate if I would shutdown MIS, remove data/ssl.ssl.cert, and relaunch MIS?

(Mine is from last summer so I guess it's 1024-bit?)

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 01 Mar 2020 at 12:05p, Black Panther pondered and said...

I also have port 24553 set up if anyone would like to try to use BINKPS.

NET 1 is now polling NET 4 using BinkP SSL

Status ─────────────────────────────────────────────────────
19:45:53 Poll BINKP node via address lookup: 21:4/100
19:45:53 1-Polling 21:4/100 on slot 1 via BINKP
19:45:53 1-Connecting to bbs.castlerockbbs.com on port 24553
19:45:54 1-Connected by IPV4 SSL to 184.155.113.241
19:45:54 1-System fsxHUB Niba [NET4]
19:45:54 1-SysOp Black Panther
19:45:54 1-Info TIME Sun, 01 Mar 2020 23:45:59 -0700
19:45:54 1-Mailer Mystic/1.12A46 binkp/1.0
19:45:54 1-Info BUILD 2020/03/01 15:36:07 Windows/32
19:45:55 1-Remote Queue: 0 files 0 bytes
19:45:55 1-Session ended (0 sent, 0 rcvd, 0 skip)
19:45:57 Polled 1 systems

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

Does that mean that the very very latest prealpha (probably later than
the one I installed yesterday morning) auto-creates a 2048-bit SSL key/certificate if I would shutdown MIS, remove data/ssl.ssl.cert, and relaunch MIS?

Yes, this exactly.

I don't know if I have uploaded a prealpha build since I made that change,
but I am about to upload a new build for testing and it will be in that
build. If you delete the ssl.cert it will recreate one that should be 2048 bit.

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

On Sun, 1 Mar 2020 15:36:10 -0800
"Al -> Avon" <0@106.4.21> wrote:

Hello Avon,

If I'm not mistaken we have binkps working between us. :)

How cool is that :)

+----------Coolness-O-Meter----------+
| Meh | Uh Huh | OK | Sure | Whammo! |
+------------------------------------+
| | | | | XXXXX |
+------------------------------------+

I think we are in a pretty good place now and getting better as we
go. :)

Good start, but there is room for much more coolness. Using obsoleted encryption is kind of uncool ;).

Me and my fidonet uplink are using binkps with TLS 1.3 for quite some time now.
Beat that! :-P

I hope all the binkps implementations will be compatible to each other and using recent TLS standards at some point.

---
* Origin: REPLY (21:1/151)

Hello Oli,

Good start, but there is room for much more coolness. Using obsoleted encryption is kind of uncool ;).

Yep, there probably is. If we can get these mailers talking securely we can always settle on a good default way of doing it.

Me and my fidonet uplink are using binkps with TLS 1.3 for quite some
time now. Beat that! :-P

This is the openssl command I use that you gave me a month or three ago for the
node line..

-pipe "openssl s_client -quiet -alpn binkp -connect *H:*I"

Does that give you a TLS 1.3 session? Is that a good default?

I've added -cipher ALL:@SECLEVEL=1 and that is working with Mystic. I had a failure with Synchronet that might be fixed with a certificate update. I'll try
that again tomorrow.

I hope all the binkps implementations will be compatible to each other
and using recent TLS standards at some point.

Yep, that seems to be coming together.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 02 Mar 2020, g00r00 said the following...

Does that mean that the very very latest prealpha (probably later tha the one I installed yesterday morning) auto-creates a 2048-bit SSL key/certificate if I would shutdown MIS, remove data/ssl.ssl.cert, an relaunch MIS?

Yes, this exactly.

I don't know if I have uploaded a prealpha build since I made that
change, but I am about to upload a new build for testing and it will be
in that build. If you delete the ssl.cert it will recreate one that should be 2048 bit.

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)

Why not add to build A46.A1

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