[lug] Public Key Signings

[matthew.w.mcillece at lmco.com]

Is this an exercise to learn how to use encrypted email?  If so, I'm
interested.  What tool(s) do I need to generate the key, sign messages, etc?

> -----Original Message-----
> Date: Wed, 27 Sep 2000 11:21:25 -0600
> From: "Michael J. Pedersen" <marvin at keepthetouch.org>
> To: lug at lug.boulder.co.us
> protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1"
> Subject: [lug] Public Key Signings
> Reply-To: lug at lug.boulder.co.us
> 
> 
> --n8g4imXOkfNTN/H1
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: quoted-printable
> 
> Okay, I'm finally ready with the plan for all this. Sorry it's taken so
> lon=
> g,
> I've been busy with work (200+ makefiles really does suck, BTW).
> 
> Basically, here's what I'll be asking everybody to do:
> 1) Reply to this message. When you do, include your public key (or public
> k=
> ey
> id, if you have your key uploaded to a server), and, very important, SIGN
> y=
> our
> reply with your key.
> 
> 2) Show up at the next lug meeting. Bring along a couple of things with
> you:
> 	a) Some form of identification. Picture ID is a must, unless I
> already
> 	know you from the last meeting.
> 	b) Your public key id number (should be 8 characters long).
> 	c) Your public key fingerprint.
> 
> 3) After the presentation and Q&A are over, I'll be finding people,
> matching
> names with keys, verifying identities with the above information I asked
> you
> to bring along. If possible, I'll do this up at front of the room, to make
> =
> it
> quicker.
> 
> 4) After that's done, anybody that would like a copy of my public key,
> plea=
> se
> come see me. I'll have a laptop along with me, and will give you a signed
> c=
> opy
> of my public key right then and there on a floppy. Note that this copy
> will=
>  be
> signed while you watch, if you wish.
> 
> 5) After you've gotten it, please take it home, sign it, and send it back
> to
> me.
> 
> 6) I'll be setting up a keyserver (with Sean's help) specifically for the
> l=
> ug,
> where we can all get these keys easily.
> 
> With Wayde's permission, I'll do this each month at the meetings.
> 
> Finally, in January, I'll be going over all of this at the meeting in a
> talk
> about GPG, PGP, and other encryption issues (though those will be my main
> focus). Anybody that has any suggestions, please pass them along. I'll
> glad=
> ly
> take them.
> 
> --=20
> Michael J. Pedersen
> My GnuPG KeyID: 4E724A60        My Public Key Available At:
> wwwkeys.pgp.net
> My GnuPG Key Fingerprint: C31C 7E90 5992 9E5E 9A02 233D D8DD 985E 4E72
> 4A60
> GnuPG available at http://www.gnupg.org
> 
> --n8g4imXOkfNTN/H1
> Content-Type: application/pgp-signature
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.3 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE50iyU2N2YXk5ySmARAgLVAJ93DDeLa++sWIpRquyhaygZJl4/fwCgusK1
> 4DJrik8Akvx9OtflPafmENY=
> =E1YR
> -----END PGP SIGNATURE-----
> 
> --n8g4imXOkfNTN/H1--
>