Repository navigation
Improvements for the approval workflow and authorization caching #836
Replies: 1 comment
|
1: This is a little tricky from a few angles - a: IME it's kind of inconsistently reported by the system, and b: sometimes it's kinda ambiguous what is actually running (eg: showing "ssh" for a program that just WRAPS ssh isn't useful, but showing "Ghostty" alone also has its own set of tradeoffs. In between those is a bunch of stuff like For both 2 and 3, there's a lot of potential room for bugs/confusion though – Secretive's security model has always been "make the system enforce guarantees*" with exceptions like caching auth, but those exceptions have typically been pretty simple. Not deadset against expanding those, and things are working in that direction now, but it's definitely a little tricky figuring out how to expose those in clear ways. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
First, thank you for making this application, and for keeping it focused and secure!
I'm evaluating moving back to Secretive after a few years of using 1Password's SSH Agent, and find myself missing a few creature comforts (and security features) from 1Password's design. I love the premise of using the Secure Enclave for keys, but the ergonomics seem to lack in a few places in my workflow. Specifically:
git pushqueues up 4 successive SSH connections for unclear reasons. Either enabling automatic caching on a per-credential level, or moving the cache unlock into the authorization window, would IMO make this both easier to discover and easier to use.git pushin my Ghostty terminal only authorizes subprocesses of Ghostty to authenticate SSH. When Zed or another application wants to do something with SSH, it gets a new authentication prompt, even if the other app's auth hasn't timed out.(3) in particular seems like a useful security benefit — allowing cached approvals without turning it into a 10-minute carte-blanche for any process on the system to use the user's credentials.
All reactions