When using the public Nginx repository for Ubuntu, I keep getting these
errors since a week or two back:
W: GPG error: http://nginx.org lucid Release: The following signatures
couldn’t be verified because the public key is not available: NO_PUBKEY
ABF5BD827BD9BF62
This used to work perfectly for me, so I guess some file went missing
when version 1.0.11 was published? Anyone here who can fix this?
When using the public Nginx repository for Ubuntu, I keep getting these
errors since a week or two back:
W: GPG error: http://nginx.org lucid Release: The following signatures
couldn’t be verified because the public key is not available: NO_PUBKEY
ABF5BD827BD9BF62
This used to work perfectly for me, so I guess some file went missing
when version 1.0.11 was published? Anyone here who can fix this?
‘Release’ file from repository was not signed, so apt-get warn about
unsigned
repo during installation. Now it warn too, but about absent key, so key
import
solve all these problems.
Even I was getting this error “W: GPG error: http://nginx.org lucid
Release:
The following signatures couldn’t be verified because the public key is
not
available: NO_PUBKEY ABF5BD827BD9BF62”, so I started searching and
landed
here.
And Yes, that mail thread reply really worked for me.
(And if you import a file retrieved over plain http straight into your
trust anchors with no further verification, you have other problems).
You are right, that what people shall do (and they also shall not
pass).
However, I was merely summing up the steps provided before which were
not
mentioning that either. But you’re right: there is one step missing.
We’ve added short explanation with links to gpg docs about how
and why pgp signatures should be checked:
VirtualBox website’s
instructionshttps://www.virtualbox.org/wiki/Linux_Downloadson how to
install their Linux packages provides a great 1-line key adding
command (key not stored in a file, simply piped to the standard input of
apt-key):