You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2007/05/25 16:26:22 UTC
Re: sa-update-keys
Duncan Findlay writes:
> On Thu, May 24, 2007 at 02:44:58PM -0400, Daryl C. W. O'Shea wrote:
> > Duncan Findlay wrote:
> > >I'm working on the 3.2.0 Debian package and I'm running into some
> > >problems with the way I handle the sa-update-keys directory.
> > >It's in /etc/spamassassin/sa-update-keys, which implies it contains
> > >configurations file. As far as I can tell, it's not something that we
> > >expect anyone to touch manually (we specifically provide sa-update
> > >--import to import keys instead of having them use gpg directly on
> > >these files), so it would seem to me that it should be in
> > >/var/lib/spamassassin/sa-update-keys or something instead.
>
> > I wouldn't put it there... you should be able to rm /var/lib/spamassassin and have everything continue to work fine.
>
> Well... It would assuming you have no non-standard channels.
>
> > >Is there a reason I'm missing for putting it in /etc?
>
> > The keys aren't really variable (we're not going to release new ones in a rule update), they are a part of the software
> > configuration and configurable (manually or with sa-update) though.
>
> I'm not sure I buy that -- they really aren't configuration. I mean
> you might configure which keys to allow, but the actual contents of
> the public keys aren't really configuration information.
The fact that the admin has imported key K for host H, however, is
important config info. I agree with Daryl -- /etc makes the most
sense for these in my opinion...
--j.