#
1 год, 7 месяцев назад
(отредактировано
1 год, 7 месяцев назад)
Сообщения:
80
Участник с: 02 апреля 2021
➜ spotify git:(master) ✗ makepkg -si
==> Сборка пакета spotify 1:1.1.56.595-1 (Пн 21 июн 2021 22:34:40)
==> Проверка зависимостей для запуска...
==> Проверка зависимостей для сборки...
==> Получение исходных файлов...
-> Найден spotify.protocol
-> Найден LICENSE
-> Найден spotify-1.1.56.595-x86_64.deb
-> Найден spotify-1.1.56.595-Release
-> Найден spotify-1.1.56.595-Release.sig
-> Найден spotify-1.1.56.595-x86_64-Packages
==> Проверка файлов source с использованием sha512sums...
spotify.protocol ... Готово
LICENSE ... Готово
spotify-1.1.56.595-x86_64.deb ... Готово
spotify-1.1.56.595-Release ... Пропущено
spotify-1.1.56.595-Release.sig ... Пропущено
spotify-1.1.56.595-x86_64-Packages ... Пропущено
==> Проверка подписей исходных файлов с помощью 'gpg'...
spotify-1.1.56.595-Release ... СБОЙ (неизвестный открытый ключ D1742AD60D811D58)
==> ОШИБКА: Одна или больше PGP-подписей не могут быть проверены!
Пытался установить Spotify. И он не установился. Проблема в том что pgp подписи не могут проверится. И как решить эту проблему
PS: Я гуглил, но ничего не нашёл. Все команды вводил из сайтов, но ни как
gpg --recv-keys D1742AD60D811D58
gpg: сбой при получении с сервера ключей: Нет имени
vall
#
1 год, 7 месяцев назад
(отредактировано
1 год, 7 месяцев назад)
Участник с: 28 марта 2017
Читайте
https://aur.archlinux.org/packages/spotify/#pinned-747857
150_Kirill_150
#
1 год, 7 месяцев назад
Сообщения:
80
Участник с: 02 апреля 2021
- Index
- » AUR Issues, Discussion & PKGBUILD Requests
- » [SOLVED] One or more PGP signatures could not be verified!
#1 2019-03-16 16:27:55
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
[SOLVED] One or more PGP signatures could not be verified!
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 A87FF9DF48BF1C90gpg: key A87FF9DF48BF1C90: public key «Spotify Public Repository Signing Key <tux@spotify.com>» imported
gpg: Total number processed: 1
gpg: imported: 1
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)
#2 2019-03-16 16:37:09
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,023
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
You used sudo, so you added the key to root’s keychain. Makepkg doesn’t run as root. Run gpg without sudo.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#3 2019-03-16 16:49:48
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
gpg: keyserver receive failed: Permission denied
#4 2019-03-16 17:16:05
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,648
Re: [SOLVED] One or more PGP signatures could not be verified!
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 A87FF9DF48BF1C90Last edited by loqs (2019-03-16 18:01:36)
#5 2019-03-16 18:00:09
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,023
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
If that doesn’t work either then post the output of
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#6 2019-03-16 19:42:15
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
Still the same:
gpg: keyserver receive failed: Permission denied
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)
#7 2019-03-16 20:37:18
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,648
Re: [SOLVED] One or more PGP signatures could not be verified!
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?
#8 2019-03-16 21:03:15
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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)
#9 2019-03-16 21:09:16
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,648
Re: [SOLVED] One or more PGP signatures could not be verified!
Did root have a different keyserver configured in its ~/.gnupg/dirmngr.conf?
#10 2019-03-16 21:40:08
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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
#11 2019-03-16 22:45:31
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,023
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
Please use code tags, not quote tags, for terminal output.
Post the output of
gpg --debug-level guru --recv-key A87FF9DF48BF1C90Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#12 2019-03-16 23:35:25
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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#13 2019-03-16 23:42:51
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,648
Re: [SOLVED] One or more PGP signatures could not be verified!
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.netThis 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)
#14 2019-03-17 12:25:18
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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?
#15 2019-03-17 17:33:17
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,023
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
Apparently. 
Please remember to mark your thread as solved by editing the first post and amending the topic title.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#16 2019-11-12 19:03:01
- Virax
- Member
- Registered: 2019-11-12
- Posts: 1
Re: [SOLVED] One or more PGP signatures could not be verified!
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:
Even if i’m on Manjaro, it worked.
Hope it can help others!
Last edited by Virax (2019-11-12 19:04:18)
#17 2019-11-12 20:03:32
- 2ManyDogs
- Forum Moderator
- Registered: 2012-01-15
- Posts: 4,259
Re: [SOLVED] One or more PGP signatures could not be verified!
Closing this old solved topic.
How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.
Здравствуйте помогите разобраться с установкой.
Версия системы:
Linux version 5.7.19-2-MANJARO (builduser@LEGION) (gcc version 10.2.0 (GCC), GNU ld (GNU Binutils) 2.35)
Окружение: Xfce
Поставил с флешки систему на ноутбук HP процессор AMD A6
Вот что выдает:
Сборка dropbox…
==> Сборка пакета dropbox 104.4.175-1 (Пт 11 сен 2020 15:29:47)
==> Проверка зависимостей для запуска…
==> Проверка зависимостей для сборки…
==> Получение исходных файлов…
-> Найден DropboxGlyph_Blue.svg
-> Найден terms.txt
-> Найден dropbox.service
-> Найден dropbox@.service
-> Найден dropbox-lnx.x86_64-104.4.175.tar.gz
-> Найден dropbox-lnx.x86_64-104.4.175.tar.gz.asc
==> Проверка файлов source с использованием sha256sums…
DropboxGlyph_Blue.svg… Готово
terms.txt… Готово
dropbox.service… Готово
dropbox@.service… Готово
==> Проверка файлов source_x86_64 с использованием sha256sums…
dropbox-lnx.x86_64-104.4.175.tar.gz… Готово
dropbox-lnx.x86_64-104.4.175.tar.gz.asc… Пропущено
==> Проверка подписей исходных файлов с помощью ‘gpg’…
dropbox-lnx.x86_64-104.4.175.tar.gz… СБОЙ (неизвестный открытый ключ FC918B335044912E)
==> ОШИБКА: Одна или больше PGP-подписей не могут быть проверены!
Не удалось собрать dropbox
Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.
#
1 год, 7 месяцев назад
(отредактировано
1 год, 7 месяцев назад)
Сообщения:
80
Участник с: 02 апреля 2021
➜ spotify git:(master) ✗ makepkg -si
==> Сборка пакета spotify 1:1.1.56.595-1 (Пн 21 июн 2021 22:34:40)
==> Проверка зависимостей для запуска...
==> Проверка зависимостей для сборки...
==> Получение исходных файлов...
-> Найден spotify.protocol
-> Найден LICENSE
-> Найден spotify-1.1.56.595-x86_64.deb
-> Найден spotify-1.1.56.595-Release
-> Найден spotify-1.1.56.595-Release.sig
-> Найден spotify-1.1.56.595-x86_64-Packages
==> Проверка файлов source с использованием sha512sums...
spotify.protocol ... Готово
LICENSE ... Готово
spotify-1.1.56.595-x86_64.deb ... Готово
spotify-1.1.56.595-Release ... Пропущено
spotify-1.1.56.595-Release.sig ... Пропущено
spotify-1.1.56.595-x86_64-Packages ... Пропущено
==> Проверка подписей исходных файлов с помощью 'gpg'...
spotify-1.1.56.595-Release ... СБОЙ (неизвестный открытый ключ D1742AD60D811D58)
==> ОШИБКА: Одна или больше PGP-подписей не могут быть проверены!
Пытался установить Spotify. И он не установился. Проблема в том что pgp подписи не могут проверится. И как решить эту проблему
PS: Я гуглил, но ничего не нашёл. Все команды вводил из сайтов, но ни как
gpg --recv-keys D1742AD60D811D58
gpg: сбой при получении с сервера ключей: Нет имени
vall
#
1 год, 7 месяцев назад
(отредактировано
1 год, 7 месяцев назад)
Участник с: 28 марта 2017
Уже было персонально для Вас, 150_Kirill_150.
Читайте
https://aur.archlinux.org/packages/spotify/#pinned-747857
150_Kirill_150
#
1 год, 7 месяцев назад
Сообщения:
80
Участник с: 02 апреля 2021
Спасибо!
- Index
- » AUR Issues, Discussion & PKGBUILD Requests
- » [SOLVED] One or more PGP signatures could not be verified!
#1 2019-03-16 16:27:55
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
[SOLVED] One or more PGP signatures could not be verified!
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 A87FF9DF48BF1C90gpg: key A87FF9DF48BF1C90: public key «Spotify Public Repository Signing Key <tux@spotify.com>» imported
gpg: Total number processed: 1
gpg: imported: 1
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)
#2 2019-03-16 16:37:09
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,012
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
You used sudo, so you added the key to root’s keychain. Makepkg doesn’t run as root. Run gpg without sudo.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#3 2019-03-16 16:49:48
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
gpg: keyserver receive failed: Permission denied
#4 2019-03-16 17:16:05
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,625
Re: [SOLVED] One or more PGP signatures could not be verified!
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 A87FF9DF48BF1C90Last edited by loqs (2019-03-16 18:01:36)
#5 2019-03-16 18:00:09
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,012
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
If that doesn’t work either then post the output of
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#6 2019-03-16 19:42:15
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
Still the same:
gpg: keyserver receive failed: Permission denied
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)
#7 2019-03-16 20:37:18
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,625
Re: [SOLVED] One or more PGP signatures could not be verified!
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?
#8 2019-03-16 21:03:15
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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)
#9 2019-03-16 21:09:16
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,625
Re: [SOLVED] One or more PGP signatures could not be verified!
Did root have a different keyserver configured in its ~/.gnupg/dirmngr.conf?
#10 2019-03-16 21:40:08
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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
#11 2019-03-16 22:45:31
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,012
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
Please use code tags, not quote tags, for terminal output.
Post the output of
gpg --debug-level guru --recv-key A87FF9DF48BF1C90Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#12 2019-03-16 23:35:25
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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#13 2019-03-16 23:42:51
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,625
Re: [SOLVED] One or more PGP signatures could not be verified!
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.netThis 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)
#14 2019-03-17 12:25:18
- TheChosenOne
- Member
- Registered: 2012-09-27
- Posts: 130
Re: [SOLVED] One or more PGP signatures could not be verified!
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?
#15 2019-03-17 17:33:17
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,012
- Website
Re: [SOLVED] One or more PGP signatures could not be verified!
Apparently.
Please remember to mark your thread as solved by editing the first post and amending the topic title.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#16 2019-11-12 19:03:01
- Virax
- Member
- Registered: 2019-11-12
- Posts: 1
Re: [SOLVED] One or more PGP signatures could not be verified!
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:
Even if i’m on Manjaro, it worked.
Hope it can help others!
Last edited by Virax (2019-11-12 19:04:18)
#17 2019-11-12 20:03:32
- 2ManyDogs
- Forum Moderator
- Registered: 2012-01-15
- Posts: 4,251
Re: [SOLVED] One or more PGP signatures could not be verified!
Closing this old solved topic.
How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.
Если у вас есть пара локальных ключей gpg, вы можете импортировать неизвестный ключ в набор ключей локальных пользователей.
В моем случае ключ 5CC908FDB71E12C2 необходимо импортировать следующим образом.
$ gpg --recv-keys 5CC908FDB71E12C2
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: key 5CC908FDB71E12C2: 8 signatures not checked due to missing keys
gpg: /home/aaron/.gnupg/trustdb.gpg: trustdb created
gpg: key 5CC908FDB71E12C2: public key "Daniel Stenberg <daniel@haxx.se>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1
—recv-keys keys: импортировать ключи с заданными идентификаторами ключей с сервера ключей.
Если вышеперечисленное не поможет, вам может потребоваться создать локальное хранилище ключей gpg / базу данных.
Приведенные ниже шаги могут больше не понадобиться, так как вышеприведенный шаг теперь создает для вас базу данных локальных ключей. Это зависит от вашего дистрибутива, версии и конфигурации
gpg.
Если у вас еще нет базы данных ключей gpg для вашего локального пользователя.
gpg --generate-key
или же
gpg --full-gen-key
Что говорят документы
--generate-key
--gen-key
Generate a new key pair using the current default parameters. This is the standard command to create a new key. In addition to the key a revocation certificate is created and stored in the
‘openpgp-revocs.d’ directory below the GnuPG home directory.
--full-generate-key
--full-gen-key
Generate a new key pair with dialogs for all options. This is an extended version of --generate-key.
There is also a feature which allows you to create keys in batch mode. See the manual section ``Unattended key generation'' on how to use this.
I’m trying to install ncurses5-compat-libs on Arch Linux with packer.
But I get this error:
==> ERROR: One or more PGP signatures could not be verified!
How can I fix it?
asked Jun 9, 2016 at 20:03
You should stick to a manual installation using makepkg and understand how the compilation and installation process from the AUR works before using an AUR helper.
Anyway, you have to import the PGP signature of the package before you install it. You can install the package without verifying its PGP signature but you shouldn’t do it. You can import the PGP signature of ncurses5-compat-libs by using this command:
gpg --keyserver pgp.mit.edu --recv-keys F7E48EDB
Read the makepkg man page and this article before installing another package from the AUR.
answered Jun 13, 2016 at 4:01
Option 1 (recommended)
It is also important to keep the archlinux-keyring-package and the system up-to-date — especially
the archlinux-keyring-package.
A not up-to-date archlinux-keyring-package can cause PGP signatures to be missing and thus problems with the PGP signatures.
—
Option 2 (not recommended)
As a quick and dirty fix this was proposed on the archbang forum:
Warning: Following these instructions chould damage yours and others system with dangerous malware!
Installation without (!) integrity check:
packer -S --skipinteg <package>
answered Aug 28, 2018 at 0:09
ArchLinuxTuxArchLinuxTux
5933 gold badges7 silver badges22 bronze badges
I’m trying to install ncurses5-compat-libs on Arch Linux with packer.
But I get this error:
==> ERROR: One or more PGP signatures could not be verified!
How can I fix it?
asked Jun 9, 2016 at 20:03
You should stick to a manual installation using makepkg and understand how the compilation and installation process from the AUR works before using an AUR helper.
Anyway, you have to import the PGP signature of the package before you install it. You can install the package without verifying its PGP signature but you shouldn’t do it. You can import the PGP signature of ncurses5-compat-libs by using this command:
gpg --keyserver pgp.mit.edu --recv-keys F7E48EDB
Read the makepkg man page and this article before installing another package from the AUR.
answered Jun 13, 2016 at 4:01
Option 1 (recommended)
It is also important to keep the archlinux-keyring-package and the system up-to-date — especially
the archlinux-keyring-package.
A not up-to-date archlinux-keyring-package can cause PGP signatures to be missing and thus problems with the PGP signatures.
—
Option 2 (not recommended)
As a quick and dirty fix this was proposed on the archbang forum:
Warning: Following these instructions chould damage yours and others system with dangerous malware!
Installation without (!) integrity check:
packer -S --skipinteg <package>
answered Aug 28, 2018 at 0:09
ArchLinuxTuxArchLinuxTux
5933 gold badges7 silver badges22 bronze badges
Когда вы пытаетесь установить программу из сторонних репозиториев разработчика программы или из PPA вы можете столкнуться с ошибкой gpg недоступен открытый ключ. Это не значит, что программа платная и вам надо приобрести к ней ключ. Дело в том, что для защиты репозиториев от подмены используется подписывание пакетов с помощью GPG ключей.
Для того чтобы пакетный менеджер мог проверить подпись пакета, который вы пытаетесь установить необходимо чтобы у вас в системе был GPG ключ этого репозитория. Для официальных репозиториев ключи поставляются автоматически, а вот для сторонних надо их вручную добавить. Давайте рассмотрим пути решения этой проблемы.
Как вы можете видеть на снимке, программа сообщает какой именно репозиторий вызвал проблему и какого ключа не хватает:
Самый простой и правильный способ решить эту проблему — добавить ключ в систему. Обычно, там где вы нашли информацию о том как добавить репозиторий есть и информация как добавить его ключ. К тому же в выводе информации об ошибке пакетный менеджер сообщает какой ключ он ожидает увидеть. Вы можете попытаться искать такой ключ в Google или на серверах ключей Ubuntu.
В данном случае не хватает ключа от репозитория Google — 78BD65473CB3BD13. Можно попытаться получить его с серверов Ubuntu:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 78BD65473CB3BD13
Или с другого сервера:
sudo apt-key adv --keyserver ha.pool.sks-keyservers.net --recv-keys 78BD65473CB3BD13
Если у вас нет ключа от PPA или любого другого репозитория, связанного с разработчиками Ubuntu это должно помочь. Ну и ключ от репозитория Google там есть:
Если же вы получаете ошибку. Ищите данный ключ в интернете, если ключа нет на сайте разработчика, то его можно найти на различных форумах. Скачайте его и добавьте в систему такой командой:
sudo apt-key add /путь/к/файлу.gpg
Ещё одна альтернатива первому способу — попытаться использовать графическую утилиту Y-PPA-Manager от webupd8. Для её установки выполните такие команды:
sudo add-apt-repository ppa:webupd8team/y-ppa-manager
sudo apt install y-ppa-manager
Затем запустите программу из главного меню или терминала. В главном окне программы выберите Advanced:
В открывшемся окне выберите Try to import all missing GPG keys, а потом дождитесь завершения работы утилиты:
После того как ключ добавлен вы можете снова попытаться импортировать репозитории и на этот раз у вас должно всё получится.
Выводы
В этой небольшой статье мы рассмотрели что делать когда возникает ошибка gpg недоступен открытый ключ и как исправить эту ошибку. Даже не думайте, что что можно обойтись без ключа. Все методы, которые позволяли просить APT игнорировать проверку ключей в современных версиях дистрибутива уже не работают. Если у вас остались вопросы, спрашивайте в комментариях!
I’m trying to install ncurses5-compat-libs on Arch Linux with packer.
But I get this error:
==> ERROR: One or more PGP signatures could not be verified!
How can I fix it?
asked Jun 9, 2016 at 20:03
You should stick to a manual installation using makepkg and understand how the compilation and installation process from the AUR works before using an AUR helper.
Anyway, you have to import the PGP signature of the package before you install it. You can install the package without verifying its PGP signature but you shouldn’t do it. You can import the PGP signature of ncurses5-compat-libs by using this command:
gpg --keyserver pgp.mit.edu --recv-keys F7E48EDB
Read the makepkg man page and this article before installing another package from the AUR.
answered Jun 13, 2016 at 4:01
Option 1 (recommended)
It is also important to keep the archlinux-keyring-package and the system up-to-date — especially
the archlinux-keyring-package.
A not up-to-date archlinux-keyring-package can cause PGP signatures to be missing and thus problems with the PGP signatures.
—
Option 2 (not recommended)
As a quick and dirty fix this was proposed on the archbang forum:
Warning: Following these instructions chould damage yours and others system with dangerous malware!
Installation without (!) integrity check:
packer -S --skipinteg <package>
answered Aug 28, 2018 at 0:09
ArchLinuxTuxArchLinuxTux
5933 gold badges7 silver badges23 bronze badges