Hey, all! I've got a new Mystic 1.12a47 system running on Ubuntu 22.04 server. So far so good, telnet access running smoothly.

However, I've followed the instructions on acquiring and compiling cryptlib and renaming/placing it in /usr/lib, with both cryptlib 3.4.5 and 3.4.6, and SSH doesn't connect. It just... silently hangs out for a while then disconnects. No errors are logged to the mis.log or node#.log files, either, as far as I can see.

I'm configuring it in Servers for 10 nodes (of 20 max for the system) on port 2222. (Telnet is running the other 10 nodes on 2323.) IPV4 only, bound to 0.0.0.0 (in both cases).

Any thoughts on what might be happening? The most common advice seems to be to just try every version of cryptlib available until something works, but not only does that feel a bit haphazard, I'm not 100% sure if I'm even resetting things properly every time I try a configuration. (I pretty much stop and start the daemon and also disable/enable SSH in the servers config.)

On 07 May 2022 at 07:35p, Kim pondered and said...

Hey, all! I've got a new Mystic 1.12a47 system running on Ubuntu 22.04 server. So far so good, telnet access running smoothly.

Hi and well done :)

However, I've followed the instructions on acquiring and compiling cryptlib and renaming/placing it in /usr/lib, with both cryptlib 3.4.5
and 3.4.6, and SSH doesn't connect. It just... silently hangs out for a while then disconnects. No errors are logged to the mis.log or node#.log files, either, as far as I can see.

I'm assuming the SSH server is enabled, that your MIS shows no errors on startup with Cryptlib? Do you have a ssl.cert auto created and sitting in your data dir? Using a different port to Telnet etc.?

What client are you using for SSL connect? Does the node logs show SSL connection etc.?

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 07 May 2022, Kim said the following...

Hey, all! I've got a new Mystic 1.12a47 system running on Ubuntu 22.04 server. So far so good, telnet access running smoothly.

However, I've followed the instructions on acquiring and compiling cryptlib and renaming/placing it in /usr/lib, with both cryptlib 3.4.5
and 3.4.6, and SSH doesn't connect. It just... silently hangs out for a while then disconnects. No errors are logged to the mis.log or node#.log files, either, as far as I can see.

I'm configuring it in Servers for 10 nodes (of 20 max for the system) on port 2222. (Telnet is running the other 10 nodes on 2323.) IPV4 only, bound to 0.0.0.0 (in both cases).

Any thoughts on what might be happening? The most common advice seems to be to just try every version of cryptlib available until something
works, but not only does that feel a bit haphazard, I'm not 100% sure if I'm even resetting things properly every time I try a configuration. (I pretty much stop and start the daemon and also disable/enable SSH in the servers config.) --- SBBSecho 3.15-Linux

All I can say is I'm using xubuntu newest version as of about 2 months ago and just compiled the newest version at the time. Had zero issues with it. I do know there are a few users that connect SSH. Did you put in all the prerequisites before compiling? Thats the only thing I can thing of. BTW only difference between normal ubuntu and xubuntu is the window manager doesn't use as many resources.

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04)
|10Standard Ports for SSH/Telnet Web/HTTP://|14Noverdu.com:808
|22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)

I'm assuming the SSH server is enabled, that your MIS shows no errors on startup with Cryptlib? Do you have a ssl.cert auto created and sitting in your data dir? Using a different port to Telnet etc.?

SSH server is enabled, no errors in the MIS service status or log file on startup. I see an ssl.cert file sitting in the data dir, yes. The port is different from Telnet, yes.

What client are you using for SSL connect? Does the node logs show SSL connection etc.?

I've tried NetRunner, SyncTERM, and PuTTY on Windows, and then just "ssh" from the local command line on the server itself (Ubuntu). Nothing shows up in any of the node logs when I try -- not even a connection attempt.

All I can say is I'm using xubuntu newest version as of about 2 months ago and just compiled the newest version at the time. Had zero issues with it.
I do know there are a few users that connect SSH. Did you put in all the prerequisites before compiling? Thats the only thing I can thing of. BTW only difference between normal ubuntu and xubuntu is the window manager doesn't use as many resources.

I could try switching back to the latest version, but I've been trying that periodically. (I assume you mean of cryptlib.) I did put in the prerequisites before compiling, yeah.

(I'm actually running headless Ubuntu Server 22.02, so no window manager at all.)

I could try switching back to the latest version, but I've been trying that periodically. (I assume you mean of cryptlib.) I did put in the prerequisites before compiling, yeah.

(Just updating to say that I did try recompiling 3.4.6, which is the latest, and it didn't work. Behaviour is slightly different in that it doesn't hang forever then not work -- it disconnects right away. But otherwise, still no dice, nothing in the node logs, no errors in mis startup.)

(Just updating to say that I did try recompiling 3.4.6, which is the latest, and it didn't work. Behaviour is slightly different in that it doesn't hang forever then not work -- it disconnects right away. But otherwise, still no dice, nothing in the node logs, no errors in mis startup.)

Okay, I've solved this. In case someone else comes across this thread, I believe this to have been the issue:

Initially, I tried using cryptlib 3.4.6, which doesn't work. However, it does create an ssl.cert file. Later, I tried every other available version of cryptlib linked from the Mystic site, and the behaviour seemed unchanged.

I did make one error -- I didn't realize that mis.log only gets written out when you shut down the BBS. So often I was looking at stale mis.log entries. When I determined that, I saw that with newer versions (3.4.5 and 3.4.6 only), I was seeing the following:

+ 2022.05.09 05:23:11 SSH Listening on IPV4 port 2222 using interface "0.0.0.0"
+ 2022.05.09 05:23:11 EVENT Starting 0 event(s)
+ 2022.05.09 05:23:36 SSH > Connect on slot 1/5 (192.168.123.14)
+ 2022.05.09 05:23:36 SSH 1-HostName Unknown
+ 2022.05.09 05:23:36 SSH 1-Negotiating SSH session
+ 2022.05.09 05:23:36 SSH Unable to set key (-2 )
+ 2022.05.09 05:23:36 SSH 1-Session failed

Which pointed to an issue with the key.

Shutting down mis, deleting (well, backing up) data/ssl.cert, replacing /usr/lib/libcl.so with version 3.4.5, starting mis back up, trying to connect and letting it generate a new ssl.cert, and then trying to connect again worked.

Now it seems to work reliably, on 3.4.5.

Thanks for the suggestions and help, everyone!

I could try switching back to the latest version, but I've been trying that periodically. (I assume you mean of cryptlib.) I did put in the prerequisites before compiling, yeah.

(I'm actually running headless Ubuntu Server 22.02, so no window manager at all.)

Yup I was referring to cryptlib. I do have the version with a window manager but typically it won't be much different between the installs. Server typically has a few more options to install the server. Did you make sure to remove and disable the built in SSH? Or at least make sure your not using the same port. Not sure if they would conflict so I wouldn't use both. I made sure to remove the one on mine. I'm not running headless at least technically. I have it in a VM so I can access it in a browser like it has a head. If you can't shut off your SSH option then make sure its at least a different port.

Are your running Mystic as sudo or did you reset permissions and run it as the local non-root user?

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04)
|10Standard Ports for SSH/Telnet Web/HTTP://|14Noverdu.com:808
|22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)

On 08 May 2022, Kim said the following...

(Just updating to say that I did try recompiling 3.4.6, which is the lat and it didn't work. Behaviour is slightly different in that it doesn't h forever then not work -- it disconnects right away. But otherwise, still dice, nothing in the node logs, no errors in mis startup.)

Okay, I've solved this. In case someone else comes across this thread, I believe this to have been the issue:

Initially, I tried using cryptlib 3.4.6, which doesn't work. However, it does create an ssl.cert file. Later, I tried every other available
version of cryptlib linked from the Mystic site, and the behaviour
seemed unchanged.

Awesome! Good info to have search-able on the network!

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04)
|10Standard Ports for SSH/Telnet Web/HTTP://|14Noverdu.com:808
|22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)

However, I've followed the instructions on acquiring and compiling cryptlib and renaming/placing it in /usr/lib, with both cryptlib 3.4. and 3.4.6, and SSH doesn't connect. It just... silently hangs out for while then disconnects. No errors are logged to the mis.log or node#. files, either, as far as I can see.

Try cryptlib 3.4.4.1, it's the only version that I found to work properly.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07── |08[|10eml|08] |15ml@erb.pw |07── |08[|10web|08] |15www.erb.pw |07───┐ |07── |08[|09fsx|08] |1521:1/158 |07── |08[|11tqw|08] |151337:1/101 |07┬──┘ |07── |08[|12rtn|08] |1580:774/81 |07─┬ |08[|14fdn|08] |152:250/5 |07───┘
|07── |08[|10ark|08] |1510:104/2 |07─┘

--- Mystic BBS v1.12 A47 2021/12/13 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

On 07 May 2022, Kim said the following...

Hey, all! I've got a new Mystic 1.12a47 system running on Ubuntu 22.04 server. So far so good, telnet access running smoothly.

However, I've followed the instructions on acquiring and compiling cryptlib and renaming/placing it in /usr/lib, with both cryptlib 3.4.5
and 3.4.6, and SSH doesn't connect. It just... silently hangs out for a while then disconnects. No errors are logged to the mis.log or node#.log files, either, as far as I can see.

I'm configuring it in Servers for 10 nodes (of 20 max for the system) on port 2222. (Telnet is running the other 10 nodes on 2323.) IPV4 only, bound to 0.0.0.0 (in both cases).

Any thoughts on what might be happening? The most common advice seems to be to just try every version of cryptlib available until something
works, but not only does that feel a bit haphazard, I'm not 100% sure if I'm even resetting things properly every time I try a configuration. (I pretty much stop and start the daemon and also disable/enable SSH in the servers config.) --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

I can tell you I just comipled the newest one on xubuntu. I didn't want to waste resources on the desktop.

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04)
|10Standard Ports for SSH/Telnet Web/HTTP://|14Noverdu.com:808
|20|15fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)