I discovered SSH Keys in the vault and it is awesome. I jumped to import a key and I got the message that the key is not valid.
It is very much valid - I use it daily to connect with ssh and it starts, as expected with
-----BEGIN OPENSSH PRIVATE KEY-----
This is an RSA 4096 key - are they not supported?
There are other posts on the topic, but they are not exactly relevant (Importing SSH Key : SSH Key is Invalid, SSH keys generated by puttygen will not import)
Hi! Which software was this key generated with?
4096-bit RSA keys are very much supported, however, some tools use a slightly different format that Bitwarden does not yet support for import. It may be fixed when the ssh-key rust crate releases a new version, and the bitwarden-sdk gets updated to use the new version (ssh-key: correctly parse OpenSSH keys generated by PuTTYgen by Eugeny · Pull Request #321 · RustCrypto/SSH · GitHub).
Ah, thank you. They were probably generated and exported with puttygen indeed.
Is there a way to load and re-export them to adhere to the correct format? (provided that this will keep the fingerprint used in ~/.ssh/authorized_keys unchanged - otherwise I will regenerate them from openssl and redeploy, something I would like to avoid because I have not automated that part)
Same issue for a oracle cloud private key.
-----BEGIN RSA PRIVATE KEY-----
Seems like a store for ssh keys should be format agnostic…
You can use sshpk-conv for that task, available on Debian-like distros at the node-sshpk package, like this: sshpk-conv /path/to/your/private/key -t ssh -p.