`gpg-agent` connection / implementation
I use GnuPG as a backend for my password manager gopass. Ideally, it would have been possible to replace gopass' GnuPG backend with a sequoia based backend but there are too many rough edges with sequoia at the moment and I'd like to kindly provide feedback as a user.
For the sake of order, I've opened separate issues for the separate subjects my feedback addresses. This issue is about gpg-agent usage / implementation:
I'm not a sequoia user yet, since I can't fully replace gpg with it because I rely on gpg-agent
for the ideal UX I seek, that includes for example, not only caching the passwords, but also e.g resetting the cache on demand with gpgconf --reload gpg-agent
.
I saw many code examples here: ipc/examples/
but I'm not sure whether that's helpful for an end user.
I see this related / depends upon #369 because somehow the agent (whether it will be an implementation of, or the good old gpg-agent) needs to know where are the secret keys' files are stored.
I hope my feedback is appreciate because I have big hopes for sequoia and I'd like it to become mainstream at some point.