Import SSH keys from CLI

Thanks for your feedback!

+1 This is a must have feature

Open sourcing the cli would help all of us making 1Password the best password manager

I created https://github.com/mickaelperrin/onepassword-tools mainly to manage my SSH Keys. The current implementation in 1Password is a good step forward but still limited for my usage.

Have a look at:

```
Usage: op-tools new-ssh-key [OPTIONS]

Generates a new SSH key and store it in 1Password. Additional information
are stored also to generate SSH config file when imported.

Options:
--return-field TEXT Field value to return
--account TEXT Account to use (shorthand)
--vault TEXT Vault uuid where to store the information
--title TEXT Name of the 1Password item
--notes TEXT Note
--from-user TEXT User who is responsible from initiating the
connection, default current user.
--from-host TEXT Host from where the SSH connection starts,
default current hostname.
--to-user TEXT Remote user, prompted if empty. [required]
--to-host TEXT Remote server hostname, prompted if empty.
[required]
--to-host-abbreviated TEXT Alias of the remote server hostname used to
initialize connection.
--no-passphrase TEXT Create ssh key without passphrase.
--passphrase TEXT Use this passphrase instead of an autogenerated
one.
--passphrase-length INTEGER Length of the autogenerated passphrase.
--port INTEGER Remote port
--help Show this message and exit.
```

and

```
Usage: op-tools ssh-add [OPTIONS] [SEARCH]

Loads a SSH key stored in 1Password by searching [SEARCH] in uuid or in
item title, and creates a ssh configuration file of the following format:

Match originalhost [][ user ]
IdentitiesOnly yes
IdentityFile
Hostname
User
Port

Options:
-D cleanup ssh agent and remove all 1Password managed
keys and configuration
--no-ssh-config TEXT Do not create ssh config file
--help Sho
```

Note that currently ssh-add uses 1password local search which is a reverse engineering decryption of 1password database locally to increase performance and is not compatible with biometric auth. This is something that should be changed because performance is not a concern for SSh key management.

Open sourcing the CLI would be a nice edition. 👍

Hey all,

Thanks for all the feedback! For the moment, the CLI is closed-source. We're having internal discussions related to open-sourcing, but nothing has been planned yet.
Related to importing&getting SSH keys with the CLI - retrieving keys should already be possible. op item get should be able to return all the fields of an SSH key. I'll try to make a case for prioritising SSH import through the CLI. No promises, though :D We'll keep everyone updated, when something starts moving on this front.
Thank you for all the suggestions and the enthusiasm.

Best,
Horia

+1 This feature is crucial!

Is there any chance to see the Roadmap or even contribute to CLI? I did not find CLI project on Github...

+1 bump for both CLI features importing key & get SSH key item.

Thank you for your suggestions! We're currently working on providing a view of SSH Key items that's more in line with the other clients: including public key, type, fingerprint etc.

In the meantime, op item get SSH-Key will only return the private key, as a field.

Importing the key via CLI is on our roadmap as well, so stay tuned!

Best,
Horia

+1 for both features import key via CLI & get SSH key item via CLI

No worries, let us know if we can help with anything else!