Board:   [fsxNet] Mystic BBS discussion/support
Subject: Mystic SSH question
From:    Accession(21:1/200)
Date:    Tue Oct 06, 2026 16:19

Hey JayDawg!

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

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

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

 J> I used syncterm and it returned a Syncterm error -41
 J> I also tried to SSH from the Linux command line and it errored with
 J> "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)
.