Changes

Enable Legacy Cipher in Linux for SecureCRT

1,203 bytes added, 18:27, 27 February 2017
The following lines were added (+) and removed (-):
You you look at the log entry you will find that there are three possible things that can go wrong during the authentication, assuming the user entered the correct username and password, that point to the problem being an incompatible cipher.  In the log entry you will see a complaint like (snip) "...sshd[1528]: fatal: no matching mac found: client hmac-md5 server ...".  Here the word "mac" is referenced, meaning a correct cipher was found but the mac "hmac-md5" which is displayed as simply "MD5" in CRT is not enabled on the server.  The error entry in the log will reference one of three: no matching cipher, no matching mac, or Unable to negotiate a key exchange method. === log analysis ===To help you identify whether it is the cipher, mac, or KexAlgorithms which is not being accepted you can utilize the auth.log.  Provided below is an example for each type of entry.  If your problem is all three, then keep in mind that once the first fails, the other two will not appear in the log.  So, if you correct the issue with the cipher, which was displayed in the log, then there still may remain other issues that have yet to appear in the log until you attempt the connection once again.
Bureaucrat, administrator
16,192
edits