Arch Linux

Haroon

Member

From: Germany

Registered: 2017-02-14

Posts: 24

[Solved] Issue fetching keys with gpg

Possible solution in last post.
Hello everyone

I've been trying my hand on GPU passtrough for a while now and I wanted to install linux-vfio kernel so I could try to fix a problem with a bad IOMMU group, which has my guest GPU and my processor in it.

Trying to install the linux-vfio kernel I got the following error which I can't resolve.

==> Verifying source file signatures with gpg...
    linux-4.9.tar ... FAILED (unknown public key 79BE3E4300411886)
    patch-4.9.8 ... FAILED (unknown public key 38DBBDC86092693E)

I've been trying to import a key with gpg for a while now I tried a bunch of different things but I keep getting the same Error
I installed the gnupg package with pacman.

gpg --recv-key 79BE3E4300411886

gpg: keyserver receive failed: No keyserver available

gpg --keyserver na.pool.sks-keyservers.net --recv-keys 79BE3E4300411886
gpg --keyserver pgp.mit.edu --recv-keys 79BE3E4300411886

gpg: keyserver receive failed: No keyserver available

these where not present I made them myself
cat /home/haroon/.gnupg/gpg.conf and dirmngr.conf

keyserver hkp://pool.sks-keyservers.net
keyserver eu.pool.sks-keyservers.net
keyserver na.pool.sks-keyservers.net
keyserver oc.pool.sks-keyservers.net
keyserver hkps.pool.sks-keyservers.net

I also looked at the following links which didn't help me solve the issue.
https://forum.manjaro.org/t/failed-to-v … ty/17641/4
https://www.se7ensins.com/forums/thread … 980/page-9
https://bbs.archlinux.org/viewtopic.php?id=192347

Also I can't find the key 00411886 on the website http://pgp.mit.edu .

Thanks for any help you can provide.

Last edited by Haroon (2017-02-18 22:52:56)

Azured

Member

Registered: 2014-02-08

Posts: 9

Re: [Solved] Issue fetching keys with gpg

Try this to see if you can even resolve the keyservers?

https://bbs.archlinux.org/viewtopic.php?id=220996

$ gpg-connect-agent --dirmngr
...
> keyserver --resolve hkp://pool.sks-keyservers.net

On my machine I get

[azured@archdesktop ~]$ gpg-connect-agent --dirmngr
> keyserver --resolve hkp://pool.sks-keyservers.net
S # http://fratercula.nerds.lu:11371
OK
> 

Haroon

Member

From: Germany

Registered: 2017-02-14

Posts: 24

Re: [Solved] Issue fetching keys with gpg

I get this output for your suggestion

$ gpg-connect-agent --dirmngr
gpg-connect-agent: no running Dirmngr - starting '/usr/bin/dirmngr'
gpg-connect-agent: waiting for the dirmngr to come up ... (5s)
gpg-connect-agent: connection to the dirmngr established
> keyserver --resolve hkp://pool.sks-keyservers.net
ERR 167772206 Syntax error in URI <Dirmngr>

I get another error now

gpg -recv-keys --keyserver http://pgp.mit.edu 79BE3E4300411886
gpg: can't open '79BE3E4300411886'

The debuglog

gpg -vvv --debug-all --recv-keys --keyserver http://pgp.mit.edu 79BE3E4300411886
gpg: reading options from '/home/haroon/.gnupg/gpg.conf'
gpg: using character set 'utf-8'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_3 <- # Home: /home/haroon/.gnupg
gpg: DBG: chan_3 <- # Config: /home/haroon/.gnupg/dirmngr.conf
gpg: DBG: chan_3 <- OK Dirmngr 2.1.18 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.1.18
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KEYSERVER --clear http://pgp.mit.edu
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_GET -- 0x79BE3E4300411886
gpg: DBG: chan_3 <- ERR 167772346 No keyserver available <Dirmngr>
gpg: keyserver receive failed: No keyserver available
gpg: DBG: chan_3 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: secmem usage: 0/32768 bytes in 0 blocks

I hope this helps me in some way

Haroon

Member

From: Germany

Registered: 2017-02-14

Posts: 24

Re: [Solved] Issue fetching keys with gpg

I managed to solve the Issue, it is a bug in the newer gnupg packages, it exists since gnupg-2.1.17+.
You can try to install a older package gnupg-2.1.16-2.
If that doesn't work you can also download the file from the archive download it to your system and then execute

$sudo pacman -U "path to the package"

I hope this helps anyone has will have this issue in the future.

Last edited by Haroon (2017-08-20 11:25:22)