Open ssaarinen opened 7 years ago
Not a fix, but a workaround: I select "Always require user confirmation when a client program requests a key to use" and "Show key selection dialog when a client program requests a list of all keys". Both may not be necessary, but my work-flow is to specifically choose which key to use. With this, I never run into "too many keys attempted" failures. It has the added benefit (for the paranoid), similar to the windows UAC notification, of requiring user interaction before allowing a key. This won't work well if/when you need either automated or rapid-fire access.
Partial fix has been released in v0.9.1. http://lechnology.com/2017/03/keeagent-beta-0-9-1-released/
You can load keys from a group, but you cannot unload from a group.
I think that loading all keys from a group might help overcoming the loading of too many keys to the agent at once. This way I could use the key timeout feature or unload when changing between different groups of servers.
To my knowledge similar funtionality could be achieved currently by using separate databases but I don't think it is as convenient as this would be.