Make sure you're using the correct version of GPG. There's two major ones: 1 and the newer version 2. The link to "gpg" might give you either. If you don't have a key pair, make one. It seems like you do.
The public key you send out:
Code:
gpg2 --export -a you@your.host.net
Test GPG to yourself to make sure you can sign, encrypt and decrypt properly:
Code:
gpg2 -u you@your.host.net -r you@your.host.net -a --encrypt --sign file.txt
That should ask for your key password and create
file.txt.asc. Check you can decrypt it with:
Code:
gpg2 -d file.txt.asc
If this part doesn't work, there's no point in going further. Fix what went wrong first before involving a second party. The
-u parameter is in case you have multiple key pairs. On the other end, the person sending to you need set "
-r you@your.host.net" to encrypt
to you. If decryption is failing, they (the remote party) might not have encrypted to the right key.
GPG is kind of complex (in my opinion the reason it never really caught on outside of techies); you'd do well to spend some time reading a tutorial on it.