Note: This page is for planning a keysigning party hosted by LUG@UCLA.
A keysigning party is an event for helping people verify each others' PGP keys and strengthening the web of trust.
- take control of your privacy
- meet other interesting members of the privacy-aware community
- Where: Boelter Hall 4760
- When: TBA
Way before the party
- create a PGP key if you haven't already:
$ gpg --gen-key
WARNING: make sure you understand the implications of holding a private key, e.g. do not generate it on a computer you don't own and have full control over.
- sync your public key with keyservers:
$ gpg --send-keys $YOUR_KEY_ID
WARNING: this is irreversible. Make sure you are prepared to protect your private key and you are using a very strong passphrase.
- submit your public key to LUG@UCLA:
$ gpg --export --output YOURNAME.key
- upload to https://linux.ucla.edu/keysigning/
Right before the party
- download the keylist and keylist hash
$ wget https://linux.ucla.edu/keysigning/keylists/keylist.txt $ wget https://linux.ucla.edu/keysigning/keyrings/keylist.txt.sha1
- check to see if your key ID is on the list next to your name
- personally verify the hash:
$ sha1sum --check keylist.txt.sha1
- add the hash to the bottom of keylist.txt:
$ cat keylist.txt.sha1 >>keylist.txt
- print keylist.txt and keep safe
During the party
- bring the printed copy of keylist.txt
- bring one or more forms of ID (e.g. drivers license + Bruin card)
- eat pizza
After the party
- retrieve your annotated keylist
- for every person on the list with two check marks, import that person's key into your local keyring:
$ gpg --search-keys "First Last"
Q: how do I install GnuPG (gpg)?
A: if your operating system doesn't come with GnuPG already installed, you should seriously consider switching to a different operating system. If you're trying to use PGP on Windows or Mac, it kind of defeats the purpose because the software on your computer cannot be trusted to begin with. See Installfest