PuTTY says my key format is "too new" — what does that mean and how do I fix it?
I converted a private key into the PuTTY format using the key generator, and when I load it into the client I get a warning that the key format is too new.
If I try to use the original unconverted key instead, I get a different complaint about it being an OpenSSH format the client does not accept.
So I appear to be caught between two formats, neither of which works. What is actually going on and what is the right way out?
@ssh_serkan · last wk.
There are two separate format questions tangled together here and separating them makes it simple.
Format one: OpenSSH versus PuTTY. The client uses its own private key format rather than the OpenSSH one. That is why your original key is rejected, and converting it with the key generator is the correct step.
Format two: which version of the PuTTY format. The key file format itself has been revised, and a newer generator produces a newer version. An older client — or another tool that reads these files, such as some file transfer clients and deployment tools — only understands the older one. That is the "too new" message: the file is valid and the reader is older than the format.
The fix is to save the key in the older version. In the key generator there is a parameter setting for the file format version; set it to the earlier version, load your key and save the private key again. You now have a file the older client accepts.
Reply
Report