On Tuesday, 7 April 2020 14:36:04 BST gevisz wrote:
> I have a long standing "gpg can't check signature: No public key"
> error while running # emerge-webrsync
> It appears because the webrsync-gpg feature has been set in my
> make.conf however I do not want to switch it off.
> The app-crypt/gentoo-keys is installed, so it is not the reason for above
> error. I have just tried to download gentoo pgp keys manually with the
> command gpg --keyserver hkps://keys.gentoo.org --recv-keys
> 13EBBDBEDE7A12775DFDB1BABB572E0E2D182910
> and got the following error message:
> gpg: keyserver receive failed: No keyserver available
> Can anybody explain me how to fix this?

As a plain user I get this:

$ gpg --keyserver hkps://keys.gentoo.org --recv-keys 
13EBBDBEDE7A12775DFDB1BABB572E0E2D182910
gpg: enabled debug flags: memstat
gpg: data source: https://keys.gentoo.org:443
gpg: armor header: Version: SKS 1.1.6
gpg: armor header: Comment: Hostname: trogan.gentoo.org
gpg: key BB572E0E2D182910: number of dropped non-self-signatures: 13
gpg: pub  rsa4096/BB572E0E2D182910 2009-08-25  Gentoo Linux Release 
Engineering (Automated Weekly Release Key) <rel...@gentoo.org>
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
invalid signature
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: removing signature from key BB572E0E2D182910 on user ID "Gentoo Linux 
Release Engineering (Automated Weekly Release Key) <rel...@gentoo.org>": 
signature superseded
gpg: key BB572E0E2D182910/2C44695DB9F6043D: removed multiple subkey binding
gpg: using classic trust model
gpg: key BB572E0E2D182910: public key "Gentoo Linux Release Engineering 
(Automated Weekly Release Key) <rel...@gentoo.org>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: keydb: handles=3 locks=2 parse=0 get=2
gpg:        build=0 update=0 insert=1 delete=0
gpg:        reset=1 found=2 not=2 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=42 cached=30 good=28 bad=2
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/65536 bytes in 0 blocks


If you can't connect then you may have some network configuration issue, or 
potentially the keyserver is busy at this moment.  However, this would only be 
a temporary problem and you report you've been getting this regularly.

Do you see if port 443 is open from where you are?

$ nc -v -z keys.gentoo.org 443
DNS fwd/rev mismatch: keys.geodns-europe.gentoo.org != trogan.gentoo.org
keys.geodns-europe.gentoo.org [89.238.71.4] 443 (https) open


Alternatively, do you also have a problem using rsync?

BTW, I use rsync and do not have 'app-crypt/gentoo-keys' installed.  Instead I 
have 'app-crypt/openpgp-keys-gentoo-release' which is how Gentoo portage keys 
are propagated:

https://wiki.gentoo.org/wiki/Project:Portage/Repository_Verification

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to