Hello all! I've found an issue in Mystic A34-35 (the two I have tested) where if I connect via SSH (mis2 and cryptlib working) I cannot run external doors/programs.

Via telnet things work great, but over SSH they all fail with disconnection.
In SyncTERM I get the error "Error receiving data". In the Mystic log file
for the node I just get the error "User dropped carrier".

I can connect via SSH and run MPL scripts, and telnet to a local telnet port using a second install of Mystic as a "SSH->Telnet bridge" and even run programs through that.

It's something with the socket handling when using SSH.

I am using the Win32 version of mystic. I have tried on Win2003R2, 2008R2 and Windows 7. Anyone else see this behavior?

Thanks.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Archaic Binary (46:1/118)

Hello all! I've found an issue in Mystic A34-35 (the two I have tested) where if I connect via SSH (mis2 and cryptlib working) I cannot run external doors/programs.

This isn't really an issue (well not a bug anyway).

In Win32 doors will not work over SSH. The only way around that in Windows 32-bit is for me to make my own "Netfoss" which I may or may not do time permitting.

But its on my list of TODOs.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

Thanks for the response! Good to hear it's not me.

I actually found this problem a long time ago, and just wanted to bring it up. I setup a second install that acts as a bridge and it's been working great for the past year or more.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Archaic Binary (46:1/118)