On Wed, Apr 13, 2016 at 10:06:11PM +1000, Russell Coker wrote:
Also it would be handy if there was a tool to check your GPG configuration and key setup for obvious mistakes.
And in proof that I had had neither enough caffeine nor blood moving through my brain; I have now remembered and confirmed that all that info is available from --list-packets and more human readable with pgpdump. So scripting something which uses export of the public key and then list-packets to check it should be fairly straight forward. I figure some little command line thing where you enter a key ID, fingerprint or UID and it'll do the rest. For UIDs then checking the secret keyring first is probably best, but multiple matches can either be dealt with a "pick one from the list" option or just running the check against every match (maybe, some public keyrings are getting a bit large now). Anyway, I'll check with the others and make sure there isn't already something like that tucked away somewhere and if not then it seems like a good side project to add somewhere. I just need to decide precisely where. Regards, Ben -- | Ben McGinnes | Adversarial Press | Twitter: benmcginnes | | Writer, Publisher, Systems Administrator, Trainer, ICT Consultant | | http://www.adversary.org/ http://publishing.adversary.org/ | | GPG Made Easy (GPGME) Python 3 API Maintainer, GNU Privacy Guard | | https://www.gnupg.org/ https://ssd.eff.org/ | | GPG key: 0x321E4E2373590E5D http://www.adversary.org/ben-key.asc |