SSH Feature questions

Former Member I'm running that locally on my machine and no entries are found.

The docs say I need to do one thing OR another, not both. If I add the appropriate line to my config file, then, according to the docs, I don't need to add an Env var.

You didn't write if you checked ssh-add -l locally or remotely. Locally it works right away and you need to make sure the documented environment variables exist. In remote ssh sessions, the ssh client automatically creates the environment variables, if agent forwarding is enabled.
However, this is no 1Password specific setting. It's how the ssh client works in general.

Former Member I'm sorry, I don;t quite understand this. Why do the docs say OR then?

ssh-add -l works in a remote ssh session only, if you activate agent forwarding. Parameter -A for ssh or ~/.ssh/config option.

floris_1P Thanks for those answers.

In regards to ssh-add -l. Your documentation says to add a line to the config file OR set the environment variable.

Theres nothing that states that to use the above command I have to use the environment variable?

How do I see all the keys in the agent then? without the env var being set?

I'm confused!

And about ssh-add -l: that only works when SSH_AUTH_SOCK is set.

1. Correct, the SSH Key item works like any other 1Password item in that sense

2. Yes, you can use the import functionality for that.

3. Almost. You would need to turn on the SSH agent in the 1Password preferences on each device, because that setting is local (by design!) and you'll need to make sure your SSH config points to the 1Password agent socket.

4. Nope! The private keys never leave the 1Password process.

5. They're not needed anymore by then. We don't automatically remove the private keys from your ~/.ssh directory after importing, so you can do that yourself whenever you're comfortable.

Ok,

Just configured this and imported a key. I've enabled the Agent and added the appropriate lines to my config file.

When I run ssh-add -l, I just get "The agent has no identities.".

Any ideas how to solve this?

From what I can see you would no longer have SSH keys in .ssh, instead your authentication would be piped through 1Password's SSH agent.