From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stephen Spector <stephen.spector@citrix.com>
Subject: Re: request to sign software
Date: Tue, 30 Mar 2010 08:00:10 +0100 [thread overview]
Message-ID: <C7D7600A.ECD8%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BB11706.5020301@invisiblethingslab.com>
On 29/03/2010 22:09, "Joanna Rutkowska" <joanna@invisiblethingslab.com>
wrote:
> ...and then publish it on xen.org and sent to xen-devel. The list is
> mirrored in a few places, so it would not be trivial for the attacker to
> subvert the public key in all the public archives. Users can always use
> more than one different internet connections to verify the key, to get
> around potential compromise at an ISP level.
>
> This could be your "master key" and then you could simply sign other
> keys (e.g. Jermey's, Keir's, etc) with this master key (simple gpg -s,
> no certs, no web of trust, needed).
I chatted with Ian Jackson about this, and our thought was to generate a
xen.org master key which we would keep safe in Cambridge: only he and I
would have copies of it (the two of us, for redundancy). We can also
generate a software-signing key, signed by the master key, which we actually
use for the business of signing releases from the xen-*.hg and
qemu-xen-*.git repositories.
We weren't sure it makes sense for Jeremy to sign anything since he's not
actually making releases out of his repository. If we decide that Jeremy
should sign things I think it best he makes his own key and we sign it with
the master key.
-- Keir
next prev parent reply other threads:[~2010-03-30 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 10:02 request to sign software Joanna Rutkowska
2010-03-29 17:47 ` Jeremy Fitzhardinge
2010-03-29 21:09 ` Joanna Rutkowska
2010-03-30 7:00 ` Keir Fraser [this message]
2010-03-30 9:46 ` Joanna Rutkowska
2010-03-30 9:59 ` Keir Fraser
2010-04-01 16:37 ` Ian Jackson
2010-04-01 20:06 ` Weird RAM handling with Xen 3.4.3-RC3 Thomas Goirand
2010-03-30 9:58 ` request to sign software Joanna Rutkowska
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=C7D7600A.ECD8%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=joanna@invisiblethingslab.com \
--cc=stephen.spector@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.