Bug 5322 - define a new config boolean for items that are unsafe in sa-update channels
Summary: define a new config boolean for items that are unsafe in sa-update channels
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 trivial
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-06 02:27 UTC by Justin Mason
Modified: 2010-01-27 03:16 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Mason 2007-02-06 02:27:43 UTC
From bug 5240: there are a number of settings that can be used to
run perl code, e.g. "loadplugin", "tryplugin", "auto_whitelist_factory".
Currently these are matched in sa-update's --allowplugins code
using a regexp.  Instead, we should define a new config flag that
indicates that the current setting should be filtered out by sa-update
unless --allowplugins is set:

  push (@cmds, {
                setting => 'auto_whitelist_factory',
                is_admin => 1,
                is_update_unsafe => 1,
                default => 'Mail::SpamAssassin::DBBasedAddrList',
                type => $Mail::SpamAssassin::Conf::CONF_TYPE_STRING
               });

'is_update_unsafe' might not be the best name ;)

opened as a separate issue since I don't think it needs to be fixed for 3.2.x or
3.1.x, and I didn't want to muddy discussion of bug 5240.
Comment 1 Justin Mason 2010-01-27 03:16:40 UTC
reassigning, too