From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] public key not found?
Date: Wed, 04 Sep 2013 16:30:10 +0200 [thread overview]
Message-ID: <522743F2.2020808@redhat.com> (raw)
In-Reply-To: <CA+aC4ksuT+nOPUiwpiCzubdD0OPrACmQ1uUmB-FpHRnLYVhZ2Q@mail.gmail.com>
Il 04/09/2013 15:11, Anthony Liguori ha scritto:
> On Wed, Sep 4, 2013 at 6:47 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>> I noticed recent merges of the pci tree have this text:
>>
>> # gpg: Signature made Sun 01 Sep 2013 03:15:36 AM CDT using RSA key
>> # ID D28D5469
>> # gpg: Can't check signature: public key not found
>>
>> Why is that?
>
> Because I haven't signed your key. We'll address this at this year's KVM Forum:
>
> http://wiki.qemu.org/KeySigningParty2013
>
>> Linus seems to have no trouble pulling trees with this
>> signature, and pulls don't have this error message.
>
> I'm not sure how wide Linus extends his trust.
Getting a kernel.org account requires 3 signatures from someone else who
has a kernel.org account *and* communicating the particular key to the
kernel.org sysadmins. So I guess Linus extends his trust to all keys
that were processed this way, or something like that.
Paolo
next prev parent reply other threads:[~2013-09-04 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 11:47 [Qemu-devel] public key not found? Michael S. Tsirkin
2013-09-04 13:11 ` Anthony Liguori
2013-09-04 14:30 ` Paolo Bonzini [this message]
2013-09-04 16:08 ` Andreas Färber
2013-09-04 16:13 ` Anthony Liguori
2013-09-04 16:15 ` Eric Blake
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=522743F2.2020808@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).