You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by LuKreme <kr...@kreme.com> on 2008/12/10 06:54:23 UTC
Re: 1000 times easier to just do sa-update --nogpg
On 5-Sep-2008, at 15:32, mouss wrote:
> curl -o sa.gpg http://spamassassin.apache.org/updates/GPG.KEY
> echo "24F434CE" >> gpg.keys
> sa-update --import sa.gpg
> echo "updates.spamassassin.org" >> channel.list
>
> curl -o jm.gpg http://yerp.org/rules/GPG.KEY
> echo "6C6191E3" >> gpg.keys
> sa-update --import jm.gpg
> echo "sought.rules.yerp.org" >> channel.list
>
> curl -o sare.gpg http://daryl.dostech.ca/sa-update/sare/GPG.KEY
> echo "856AA88A" >> gpg.keys
> sa-update --import sare.gpg
> #echo "...." >> channel.list
The three lines that are echo "HEXCODE" >> gpg.keys are the issue for
me, I guess. Where do those numbers come from?
--
'How do you know I'm mad?' said Alice 'You must be' said the Cat
'or you wouldn't have come here.'
Re: 1000 times easier to just do sa-update --nogpg
Posted by Kai Schaetzl <ma...@conactive.com>.
LuKreme wrote on Tue, 9 Dec 2008 23:23:19 -0700:
> Ok, where in those directions are you supposed to find the keyid?
where the channel maintainer announces the channel and tells you how to
use it.
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
Re: 1000 times easier to just do sa-update --nogpg
Posted by LuKreme <kr...@kreme.com>.
On 9-Dec-2008, at 23:11, Theo Van Dinter wrote:
> On Tue, Dec 09, 2008 at 10:54:23PM -0700, LuKreme wrote:
>>
>>> curl -o sa.gpg http://spamassassin.apache.org/updates/GPG.KEY
>>> echo "24F434CE" >> gpg.keys
>>> sa-update --import sa.gpg
>>> echo "updates.spamassassin.org" >> channel.list
>>
>> The three lines that are echo "HEXCODE" >> gpg.keys are the issue for
>> me, I guess. Where do those numbers come from?
>
> They're the keyids for the given channels you're using. The channel
> publishers should state the keyid in use for the channel. You need
> to specify them so that when sa-update checks the signature on the
> update file, it will know what keyid to consider valid, which
> protects you from someone else creating a channel update file and
> signing it with another random key.
Ok, where in those directions are you supposed to find the keyid?
--
Growing up leads to growing old, and then to dying/And dying to me
don't sound like all that much fun.
Re: 1000 times easier to just do sa-update --nogpg
Posted by Theo Van Dinter <fe...@apache.org>.
On Tue, Dec 09, 2008 at 10:54:23PM -0700, LuKreme wrote:
> >echo "24F434CE" >> gpg.keys
> >echo "6C6191E3" >> gpg.keys
> >echo "856AA88A" >> gpg.keys
>
> The three lines that are echo "HEXCODE" >> gpg.keys are the issue for
> me, I guess. Where do those numbers come from?
They're the keyids for the given channels you're using. The channel
publishers should state the keyid in use for the channel. You need to specify
them so that when sa-update checks the signature on the update file, it will
know what keyid to consider valid, which protects you from someone else
creating a channel update file and signing it with another random key.
--
Randomly Selected Tagline:
"I've always tried to teach you two things. Never let them see you bleed,
always have an escape plan." - Q in "The World is Not Enough"