Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Fwd: Boston Linux Meeting Wednesday, September 18, 2013 - PGP/GnuPG Keysigning Party XIV



KEYSIZE for this year is 2048.

Key size 1024 is no longer considered safe for public keys expiring later
than Dec 2013.

Please use size 2048 this year, whether choosing RSA/RSA or DH/DSA (or RSA
or DSA signing-only keys)
Folks who have 1024 size keys should make 2048 keys. (You can sign the new
2048 with the old 1024 to prove it's the same person, and eventually revoke
the 1024 once enough people have seen the 2048.)

(3072 and 4096 are still too large for most purposes and may not be fully
supported. So 2048 is really the only choice.)

(ECC keys are still ok at 256 but are still only in DEV branch of GPG,
possibly due to Patent concerns, so aren't highly interoperable yet. Which
is too bad since strength per key length is better and not affected by
mathematical advances that put both RSA and DH in play in the future.  I'll
speak more on this Wednesday. Lots of news this year, besides what you've
seen on Cable TV news, which really shouldn't have been a surprise.)

http://news.netcraft.com/archives/2012/09/10/minimum-rsa-public-key-lengths-guidelines-or-rules.html
http://nakedsecurity.sophos.com/2013/05/27/anatomy-of-a-change-google-announces-it-will-double-its-ssl-key-sizes/





On Wed, Sep 11, 2013 at 7:32 AM, Jerry Feldman <gaf at blu.org> wrote:

> When: September 18, 2013 7PM (6:30PM for Q&A)
> Topic: PGP/GnuPG Keysigning Party
> Moderator:Bill Ricker
> Location: MIT Building E51, Room 315
>
>
> Summary
>         A talk about PGP and GnuPG, followed by a keysigning party.
>         Please Register your key in advance to participate!
>
> Abstract
>
>     A key signing party is a get-together of people who use the PGP
> encryption system with the purpose of allowing those people to sign each
> others keys. Key signing parties serve to extend the web of trust to a
> great degree. Key signing parties also serve as great opportunities to
> discuss the political and social issues surrounding strong cryptography,
> individual liberties, individual sovereignty, and even implementing
> encryption technologies or perhaps future work on free encryption software.
>
>     The basic workflow of signing someone's key is as follows:
>
>         Verify that the person actually is who they claim to be;
>         Have them verify their key ID and fingerprint;
>         Sign their key;
>         Send the signed key back to them
>
>     At the meeting, we go through the first two steps. Each person who
> preregistered their key will announce their presence and then read off
> their key ID and fingerprint, so everyone can verify that their copy of
> the list of keys is correct. Once we've run down the list, we line up,
> and each of us examines everyone else's photo IDs to verify that they
> are who they claim to be. After the meeting is over, each participant
> can then retrieve the keys that they've personally verified, sign those
> keys, and send the signed keys back to their respective owners.
>
>     In order to complete the keysigning in the allotted time, we follow
> a formal procedure as seen in V. Alex Brennen's "GnuPG Keysigning Party
> HOWTO", attached below. It is strongly advised that if you have not been
> to a keysigning party before, you read this document. We're using the
> List-based method for this keysigning party, and the keyserver at
> subkeys.pgp.net.
>
>     It is essential that, before the meeting, you register on the signup
> form listed in the attachments. You should bring at least one picture ID
> with you. You must also bring your own printout of the report on that
> page, so you can check off the names/keys of the people you have
> personally verified.
>
>     The list will be printed on Wednesday afternoon, the day of the
> meeting; be sure to register your key for the keysigning before that.
> The official cutoff time is 3:00 pm.
>
> Additional Links:
> Registration http://blu.org/keysignings/**keypartyregister.php<http://blu.org/keysignings/keypartyregister.php>
> GNUPG Keysigning Party Howto:
> http://www.cryptnet.net/fdp/**crypto/gpg-party.html<http://www.cryptnet.net/fdp/crypto/gpg-party.html>
> GNU Privacy Guard: http://www.gnupg.org/
>
> For further information and directions please consult the BLU Web site
> http://www.blu.org
> Please note that there is usually plenty of free parking in the E-51
> parking lot at 2 Amherst St, or directly on Amherst St.
>
> After the meeting we will adjourn to the official after meeting meeting
> location at The Cambridge Brewing Company
> http://www.**cambridgebrewingcompany.com/<http://www.cambridgebrewingcompany.com/>
>
> --
> Jerry Feldman <gaf at blu.org>
> Boston Linux and Unix
> PGP key id:3BC1EB90
> PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66  C0AF 7CEA 30FC 3BC1 EB90
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


-- 
Bill
@n1vux bill.n1vux at gmail.com



-- 
Bill
@n1vux bill.n1vux at gmail.com



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org