public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: Phillip Lougher <phil.lougher@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org,
	phillip@lougher.demon.co.uk
Subject: Re: Procedural requirements for restoring kernel.org accounts
Date: Thu, 20 Oct 2011 16:47:59 -0400	[thread overview]
Message-ID: <20111020204759.GB16820@thunk.org> (raw)
In-Reply-To: <CA+2-8GA-R3TETVLubOO8uMQq1a3-LmQ=STrXM1kf+8WbgfhTLQ@mail.gmail.com>

On Thu, Oct 20, 2011 at 09:33:20PM +0100, Phillip Lougher wrote:
> 
> I notice a key signing has been announced for the KS
> (http://sites.google.com/site/kernelsummit2011/gpg-key-verification) @
> 4.30pm on Tuesday, open to all LCE attendees.   However, I'm sure I'm
> not the only one who doesn't get into Prague early enough to go to
> this.  So, will there be another key signing session held during the
> three days of LCE, and will the procedure mentioned in the link above
> ("If you would like to participate, please send an e-mail to
> prague-key-submission@googlegroups.com") apply too?

If you're not going to be able to make the key signing on Tuesday,
please don't bother to send your key to
prague-key-submission@googlegroups.com, since that won't do much good.

Instead, I would suggest that you use the script called gpg-key2ps,
which can be found in a package called pgp-tools (Fedora/Red Hat/SuSE)
or signing-party (Debian/Ubuntu), or from the source tree found at
http://pgp-tools.alioth.debian.org.

This will print out your keys multiple times on a piece of paper, so
you can cut them into paper strips.  There will be many kernel
developers staying the whole week.  You can ask them to sign your key,
and then hand them one of the strips of paper.  You will need to
convince them of your identity; this can be done with government
issued ID, although some kernel developers may not be comfortable
doing this since they might not know what a Welsh identity card or UK
passport might look like.  So some kernel developers may only sign a
key if they know you personally.  Other kernel developers are willing
to trust government issued ID (I've been around the world enough so I
know what a UK passport looks like :-).

Regards,

						- Ted

  reply	other threads:[~2011-10-20 20:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 15:21 Answers to some common kernel.org account questions Greg KH
2011-10-14 18:54 ` Procedural requirements for restoring kernel.org accounts H. Peter Anvin
2011-10-20 20:33   ` Phillip Lougher
2011-10-20 20:47     ` Ted Ts'o [this message]
2011-10-20 21:24       ` Phillip Lougher
2011-10-20 21:09     ` Alan Cox
2011-10-20 21:16       ` Ted Ts'o
2011-10-20 21:20         ` H. Peter Anvin
2011-10-20 21:27       ` Phillip Lougher
2011-10-28  0:27   ` Aníbal Monsalve Salazar
2011-10-15  6:42 ` Answers to some common kernel.org account questions Willy Tarreau
2011-10-15 16:18   ` Greg KH
2011-10-15 17:04     ` Willy Tarreau

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=20111020204759.GB16820@thunk.org \
    --to=tytso@mit.edu \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil.lougher@gmail.com \
    --cc=phillip@lougher.demon.co.uk \
    /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