Hello g00r00,

I installed Cryptlib and enabled SSH as a Mystic server. The server seems to load fine.

But when I try a SSH connection from MIS2 I get:

----------------------------------------------
+ 20:37:19 SSH > Connect on slot 1/5
+ 20:37:19 SSH 1-Address 192.168.0.20
+ 20:37:19 SSH 1-HostName bbs2.ouijabrd.net
+ 20:37:19 SSH 1-Negotiating SSH session
+ 20:37:44 SSH 1-Creating terminal process ----------------------------------------------
And from the terminal window I get:

----------------------------------------------
Mystic BBS v1.12 A36 for Linux Node 1
Copyright (C) 1997-2017 By James Coyle

Detecting terminal emulation: ASCII detected.

(0) Ascii (No Color)
(1) Ansi (Color)

Graphics Mode ->
----------------------------------------------
An that is as far as the connection gets. No input from the terminal is accepted. Mystic will eventually timeout the connection with: ----------------------------------------------
Inactivity timeout. Hanging up!

Connection to bbs2.ouijabrd.net closed by remote host.
Connection to bbs2.ouijabrd.net closed. ----------------------------------------------

Any thoughts?


Jeff

--- Mystic BBS v1.12 A36 2017/11/30 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.2)

But when I try a SSH connection from MIS2 I get:

What terminal?

--- Mystic BBS v1.12 A36 2017/11/30 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

But when I try a SSH connection from MIS2 I get:

What terminal?

A Linux terminal window. I open a terminal window and issue the command

ssh Jeffs@bbs2.ouijabrd.net

I then get in the MIS2 log:
---------------------------------------
+ 23:55:22 SSH > Connect on slot 1/5
+ 23:55:22 SSH 1-Address 192.168.0.50
+ 23:55:22 SSH 1-HostName Unknown
+ 23:55:22 SSH 1-Negotiating SSH session
+ 23:55:33 SSH 1-Creating terminal process ---------------------------------------
In the terminal window I get:
---------------------------------------
Mystic BBS v1.12 A36 for Linux Node 1 Copyright (C) 1997-2017 By James Coyle

Detecting terminal emulation: ASCII detected.

(0) Ascii (No Color)
(1) Ansi (Color)

Graphics Mode ->
----------------------------------------

At which point Mystic seems to stop accepting input as nothing I type does anything. After a few minutes the connection times out.


Jeff


--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

ssh Jeffs@bbs2.ouijabrd.net

This is likely a problem. Try with NodeSpy, SyncTerm, etc. But also update your version of Mystic so we can see detailed SSL errors and see if we can fix it :)

--- Mystic BBS v1.12 A36 2017/11/30 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

On 12/01/17, g00r00 said the following...

This is likely a problem. Try with NodeSpy, SyncTerm, etc. But also update your version of Mystic so we can see detailed SSL errors and see
if we can fix it :)

I updated Mystic to the latest available at /prealpha. Which was
Mystic v1.12 A36 2017/11/30.

I used NodeSpy and attempted a SSH connection to Mystic.

MIS window display:

17:05:59 SSH > Connect on slot 1/5
17:05:59 SSH 1-Address 192.168.0.20 17:05:59 SSH 1-HostName bbs2.ouijabrd.net
17:05:59 SSH 1-Negotiating SSH session 17:06:00 SSH 1-Creating terminal process

Mis log display:

+ 2017.12.01 17:05:59 SSH > Connect on slot 1/5
+ 2017.12.01 17:05:59 SSH 1-Address 192.168.0.20
+ 2017.12.01 17:05:59 SSH 1-HostName bbs2.ouijabrd.net
+ 2017.12.01 17:05:59 SSH 1-Negotiating SSH session
+ 2017.12.01 17:06:00 SSH 1-Creating terminal process

Node #1 log display:

------------------- Node 1 (Mystic v1.12 A36 2017/11/30)
2017.12.01 17:06:00 Connect from 192.168.0.20 (bbs2.ouijabrd.net)
2017.12.01 17:11:06 Inactivity timeout
2017.12.01 17:11:06 Shutting down

NodeSpy terminal display:

Mystic BBS v1.12 A36 for Linux Node 1
Copyright (C) 1997-2017 By James Coyle

Detecting terminal emulation: ASCII detected.

(0) Ascii (No Color)
(1) Ansi (Color)

Graphics Mode ->

The connection halts in exactly the same spot. Any keyboard
input has no effect and the connection will timeout and
terminate after 3-5 minutes. I don't notice any log display
increase with the Mystic A36 Lin64 /11/30 prealpha. That is
assuming I am looking at the correct log file for the requested
log info.


Jeff

--- Mystic BBS v1.12 A36 2017/11/30 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.2)

I used NodeSpy and attempted a SSH connection to Mystic.

MIS window display:

17:05:59 SSH > Connect on slot 1/5
17:05:59 SSH 1-Address 192.168.0.20 17:05:59 SSH 1-HostName bbs2.ouijabrd.net
17:05:59 SSH 1-Negotiating SSH session 17:06:00 SSH 1-Creating terminal process

Not sure whats going on, there are no errors received prior to the node being created, so I've added some logging into the node logging now for SSL errors
in the latest build I am putting up tonight. Whatever happens must happen after the node is created.

I've tested it just now with SSH, NodeSpy, etc in Linux/64 and it works fine for me. One thing I noticed with SSH is that you have to use it like this
for a terminal connection:

ssh hostname -l username

Otherwise it seems like its trying to authenticate and execute a shell, which is going to fail and disconnect you because you're not connecting to a shell.

You could also try deleting your ssl.cert in the DATA directory also as a
last resort.

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

From a terminal window I entered the command ssh bbs2.ouijabrd.net -l jeffs. From the MIS window I got:

----------------------------------------------------------
+ 2017.12.04 03:56:10 SSH > Connect on slot 4/5
+ 2017.12.04 03:56:10 SSH 4-Address 192.168.0.20
+ 2017.12.04 03:56:10 SSH 4-HostName bbs2.ouijabrd.net
+ 2017.12.04 03:56:10 SSH 4-Negotiating SSH session ----------------------------------------------------------

I moved ssl.cert out of the DATA directory and restarted MIS. From a Linux termiminal window I then issued the command:

mystic@bbs2:~$ ssh bbs2.ouijabrd.net -l jeffs

In the trerminal window immediately displayed was:

----------------------------------------------------------- @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is SHA256:a4S2P6FLNMnRWyAYcdhmk8YRGumz4nFmOPYDyWeS3zw.
Please contact your system administrator.
Add correct host key in /home/mystic/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/mystic/.ssh/known_hosts:2
remove with:
ssh-keygen -f "/home/mystic/.ssh/known_hosts" -R bbs2.ouijabrd.net
RSA host key for bbs2.ouijabrd.net has changed and you have requested strict checking.
Host key verification failed. ------------------------------------------------------

As a result the MIS window displayed:

-------------------------------------------------------
+ 2017.12.04 04:09:24 SSH > Connect on slot 1/5
+ 2017.12.04 04:09:24 SSH 1-Address 192.168.0.20
+ 2017.12.04 04:09:24 SSH 1-HostName bbs2.ouijabrd.net
+ 2017.12.04 04:09:24 SSH 1-Negotiating SSH session
+ 2017.12.04 04:09:24 SSH Cannot activate (No data was
read because the remote system closed the connection (recv() == 0))
+ 2017.12.04 04:09:24 SSH 1-Session failed -------------------------------------------------------

After moving ssl.cert back to the /data directory and again restarting MIS.

If I again issue the command from a terminal window ssh bbs2.ouijabrd.net -l jeffs the MIS window displays:

-------------------------------------------------------
+ 2017.12.04 04:24:35 SSH > Connect on slot 1/5
+ 2017.12.04 04:24:35 SSH 1-Address 192.168.0.20
+ 2017.12.04 04:24:35 SSH 1-HostName bbs2.ouijabrd.net
+ 2017.12.04 04:24:35 SSH 1-Negotiating SSH session
+ 2017.12.04 04:24:35 SSH Cannot activate (No data was read because the
remote system closed the connection (recv() == 0))
+ 2017.12.04 04:24:35 SSH 1-Session failed -------------------------------------------------------


Using Nodespy if I attempt a SSH connection I get the following
from the Nodespy window:

----------------------------------------------
Mystic BBS v1.12 A36 for Linux Node 1
Copyright (C) 1997-2017 By James Coyle

Detecting terminal emulation: ASCII detected.

(0) Ascii (No Color)
(1) Ansi (Color)

Graphics Mode ->
----------------------------------------------

Again the connection halts at that point with no user input possible.

Let me know if you would like any specific configuration setup on
this end to conduct further tests.




Jeff

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.2)

On 12/03/17, g00r00 said the following...

Not sure whats going on, there are no errors received prior to the node being created, so I've added some logging into the node logging now for SSL errors in the latest build I am putting up tonight. Whatever
happens must happen after the node is created.

Could Cryptlib be playing any factor in the SSH connect issue? Cryptlib installed as a shared library without any noticable issues and Mystic seems
to see and use it. I am trying to consider all aspects of the situation.




Jeff

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.2)

On 12/03/17, g00r00 said the following...

I've tested it just now with SSH, NodeSpy, etc in Linux/64 and it works fine for me. One thing I noticed with SSH is that you have to use it
like this for a terminal connection:

ssh hostname -l username

Otherwise it seems like its trying to authenticate and execute a shell, which is going to fail and disconnect you because you're not connecting
to a shell.
You could also try deleting your ssl.cert in the DATA directory also as a last resort.

I seem to have the same issue as Jeffs, but with Telnet and ssh! I found
your right:
telnet localhost -l bcw142
does let me login with both Telnet and SSH, rlogin works normally.
Is there a way to pass port information to telnet/ssh when used that way?
I notice it changes the setup and I have to answer 1 for Ansi and then
1 for UTF-8 to get the correct look even though I have it set that way
in configuration (Login/Matrix Settings: Default CodePage CP437, Local CodePage UTF8). I have settings to Ask so I get around it that way.
I guess the odder thing is that rlogin works normally.

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

Offending RSA key in /home/mystic/.ssh/known_hosts:2
remove with:
ssh-keygen -f "/home/mystic/.ssh/known_hosts" -R bbs2.ouijabrd.net

Did you follow these instructions to remove on your old key? Sorry I wasn't very clear here... The point of removing the certificate is so Mystic would generate a new one and you would remove the old one from SSH.

Let me know if you would like any specific configuration setup on
this end to conduct further tests.

You need to regen the key and remove it from SSH. Afterwards if there is a problem before the terminal session is opened, the error will be in mis.lot, otherwise it'll be in the node's log.

--- Mystic BBS v1.12 A37 2017/12/04 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Could Cryptlib be playing any factor in the SSH connect issue? Cryptlib installed as a shared library without any noticable issues and Mystic seems to see and use it. I am trying to consider all aspects of the situation.

Cryptlib handles 100% of the SSH, thats what its there for. It is unlikely there is a bug with Cryptlib handshaking though because its so frequently
used.

--- Mystic BBS v1.12 A37 2017/12/04 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)