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.
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
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.?
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.
(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.)
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.)
(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.
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.
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)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,060 |
Nodes: | 17 (0 / 17) |
Uptime: | 77:16:03 |
Calls: | 501,078 |
Files: | 109,390 |
D/L today: |
34 files (28,463K bytes) |
Messages: | 3,436,275,134 |