This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] request to sign software

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] request to sign software
From: Joanna Rutkowska <joanna@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 30 Mar 2010 11:46:49 +0200
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Stephen Spector <stephen.spector@xxxxxxxxxx>
Delivery-date: Tue, 30 Mar 2010 02:46:25 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:date:from:mime-version:to:cc:subject:references:in-reply-to:content-type; s=smtpout; bh=k4BGVrtNDekvkz/kphWxqTvPsGA=; b=KcChI/kz048DqbOe58R5D9296k+aqphTTvrfAiHEXGZSR3uvFHiROuOMx3Jm5Zok+1F4WS49mZqMu4/b9XCQEYm4EBs0PYuMsJwYlS680Wnuq8Gj7TvAjulNVFskiWQ+CDlpyp4j8BwlqS5tDKwyr4VBfaCP9ZgMVA4spt8eK2A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7D7600A.ECD8%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C7D7600A.ECD8%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.3
On 03/30/2010 09:00 AM, Keir Fraser wrote:
> On 29/03/2010 22:09, "Joanna Rutkowska" <joanna@xxxxxxxxxxxxxxxxxxxxxx>
> 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.
Right. But I think it would make lots of sense for Jeremy to tag, at
least some of the pvops branches (stable-2.6.{31.32}.x), anyway.
Otherwise this every-changing repo might scare away lots of people.
Perhaps Jeremy could apply some tag (and sign it) every week, or after
some more major merges, etc.

Would be nice e.g. to have some particular commit from the pvops marked
as the official release for the upcoming Xen 4.0.0, wouldn't it?


Attachment: signature.asc
Description: OpenPGP digital signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>