1. Forum
  2. fsxNet
  3. FSX MYS

  • SSH Fail

    From Otto Reverse@21:1/225 to All on Mon May 17 11:15:58 2021
    I've been trying to get SSH logins working with Mystic on Linux (Ubuntu
    Server 18.04). For testing clients I've tried Putty (v0.73), latest
    NetRunner, year old SyncTERM and various Linux SSH clients.

    The client (Linux) fails with this message:

    ssh_exchange_identification: Connection closed by remote host

    With Cryptlib 3.4.4.1 I get the following in the log:

    SSH 1-Negotiating SSH session
    SSH Cannot load private key
    SSH Cannot load certificate
    SSH 1-Session failed

    With Cryptlib 3.4.6 I get:

    SSH 1-Negotiating SSH session
    SSH Unable to set key (-2)
    SSH 1-Session failed

    Cryptlib 3.4.5 won't compile for me with the error:

    ./misc/consts.h:351:30: error: initializer element is not constant
    #define CURRENT_TIME_VALUE ( ( DATE_YEAR + DATE_MONTH + DATE_DAY - 30 )
    * 86400 )

    I figure the issue there is a change in the GCC compiler from whatever I'm using in Ubuntu Server 18.04 and whatever Cryptlib 3.4.5 was developed on.

    As for the previous two fails my best guess is it is a failure to find a compatible cipher between client and server.

    Anyone run into this and solve it?

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Free Speech You Smeg Head (21:1/225)
  • From bcw142@21:1/145 to Otto Reverse on Mon May 17 09:30:35 2021
    On 17 May 2021, Otto Reverse said the following...

    I've been trying to get SSH logins working with Mystic on Linux (Ubuntu Server 18.04). For testing clients I've tried Putty (v0.73), latest NetRunner, year old SyncTERM and various Linux SSH clients.

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

    why NetRunner or syncTERM and not the built in nodespy?

    --- Mystic BBS v1.12 A47 2021/04/08 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)
  • From Otto Reverse@21:1/225 to bcw142 on Mon May 17 14:50:50 2021
    First question: are you using standard ports? The tag line shows Linux/64 so the ssh from Linux and Mystic would be on the same port 22. Your best moving the Linux one if it's loaded (it's not loaded by default). If present it's at /etc/ssh/sshd_config and you need sudo to edit it.
    Other than that everything should be covered at: "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.

    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)