[ale] URGENT! Need HELP to Salvage GPG PGP Key Signing for Nov.19th!

[Jeremy T. Bouse]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

    The problem with using the MIT key servers vs subkeys.pgp.net is
that the MIT key servers have had problems corrupting keys that use
subkeys. I myself use subkeys exclusively and only pull my primary key
out of the safe when I'm signing someone's key or re-issuing new
subkeys as per my key usage policy.

    For the purpose of a keysigning party like this having a keyring
for the party can make it easier to get all the keys to sign, as not
everyone has published their public keys to the keyservers usually. If
everyone is submitting their keys prior to the signing event then they
are all easily collected and can be provided to all.

Derek Carter (aka goozbach) wrote:
> On 11/12/2009 11:06 AM, aaron wrote:
>> Thanks for the offer, Jeremy!
>>
>> The physical part of hosting the key signing party is straight
>> forward enough that I think I can step up to handle that --
>> basically just organizing the steps of confirming fingerprints
>> and ID from the distributed list of submitted pre-registrations.
>> I'd also be happy to handle compiling that check list with
>> everyone's User ID, Key Type, Key Size, and Hex Fingerprint from
>> the required pre-registration emails.
>>
>> I'm not, however, up to speed on arranging a key server or
>> setting up a key ring (as you suggested), so that is where we're
>> seeking some help.  I'll include your offer in the options and be
>> in touch off list.
>>
>
> Any reason not to use MIT keyservers? They're kinda the "de facto"
>  "authoritative" keyservers for PGP/GPG.
>
> -- Derek aka gooz
>
> _______________________________________________ Ale mailing list
> Ale at ale.org http://mail.ale.org/mailman/listinfo/ale See JOBS,
> ANNOUNCE and SCHOOLS lists at http://mail.ale.org/mailman/listinfo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iF0EARECAB0FAkr8RMAWGGhrcDovL3N1YmtleXMucGdwLm5ldAAKCRCagQNPdb5V
OeH0AJ9f5XKWMhT1jfef+VY+qzdALBZpwwCg4U7pfHosr0lC6gRHXPoOdCVYhqk=
=AvNw
-----END PGP SIGNATURE-----