public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: linux-kernel@vger.kernel.org,
	ksummit-2013-discuss@lists.linuxfoundation.org
Subject: Kernel Summit 2013 keysigning
Date: Tue, 24 Sep 2013 16:33:34 -0400	[thread overview]
Message-ID: <20130924203334.GA17514@gmail.com> (raw)

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

Hi, all:

We're about a month away from the Kernel Summit in Edinburgh, so I'm
organizing another keysigning event. Since this is the second time I'm
doing it, hopefully I'll be bitter^W better prepared and have cuter
stickers.

We'll be using the "hashed list" approach again, 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 Edinburgh
next month in order to participate. If you are NOT coming to Kernel
Summit, please disregard this message.

If you want to participate, please send your key fingerprint by the end
of Tuesday, October 15th 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 ks2013-keys@kernel.org. It doesn't
matter if your 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
Senior Systems Administrator
Linux Foundation Collab Projects
Montréal, Québec

[-- Attachment #2: Type: application/pgp-signature, Size: 665 bytes --]

                 reply	other threads:[~2013-09-24 20:33 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=20130924203334.GA17514@gmail.com \
    --to=mricon@kernel.org \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.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