I have upgraded to Mystic v1.12 A46 as result, I have binkps running on
24553 in addition to binkp on the default port.

(I'm not sure where I should post this.. let me know if there's a better echo..)

matt // eggy
Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

--- Mystic BBS v1.12 A46 2020/03/15 (Linux/64)
* Origin: Eggy BBS (21:4/143)

I have upgraded to Mystic v1.12 A46 as result, I have binkps running on
24553 in addition to binkp on the default port.

(I'm not sure where I should post this.. let me know if there's a better echo..)

This is a good place I think.

Are you sending to to 4/100 over tls and is he sending to you? :)

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Are you sending to to 4/100 over tls and is he sending to you? :)

Hopefully soon.. I've contacted BP via netmail to make arrangements :)

matt // eggy
Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

--- Mystic BBS v1.12 A46 2020/03/15 (Linux/64)
* Origin: Eggy BBS (21:4/143)

Re: Finally upgraded to A46
By: eggy to All on Sun Mar 15 2020 08:41 pm

I have upgraded to Mystic v1.12 A46 as result, I have binkps running on 24553 in addition to binkp on the default port.
(I'm not sure where I should post this.. let me know if there's a better echo..)

Here is as good as any...

You might want to let your hub know if you want them to send you stuff over the
SSL connection. There isnt any way a non-configured system can do it (yet).

Perhaps we should lead the pack in that regard?
...deon


... Bosses come and bosses go, but a good secretary lasts forever.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On Sun, 15 Mar 2020 20:41:41 -0500
"eggy -> All" <0@143.4.21> wrote:

I have upgraded to Mystic v1.12 A46 as result, I have binkps running
on 24553 in addition to binkp on the default port.

not working with binkd / openssl:

+ 09:20 [7899] call to 21:4/143@fsxnet
+ 09:20 [7899] External command 'openssl s_client -quiet -connect eggy.fsxnet.nz:24553' started, pid 7900
09:20 [7899] connected
+ 09:20 [7899] outgoing session with eggy.fsxnet.nz:24554 1996398608:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:../ssl/statem/statem_lib.c:1929:
? 09:20 [7899] recv: connection closed by foreign host
+ 09:20 [7899] done (to 21:4/143@fsxnet, failed, S/R: 0/0 (0/0 bytes))
09:20 [7899] session closed, quitting...

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

On 15 Mar 2020, eggy said the following...

I have upgraded to Mystic v1.12 A46 as result, I have binkps running on 24553 in addition to binkp on the default port.

Could somebody test this with openssl for me? I'd like to verify folks are
able to connect from the outside as I think I have resolved my firewall
issues.

matt // eggy
Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: Eggy BBS (21:4/143)

I have upgraded to Mystic v1.12 A46 as result, I have binkps running 24553 in addition to binkp on the default port.

Could somebody test this with openssl for me? I'd like to verify folks
are able to connect from the outside as I think I have resolved my firewall issues.

So, how is A46, I see a lot of people have already swapped over. I've been dragging my feet...

|07E|10m|07b|10a|07l|10m|07e|10d |12-----------------------------------------------------
|09Black Lodge Research BBS |11blacklodgeresearch.org:4022
|11fsx|08Net: |0721:4/166 |11sci|08Net: |0777:1/133

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Black Lodge Research BBS (21:4/166)

On Thu, 19 Mar 2020 09:19:31 -0500
"eggy -> All" <0@143.4.21> wrote:

On 15 Mar 2020, eggy said the following...

I have upgraded to Mystic v1.12 A46 as result, I have binkps
running on 24553 in addition to binkp on the default port.

Could somebody test this with openssl for me? I'd like to verify
folks are able to connect from the outside as I think I have resolved
my firewall issues.

+ 17:25 [2698] call to 21:4/143@fsxnet
+ 17:25 [2698] External command 'openssl s_client -quiet -connect eggy.fsxnet.nz:24553' started, pid 2699
17:25 [2698] connected
+ 17:25 [2698] outgoing session with eggy.fsxnet.nz:24554 1995849744:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:../ssl/statem/statem_lib.c:1929:
? 17:25 [2698] recv: connection closed by foreign host
+ 17:25 [2698] done (to 21:4/143@fsxnet, failed, S/R: 0/0 (0/0 bytes))

Firewall seems to be okay, but Mystic is unable to speak TLS 1.2 - test failed.

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

Re: Re: binkps test A46 upgrade
By: eggy to All on Thu Mar 19 2020 09:19 am

Could somebody test this with openssl for me? I'd like to verify folks are able to connect from the outside as I think I have resolved my firewall issues.

Looks OK from me:

$ openssl s_client -quiet -connect eggy.fsxnet.nz:24553

depth=0 CN = eggy.cc
verify error:num=18:self signed certificate
verify return:1
depth=0 CN = eggy.cc
verify return:1
SYS Eggy BBS ...
...deon


... May you live all the days of your life.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)