Is it possible to connect to my switch using ssh from the checkpoint cli ?

[nflnetwork29]

is it possible to connect to my switch using ssh from the checkpoint cli ?

Here is the message i got .

no matching cipher found: client aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se server aes128-ctr,aes192-ctr,aes256-ctr

[PhoneBoy]

It means the SSH client on the gateway doesn’t support the same ciphers the SSH server is configured to use.
What kind of gateway are you SSHing from and what software version?

[nflnetwork29]

SMB 1450 R77.20.15

I guess another limitation of the SMB model line?

[PhoneBoy]

The version string on our SSH client on SMB says: SSHield_2.1.0 derived from OpenSSH_3.5p1, SSH protocols 1.5/2.0, which I believe is used on VXworks systems.
I checked on both R77.20.x and R80.20.x systems, same version string.
OpenSSH 3.5 is pretty old and doesn't support more modern ciphers.
Even our regular gateways, until recently, were using a fairly old version of OpenSSH.
We updated that (along with the Linux kernel) in R80.40.

Getting this client updated on SMB would be an RFE.
Meanwhile, you will have to reconfigure your SSH server to support at least one cipher in common with the client.

[nmelay2 · Accepted solution]

Yeah I know this is a pretty old thread, but FYI, on the SMB 700/1400 product line, you might want to use dbclient, the dropbear SSH client, instead of ssh/openssh.

[PhoneBoy]

Turns out dbclient will also work when connecting to a 700/1400 series appliance from a different host when SSH won't work because of the cipher configuration.
Great tip!

[the_rock]

Phoneboy's response is 100% correct actually. Definitely means it would not support same ciphers...I had seen this before.