From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stephen Spector <stephen.spector@citrix.com>,
Joanna Rutkowska <joanna@invisiblethingslab.com>
Subject: Re: request to sign software
Date: Thu, 1 Apr 2010 17:37:56 +0100 [thread overview]
Message-ID: <19380.52196.965181.226230@mariner.uk.xensource.com> (raw)
In-Reply-To: <C7D7600A.ECD8%keir.fraser@eu.citrix.com>
Keir Fraser writes ("Re: [Xen-devel] request to sign software"):
> 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.
Right. I think the best plan is to have a master key we use for
certifying other keys, including probably a single key for each
relevant tree.
So we'll have a key for xen-*.hg which we'll use with the hg repo
signing support to sign 4.0.0, a key for qemu-xen-*.git likewise, and
probably at least one more key for signing tarball releases.
I trust Jeremy can generate his own special key for generating a
signed tag for a suitable pvops version. Jeremy ?
The public half of the master key at least (and perhaps some of the
others) will be on the website and I'll cross-certify it with my own
personal PGP keys.
Ian.
next prev parent reply other threads:[~2010-04-01 16:37 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
2010-03-30 9:46 ` Joanna Rutkowska
2010-03-30 9:59 ` Keir Fraser
2010-04-01 16:37 ` Ian Jackson [this message]
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=19380.52196.965181.226230@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=Keir.Fraser@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.