Re: pgadmin3-1.20.0.dmg.sig can't be verified (while pgadmin3-1.18.1.dmg.sig can be)

On Thu, Dec 25, 2014 at 4:16 AM, Lei L <voidpointer00(at)gmail(dot)com> wrote:
> Hi,
>
> The GPG signature file "pgadmin3-1.20.0.dmg.sig" I downloaded from http://www.postgresql.org/ftp/pgadmin3/release/v1.20.0/osx/ can't be verified.
>
> C:\Inbox>gpg --verify pgadmin3-1.20.0.dmg.sig
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/documentation/faqs.html for more information
> gpg: Signature made Fri Dec 19 19:14:58 2014 CST using RSA key ID 698F1519
> gpg: Can't check signature: public key not found
>
>
> However, pgadmin3-1.18.1.dmg.sig CAN be verified
>
> C:\Inbox>gpg --verify pgadmin3-1.18.1.dmg.sig
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/documentation/faqs.html for more information
> gpg: Signature made Fri Oct 11 19:25:53 2013 CST using DSA key ID 1A19643B
> gpg: Good signature from "Dave Page <dpage(at)postgresql(dot)org>"
> gpg: aka "Dave Page <dpage(at)pgadmin(dot)org>"
> gpg: aka "Dave Page <dave(dot)page(at)enterprisedb(dot)com>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 752C 3D8A 5274 C381 9231 7EAA 9602 0E04 1A19 643B
>
>
> Something wrong with .sig?

That just means you don't have my key (which was replaced a year or so
back) in your keyring. You should be able to add it with:

gpg --recv 698F1519

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company