Ability to get your GPG passphrase from a keychain/password manager

21 votes

I have configured gpg to use the MacOS keychain to store my passphrase. From the command line, I am not prompted for my gpg passphrase when committing. However, selecting the same gpg binary in GitKraken, I am prompted. I'm guessing this is because you're passing a custom config to gpg and not using the one from my home dir.

This adds enough of a burden to committing with GitKraken that it's worth it to just switch to the command line for me.

For reference, my setup involves installing pinentry-mac from Homebrew and adding the following lines to ~/.gnupg/gpg-agent.conf:
use-standard-socket
pinentry-program /usr/local/bin/pinentry-mac

Under consideration Suggested by: Andy (30 Jun, '21) • Upvoted: 01 Dec, '23 • Comments: 2

Comments: 2

11 Aug, '22
Xander F.
I believe that this is really more of an issue of GitKraken supporting gpg-agent just like it supports a local ssh-agent so that you're not continually prompted for your ssh password.
1
03 Nov, '22
Kubijo
Can this please be addressed? There is no way I'm gonna enter the passphrase for every commit, making the auto-sign option unusable for daily practice
1