Okay, I knew less than I thought about GPG! The above link was helpful. GPGee may need to be configured. I did not get the comment info in the verify command initially so I configured GPGee. After I got the info, I cleared out the configuration parameters as a test. It was still ok. Here are some of the GPG commands I needed to refresh my memory on:
- gpg –refresh-keys –keyserver pgp.mit.edu
- gpg –import kurt.asc
- gpg –edit-key kurt@somebody.org
- The search pages for keyservers did not find my public key until I put the 0x at the front of uid. When in doubt use the email address!
- I actually was not able to verify my exported public key with the –verify command. I got an error about unexpected data. Huh?
Despite my obvious stumbles with GPG, GPGee works as advertised and it should make working with GPG signatures practically painless.
Related posts:
- Gpg4win - EMail-Security using GnuPG for Windows
- RE: GnuPG Explorer Extension (GPGee) version 1.2.1 released
- gpg4win - EMail-Security using GnuPG for Windows
- Picks and Pans for pfSense packages
- Putty configuration
Related posts brought to you by Yet Another Related Posts Plugin.
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.
Leave a Comment