Ability to specify which key to use (otherwise: Too many authentication failures)

Hey Jack_P_1P apologies for not getting back earlier, but I did see this hit the release channel before I'd had the chance to test the nightly. Thanks very much for putting this in, it works great!

Awesome, thanks a lot! :)

Hi @jenssgb and @Ekami67:

As of yesterday, 1Password for desktop now includes the ability to better customize which keys are used: SSH agent config file | Developer Documentation

Jack

Hi Jack_P_1P

Is there an update or roadmap to the SSH agent improvements?

I stumbled across the 6-SSH key limitation today, and it took me a while to figure it out.

Tip:ssh -v <user>@<host>

Adjusting the config file on my system and storing the key locally again breaks the complete advantage of 1Password for SSH.

Thanks @"chris.db_1p" , any idea when this feature will hit the release channel?

@billvortex @Gudlyf @zaxaz @Ekami67 @digitalfiz @rodneyt @jontyb @yboulkaid @ajcos @VJmes gmay @akschu

The following features are now available to try on the Nightly release channel today:

• Control which SSH keys are enabled in the agent, even if they're from other vaults than the Private vault.
• Control the order in which keys are offered to SSH servers.

You can find more information, including instructions for the feature, by joining the #ssh-agent-config channel in our https://join.slack.com/t/1password-devs/shared_invite/zt-15k6lhima-GRb5Ga%7Efo7mjS9xPzDaF2A. It would be great to get your feedback.

Next up is support for multiple agent config files/sockets, the earliest updates for which will be made in our Slack workspace.

Thanks for the update floris_1P! I've joined the Slack channel.

@jontyb @yboulkaid gmay @akschu

I wanted to let you know that we're working on a solution that allows for the following:
- Control which SSH keys are enabled in the agent, even if they're from other vaults than the Private vault.
- Control the order in which keys are offered to SSH servers.
- Create isolated setups with certain keys offered on a separate socket.

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.

@akschu Being able to configure different sockets is something we're investigating! As for disabling keys, you can already do that now by moving them to a different vault. The agent will then ignore them, even if they're of the SSH Key item type. There will be more customization on that front coming too.

the -agent.sock above had brackets to note account name, but the forum ate them. Something like accountname-agent.sock.