FAQ: What causes the "No compatible cipher" error in SecureCRT?
If you are getting some form of the below error in SecureCRT:
Key exchange failed.You can turn on Trace Options output (File menu) and find this info:
[LOCAL] : Available Remote Send Ciphers = email@example.com,aes128-ctr,aes192-ctr,aes256-ctr,firstname.lastname@example.org,email@example.com [LOCAL] : Selected Send Cipher = aes256-ctr [LOCAL] : Available Remote Recv Ciphers = firstname.lastname@example.org,aes128-ctr,aes192-ctr,aes256-ctr,email@example.com,firstname.lastname@example.org [LOCAL] : Selected Recv Cipher = aes256-ctr
Ciphers: The "Available" lists what the remote is advertising it supports. SecureCRT will try its listed cipher methods (in the Connection / SSH2 / Advanced category of Session Options) in order. The list can be reordered using the Up/Down arrow buttons next to the list.
As of version 8.5.1, current Ciphers supported are (with version when support was first added):
You can employ the power of editing the Default session to enable any new ciphers in all of your existing and future sessions. Here are some links to a tip and a video that provide more details about using the Default session to make mass changes to multiple sessions:
Last edited by bgagnon; 03-01-2019 at 09:10 AM. Reason: Changed icon to question mark
|chacha , cipher , ctr , debugging , faq , gcm , securecrt , securefx , troubleshooting|
|Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)|