[SOLVED] One or more PGP signatures could not be verified!

TheChosenOne · 2019-03-16 16:27:55

yaourt -S spotify

spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90)
==> ERROR: One or more PGP signatures could not be verified!

sudo gpg --recv-key A87FF9DF48BF1C90

gpg: key A87FF9DF48BF1C90: public key "Spotify Public Repository Signing Key <tux@spotify.com>" imported
gpg: Total number processed: 1
gpg: imported: 1

yaourt -S spotify

spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90)
==> ERROR: One or more PGP signatures could not be verified!

wat?

Last edited by TheChosenOne (2019-03-17 20:23:01)

WorMzy · 2019-03-16 16:37:09

You used sudo, so you added the key to root's keychain. Makepkg doesn't run as root. Run gpg without sudo.

TheChosenOne · 2019-03-16 16:49:48

gpg: keyserver receive failed: Permission denied

loqs · 2019-03-16 17:16:05

If you have not configured dirmngr for root or the none root user and the network connection you were using is the same please try:

killall dirmngr #kill the current dirmngr to hopefully use a different one from the pool on next use
gpg --recv-key A87FF9DF48BF1C90

Last edited by loqs (2019-03-16 18:01:36)

WorMzy · 2019-03-16 18:00:09

If that doesn't work either then post the output of

ls -la ~/.gnupg

TheChosenOne · 2019-03-16 19:42:15

Still the same:

gpg: keyserver receive failed: Permission denied

ls -la ~/.gnupg

drwxr-xr-x 2 thechosenone thechosenone 4096 Oct 5 2015 crls.d
-rw------- 1 thechosenone thechosenone 2643 May 24 2016 dirmngr.conf
-rw------- 1 thechosenone thechosenone 42 Oct 5 2015 gpg-agent.conf
-rw------- 1 thechosenone thechosenone 7711 Mar 2 2017 gpg.conf
-rw-r--r-- 1 thechosenone thechosenone 0 Feb 2 2015 .gpg-v21-migrated
-rw-r--r-- 1 thechosenone thechosenone 684 May 13 2014 key.txt
drwxr-xr-x 2 thechosenone thechosenone 4096 Oct 6 2017 openpgp-revocs.d
drwx------ 2 thechosenone thechosenone 4096 Oct 6 2017 private-keys-v1.d
-rw------- 1 thechosenone thechosenone 33583 Oct 5 2015 pubring.gpg
-rw------- 1 thechosenone thechosenone 33583 Oct 5 2015 pubring.gpg~
-rw-r--r-- 1 thechosenone thechosenone 44071 Dec 23 15:57 pubring.kbx
-rw-r--r-- 1 thechosenone thechosenone 42798 Oct 6 2017 pubring.kbx~
-rw------- 1 thechosenone thechosenone 600 Jan 12 22:19 random_seed
-rw------- 1 thechosenone thechosenone 12859 Feb 2 2015 secring.gpg
-rw-r----- 1 thechosenone thechosenone 676 Oct 5 2015 sshcontrol
-rw-r--r-- 1 thechosenone thechosenone 49152 Dec 23 15:57 tofu.db
-rw------- 1 thechosenone thechosenone 2480 Dec 23 23:11 trustdb.gpg

Last edited by TheChosenOne (2019-03-16 19:42:38)

loqs · 2019-03-16 20:37:18

Is there a keyserver specified in ~/.gnupg/dirmngr.conf ? If there is and you comment it out then then restart dirmngr again is the result the same?

TheChosenOne · 2019-03-16 21:03:15

This is what is says:

keyserver hkp://keys.gnupg.net

Commented it out, but behavior is still the same (I did killall dirmngr).

Last edited by TheChosenOne (2019-03-16 21:05:03)

loqs · 2019-03-16 21:09:16

Did root have a different keyserver configured in its ~/.gnupg/dirmngr.conf?

TheChosenOne · 2019-03-16 21:40:08

It doesn't have this file.

drwx------ 2 root root 4096 Oct 15 2016 crls.d
drwx------ 2 root root 4096 Jun 30 2018 private-keys-v1.d
-rw-r--r-- 1 root root 36235 Mar 16 17:20 pubring.kbx
-rw-r--r-- 1 root root 34923 Oct 20 20:12 pubring.kbx~
-rw------- 1 root root 1200 Oct 20 20:12 trustdb.gpg

WorMzy · 2019-03-16 22:45:31

Please use code tags, not quote tags, for terminal output.

Post the output of

gpg --debug-level guru --recv-key A87FF9DF48BF1C90

TheChosenOne · 2019-03-16 23:35:25

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/thechosenone/.gnupg
gpg: DBG: chan_3 <- # Config: /home/thechosenone/.gnupg/dirmngr.conf
gpg: DBG: chan_3 <- OK Dirmngr 2.2.13 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.2.13
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KEYSERVER --clear hkp://subkeys.pgp.net
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_GET -- 0xA87FF9DF48BF1C90
gpg: DBG: chan_3 <- ERR 167804929 Permission denied <Dirmngr>
gpg: keyserver receive failed: Permission denied
gpg: DBG: chan_3 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
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/32768 bytes in 0 blocks

loqs · 2019-03-16 23:42:51

TheChosenOne wrote:

This is what is says:
keyserver hkp://keys.gnupg.net
Commented it out, but behavior is still the same (I did killall dirmngr).

gpg: DBG: chan_3 -> KEYSERVER --clear hkp://subkeys.pgp.net

This seems to show it is still enabled / in use.
Edit:
It appears to a different server but it does not appear to be in the default pool https://sks-keyservers.net/status/
What is the contents of ~/.gnupg/dirmngr.conf now?
Edit2:
Please also check if there is a keyserver entry in ~/.gnupg/gpg.conf

Last edited by loqs (2019-03-16 23:53:15)

TheChosenOne · 2019-03-17 12:25:18

Problem solved. Thanks for all the help!
There was still a keyserver in ~/.gnupg/gpg.conf (hkp://subkeys.pgp.net).
Is there a problem with this keyserver?

WorMzy · 2019-03-17 17:33:17

Apparently.

Please remember to mark your thread as solved by editing the first post and amending the topic title.

Virax · 2019-11-12 19:03:01

Hi !

I had the same issue, but the solutions you suggested here didn't worked for me.
However, i could resolve it by downloading the spotify's public key directly from their repos and added it to the list of gpg keys:

 curl -sS https://download.spotify.com/debian/pubkey.gpg | gpg --import -

then i could execute the pamac build without problems:

 pamac build spotify

Even if i'm on Manjaro, it worked.
Hope it can help others!

Last edited by Virax (2019-11-12 19:04:18)

2ManyDogs · 2019-11-12 20:03:32

Closing this old solved topic.

Arch Linux

#1 2019-03-16 16:27:55

[SOLVED] One or more PGP signatures could not be verified!

#2 2019-03-16 16:37:09

Re: [SOLVED] One or more PGP signatures could not be verified!

#3 2019-03-16 16:49:48

Re: [SOLVED] One or more PGP signatures could not be verified!

#4 2019-03-16 17:16:05

Re: [SOLVED] One or more PGP signatures could not be verified!

#5 2019-03-16 18:00:09

Re: [SOLVED] One or more PGP signatures could not be verified!

#6 2019-03-16 19:42:15

Re: [SOLVED] One or more PGP signatures could not be verified!

#7 2019-03-16 20:37:18

Re: [SOLVED] One or more PGP signatures could not be verified!

#8 2019-03-16 21:03:15

Re: [SOLVED] One or more PGP signatures could not be verified!

#9 2019-03-16 21:09:16

Re: [SOLVED] One or more PGP signatures could not be verified!

#10 2019-03-16 21:40:08

Re: [SOLVED] One or more PGP signatures could not be verified!

#11 2019-03-16 22:45:31

Re: [SOLVED] One or more PGP signatures could not be verified!

#12 2019-03-16 23:35:25

Re: [SOLVED] One or more PGP signatures could not be verified!

#13 2019-03-16 23:42:51

Re: [SOLVED] One or more PGP signatures could not be verified!

#14 2019-03-17 12:25:18

Re: [SOLVED] One or more PGP signatures could not be verified!

#15 2019-03-17 17:33:17

Re: [SOLVED] One or more PGP signatures could not be verified!

#16 2019-11-12 19:03:01

Re: [SOLVED] One or more PGP signatures could not be verified!

#17 2019-11-12 20:03:32

Re: [SOLVED] One or more PGP signatures could not be verified!

Board footer