I have typical (I guess) vaults for personal use and for work use - and extra vaults in linked accounts. All of these may contain SSH Keys that I may want to use. Needing to have SSH Keys in my personal vault is limiting. I don't want my work keys there. I want keys in other vaults to be visible in the agent. I might end up with a whole lot of keys being exported, conceivably triggering a too many authentication failures error. Choosing which keys to export might alleviate this - possibly connected to the new Collections feature? 1Password Version: 1Password for Mac 8.6.0 Extension Version: Not Provided OS Version: macOS 12.2.1

@Goddesen @zhaoweny @kormoc @ascarter @Aurond I wanted to let you know that we're currently working on a solution that allows for the following: - Enable keys from other vaults than the Private/Personal vault. - Create isolated setups with certain keys offered on a separate socket. - Control the order in which keys are offered to SSH servers. It would be great to get your feedback on our proposal, if you're (still) interested. You can do so by joining the #ssh-agent-config channel in our Slack workspace.

Yes, we will eventually lift this requirement, but we'll need to have an opt-in mechanism for that. Would you prefer an opt in per vault or per key?

Hi, currently I have 1 key for personal use, and another key for work stuff. So I would be fine with opt-in per vault. But considering there might be someone with much more keys, I think it would be better if 1Password allows opt-in per per key.

I would purpose a different solution. I would like to see the agent.sock be available per vault and per collection Host * IdentityAgent "~/Library/Group Containers/XXXXXXXXXX.1password/t/agent-vault-personal.sock" Host *.work.com IdentityAgent "~/Library/Group Containers/XXXXXXXXXX.1password/t/agent-collection-work.sock" Host *.foo.org IdentityAgent "~/Library/Group Containers/XXXXXXXXXX.1password/t/agent-vault-foo.sock"

I would not want a separate socket for each group. I have one key in my Personal vault for my Family account and three keys in my work account Private vault. All of them present correctly.

Forum Discussion

Former Member

4 years ago

Suggestion: Allow SSH Keys in any vault, choose which ones to export

I have typical (I guess) vaults for personal use and for work use - and extra vaults in linked accounts. All of these may contain SSH Keys that I may want to use.

Needing to have SSH Keys in my personal vault is limiting. I don't want my work keys there. I want keys in other vaults to be visible in the agent.
I might end up with a whole lot of keys being exported, conceivably triggering a too many authentication failures error. Choosing which keys to export might alleviate this - possibly connected to the new Collections feature?

1Password Version: 1Password for Mac 8.6.0
Extension Version: Not Provided
OS Version: macOS 12.2.1

SSH

Former Member
3 years ago
Hi, currently I have 1 key for personal use, and another key for work stuff. So I would be fine with opt-in per vault.

But considering there might be someone with much more keys, I think it would be better if 1Password allows opt-in per per key.
floris_1P
1Password Team
3 years ago
Yes, we will eventually lift this requirement, but we'll need to have an opt-in mechanism for that. Would you prefer an opt in per vault or per key?

Forum Discussion

Suggestion: Allow SSH Keys in any vault, choose which ones to export

Recent Discussions

connect server - connection refused

Revoked service accounts

my 1password cli can't connect the app

IP list for SCIM bridge?

Give preference to 1p ssh key defined in git config