Yes! Please add this feature! I first time saw it with 1Password and I thought, surely Bitwarden has this already, too, right? Turns out it doesn’t
I saw a comment here that was mentioning it was a bad idea to put keys into cloud with the passphrases, and I agree with that part. I might target to do it so, that it is still the ssh-agent that keeps the hold of the keys and it would ask for the passphrase from Bitwarden specifically. I can sort of see this as a fork of the bitwarden-ssh-agent really. For myself, I already import the keys in session start, and now I have to type in the passphrase, and I would love to use thumbprint instead of the phrase. So this feature would then in my mind become passphrases for signatures, where they key has the public signature available and it is requesting access to the private part.
I can see the appeal of storing keys and passphrases on the manager directly. To me it would equate to storing keys with empty passphrases pretty much from security standpoint. Then again, you’d perhaps store a copy of those keys somewhere like usb key or cloud in any case for the chance of the computer going bust at some point.
Cheers and salutations to a good discussion!
The ‘other’ kind of authentication I find myself having to manage is ssh keys. In a perfect world, there would be some mechanism that I could trust to generate a long key, store the key pair on the origin machine only (and back them up to a secure vault) and distribute the public key to the servers I nominate.
Having some central control over this would certainly help preserve (what remains of) my sanity:
just by managing the files themselves, and their secure delivery to servers. Making this easier reduces the urge to slip into the bad habit of reusing key pairs. Automating the ‘best practices’ means they’re much more likely to be followed.
being able to invalidate keys at a stroke would do much to mitigate the lack of passphrases on keys (e.g. the situation where a laptop is stolen - open the Bitwarden app on your smartphone and mark that key pair as revoked).
the ability to externally impose an ‘expiration’ period on keys. Bonus points for automatic rotation of keys on a schedule, so it ‘just happens’ without manual intervention.
This is a pain-point for me, and I expect every developer/dev ops/infosec person out there.
- Bitwarden for Devs and Admins
Bitwarden should be able to generate and store SSH Keys and other types of keys.
What will this feature do differently?
It would Focus more on Devs and IT Admins who need to manage more then passwords like SSH Keys for Servers or PGP keys for Encryption or Cert files for Domains etc.
What benefits will this feature bring?
For Example: I store my ssh keys on my computer directly but with this implementation I would be able to store them in Bitwarden and my ssh agent will grab the encrypted keys from Bitwarden. So I don’t need to always upload all my ssh keys on a PC or the cloud.
Currently Bitwarden is in my opinion the best Password Manager but may not be the best in functionality. I saw an interesting approach from 1Password who is only in UI/UX better.
Developer Tools | 1Password
There will be some great features explained which I wish to see in Bitwarden one day.
I believe there is a beta wait-list for this feature currently if you wish to sign up for any future notifications, but this appears to be high on the radar for the Bitwarden Team.
1Password recently shipped this functionality and it’s pretty great: SSH agent | 1Password Developer Documentation
Would be great to see something similar in Bitwarden.
Starting work on SSH Key generation/import/storage support:
Ssh agent support is out of scope of the pull request. Might do that afterwards, or someone else can if they want to.
Hi, quick update: I’m putting work on the ssh key-generation/import/storage support pull-request on hold for now as Bitwarden is working on custom item types already and thus currently does not intend to merge the PR.
Once custom (or better pre-defined) item types arrive I might look at ssh-agent support.
Any updates here? Would be really nice to have this feature!
I’m a bit disappointed in this thread. This has been open for 5 years with mostly workarounds and when a community member starts developing the feature it gets squashed because a partially associated feature is on the roadmap.
There’s a lot more to this than just an ssh key item type - the powerful thing is the ability to generate ssh keypairs within bitwarden and then leverage them through a built-in ssh-agent. Essentially, the ability to have the key NEVER exist outside the vault.
I can see a design where bitwarden introduces custom types AND a client plugin system similar to keepass where the plugin creates the item type it requires and implements additional functionality. Unfortunately, this would require implementing an entire run-time plugin capability in addition to the custom item types and probably has a whole list of security and cross-platform compatibility concerns as well.
Meanwhile I wrote some scripts to use Bitwarden CLI with TouchID on macOS to
ssh into servers until there is a official solution.
Feel free to use, modify or enhance to your needs:
This should also work on Linux (minus the TouchID part), but I haven’t tested it.
duplicate: Creating SSH Key in Secrets
i was wrong, not a dupe
Hi, my request is not duplicated because my request is only about the possibility to save SSH keys within Secret Manager secrets.
I do use Kleoprata to manage my keys on Windows. I would love to see something similar for Bitwarden, where i do have an ssh-/gpg-agent and can manage my keys in an GUI.
Any progress on this? Im almost tempted to partially going back to KeePass until there is a nice solution.
While it’s not an official Bitwarden solution, my Bitwarden-compatible client SSH Login & Git Commit Signing · quexten/goldwarden Wiki · GitHub supports serving an SSH agent. The ssh keys are stored as Bitwarden secure notes with custom fields.
You just have to configure some environment variables (same as with 1Password, I don’t know for Keepass) and then ssh and git ssh signing will use the key from your Bitwarden vault.
On Linux, there is a CLI client, and I’m getting close to releasing a graphical client on FlatHub. There are Windows and Mac builds too, but they are not as feature complete, albeit the SSH agent part should work.
For the official clients, there are no custom types, and thus there is also no good way for the desktop client to support serving an SSH agent.