-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
Labels
Description
Have you searched for an existing issue?
- Yes, I tried searching and reviewed the pinned issues
Brief Summary
Importing a Bitwarden JSON file does not import SSH key "contents" (i.e. the private and public keys), it only imports an empty entry.
Steps to Reproduce
- Create an SSH key entry in Bitwarden.
- Export the vault as JSON. The file will contain the entry and SSH key data under the JSON key
sshKey: {privateKey, publicKey}. - Import the vault in KeePassXC.
- Observe that while the entry imported, its contents are all empty (except the name).
Expected Versus Actual Behavior
The SSH key should be imported, or at the very least the user should be warned that it could not have been imported. Potentially for more robustness the user could be warned about any entry that imported without a password, to catch potential similar issues in the future.
The import implementation shouldn't be difficult, as the key is already in PEM format, although I'm not sure if that is always the case.