|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] keysigning party tomorrow
|
I've now got 9 fingerprints that I'll be bringing copies of to the meeting
tomorrow to be signed (if their owners are there). If you'd like to
participate, do "gpg -a --export your@email_address > file" and email me
the file. I have the following keys:
pub 1024D/0E9FF879 2000-09-05 Darxus <Darxus@ChaosReigns.com>
Key fingerprint = DE37 8846 3B06 B97C F661 D68F 7FB5 B0BE 0E9F F879
sub 1024g/2EEAB976 2000-09-05 [expires: 2001-09-05]
pub 1024D/52AC566B 2000-02-10 Michael C. Toren (MCT) <michael@toren.net>
Key fingerprint = 2FB7 80E0 BBF9 3E62 F4C8 13A9 D674 2149 52AC 566B
uid Michael C. Toren (MCT) <mct@netaxs.com>
uid Michael C. Toren (MCT) <mct@netisland.net>
sub 2048g/5818771B 2000-02-10
pub 1024D/E4642C01 2000-07-19 Bill Jonas <bj@linuxforce.net>
Key fingerprint = B3E2 E03E E859 8A18 62F1 C05B CBE5 06D8 E464 2C01
uid Bill Jonas (This address preferred) <bill@billjonas.com>
sub 1024g/C08A8580 2000-07-19
pub 1024D/B3EA8E22 1999-09-15 Chris Fearnley (Dare to be Naïve) <Chris@CJFearnley.com>
Key fingerprint = 91C9 D2CB AB50 FB01 86B7 2D5E B586 4017 B3EA 8E22
sub 1024g/55D53FE3 1999-09-15
pub 1024D/0FCC27C6 1999-06-01 David L. Coe <david.coe@someotherplace.org>
Key fingerprint = A360 2018 526B 3DFF 52BE E5AA B0F7 E8C6 0FCC 27C6
uid David Coe <david.coe@someotherplace.org>
uid David L. Coe <davidc@debian.org>
uid David Coe <davidc@debian.org>
sub 2048g/ADBFA039 1999-06-01
pub 1024D/EB281E23 1999-03-12 Alexander M. Shinn (f00f) <ashinn1@umbc.edu>
Key fingerprint = 919F 5B5E 589D 7FB6 EC3A 8092 1827 0C14 EB28 1E23
uid Alexander Shinn <foof@debian.org>
sub 2016g/7018A653 1999-03-12
pub 1024D/5AA5BCDF 2000-07-18 Michael J. Leone <userdude@yahoo.com>
Key fingerprint = 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
sub 2048g/BA1876EE 2000-07-18
pub 1024D/80675E65 1997-07-30 Leonard D. Rosenthol <leonardr@lazerware.com>
Key fingerprint = C76E 0497 C459 182D 0C6B AB6B CA10 B4DF 8067 5E65
uid Leonard D. Rosenthol <leonardr@life-online.org>
uid Leonard D. Rosenthol <leonardr@digapp.com>
uid Leonard D. Rosenthol <leonardr@westcodesoft.com>
sub 2048g/FD56CD08 1997-07-30
pub 1024D/69350CFC 2000-09-14 Pete Foley <lynchman@speakeasy.org>
Key fingerprint = A43C 0005 7464 9082 5CFF 478F 0F06 EE93 6935 0CFC
uid Pete Foley <pfoley@ecal.com>
sub 1024g/01F4B2E5 2000-09-14
On 09/21, Darxus@chaosreigns.com wrote:
> I'd like to do a keysigning party at the next plug meeting, after Mike
> Ryan's presentation on firewalls.
>
> To participate:
> * Email me your GPG key
> * Bring your photo ID (license / passport) to the meeting
> * Bring a *confirmed*copy* of your fingerprint to the meeting
>
> That's all you have to do.
>
> The rest of this email is an explanation of the process.
>
>
> "*confirmed*copy*" means that you printed or wrote it out, and confirmed
> its accuracy yourself. Get your fingerprint by doing "gpg --fingerprint
> your@email_address.com". It'll look like:
>
> pub 1024D/0E9FF879 2000-09-05 Darxus <Darxus@ChaosReigns.com>
> Key fingerprint = DE37 8846 3B06 B97C F661 D68F 7FB5 B0BE 0E9F F879
> sub 1024g/2EEAB976 2000-09-05 [expires: 2001-09-05]
>
>
> IF YOU DO NOT HAVE A GPG KEY, download gpg from www.gnupg.org (or your
> distribution's package archive), and install it, then run:
>
> gpg --gen-key
>
> Entering a "Real name" that matches your photo id will reduce
> complications.
>
>
> TO WRITE YOUR PUBLIC KEY TO A FILE to mail to me, do:
>
> gpg -a --export-key your@email_address.com > my.key.asc
>
> (substitute "your@email_address.com" with your address)
> And email me the file "my.key.asc"
>
>
>
> At the meeting:
> * I will distribute copies of everyone's fingerprints to all who are
> participating
> * Each participant will read off their *confirmed*copy* of their key, so
> that everyone else can verify with complete certainty that the key is
> valid.
> * Each participant will pass around their photo ID so that everyone can
> confirm their identity.
>
>
> After the meeting, every participant will download 1 file containing all
> participants' keys, import them (with "gpg --import plug.keyring"), and
> then sign each verified key, with:
>
> gpg --sign-key 0E9FF879
>
> Where "0E9FF879" is the key id of the key you're signing. Key IDs are
> listed here:
>
> ||||||||
> vvvvvvvv
> pub 1024D/0E9FF879 2000-09-05 Darxus <Darxus@ChaosReigns.com>
> Key fingerprint = DE37 8846 3B06 B97C F661 D68F 7FB5 B0BE 0E9F F879
> sub 1024g/2EEAB976 2000-09-05 [expires: 2001-09-05]
>
> --
> http://www.ChaosReigns.com
>
>
> ______________________________________________________________________
> Philadelphia Linux Users Group - http://www.phillylinux.org
> Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
> General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
--
http://www.ChaosReigns.com
______________________________________________________________________
Philadelphia Linux Users Group - http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|