On Thu, Jan 10, 2008 at 12:24:00PM +0000, Justin Mason wrote: > > >> # /usr/bin/sa-update --allowplugins --gpgkey > > >> D1C035168C1EBC08464946DA258CDB3ABDE9DC10 --channel > > >> saupdates.openprotect.com error: GPG validation failed! > > >> The update downloaded successfully, but it was not signed with a trusted > > >> GPG key. Instead, it was signed with the following keys: > > >> > > >> BDE9DC10 > > >> > > >> Perhaps you need to import the channel's GPG key? For example: > > >> > > >> wget http://spamassassin.apache.org/updates/GPG.KEY > > >> sa-update --import GPG.KEY > > >> > > >> channel: GPG validation failed, channel failed > > ok, that's not it. sounds like the newly cross-signed key isn't > valid for some versions of GPG?
This has nothing to do with our new cross-signed key, the commandline is
downloading updates from saupdates.openprotect.com. I'd want to see the debug
output from the sa-update run though. It could be the cross-certify thing for
the BDE9DC10 key, or it could be something else, hard to say with the given
info..
--
Randomly Selected Tagline:
"That thing [the space shuttle] has the glide slope of a brick."
- Joe Ruga at LISA '99
pgpdXUorvrp8p.pgp
Description: PGP signature
