public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Kernel Summit 2012 keysigning party
Date: Wed, 22 Aug 2012 15:02:17 -0700	[thread overview]
Message-ID: <503556E9.6040101@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

Hi, all:

I'm going to try to organize a keysigning party at the Kernel Summit. As
it is pretty late in the game, I'm not sure we'd be able to fit it into
the schedules, but it doesn't hurt to try.

We'll be using the "hashed list" approach to make this quick and easy.
If you are not familiar with that procedure, please read
http://cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html#hash_based

You have to be present -- in person -- at the Kernel Summit in San Diego
next week in order to participate. If you are not coming to Kernel
Summit next week, please disregard this message.

If you want to participate, please send your key fingerprint by the end
of Friday, August 24th so I have enough time to distribute the hashed
list to participants.

Step 1: make sure your key is on the keyserver
Please read the friendly "man gpg" on how to upload your keys to the
keyservers.

Step 2: Send in your fingerprint
To generate the fingerprint, run "gpg --fingerprint your_email_address".
Send the output of that command to ks2012-keys@kernel.org. It doesn't
matter if that email is signed or not.

I will send more details about what comes next together with the hashed
list of all signatures received.


Best,
-- 
Konstantin Ryabitsev
Systems Administrator
Linux Foundation, kernel.org
Montréal, Québec




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 729 bytes --]

                 reply	other threads:[~2012-08-22 22:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=503556E9.6040101@kernel.org \
    --to=mricon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox