Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
What is the best way to keep the SSH agent responding to background requests?
I've got the SSH agent set up, asking for approval for each new application, remembering approval for 24 hours.
I have the 1Password agent set up as an IdentityAgent in ~/.ssh/config, and the GitH...
Okay, I just increased the 1Password idle lock timing (if I wasn't at home, I'd lock my computer when I walk away anyway), and changed the key approval to "until 1Password locks". I'll see how that goes; at least it should be more obvious what's going on.
Good to clarify: the SSH private key is still tied to the 1Password "lock state", so locking 1Password means that there's no more private key available until you unlock...
Since "remember key approval" has "until 1Password locks" as an option, it's easy to think that the other options override the lock state of 1Password, allowing SSH access by time rather than by 1Password lock state. Please consider this a feature request for an option to allow SSH key approval to be by time rather than by lock state. It'd be really nice to be able to use 1Password more or less like a traditional SSH agent, just with more secure key store.
Thanks for the help!
