Removing the need to manually enter a passphrase for GPG private keys.
I expect the following behavior when I'm unlocking my KeePassXC database..
Possible Solution).git commit -S -m "[...]", git push -u origin master, etc).We could execute a GPG command (e.g. encrypt Hello, world!) and pass the specified passphrase to GPG, although I think there's a better solution.
I've the same problem KeePassXC solved with the SSH-Agent plugin, but for GPG. My current, rather uncomfortable, solution is saving GPG key passphrases as normal entries and copying the password every time I restart my computer as they're are only being saved temporarly.
I did the same thing with SSH keys until the KeePassXC community made the SSH-Agent plugin. Srsly, I love the plugin as it removes a lot of manual actions performed by the end-user, especially if you've multiple keys (true in both scenarios for me).
There are already wonderful GPG tools like Kleopatra that also handle all the other aspects of GPG. As for the Git command, I simply auto-type the gpg password into the prompt using keepassxc.
As for the Git command, I simply auto-type the gpg password into the prompt using keepassxc.
Hmm.. this doesn't seem to be working on my end.


5700 is the process identifier, which, of course, is random.
I could rename all of my private key entries to archlinux, but this isn't a perfect solution as this will only work for a machine running linux with the hostname archlinux. Furthermore, there could be more factors than running linux and having the correct hostname (e.g. which desktop are you running on, etc).
You can use Ctrl+Shift+V to Auto-Type into the last selected window. It's unfortunate that the GPG window doesn't have a proper title.
OK. This is working and sadly still annoying as I'm using i3. I'd have to do the following actions to autotype manually..
UPDATE: I just found out this workaround doesn't work for me either as certain ASCII characters unfocused the window and thus prevented autotype to type the complete passphrase into the prompt.
GnuPG supports libsecret for storing the passphrase for pinentry. It should be possible to use the Secret Service implementation in KeePassXC to provide the passphrase automatically.
You can create the entry using pinentry-gtk-2, which has the option to store secrets (I couldn't find how pinentry sets the key for the GPG key). I made a small tutorial here.
Most helpful comment
You can create the entry using
pinentry-gtk-2, which has the option to store secrets (I couldn't find how pinentry sets the key for the GPG key). I made a small tutorial here.