I'm using Mystic BBS and installed cryptlib so I can login ssh to the BBS. I fowarded ports and configured Mystic also moved cl32.dll to the Mystic folder but still can't login on ssh. Am I missing something?

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (46:10/131)

I'm using Mystic BBS and installed cryptlib so I can login ssh to the
BBS. I fowarded ports and configured Mystic also moved cl32.dll to the Mystic folder but still can't login on ssh. Am I missing something?

If you are on Linux you can't use Windows .dll files, you need to compile cryptlib for yourself.

There are instuctions on the Mystic BBS Wiki under the Linux section here: http://wiki.mysticbbs.com/doku.php?id=cryptlib

[SNIP]
The following steps can be executed to compile and install Cryptlib:

Download the source code .zip into its own directory (lets say /cryptlib and cl3441.zip for this example)
Switch to the /cryptlib directory where the cl3441.zip is located
Type "unzip -a cl3441.zip" to extract the source code ZIP into the /cryptlib directory
Type "sudo make shared"
Type "ls libcl*.so*" to see the name of the generated library. For example: libcl.so.3.4.4
Move the library into the library path and rename it so that Mystic will find it. Execute the following:
"sudo mv libcl.so.3.4.4 /usr/lib/libcl.so"
[SNIP]

--- Mystic BBS v1.12 A47 2021/01/30 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (46:1/127)

Sorry I neglected to say I'm using Windows 7. When I telnet the windows
telnet program I get this: "SSH-2.00-cryptlib" "Handshake failed Connection
to host lost."

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (46:10/131)

Sorry I neglected to say I'm using Windows 7. When I telnet the windows telnet program I get this: "SSH-2.00-cryptlib" "Handshake failed Connection to host lost."

Telnet clients cannot connect to ssh servers. ssh clients can connect to ssh servers.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: monterey bbs (46:1/111)

I've tried PUTTY and SyncTerm and still can't connect.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (46:10/131)

Hello ryan,

On Mon Feb 01 2021 00:00:30, ryan wrote to cozmo:

Sorry I neglected to say I'm using Windows 7. When I telnet the
windows telnet program I get this: "SSH-2.00-cryptlib" "Handshake
failed Connection to host lost."

Telnet clients cannot connect to ssh servers. ssh clients can connect
to ssh servers.

I would have to assume Deuce has incorporated this fairly well into Syncterm. But sure, *most* telnet clients probably shouldn't be used for SSH. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (46:1/100)

I would have to assume Deuce has incorporated this fairly well into Syncterm. But sure, *most* telnet clients probably shouldn't be used for SSH. ;)

Agreed, but I wouldn't call Syncterm simply a telnet client. It's also an ssh client :)

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: monterey bbs (46:1/111)

Re: Re: Mystic cryptlib ssh
By: ryan to Accession on Sat Feb 06 2021 10:17 am

I would have to assume Deuce has incorporated this fairly well into Syncterm. But sure, *most* telnet clients probably shouldn't be used for SSH. ;)

Agreed, but I wouldn't call Syncterm simply a telnet client. It's also an ssh client :)

And truth be told, it started life as an RLogin (only) client. In many ways, RLogin is still the first-class protocol of SyncTERM.
--
digital man

Sling Blade quote #2:
Karl (re: killing Doyle): I hit him two good whacks in the head with it.
Norco, CA WX: 61.8°F, 49.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (46:10/139)

Hello ryan,

On Sat Feb 06 2021 10:17:28, ryan wrote to Accession:

I would have to assume Deuce has incorporated this fairly well
into Syncterm. But sure, *most* telnet clients probably shouldn't
be used for SSH. ;)

Agreed, but I wouldn't call Syncterm simply a telnet client. It's also
an ssh client :)

Truth, but not so much advertised as such.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (46:1/100)

Hello Digital,

On Sat Feb 06 2021 19:43:22, Digital Man wrote to ryan:

Agreed, but I wouldn't call Syncterm simply a telnet client. It's
also an ssh client :)

And truth be told, it started life as an RLogin (only) client. In many ways, RLogin is still the first-class protocol of SyncTERM.
--
digital man

PFFFFFFFT. LAAAAAAAAME!

Just kidding dude. You old fuckers do great work. ;)

I just got into a mobile game, and I'm the old fucker. Generation gaps suck. lol

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (46:1/100)