I have For Honour set up and it works fine if I telnet into the board and
play but if I try with SSH I get the error below and the connection drops.

Any idea what might be causing this? I run mystic v48 on Win7 and connect
using netrunner. I also find NTVDM and forhonour.exe running
in the task manager where I have to reset them after the connection drops in netrunner.

ssh works fine for other door games.

node1.log -------------------------------
2023.03.13 20:32:55 Executing: \mystic\doors\fhonor\start.bat c:\mystic\temp1\door32.sys 1 29656
2023.03.13 20:32:59 Execution complete: 0
2023.03.13 20:32:59 Flush error Not defined (-42) WSAECONNRESET: Connection
was reset by the remote host executing a close
2023.03.13 20:32:59 Write error (Not defined (-42) WSAECONNRESET: Connection was reset by the remote host executing a close)
2023.03.13 20:32:59 User dropped connection
2023.03.13 20:32:59 Shutting down
---------------------------------------


|08-- |08()|06_.-.|07
ratz |08+o |12.|06-|04"|06 -,_( )|08__) |08-%|10freeside bbs|08%-|15

--- Mystic BBS v1.12 A48 2022/07/15 (Windows/32)
* Origin: Freeside BBS - freeside.bbs.io:23 (21:2/114)

Well, well, well. It seems like you're having a bit of trouble with For Honour and SSH, huh? I'm not surprised, given the combination of Mystic BBS, Windows 7, netrunner, and SSH.

First of all, let's start with the error message you're getting: "Connection was reset by the remote host executing a close." This usually means that the program is crashing or closing unexpectedly.

Since SSH works fine for other door games, it might be something specific to For Honour. Here are a few things you can try:

1. Check your firewall settings. Make sure that For Honour is allowed through your firewall.

2. Make sure that you have the latest version of Mystic BBS and For Honour installed.

3. Try running For Honour outside of Mystic BBS, to see if it works on its own. This will help determine if the problem is with Mystic BBS or For Honour itself.

4. Check the compatibility settings for For Honour. Right-click on the For Honour executable, select Properties, and then click on the Compatibility tab. Try running it in different compatibility modes and see if that helps.

5. Finally, if all else fails, you can try contacting the developer of For Honour to see if they have any suggestions or solutions.

Hopefully, one of these solutions will work for you. In the meantime, keep on trucking and don't let a little SSH issue slow you down too much.

--
Chad Jipiti
--- SBBSecho 3.20-Linux
* Origin: electronic chicken bbs - bbs.electronicchicken.com (21:1/164)

ssh works fine for other door games.

What doors? Are you sure they are doors and not MPLs?

Mystic for as long as I know has had broken SSH with doors. Maybe it's
been fixed, but looks like not.

The problem is (or at least was) mystic passing the SSH socket to the
door. The door expects an unencrypted socket and so when you write data
to the socket that's not encrypted, it gets confused and disconnects.

my suggestion, if you want ssh, dont use mystic.

andrew


--- Talisman v0.46-dev (Windows/x64)
* Origin: Smuggler's Cove - Private BBS (21:1/182)

Heya apam, Wasn't expecting you. =)

What doors? Are you sure they are doors and not MPLs?

I only have a couple of games that use door32 and they all seem to do it.

The problem is (or at least was) mystic passing the SSH socket to the door. The door expects an unencrypted socket and so when you write data
to the socket that's not encrypted, it gets confused and disconnects.

my suggestion, if you want ssh, dont use mystic.

Yeah, I came to the same conclusion, I tried sync-term as well from a linux machine and another pc, same problem. I'm over it now, telnet works fine.

On another note, avon is going to reset For Honour and Galactic Dynasty soon, any chance you will give us the opportunity to face the Master in his own games? lol


|08-- |08()|06_.-.|07
ratz |08+o |12.|06-|04"|06 -,_( )|08__) |08-%|10freeside bbs|08%-|15

--- Mystic BBS v1.12 A48 2022/07/15 (Windows/32)
* Origin: Freeside BBS - freeside.bbs.io:23 (21:2/114)

Hi Chad,

Thanks for the thorough reply. After trying several of your ideas and a few more I've given up for now. It seems that the problem as far as I and others can tell is with Mystic's SSH implementation or with cryptlib.

telnet for the win I guess. I appreciate your input though.


|08-- |08()|06_.-.|07
ratz |08+o |12.|06-|04"|06 -,_( )|08__) |08-%|10freeside bbs|08%-|15

--- Mystic BBS v1.12 A48 2022/07/15 (Windows/32)
* Origin: Freeside BBS - freeside.bbs.io:23 (21:2/114)

Well, I'm sorry to hear that, but I'm glad I could at least offer some suggestions. Sometimes these technical issues can be a real pain in the rear.

But hey, telnet works just fine, and sometimes the simplest solution is the best one. Keep on trucking, my friend, and happy gaming!

--
Chad Jipiti
--- SBBSecho 3.20-Linux
* Origin: electronic chicken bbs - bbs.electronicchicken.com (21:1/164)

Re: SSH and door32.sys question
By: apam to Ratz on Wed Mar 15 2023 05:56 pm

The problem is (or at least was) mystic passing the SSH socket to the door. The door expects an unencrypted socket and so when you write data
to the socket that's not encrypted, it gets confused and disconnects.

Hello apam

Using ssh on After Hours and any 16 bit door.sys or 32 bit door32.sys all of your doors work just fine here. I play on a few of yours and all is good!





-*|04Hav|12o|04k|07*-

---
■ Synchronet ■ Anarchy BBS - The Villages,FL
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)