qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, Michael Roth <mdroth@linux.vnet.ibm.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [qemu-web RFC PATCH] _download/source.html: show the GPG fingerprint for releases
Date: Mon, 8 Mar 2021 14:57:11 +0100	[thread overview]
Message-ID: <03f8be00-7ae7-45ed-bc27-02fbb8aeee62@redhat.com> (raw)
In-Reply-To: <20210308111649.14898-1-alex.bennee@linaro.org>

On 08/03/2021 12.16, Alex Bennée wrote:
> At the moment we mention the signature but don't actually say what it
> is or how to check it. Lets surface the fingerprint on the information
> along with a guide of how to verify the download.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>   _download/source.html | 13 ++++++++++---
>   1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/_download/source.html b/_download/source.html
> index 35fd156..6c2f6f6 100644
> --- a/_download/source.html
> +++ b/_download/source.html
> @@ -8,14 +8,21 @@
>   	<div id="releases">
>   	{% include releases.html %}
>   	</div>
> -	<p>or stay on the bleeding edge with the
> -	   <a href="https://gitlab.com/qemu-project/qemu">git repository!</a></p>
> -
> +	<p>
> +          Our source code tarballs are signed with the release
> +          managers key, fingerprint:

I'd like to suggest to replace the above sentence with:

Our source code tarballs are signed with the
<a 
href="http://hkps.pool.sks-keyservers.net/pks/lookup?op=vindex&fingerprint=on&search=0xCEACC9E15534EBABB82D3FA03353C9CEF108B584">release 
managers key</a>. The fingerprint of this key is:


> +          <pre><code>CEAC C9E1 5534 EBAB B82D  3FA0 3353 C9CE F108 B584</code></pre>.
> +          Alternatively stay on the bleeding edge with the
> +	  <a href="https://gitlab.com/qemu-project/qemu">git repository!</a></p>
>   	<h2>Build instructions</h2>
>   
>   	{% for release in site.data.releases offset: 0 limit: 1 %}
>   	<p>To download and build QEMU {{release.branch}}.{{release.patch}}:</p>
>   <pre>wget https://download.qemu.org/qemu-{{release.branch}}.{{release.patch}}.tar.xz
> +# optional verify signature
> +wget https://download.qemu.org/qemu-{{release.branch}}.{{release.patch}}.tar.xz.sig
> +gpg --output qemu-{{release.branch}}.{{release.patch}}.tar.xz --verify qemu-{{release.branch}}.{{release.patch}}.tar.xz.sig
> +# extract and build
>   tar xvJf qemu-{{release.branch}}.{{release.patch}}.tar.xz
>   cd qemu-{{release.branch}}.{{release.patch}}
>   ./configure
> 

  Thomas



  parent reply	other threads:[~2021-03-08 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 11:16 [qemu-web RFC PATCH] _download/source.html: show the GPG fingerprint for releases Alex Bennée
2021-03-08 13:44 ` Paolo Bonzini
2021-03-08 13:57 ` Thomas Huth [this message]
2021-03-08 14:03 ` Peter Maydell

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=03f8be00-7ae7-45ed-bc27-02fbb8aeee62@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).