All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] public key not found?
Date: Wed, 04 Sep 2013 10:15:34 -0600	[thread overview]
Message-ID: <52275CA6.2040809@redhat.com> (raw)
In-Reply-To: <52275B09.2060006@suse.de>

[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]

On 09/04/2013 10:08 AM, Andreas Färber wrote:
> Am 04.09.2013 15:11, schrieb Anthony Liguori:
>> 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
> 
> Doesn't "public key not found" rather indicate that you have not
> imported that key to your keyring yet, not even with untrusted status?
> 
> Some days ago I had asked about the indicated keyserver.cryptnet.net,
> which was ping'able but not reachable via http, https, ldap or hkp.
> Today there is a Fedora Apache test page via http, but still no success
> using that server with Seahorse.
> 
> Eric was said to have succeeded in uploading his key there?

If I recall, I had to upload my key by pasting it into the form on the
web-page, rather than my typical procedure of 'gpg --send-keys ...' with
a specific keyserver listing.  Don't know why the site seems to have
gone down in the meantime.

> 
> Usually it is no problem configuring multiple key servers for you to
> obtain our (untrusted) keys to at least improve the error message. :)

In particular, a lot of the keyservers participate in a sharing setup,
so that if you put your keys on one, they will show up in others within
a few hours.  I may be showing some bias, but I like:

Web interface at http://keys.fedoraproject.org or
https://keys.fedoraproject.org
HKP (keyserver protocol) by doing "gpg --keyserver
keys.fedoraproject.org --recv-keys 0x110810E9" (just an example)

You could also put in ~/.gnupg/gpg.conf:
  keyserver hkp://keys.fedoraproject.org


-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

      parent reply	other threads:[~2013-09-04 16:15 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
2013-09-04 16:08   ` Andreas Färber
2013-09-04 16:13     ` Anthony Liguori
2013-09-04 16:15     ` Eric Blake [this message]

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=52275CA6.2040809@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --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 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.