Working SSH client

[davorin]

Does someone know a working SSH client for OS9?

Latest MacSSH throws errors as it can negotiate a secure connection for example to a Debian 8 or FreeBSD 10 system.

[Mat]

I don´t face any problems with MacSSH PPC Version 2.1fc3, connecting to 3 years old Lubuntu and latest Debian Kernel Servers.

Did you create a keypair, and select the proper Encryption, Authentication and Compression methods?

[davorin]

So you're saying MacSSH won't let me do ssh connection without installing a public key on the SSH server?


Copied now testwise the exported public key on my local Debian machine...tried all SSH2 settings..but getting always:

Code: [Select]

lsh: handle_connection: Received packet of type 20 (KEXINIT)
lsh: Received KEXINIT message. Key exchange initated.
lsh: keyexchange.c:209: Unknown: Raising exception No common key exchange method.
 (type 4096), using handler installed by connection.c:282: Unknown
lsh: Protocol error: No common key exchange method.


[Mat]

So you're saying MacSSH won't let me do ssh connection without installing a public key on the SSH server?

No. I am saying that MacSSH client needs a locally newly created keypair once for all later SS2 connections.
See the QuickStart document provided with MacSSH.

Sadly I cannot help you with further advices as I am no ssh professional. I just can use MacSSH without problems and latest Linux kernels.

[Protools5LEGuy]

SSH is Chinese to me. But just in case:

https://sourceforge.net/projects/macssh/

SSH2 client for MacOS before X, based on BetterTelnet, lsh and GUSI.

http://saf.bio.caltech.edu/macssh_instruct.html

http://www.club.cc.cmu.edu/~rbraun/macssh/

[MacNewbie]

Does someone know a working SSH client for OS9?

Latest MacSSH throws errors as it can negotiate a secure connection for example to a Debian 8 or FreeBSD 10 system.

I found the fix for this...

In OpenSSH 6.7 and later, certain ciphers (methods of encrypting) are considered less-desirable and possibly able to be compromised, so they are disabled by default.

Adding the following 2 lines to /etc/ssh/sshd_config (or wherever your sshd_config file lives), fixed the problem and let me log in:

KexAlgorithms diffie-hellman-group1-sha1,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1

Ciphers 3des-cbc,blowfish-cbc,cast128-cbc,arcfour,arcfour128,arcfour256,aes128-cbc,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],[email protected]

Note, there are no line breaks, just 2 very long lines.

Don't forget to restart sshd after, in order to restart and then test this config.

[ovalking]

I've also have trouble with MacSSH 2.1fc3.
I need to connect to a bunch of remote routers but have never been able to make a connection from a Mac.
Tried all sorts of settings, and the generate keys thing.

Usual error message is:
lsh: Protocol error: Algorithm negotiation failed.

I don't have a file called sshd_config anywhere.

I can connect fine using Putty on Windows (without playing with any settings).

[MacNewbie]

I've also have trouble with MacSSH 2.1fc3.
I need to connect to a bunch of remote routers but have never been able to make a connection from a Mac.
Tried all sorts of settings, and the generate keys thing.

Usual error message is:
lsh: Protocol error: Algorithm negotiation failed.

I don't have a file called sshd_config anywhere.

I can connect fine using Putty on Windows (without playing with any settings).

The sshd_config file is on the remote Linux server. 

There may or may not be a config file option when dealing with routers; depends on the specific router. Here is an overview for some Cisco routers, but probably even this is not defnitive:  https://www.cisco.com/c/en/us/support/docs/security-vpn/secure-shell-ssh/4145-ssh.html

Was thinking of installing Virtual PC with a command line Linux just to have it around. Not sure if I will do that.

[ovalking]

Thanks for bringing this subject up, as it encouraged me to revisit my problem.
And I found a solution!
Trick was to turn off compression.
The (confusing) keys don't seem to be needed.

[V.Yakob]

Quite by chance I came across a modern application for "Classic" Macs -- ssheven.
Does not require special server settings, at least it connects to macOS 13.0.1. Cool!

[Knezzen]

I'm an avid user of ssheven as well. Wonderful client and a wonderful addition to the platform!