Finer grained control over SSH keys?
With SSH keys, I would like to provide more granular control, where there's keys that can always be accessed (so long as the vault is unlocked), keys that ask for permission before use but if already unlocked, but otherwise don't require the password, and others that require the password every time. Is there any desire to support something like this?
To clarify my use case, I want my Git transport key to be mostly open after the app has been authorized before, my commit signing key to require auth every time it's used (re-"locking" quickly), and the key to SSH into servers to require additional authorization every time (Windows Hello/the password)
1Password Version: 8.10.27
Extension Version: Not Provided
OS Version: Windows 11
Browser: Not Provided
Comments
-
Ditto, I would like SSH signing keys to require approval upon every request to use it.
0
