multiple 1Password ssh agents, or scoped socket files?
After reading the pages on six key limit article and agent config I seem like I'm still going to run into the six key issue with enough keys (provided I'm not misunderstanding something) between the multiple companies I consult for (and their love of ssh keys).
Would it make sense for 1Password to create multiple ssh agents (or a scoped socket file) to a specific vault? This way I could match in my .ssh/config file for a specific Host pattern and then point that patterns towards to a specific vault by virtue of a vault scoped IdentityAgent line. This make sense?
And have to say that I absolutely love the ssh agent integration. Marvelous
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
You should not run into the limit when you specify the key for the host and use the
IdentitiesOnly yesoption. This should result in the key specified being used and no others need to be tried.If you're not able to do this for some reason, then it will, unfortunately, be a problem.
0 -
sure, just looking for a way to avoid having to put in IdentitiesOnly. I'd rather have a ssh_config block that machines specific domains or the like and restrict the search to a specific vault. I'm unlikely to have more than 6 keys for a specific company..
0 -
In that case, wouldn't separating the keys by vault help?
0
