From: Ricardo Wurmus <rekado@elephly.net>
To: Quiliro <quiliro@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: Retrieving the OpenPGP key used to sign the release
Date: Wed, 24 May 2017 20:27:35 +0200 [thread overview]
Message-ID: <87shju8608.fsf@elephly.net> (raw)
In-Reply-To: <20170524131848.6ce8ebd9@riseup.net>
Quiliro <quiliro@riseup.net> writes:
> El Tue, 23 May 2017 22:24:38 +0200
> ludo@gnu.org (Ludovic Courtès) escribió:
>
>> Quiliro <quiliro@riseup.net> skribis:
>>
>> > $ gpg --verify guixsd-usb-install-0.13.0.i686-linux.xz.sig
>> > gpg: supozas subskribitajn datenojn en 'guixsd-usb-install-0.13.0.i686-linux.xz'
>> > gpg: Signature made lun 22 Maj 2017 07:51:35 -0500 ECT using RSA key ID 3D9AEBB5
>> > gpg: Ne povas kontroli subskribon: publika ŝlosilo ne trovita
>> >
>> > $ gpg --keyserver keys.gnupg.net --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
>> > gpg: requesting key 3D9AEBB5 from hkp server keys.gnupg.net
>> > ?: keys.gnupg.net: Host not found
>> > gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused
>> > gpg: validaj OpenPGP-datenoj ne trovitaj.
>> > gpg: Nombro traktita entute: 0
>>
>> Oops, keys.gnupg.net seems to be retired. Please use
>> pool.sks-keyservers.net instead, for example.
>
> How? Is that documented?
Instead of
gpg --keyserver keys.gnupg.net --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
use
gpg --keyserver pool.sks-keyservers.net --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-05-24 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 13:16 GNU Guix & GuixSD 0.13.0 released Ludovic Courtès
2017-05-22 14:01 ` Catonano
2017-05-22 15:38 ` Quiliro
2017-05-23 20:24 ` Retrieving the OpenPGP key used to sign the release Ludovic Courtès
2017-05-24 18:18 ` Quiliro
2017-05-24 18:27 ` Ricardo Wurmus [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shju8608.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=quiliro@riseup.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).