Hi! I've tossed up a Mystic BBS 1.12 A47 system on a Ubuntu 22.04/amd64 system that I had spare. The biggest issue that I'm having at the moment is in getting SSH up and running. (Telnet works fine.)

I've set up the servers section to allow up to 20 nodes, and enabled Telnet on IPV4 with a maximum of 10 nodes, address 0.0.0.0 port 2323. All good there.

I've enabled SSH on IPV4 with a maximum of 10 nodes, address 0.0.0.0 port 2222. I've also followed the instructions here:

http://wiki.mysticbbs.com/doku.php?id=cryptlib

To setup cryptlib and place it in the /usr/lib folder. I've tried cryptlib 3.4.5 and 3.4.6. It took a little jiggering to get 3.4.5 to compile. 3.4.6 compiled right out of the box.

I've also stopped and started the BBS, disabled and enabled the protocols, etc., etc.

Each time, I can't connect via SSH. I've tried NetRunner on Windows, PuTTY on Windows, and ssh from the local command line of the system running the BBS.

Unlike other reports I've seen, nothing shows up in the mis.log or any of the node#.log files, so I don't really have any errors to go on either. With PuTTY or NetRunner it just sits there for a bit and disconnects. With ssh from the local command line,
I get a connection but again it just sits there and doesn't prompt for a password or anything. I can hit enter a bunch of times.

(Note that if I put an invalid port, it refuses connection right away, so *something* is happening.)

Any ideas on how to resolve this? I could try compiling various versions of cryptlib, but people keep saying 3.4.5 is good for this configuration, and also I don't even know if I need to "reset" the system somehow after replacing it.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

PuTTY on Windows, and ssh from the local command line of the system

when you do it from the command line try putting -c 3des-cbc at the end
it might be a cryptography problem

... Aluminum Dragons also do 3d6 of krinkle damage.

--- Mystic BBS v1.12 A48 2022/04/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbS>>20ForBeers.com:1337 (1:105/420)

On Saturday, May 7, 2022 at 11:20:40 PM UTC-4, drago marelic wrote:

PuTTY on Windows, and ssh from the local command line of the system

when you do it from the command line try putting -c 3des-cbc at the end
it might be a cryptography problem

When I try that, instead of hanging until I ^C it, it closes the connection immediately. So... different behaviour depending on protocol? Not sure if that's a step forward or not. :)

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Sunday, May 8, 2022 at 11:12:55 PM UTC-4, Irfon-Kim Ahmad wrote:

On Saturday, May 7, 2022 at 11:20:40 PM UTC-4, drago marelic wrote:

PuTTY on Windows, and ssh from the local command line of the system

when you do it from the command line try putting -c 3des-cbc at the end
it might be a cryptography problem

When I try that, instead of hanging until I ^C it, it closes the connection immediately. So... different behaviour depending on protocol? Not sure if that's a step forward or not. :)

Okay, I solved this. Documenting for anyone else who has this issue:

cryptlib 3.4.6 didn't work for me, but did generate a faulty ssl.cert file in "data". Trying any other version would thereafter fail (earlier versions wouldn't even load and listen, but 3.4.5 would fail because of the bat cert). Shutting down mis,
removing the cert file, replacing cryptlib with 3.4.5, starting it back up, trying a connection to let it generate a new cert file, and then reconnecting did the trick.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Okay, I solved this. Documenting for anyone else who has this issue:

cryptlib 3.4.6 didn't work for me, but did generate a faulty ssl.cert
file in "data". Trying any other version would thereafter fail (earlier versions wouldn't even load and listen, but 3.4.5 would fail because of the bat cert). Shutting down mis,
removing the cert file, replacing cryptlib with 3.4.5, starting it back up, trying a connection to let it generate a new cert file, and then reconnecting did the trick.

Thanks for the update and for letting us know!

3.4.5 is the version the website says is supported.

As you've found there is a 3.4.6 beta but it does not appear to work, unfortunately. I did spend some time to try to figure out why but I wasn't able to. I was mostly waiting for a 3.4.6 final version but it seems this beta/release candidate has been around for a long time now so I may need to rethink that approach.

... System halted - Press all keys at once to continue

--- Mystic BBS v1.12 A48 2022/04/26 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)