michaelk83

The Secret Service API allows an arbitrary set of lookup attributes to be associated with each password, where each attribute is a key-value pair. So I don't think the filesystem...

> I don't think I can help much here beyond testing any changes Hi @aidalgol , I was thinking that since you were the one who contributed the current `.service`...

> Are there any installation instructions for this? See the [readme](https://github.com/mdellweg/pass_secret_service/blob/develop/README.md), https://github.com/mdellweg/pass_secret_service/issues/32#issuecomment-1239308966 , and https://github.com/mdellweg/pass_secret_service/issues/23#issuecomment-1239364257

> 1. some known users of the secret_service dbus API (is the API used at all?) Any app that uses `libsecret`, which is probably most GNOME apps (those that have...

> My point was more about adding this information to the README That's up to the developer. But better here than nowhere.

I think this can be left here for now. Adding this to the readme would require some rearrangement into appropriate sections, and better formatting. The issue references wouldn't be appropriate...

Related to #11. > Am I supposed to lock and unlock gpg? Probably, for now.

The way it's done with GPG KWallet, is you set up a passphrase-protected key via the likes of Kgpg or Kleopatra, and use that for the GPG encryption. The passphrase...

> Note that this means that anyone can decrypt your secrets without re-entering the passphrase, as long as it remains cached. If you want to require re-entry of the passphrase,...

> > The fix is to set the no-allow-external-cache option in ~/.gnupg/gpg-agent.conf > > Is this the fix for this issue? That's the fix for `pinentry` trying to read the...