Hacker News Reader

It accepted an ascii-armored export of my key (gpg --armor --export $GPGKEY), have you tried to add that?

I did and it failed to parse.

same here, I tried with both gpg2 and gpg

PS: the problem was that I had multiple keys locally... but weirdly, now that I managed to upload my correct one, my commits are still seen as unsigned

Apparently I had the same issue... I specified the key ID when exporting, instead of the email address, and it worked!

Funny enough, in my case it was the opposite (but I have multiple keys for the same email address). Also, the problem about the commit still appearing ad unverified was just a temporary issue: by looking at another repository the changes were verified correctly (I guess that github caches gpg output, and doesn't reexecutes it with every page load, obviously)

Reply on news.ycombinator.com