News for hackers. Stuff that matters.

A comment on GPG signature verification. Parent comment

Re:GPG signature verification by alain_gilbert on Tuesday April 05, 2016 @09:01PM (#11435861)
There is no UI that allows you to specify that you want the merge commit to be signed.

And if you configure git to sign all commits, you get this error:

https://confluence.atlassian.com/sourcetreekb/sourcetree-com...

[ Parent | on HN ]
Re:GPG signature verification by standardhuman on Tuesday April 05, 2016 @11:26PM (#11436410)
For what it's worth, I had that same error message (OS X), and I managed to fix it. After using homebrew to make sure my git was up-to-date and gpg was also installed correctly, I told git where gpg is (for some reason, despite being in my PATH, it wasn't registering?): git config --global gpg.program /usr/local/bin/gpg

After that, I had to make a tweak to gpg so I didn't get another annoying error. In ~/.gnupg/gpg.conf, adding 'no-tty' got everything working smoothly.

I agree that that was way too tedious, but it did work out. :)

[ Parent | on HN ]
Re:GPG signature verification by alain_gilbert on Wednesday April 06, 2016 @04:20PM (#11441703)
It looks like adding the no-tty in gpg.conf fixed it :D

Thank you !

[ Parent | on HN ]
Re:GPG signature verification by standardhuman on Wednesday April 06, 2016 @04:58PM (#11442043)
No problem. :) I'm glad it worked out for you!
[ Parent | on HN ]
Re:GPG signature verification by mrsteveman1 on Tuesday April 05, 2016 @09:18PM (#11435921)
> There is no UI that allows you to specify that you want the merge commit to be signed.

Ah ok, I see what you mean. I don't think theres a way to have rebase re-sign things inside SourceTree either, I run in to that one constantly and have to open a terminal.

[ Parent | on HN ]