Git signed commits - How to suppress "You need a passphrase to unlock the secret key..."

git gnupg git-commit
friederbluemle picture friederbluemle · Jun 11, 2016 · Viewed 8.4k times · Source

I changed my global Git configuration to sign all commits. I also use gpg-agent so that I don't have to type my password every time.

Now every time I make a new commit I see the following five lines printed to my console:

[blank line]
You need a passphrase to unlock the secret key for
user: "John Doe <[email protected]>"
2048-bit RSA key, ID ABCDEF12, created 2016-01-01
[blank line]

Even worse, when I do a simple stash, this message is printed twice, needlessly filling my console (I assume for one for each of the two commit objects that are created).

Is there a way to suppress this output?

Answer

VonC picture VonC · Jun 11, 2016

This is more a gpg configuration issue than a git one.

Since you are using an agent, you could as a workaround add no-tty to your gpg.conf. 

echo 'no-tty' >> ~/.gnupg/gpg.conf

(this seems working even better than the --batch option)

Related questions

Git error - gpg failed to sign data

I just started using git and I install git and gpg via homebrew. For some reason, I get this error when i do git commit I looked at so many other stackoverflow questions regarding this topic and none of them …

Read More
Is there a way to "autosign" commits in Git with a GPG key?

Is there an easy way to make Git always signs each commit or tag that is created? I tried it with something like: alias commit = commit -S But that didn't do the trick. I don't want to install a different …

Read More
git - gpg onto mac osx: error: gpg failed to sign the data

I installed GPG from brew. brew install gpg It is gnupg2-2.0.30_2. When I commit, I do get a error message: You need a passphrase to unlock the secret key for user: "Max Mustermann (mycomment) <[email protected]>" 2048…

Read More