Dominik Schulz

Yes, indeed. This sounds like a very good use case. Maybe you could try to come up with a succinct PR creating this kind of documentation in the docs folder?...

Thanks for the suggestion. It's actually an interesting project and I did look at this before. However back then it had at least one show stopper. Either depending on shelling...

The `git config` format is a great idea, but that would be a big change.

Yes, it is overkill and I am strongly considering the git config idea. We have the YAML format because the config used to be more complex (but not complex enough...

Notable changes I've found so far: * IDFiles for age need to be renamed from `.age-ids` to `.age-recipients` * The whole [`keyring.go`](https://github.com/gopasspw/gopass/blob/master/internal/backend/crypto/age/keyring.go) should go away. It will be replaced by...

* `.age-ids` has been renamed * `keyring.go` is mostly gone (except for backwards compatibility) Next steps, if we choose to: * Use passage identities * Use passage store

Yes, that seems like a reasonable request. GPG can be quite annoying in that regard.

Likely a bug ...

Yes, you can export the updated public key into that directory using the correct name and commit the change. However we won't automatically import/update the key.

My aim for gopass was always to provide a good user experience for the majority of the users (and to cover my own use-cases). I think @metalmatze makes a good...