W: GPG error: http://ftp.us.debian.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY NNNNNNNNNNNNNNNN
How to find and add a key
The debian-archive-keyring package is used to distribute keys to apt. Upgrades to this package can add (or remove) gpg keys for the main Debian archive.
For other archives, there is not yet a standard location where you can find the key for a given apt repository. There's a rough standard of putting the key up on the web page for the repository or as a file in the repository itself, but no real standard, so you might have to hunt for it.
The current and the retired Debian archive "signing" keys are available from https://ftp-master.debian.org/keys.html.
gpg itself has a standard way to distribute keys, using a keyserver that gpg can download a key from and add it to its keyring. For example:
### gpg --keyserver subkeys.pgp.net --recv-keys NNNNNNNN ### gpg -a --export NNNNNNNN | sudo apt-key add - http://wiki.debian.org/SecureApt#How_apt_uses_Release.gpg http://wiki.debian.org/SecureApt#How_to_find_and_add_a_key
no subject
Date: 2015-02-06 03:06 am (UTC)Posted by admin
Бывают случаи, когда при выполнении команды apt-get update, выводится ошибка, где упоминается GPG:
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://www.deb-multimedia.org stable Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
Номер публичного ключа при этом может быть иным.
Решением проблемы является добавление в систему публичного GnuPG-ключа репозитория, из которого осуществляется попытка установить пакет (который, в свою очередь, подписан данным ключом):
#gpg --keyserver pgpkeys.mit.edu --recv-key 5C808C2B65558117
#gpg -a --export 5C808C2B65558117 | apt-key add -
Posted in Debain
http://superuserdo.info/?p=168