On Fri, Jan 11, 2008 at 02:34:29PM -0500, Gene Heskett wrote: > Is there a fix in the works for those who use sa-update other than disabling > it in our crontabs?
You'd want to be more specific about what your problem is. If the issue is the cross-certify problem for the updates.spamassassin.org channel, there are at least two possibilities: a) import the new cross-certified key. The Bugzilla ticket https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5775 covers the problems. You can either grab the new pubkey file (http://svn.apache.org/repos/asf/spamassassin/trunk/rules/sa-update-pubkey.txt) and update it via: gpg --homedir /etc/mail/spamassassin/sa-update-keys --import sa-update-pubkey.txt or use a keyserver and download the update: gpg --homedir /etc/mail/spamassassin/sa-update-keys --keyserver pgp.mit.edu \ --recv-key 5244EC45 b) configure gpg to not look for the cross certification. it used to be an error, but newer gpg versions made it an error. I believe this is simply putting "no-require-cross-certification" in ~/.gnupg/gpg.conf. I'd do this if you can't do (a) for some reason. There hasn't been any talk yet of how to import the new key via the next release. I'm guessing it'll be a manual fix mentioned in the release notes through 3.3.0. If your problem is with other update channels, you'd need to either post more information or (if it's the same cross certify issue) talk to the channel publisher. Hope this helps. -- Randomly Selected Tagline: "I hate going to the dentist. Everytime I go my tongue gets depressed." - Home Movies, "Therapy"
pgpsizGZooCpR.pgp
Description: PGP signature
