Nota Bene
The key indicated below has been compromised since around 03/2007. I'll generate a new one and upload it to the MIT key server when my domain is securely back in place.

---

to generate a gpg key, run the following:

gpg --gen-key

when that completes, run

gpg --list-keys <email you used>

for instance, to get the key information from my pub key, I run:

$ gpg --list-keys cjcollier@mysql.com
pub 1024D/6CC27EA8 2001-04-27
uid C.J. Collier <cjcollier@colliertech.org>
uid C.J. Collier <cjcollier@sinclair.net>
uid C.J. Collier <cjcollier@mysql.com>
uid [jpeg image of size 9187]

After you generate it, you should publish your public key:

gpg --keyserver pgp.mit.edu --send-keys <your id>

mine looks like this:

$ gpg --keyserver pgp.mit.edu --send-keys 6CC27EA8
gpg: sending key 6CC27EA8 to hkp server pgp.mit.edu

You can get my GnuPG key with the following command:

$ gpg --keyserver pgp.mit.edu --recv-keys 6CC27EA8

Let me know what your ID is when you complete this. When I see you
next, I'll sign your key. Provided you remind me :)

Tags: authentication, chapter 19.34 rcw, electronic authentication act, gpg, rcw 19.34, security