the new server version has arrived at CentOS8 today, but SSH Secure Shell is still 3.2.9 years ago, so I encountered an error in the title when connecting to the server. This question is a tragic waste of my time.
there are many, many posts on the web that address this problem, and they all go like this:
Sshd_config
sudo vim /etc/ssh/sshd_config
2. at the end of the file add the following information
Ciphers either aes128 – CBC, aes192 – CBC, aes256 – CBC, either aes128 – CTR, aes192 – CTR, aes256 – CTR, 3 des – CBC, arcfour128, arcfour256, arcfour, blowfish – CBC, cast128 – CBC
MACs Hmac – md5, hmac – sha1, [email protected], hmac – ripemd160 digest, hmac – sha1-96, hmac – md5-96
KexAlgorithms diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-g roup1-sha1,[email protected]
3. after saving SSH service
sudo /etc/init.d/ SSH restart
everyone said it was good, but after I tried it, it was tragic. After I added the configuration, I could not restart SSH and it would report an error.
these two articles explain the real reason and offer a solution:
https://blog.csdn.net/pgmzyy/article/details/88586101
https://blog.csdn.net/Vertoria/article/details/82226340
, however, I still failed to solve the problem, and finally decided to abandon the outdated SSH Secure Shell Client and replace it with FileZilla to solve the problem: FileZilla also supports SSH protocol to transfer files, and its operation is slightly more humane than SSH Secure Shell Client