http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5775
------- Additional Comments From [EMAIL PROTECTED] 2008-01-10 02:23 ------- (In reply to comment #11) > Ok, I think I figured it out. It appears the key files that we're actively using doesn't have the full set of > secret keys associated with it. Specifically, it appears that it's a stub secret key. I found a backup copy > of the key files w/ the full set of secret keys under the BACKUP dir and was able to cross-certify. :) too much paranoia! I shouldn't have done that. can you put the full set of secret keys into the "key" directory in case we need to do something similar again? > The new public key was imported into the normal key directory, and I uploaded the key to pgp.mit.edu. > I'll update the included pubkey in 3.1, 3.2, and trunk in a minute. > > However ... We need to document somewhere that if people can't do an update, and they see the error > in the debug output, they'll need to get the new pubkey imported. Ala: > > sudo gpg --homedir /etc/mail/spamassassin/sa-update-keys --import /usr/share/spamassassin/sa- > update-pubkey.txt > > or > > sudo gpg --homedir /etc/mail/spamassassin/sa-update-keys --keyserver pgp.mit.edu --recv-key 5244EC45 damn, that's annoying. stupid gpg! still, we probably have a while before the distros start packaging 1.4.8. it's lucky I spotted the message; I wouldn't have seen it otherwise, since it only appears with sa-update --debug in gpg 1.4.7. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
