Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
rctneil
4 years agoSuper Contributor
SSH Feature questions
Hi,
Just some quick questions about the new SSH feature.
I'm assuming that the SSH keys are synced between your machines etc?
Is it possible to import existing keys from multiple machines into 1Password?
If I had my keys stored in 1Password and I was setting up a brand new machine, i'm assuming all I would need to do is set up 1Password and i'd be good to go right?
If I do use 1Password's SSH features, do the keys still show up in my Mac's .ssh directory?
Once the keys are in 1Password, do I need to remove from from the .ssh directory?
I have had a glance at the dev documentation but would like just a little more info. I've not enabled the feature yet though but really excited to!
Thanks,
Neil
1Password Version: 8.6
Extension Version: Not Provided
OS Version: MacOS 12
39 Replies
- rctneilSuper Contributor
I'm really sorry but this is not making any sense to me.
In your documentation, you state:
"On Mac and Linux, add the IdentityAgent to your config file or set the SSH_AUTH_SOCK environment variable."
and
"Add the IdentityAgent snippet to your ~/.ssh/config file:
Host *
IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock"Or set the SSH_AUTH_SOCK environment variable in the shell where your SSH command runs:
export SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock
"You explicitly say the word "or" twice. This indicates that the user has to do one OR the other.
If you HAVE to do both then surely the documentation needs to be updated. I run
ssh-add -land it fails to show any keys.If I am misunderstanding then that's fine, but please ensure your documentation is cleared up and everything clarified to ensure misunderstandings like this don't happen.
Please could you explain again here so I can try to understand.
- Former Member
Is there a way to target addtional/other vaults?
- Former Member
when I move the key back to the personal vault I get the valid output:
shell
Mon 28 8:26pm in ~ took 1m 51s
•100% ▶ SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l
256 SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (ED25519)
- Former Member
it is in a private vault specifically for work
- floris_1P
1Password Team
Is the SSH key you imported in a Private vault or a shared vault?
- Former Member
floris_1P I get:
shell
Mon 28 9:01am in ~
⇣94% ▶ SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l
The agent has no identities.
- floris_1P
1Password Team
@kevinneufeld And what do you get when you run:
SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l
- Former Member
I followed the instruction as well, but cannot get it to work. Imported my key, moved it out of .ssh and added
export SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sockto my shell and I get the following error.shell
Thu 24 10:39pm in ~
•100% ▶ ssh -T git@gitlab.com
git@gitlab.com: Permission denied (publickey,keyboard-interactive).
- Former Member
I followed the instruction as well, but cannot get it to work. Imported my key, moved it out of .ssh and added
export SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sockto my shell and I get the following error.shell
Thu 24 10:39pm in ~
•100% ▶ ssh -T git@gitlab.com
git@gitlab.com: Permission denied (publickey,keyboard-interactive).
- floris_1P
1Password Team
ssh-adddoes not work withIdentityAgent, so you have to use theSSH_AUTH_SOCKenvironment variable there.We're working on a docs page that lists compatibility for SSH clients/tools with certain features, which should give more clarity on this subject.