Although this will not be specific to Mystic, I'm looking to see how others have implemented SSH for their boards. Here's the rub: I'm running Linux and my internet facing SSH is public key authentication only. I would, however, like to offer SSH access
to the board. Is anyone else running anything like this?
Best regards,
JayDawg

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Off The Hook BBS - Denver, CO (21:3/257)

On 04 Oct 2026, JayDawg said the following...

Although this will not be specific to Mystic, I'm looking to see how others have implemented SSH for their boards. Here's the rub: I'm
running Linux and my internet facing SSH is public key authentication only. I would, however, like to offer SSH access
to the board. Is anyone else running anything like this?

I just run Mystic's SSH on another port, 2222 in my case.


Jay

... A bachelor never makes the same mistake once

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (21:3/110)

I just run Mystic's SSH on another port, 2222 in my case.

Hi,
I also want to try the SSH login on Mystic but it don't work.
Actived the SSH server on port 2222. Compiled the cryptlib library,
put the compiled "libcl.so" file to the Linux LIB path (/usr/lib/).
Have no SSH connection. I don't know if i must change something in the OS ?
I'm on RasPi4, running the official OS (Debian 12).

... Listen: A telephone tingling with anticipation.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

On 05 Oct 2026, Gods69 said the following...

I also want to try the SSH login on Mystic but it don't work.
Actived the SSH server on port 2222. Compiled the cryptlib library,
put the compiled "libcl.so" file to the Linux LIB path (/usr/lib/).
Have no SSH connection. I don't know if i must change something in the
OS ? I'm on RasPi4, running the official OS (Debian 12).

Try shutting down mis, then go into mytsic -cfg -> Servers -> Logging Options and set the log level to Verbose or Max. Restart mis and try again, if it doesn't work, have a look at mis.log, it should give you a little more info.


Jay

... Construct a system that even a fool can use and only a fool will want to

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (21:3/110)

Try shutting down mis, then go into mytsic -cfg -> Servers -> Logging Options and set the log level to Verbose or Max. Restart mis and try again, if it doesn't work, have a look at mis.log, it should give you a little more info.

Well, i got SSH to work. Downgraded the cryptlib from v3.4.9.5 to v3.4.5
and open the TCP port 2222 on the internet router.
(on mis.log, mystic can't find the cryptlib)

... Electricity travels a foot in a nanosecond.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Try shutting down mis, then go into mytsic -cfg -> Servers -> Logging Options and set the log level to Verbose or Max. Restart mis and try again, if it doesn't work, have a look at mis.log, it should give you a little more info.

My SSH port is set to 2222, Linux is handling port 22 with public key.
I set up Max logging and still failing. I thought maybe a cryptlib problem but I'm not sure.
Here's my log:

+ 2026.10.05 17:33:15 SSH > Connect on slot 1/10 (178.249.xxx.xxx)
+ 2026.10.05 17:33:15 SSH 1-Hostname xxxxxxxx.xxxxx.com
+ 2026.10.05 17:33:15 SSH 1-Negotiating SSH session
+ 2026.10.05 17:33:15 SSH Unable to set key (-2)
+ 2026.10.05 17:33:15 SSH 1-Session failed

I used syncterm and it returned a Syncterm error -41
I also tried to SSH from the Linux command line and it errored with "Permission denied (publickey"

Thoughts?
JayDawg

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Off The Hook BBS - Denver, CO (21:3/257)

try to deactivate the MIS server. Go to mystic/data folder and
delete the "ssl.cert" file. reactivate the MIS server and try again.

... This may be the purpose of the universe.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Gods69 wrote to Warpslide <=-

I just run Mystic's SSH on another port, 2222 in my case.

Hi,
I also want to try the SSH login on Mystic but it don't work.
Actived the SSH server on port 2222. Compiled the cryptlib library,
put the compiled "libcl.so" file to the Linux LIB path (/usr/lib/).
Have no SSH connection. I don't know if i must change something in the
OS ? I'm on RasPi4, running the official OS (Debian 12).

Have you gone into raspi-config and enabled SSH? Pi's don't look at SSH
until you do that.


... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.37-Linux
* Origin: Bayou Blog BBS * bayoublog.ddns.net (21:3/232)

Have you gone into raspi-config and enabled SSH? Pi's don't look at SSH until you do that.

Yes. SSH is enabled but i think is only for port 22. I use port 2222 on my BBS. Using nmap the TCP port 2222 is open so Mystic open it itself.

... A lie in time saves nine.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Hey JayDawg!

On Mon, Oct 05 2026 17:49:20 -0600, you wrote:

My SSH port is set to 2222, Linux is handling port 22 with public key.
I set up Max logging and still failing. I thought maybe a cryptlib problem but I'm not sure. Here's my log:

+ 2026.10.05 17:33:15 SSH > Connect on slot 1/10 (178.249.xxx.xxx)
+ 2026.10.05 17:33:15 SSH 1-Hostname xxxxxxxx.xxxxx.com
+ 2026.10.05 17:33:15 SSH 1-Negotiating SSH session
+ 2026.10.05 17:33:15 SSH Unable to set key (-2)
+ 2026.10.05 17:33:15 SSH 1-Session failed

I used syncterm and it returned a Syncterm error -41
I also tried to SSH from the Linux command line and it errored with "Permission denied (publickey"

I saw this when trying to connect to another Mystic system recently. I ended up having to use my console, and specify the specific cipher spec with the '-c' option (I think I had to use aes128-cbc), in order to actually connect.

There's a good chance the outdated version of cryptlib that Mystic supports doesn't include new(er) ciphers. Syncterm may have moved on from that. You might be able to find an older terminal program (Netrunner would be my guess) to connect via SSH to Mystic, or ask Deuce to go back to supporting whatever it was that worked before?

There's also the possibility that the Mystic system I was trying to connect to didn't have it setup correctly, too. *shrug* ;)

It's definitely possible sooner or later SSH won't be achievable with Mystic's built in SSH server, unless it gets updated.

Regards,
Accession

... Be kind to your kids, they'll be choosing your nursing home.
--- AmberEdit/linux 0.9.1
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)