Dominik Schulz

Ok, this is a little bit buggy. `gopass setup` will abort if the store is already initialized. But that doesn't seem to work if it's not initialized with gpg/gitfs.

[gon](https://github.com/mitchellh/gon) seems like the best choice.

I think this has been reported before and I've started working on a [fix](https://github.com/gopasspw/gopass/pull/2524). But it turns out this is more tricky / ugly than I first thought (one example:...

> limiting the access of a GPG key is generally very lacking within gopass. Yes, this is true. We do have limited support but it's not great. I usually tend...

Oh my, I don't like git submodules. The UX is terrible. Let me see how much complexity this would add ...

There has been no feedback so far, so I think we can keep the current level of support for hooks. But at the same time I don't want to increase...

I don't see how this could be a gopass specific defect. I found this old Go issue that might be related: https://github.com/golang/go/issues/37712

I wonder if this might be related to https://github.com/gopasspw/gopass/issues/2325

This is a strange issue. If using the GPG backend we should limit concurrency to 1 already, but maybe that's buggy. Or it's yet another issue. @c0dev0id Could you maybe...

The code is confusing. But it looks like it's really only a warning: https://github.com/gpg/gnupg/blob/master/g10/call-agent.c#L2277