Subj : Re: SSH Fail
To   : bcw142
From : Otto Reverse
Date : Mon May 17 2021 02:50 pm

 bc> First question: are you using standard ports? The tag line shows Linux/64
 bc> so the ssh from Linux and Mystic would be on the same port 22. Your best
 bc> moving the Linux one if it's loaded (it's not loaded by default). If 
 bc> present it's at /etc/ssh/sshd_config and you need sudo to edit it.
 bc> Other than that everything should be covered at:
 bc> "http://wiki.mysticbbs.com/doku.php?d=config_server_servers#ssh"

I'm running Mystic as a non-priveleged used for security so the ports are
above 1024 (6623 and 6622 for telnet and ssh respectively).  Mystic's SSH is
running and listening. When it is not the error on the client side is
"connection refused" which is commonly SSH lingo for "ain't no one here".

The Mystic wiki has no info on this problem.  It is likely a problem with
Cryptlib and clients.

 bc> why NetRunner or syncTERM and not the built in nodespy?

Because I'm testing. BBS callers won't be using nodespy they'll be
using typical terminal clients.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
 * Origin: Free Speech You Smeg Head (21:1/225)

.