SSH to Cisco Switch with Private Key Error
Hey%20guys%2C%3Cbr%3E%3Cbr%3EI%20am%20setting%20entries%20up%20in%20my%20RDM%20for%20my%20Cisco%20switches%20but%20for%20some%20reason%2C%20it%20doesn%27t%20want%20to%20work%20with%20Private%20keys.%3Cbr%3E%3Cbr%3EWhen%20I%20use%20username/password%20credential
edited by khakkinen on 11/7/2014
All Comments (19)
Whoops, double post and something went wrong :S
Here is what I wrote:
Hey guys,
I am setting entries up in my RDM for my Cisco switches but for some reason, it doesn't want to work with Private keys.
When I use username/password credentials, it works perfectly fine.
When I use a Private Key,C it comes up with the following error
"Unable to connect. Verify your settings. Unsupported packet 60."
I can login using my private key fine using putty but I would prefer to use SSH Shell in RDM so it is all contained in one program.
Any ideas what is happening?
Thanks,
Karl
Hi,
It seems to be an issue with the third party we use for the SSH. They just released an new version. Would mind checking for the next beta update coming soon to see if this is resolved? You can expect it for the end of next week.
David Hervieux
That I can do :) Thanks David.
Hey David,
I just updated to the latest version but it is still happening.
Thanks,
Karl
I think that the update didn't made the cut and it was not included. It will be in the next version.
David Hervieux
So it seems that the new version does not resolve your issue. We will have to check with the third party. André will verify on their forum
David Hervieux
Hi,
Here the answer of the third party support team.
It looks like the private key is encrypted using an unsupported algorithm (even though the key format is supported).
As a workaround, please download the PuTTYgen utility (I attached it) and use it to convert the private key you have into PuTTY '.ppk' format.
You should then be able to connect using the converted .ppk private key.
Current version supports loading the following private key formats:
•PKCS #8 format (PBKDF1, PBKDF2, PKCS #12 key generation, DES, 3DES, RC2, RC4, AES encryption)
•OpenSSH/OpenSSL SSLeay format (we only support TripleDES encryption)
•PuTTY PPKv2 format (it only uses AES)
In addition to encryption algorithms listed, keys with no encryption are supported as well.
I hope that this will solve your issue.
Best regards,
edited by asanscartier on 10/30/2014
edited by asanscartier on 10/30/2014
André Sanscartier
Thanks for the information. Unfortunately, the key is already unencrypted and has no pass phrase. I tried exporting it to the other formats but they gave me the same issue, "Unsupported Packet 60".
Thanks for the information. Unfortunately, the key is already unencrypted and has no pass phrase.
I tried exporting to other formats with the same issue (Unsupported Packet 60).
The key is already in ppk format.
I've noticed that if I use an SSH-2 DSA Key, I do not get the Unsupported packet error. I get the erroe when using SSH-1 RSA and SSH-2 RSA keys. Unforchunatly, DSA is not supported on Cisco devices.
Hi,
Could you generate a key as an example of what you need to use and send it to us with all information that you think that could be useful.
We will send it to the third party and ask them to add support to it.
Best regards,
André Sanscartier