When using SecureCRT (version 9.2+), part of being FIPS compliant is that the ssh key of the host being connected to, must be a multiple of 256. To be clear, I'm refering to the HOST key on the router itself, not the key used by the client to connect. Out of the box default for Merlin is not the case(?). This is the error when connecting:
How can I change the router ssh key to be a mutipleof 256. I'm not familier with dropbear at all, nor Merlin's implementation of it.
BTW, IMHO, SecureCRT is the best dam ssh client, period. I've used them all. Version 9.2 adds RDP capabilities.
If anyone feels like testing, there is a trial version of secureCRT available from VanDyke.
The client has disconnected from the server. Reason: The server's host key failed to verify.
This problem is most likely caused by the server's host key being a bit size that is not a multiple of 256.
For information about possible solutions to this issue, please visit the following website: https://www.vandyke.com/support/possible-host-key-failure-due-to-key-size.html
How can I change the router ssh key to be a mutipleof 256. I'm not familier with dropbear at all, nor Merlin's implementation of it.
BTW, IMHO, SecureCRT is the best dam ssh client, period. I've used them all. Version 9.2 adds RDP capabilities.
If anyone feels like testing, there is a trial version of secureCRT available from VanDyke.
Last edited: