Another idea is to try explicit request the key see if it works gpg --keyserver keys.gnupg.net --recv 767E7473
If it still can't connect to the keys server, then maybe a network issue? On Fri, Apr 14, 2017 at 10:59 AM, Michael Han <[email protected]> wrote: > Works for me: > > gpg2 --verify zookeeper-3.5.3-beta.tar.gz.asc zookeeper-3.5.3-beta.tar.gz > > gpg: Signature made Mon Apr 3 09:39:14 2017 PDT using RSA key ID 767E7473 > > gpg: Good signature from "Michael Han (CODE SIGNING KEY) <[email protected]>" > [ultimate] > > My gpg version: > > gpg2 --version > > gpg (GnuPG) 2.0.30 > > libgcrypt 1.7.6 > > Copyright (C) 2015 Free Software Foundation, Inc. > > A search indicates others hit similar issue, maybe this is only > reproducible for specific pgp and/or OS version? > > https://lists.gnupg.org/pipermail/gnupg-users/2015-October/054540.html > > On Fri, Apr 14, 2017 at 10:56 AM, Patrick Hunt <[email protected]> wrote: > >> Did you import the KEYS? >> >> Patrick >> >> On Fri, Apr 14, 2017 at 10:42 AM, Flavio Junqueira <[email protected]> >> wrote: >> >> > Michael, >> > >> > I can't verify the signature of the RC: >> > >> > $ gpg2 --verify zookeeper-3.5.3-beta.tar.gz.asc >> > zookeeper-3.5.3-beta.tar.gz >> > gpg: Signature made Mon Apr 3 18:39:14 2017 CEST using RSA key ID >> 767E7473 >> > gpg: requesting key 767E7473 from hkp server keys.gnupg.net >> > : can't connect to `keys.gnupg.net': host not found >> > gpgkeys: HTTP fetch error 7: couldn't connect: Not found >> > gpg: no valid OpenPGP data found. >> > gpg: Total number processed: 0 >> > gpg: Can't check signature: No public key >> > >> > Is there anything I'm doing wrong? >> > >> > -Flavio >> > >> > > On 03 Apr 2017, at 19:26, Michael Han <[email protected]> wrote: >> > > >> > > Hi all, >> > > >> > > This is the second release candidate (RC1) of 3.5.3-beta, following >> the >> > > first release candidate (RC0) cut off last week [1]. It fixes >> incorrect >> > > Implementation-Version information contained in the manifest file of >> the >> > > generated artifacts. There is no code changes, just regenerated and >> > > resigned artifacts. >> > > >> > > The full release notes are available at: >> > > >> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> > > projectId=12310801&version=12335444 >> > > >> > > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. >> **** >> > > >> > > Source files: >> > > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/ >> > > >> > > Maven staging repo: >> > > https://repository.apache.org/content/groups/staging/org/ >> > > apache/zookeeper/zookeeper/3.5.3-beta/ >> > > >> > > The tag to be voted upon: >> > > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1 >> > > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>* >> > > >> > > ZooKeeper's KEYS file containing PGP keys we use to sign the release: >> > > http://www.apache.org/dist/zookeeper/KEYS >> > > >> > > Should we release this candidate? >> > > >> > > [1] >> > > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/ >> > 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij >> > CrHUrw%40mail.gmail.com%3E >> > > >> > > -- >> > > Cheers >> > > Michael. >> > >> > >> > > > > -- > Cheers > Michael. > -- Cheers Michael.
