asked on
What type of OpenSSH key?
I have an example of a public key (I do not have the matching private key):
AAAAB3NzaC1kc3MAAACAc/gsM3
Although it looks like OpenSSH format, it is missing the first part which says what type of key it is (e.g. ssh-dss, ssh-rsa etc).
Is there any way of working out what type it is?
AAAAB3NzaC1kc3MAAACAc/gsM3
Although it looks like OpenSSH format, it is missing the first part which says what type of key it is (e.g. ssh-dss, ssh-rsa etc).
Is there any way of working out what type it is?
SSH / Telnet Software
Last Comment
clariso
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I can read your key (just copy-and-paste via PuTTY) without any issue and get this:
ssh-dss AAAAB3NzaC1kc3MAAACAc/gsM3
I tried with OpenSSH_5.8p1 and OpenSSH_6.0p1. Both work.
ssh-dss AAAAB3NzaC1kc3MAAACAc/gsM3
I tried with OpenSSH_5.8p1 and OpenSSH_6.0p1. Both work.
ASKER
I've just tried the one I posted at the top, and it works for me too (using OpenSSH_6.2p2). Others that I'm trying give the errors, such as:
AAAAB3NzaC1kc3MAAAEBAO43lL
(gives "input line too long")
and
AAAAB3NzaC1yc2EAAAABIwAAAQ
(gives the buffer error)
AAAAB3NzaC1kc3MAAAEBAO43lL
(gives "input line too long")
and
AAAAB3NzaC1yc2EAAAABIwAAAQ
(gives the buffer error)
I cannot convert them either. Those files might be corrupted or incomplete.
Both seem to contain (part of?) RFC4716 converted OpenSSH keys.
I tried the other key formats nonetheless, but they don't work (as expected).
Can you get new versions of the keys (perhaps by retransmitting them from where they originally came from)?
Besides that, I fear it will not be possible to repair those files, at least I don't know how it could be done.
Both seem to contain (part of?) RFC4716 converted OpenSSH keys.
I tried the other key formats nonetheless, but they don't work (as expected).
Can you get new versions of the keys (perhaps by retransmitting them from where they originally came from)?
Besides that, I fear it will not be possible to repair those files, at least I don't know how it could be done.
ASKER
The strange thing is that they still work in our old SFTP software (CoreFTP), but our new software (Cerberus FTP) requires them to be proper OpenSSH keys (hence me needing to add the first bit on).
Therefore I don't believe they are corrupt.
Anybody else got any ideas?
Therefore I don't believe they are corrupt.
Anybody else got any ideas?
ASKER
I think that for the ones which don't work, it was an issue with how they were transferred to my *nix box (which has the ssh-keygen application).
I'm all sorted now.
Many thanks for your help!
I'm all sorted now.
Many thanks for your help!
ASKER
The original post actually solved the problem, but issues my side prevented me from being able to use it!
buffer_get_ret: trying to get more bytes 4 than in buffer 0
buffer_get_string_ret: cannot extract length
key_from_blob: can't read key type
decode blob failed.
or
input line too long.