Uzantı:AbuseFilter

From MediaWiki.org
Jump to navigation Jump to search
This page is a translated version of the page Extension:AbuseFilter and the translation is 24% complete.
Other languages:
Deutsch • ‎English • ‎Türkçe • ‎català • ‎dansk • ‎español • ‎français • ‎galego • ‎magyar • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎sicilianu • ‎čeština • ‎български • ‎русский • ‎עברית • ‎سنڌي • ‎فارسی • ‎हिन्दी • ‎中文 • ‎日本語 • ‎粵語 • ‎한국어
MediaWiki manüel uzantıları
OOjs UI icon advanced.svg
AbuseFilter
Yayın durumu: sabit
AbuseFilter-Management.png
Uygulama Kullanıcı etkinliği , Özel sayfa , API
Açıklama Wiki aktivitesine belirli davranışa dayalı kısıtlamalar getirilmesine izin verir
Yazar(lar)
Uyumluluk politikası dal yayını
MediaWiki 1.33+
PHP 5.4+ önerilir
Veritabanı değişiklikleri Evet
Tablolar abuse_filter
abuse_filter_action
abuse_filter_history
abuse_filter_log
Lisans GNU Genel Kamu Lisansı 2.0 veya üstü
İndir
  • $wgAbuseFilterActions
  • $wgAbuseFilterConditionLimit
  • $wgAbuseFilterEmergencyDisableThreshold
  • $wgAbuseFilterEmergencyDisableCount
  • $wgAbuseFilterEmergencyDisableAge
  • $wgAbuseFilterParserClass
  • $wgAbuseFilterRestrictions
  • $wgAbuseFilterNotifications
  • $wgAbuseFilterNotificationsPrivate
  • $wgAbuseFilterCentralDB
  • $wgAbuseFilterIsCentral
  • $wgAbuseFilterDisallowGlobalLocalBlocks
  • $wgAbuseFilterBlockDuration
  • $wgAbuseFilterAnonBlockDuration
  • $wgAbuseFilterCustomActionsHandler
  • $wgAbuseFilterValidGroups
  • $wgAbuseFilterDefaultWarningMessage
  • $wgAbuseFilterIPMaxAge
  • $wgAbuseFilterProfileActionsCap
  • $wgAbuseFilterLogPrivateDetailsAccess
  • $wgAbuseFilterPrivateDetailsForceReason
  • abusefilter-view
  • abusefilter-log
  • abusefilter-log-detail
  • abusefilter-revert
  • abusefilter-privatedetails
  • abusefilter-privatedetails-log
  • abusefilter-view-private
  • abusefilter-log-private
  • abusefilter-hidden-log
  • abusefilter-hide-log
  • abusefilter-modify
  • abusefilter-modify-restricted
  • abusefilter-modify-global
AbuseFilter uzantısını çevirin translatewiki.net adresinde mevcutsa
Kullanım ve sürüm matrisini kontrol edin.
Sorunlar Görevleri aç · Bir hatayı bildir

AbuseFilter uzantısı, ayrıcalıklı kullanıcıların, düzenlemeler gibi kullanıcılar tarafından yapılan işlemler belirli ölçütlerle eşleştiğinde gerçekleştirilecek belirli eylemleri ayarlamasına olanak tanır.

Örneğin, isimsiz kullanıcıların harici bağlantılar eklemesini engellemek veya 2000'den fazla karakteri kaldıran bir kullanıcıyı engellemek için bir filtre oluşturulabilir.

Kurulum

  • İndir ve dosyaları extensions/ klasörünüzdeki AbuseFilter adlı bir dizine yerleştirin.
  • Sadece git'ten kurarken PHP bağımlılıklarını kurmak için Composer komutunu çalıştırın, eklenti dizinine composer install --no-dev vererek. (Potansiyel komplikasyonlar için T173141 bakınız.)
  • LocalSettings.php'inizin altına aşağıdaki kodu ekleyin:
    wfLoadExtension( 'AbuseFilter' );
    
  • Bu uzantının ihtiyaç duyduğu gerekli veritabanı tablolarını otomatik olarak oluşturacak bitik güncelleme komutunu çalıştırın.
  • Configure as required.
  • Yes Yapıldı – Uzantının başarıyla yüklendiğini doğrulamak için wikinizde Special:Version seçeneğine gidin.

MediaWiki 1.26 veya önceki bir sürümü çalıştıran kullanıcılara:

Yukarıdaki talimatlar, bu eklentiyi wfLoadExtension() kullanarak kurmanın yeni yolunu açıklar. Bu uzantıyı önceki sürümlerine (MediaWiki 1.26 ve önceki sürümler) yüklemeniz gerekirse, wfLoadExtension( 'AbuseFilter' ); yerine kullanmanız gerekir:

require_once "$IP/extensions/AbuseFilter/AbuseFilter.php";

Yapılandırma

Kullanıcı hakları

Uzantıyı yükledikten sonra, kullanıcı haklarını "LocalSettings.php" içinde ayarlamanız gerekir.

Yetki Açıklama
abusefilter-modify Kötüye kullanım süzgeçlerini değiştir
abusefilter-view Kötüye kullanım süzgeçlerini gör
abusefilter-log Kötüye kullanım günlüğünü gör
abusefilter-log-detail Ayrıntılı suistimal girdilerini gör
abusefilter-privatedetails Kötüye kullanım günlüğündeki özel verileri gör
abusefilter-modify-restricted Kısıtlı eylemler içeren suistimal filtrelerini değiştir
abusefilter-modify-global Küresel suistimal süzgeçleri oluştur ya da değiştir
abusefilter-revert Verilen bir suistimal filtresi tarafından yapılan tüm değişiklikleri geri al
abusefilter-view-private Özel olarak işaretlenmiş suistimal filtrelerini gör
abusefilter-log-private Özel olarak işaretlenmiş suistimal süzgeci günlük girdilerini gör
abusefilter-hide-log Girdileri kötüye kullanım günlüğünde gizle
abusefilter-hidden-log Gizli suistimal günlüğü girdilerine bak
abusefilter-privatedetails-log AbuseFilter özel ayrıntıları erişim günlüğünü görüntüle

Örneğin, aşağıdaki örnek yapılandırma hizmetlilerin AbuseFilter ile istedikleri her şeyi yapmalarını ve herkesin günlüğü görüntülemesini ve genel filtre ayarlarını görmelerini sağlar:

$wgGroupPermissions['sysop']['abusefilter-modify'] = true;
$wgGroupPermissions['*']['abusefilter-log-detail'] = true;
$wgGroupPermissions['*']['abusefilter-view'] = true;
$wgGroupPermissions['*']['abusefilter-log'] = true;
$wgGroupPermissions['sysop']['abusefilter-privatedetails'] = true;
$wgGroupPermissions['sysop']['abusefilter-modify-restricted'] = true;
$wgGroupPermissions['sysop']['abusefilter-revert'] = true;
Özel olarak işaretlenen filtreler, yalnızca kötüye kullanım filtresini değiştir veya kötüye kullanım filtresini görüntüle özel iznine sahip kullanıcılar tarafından görüntülenebilir.

Parametreler

Değişken ismi Varsayılan değer Açıklama
$wgAbuseFilterActions
[
    'throttle' => true,
    'warn' => true,
    'disallow' => true,
    'blockautopromote' => true,
    'block' => true,
    'rangeblock' => false,
    'degroup' => true,
    'tag' => true
]
Kötüye kullanım filtreleriyle gerçekleştirilebilecek olası eylemler. Yeni bir işlem eklerken, $wgAbuseFilterRestrictions bölümünde kısıtlı olup olmadığını kontrol edin ve uygunsa abusefilter-configure-restted'i uygun kullanıcı grupları şekilde eklemeyi unutmayın.
$wgAbuseFilterConditionLimit
1000
Filtrelerin bir değişikliğe karşı çalıştırılmasında kullanılabilecek maksimum 'koşul' sayısı. (Daha karmaşık filtreler daha fazla 'koşul' gerektirir).
$wgAbuseFilterValidGroups
[
    'default'
]
"Gruplar" filtrelerinin listesi ayrılabilir. Varsayılan olarak sadece bir grup var. Diğer uzantılar başka gruplar ekleyebilir.
$wgAbuseFilterEmergencyDisableThreshold
[
    'default' => 0.05
]
Filtrenin son 86400 saniyede değiştirilmediği sürece, "gözlenen" dönemde (en fazla bir gün) filtre grubuna karşı kontrol edilen eylemlerin% 5'inden fazlasını oluşturan, 2'den fazla düzenlemeyle eşleşmesi durumunda filtreyi devre dışı bırakın (bir gün). Bkz acil durum azaltma.
$wgAbuseFilterEmergencyDisableCount
[
    'default' => 2
]
$wgAbuseFilterEmergencyDisableAge
[
    'default' => 86400
]
$wgAbuseFilterParserClass
'AbuseFilterParser'
AbuseFilter'ın ayrıştırıcı sınıfının adı.
$wgAbuseFilterRestrictions
[
    'block' => true,
    'degroup' => true,
    'blockautopromote' => true,
    'rangeblock' => true
]
Kullanıcılar, bu eylemleri gerçekleştiren filtreler oluşturmak veya değiştirmek için "abusefilter-modify-restricted" kullanıcı hakkına ve "abusefilter-modify"ye sahip olmalıdır.
$wgAbuseFilterNotifications
false
Allows to configure the extension to send hit notifications to Special:RecentChanges or UDP. Available options: rc, udp, rcandudp
$wgAbuseFilterNotificationsPrivate
false
Enable notifications for private filters.
$wgAbuseFilterCentralDB
null
Name of a database where global abuse filters will be stored in (only supported in the latest, development version).
$wgAbuseFilterIsCentral
false
Set this variable to true for the wiki where global AbuseFilters are stored in (only supported in the latest, development version).
$wgAbuseFilterDisallowGlobalLocalBlocks
false
Disallow Centralised filters from taking actions that locally block, remove from groups, or revoke permissions.
$wgAbuseFilterBlockDuration
'indefinite'
Duration of blocks made by AbuseFilter.
as of 1.31.0-wmf.25 block durations may be specified for every single filter and will override this variable. This variable is only used when enabling the block in order to preselect a default duration.
$wgAbuseFilterAnonBlockDuration
null
Duration of blocks made by AbuseFilter on users who are not logged in. The value of $wgAbuseFilterBlockDuration will be used if this is not set.
as of 1.31.0-wmf.25 block durations may be specified for every single filter and will override this variable. This variable is only used when enabling the block in order to preselect a default duration.
$wgAbuseFilterCustomActionsHandlers
[ ]
Callback functions for custom actions.
$wgAbuseFilterDefaultWarningMessage
[
    'default' => 'abusefilter-warning'
]
Default warning messages, per filter group
$wgAbuseFilterLogIPMaxAge
3 * 30 * 24 * 3600
Age used as cutoff when purging old IP log data. Defaults to 3 months. Used by maintenance script purgeOldLogIPData.php.
$wgAbuseFilterProfileActionsCap
10000
Number of action that determines when to reset profiling stats.
$wgAbuseFilterLogPrivateDetailsAccess
false
Whether accessing private information from a filter log entry is logged.
$wgAbuseFilterPrivateDetailsForceReason
false
Whether users are forced to provide a reason for accessing private information from a filter log entry.

Emergency throttling

AbuseFilter comes with a feature that automatically throttles (disable) filters that have been edited recently and match a certain theresold of the latest actions.

This is done to prevent harmful edits on the filters to block every user that performs an action on the wiki or similar.

The condition to disable the filter depend on those variables:

  • $wgAbuseFilterEmergencyDisableThreshold - Percent of matches over the total amount of actions in the observed period.
  • $wgAbuseFilterEmergencyDisableCount - Count of matches of the filter in the observed period.
  • $wgAbuseFilterEmergencyDisableAge - Age of the filter to take it into account. If the last edit of the filter is older than this number of seconds, the filter won't be throttled, unless it's already throttled.
  • $wgAbuseFilterProfileActionsCap - Maximum number of recent actions to count against the threshold. Note that each action increments a counter, and once this counter reaches this configured value, this counter and the number of recent actions that matches all filters are reset to 0.

Throttled filters can be identified in the list of filters (Special:AbuseFilter) with the state Enabled, throttled. Throttling happens silently, and there's no way to see when a filter got throttled.

When a filter gets throttled, it doesn't perform any dangerous action (the ones specified in $wgAbuseFilterRestrictions), and only "safe" actions are allowed. Throttled filters don't get enabled automatically. To disable the throttling, you need to edit the filter. Note that you need to actually change something from the filter: changing somethin from the filter's notes is sufficient.

Note that editing the filter updates its age, and can cause it to be disabled if it reaches again the conditions to be throttled in a short period since the last edit, leading to a unusable filter if your wiki has more abuse edits than legitimate ones. Filters can also get randomly throttled if the action count reaches $wgAbuseFilterProfileActionsCap, causing all filter matches count to reset to 0, and then someone repeatedly makes a filter to hit.

Creating and managing filters

Once the extension has been installed, filters can be created/tested/changed/deleted and the logs can be accessed from the Abuse filter management page Special:AbuseFilter.

API

AbuseFilter adds two API list modules, one for details of abuse filters ("abusefilters") and one for the abuse log, since it is separate from other MediaWiki logs ("abuselog"). It is not possible to create or modify abuse filters using the API.

list = abusefilters

List information about filters

Parameters
  • abfstartid - The filter id to start enumerating from
  • abfendid - The filter id to stop enumerating at
  • abfdir - The direction in which to enumerate (older, newer)
  • abfshow - Show only filters which meet these criteria (enabled|!enabled|deleted|!deleted|private|!private)
  • abflimit - The maximum number of filters to list
  • abfprop - Which properties to get (id|description|pattern|actions|hits|comments|lasteditor|lastedittime|status|private)

When filters are private, some of the properties specified with abfprop will be missing unless you have the appropriate user rights.

Examples

List non-private abuse filters

list = abuselog

List instances where actions triggered an abuse filter.

Parameters
  • aflstart - The timestamp to start enumerating from
  • aflend - The timestamp to stop enumerating at
  • afldir - The direction in which to enumerate (older, newer)
  • afluser - Show only entries where the action was attempted by a given user or IP address.
  • afltitle - Show only entries where the action involved a given page.
  • aflfilter - Show only entries that triggered a given filter ID
  • afllimit - The maximum number of entries to list
  • aflprop - Which properties to get (ids|user|title|action|result|timestamp|details)
Example

List instances where the abuse filter was triggered in response to actions from the user "SineBot"

Possible errors

  • Some users might experience that creating new filters or modifying old filters fail and the user just gets redirected to the original page. If the Wiki is using SSL certificates, this error could possibly be because of the $wgServer value, which might be using "http://" instead of "https://". An indication of this error will be, the browser giving https warning for Special:AbuseFilter pages. (Topic:T23dyyih0ofjada5)

Integration with other extensions

You can integrate AbuseFilter with other extension in various ways.

Adding variables for filtering

It is possible to add new variables, to be used in abuse filters. A list of examples is available . To do that, you should:

  • Add a handler for the AbuseFilter-builder hook. To add a variable, you should use $builder['vars']['variable_name'] = 'i18n-key';, where variable_name is the name of the variable, and i18n-key is the fragment of an i18n key. The full key will be abusefilter-edit-builder-vars-{$your_key}.
  • Add the i18n messages you chose at the previous point.
  • Choose a hook handler where the variable will be computed. Depending on your use case, you could:
    • Implement the AbuseFilter-generateTitleVars hook; this is specifically thought for page-related variables;
    • Implement the AbuseFilter-generateUserVars hook; this is specifically thought for user-related variables;
    • Implement the AbuseFilter-generateStaticVars hook; this is specifically thought for "static" variables, i.e. variables whose value shouldn't depend on the context. This is rarely useful;
    • Implement the AbuseFilterAlterVariables hook; this is a bit more flexible than the other hooks, but it has a downside: your variable will not be available when examining past RecentChanges entries. If you want to implement that feature (and it's recommended to do so), you should use one of the hooks listed above, and use its third parameter ($RCRow).
  • Inside the hook handler, there are two ways to add a variable:
    • The "direct" way is calling $vars->setVar( 'var_name', var_value );. This is ideal only when the value is easy and quick to compute: the value is computed even if no active filter will use it.
    • The "lazy" way is calling $vars->setLazyLoadVar( 'var_name', 'method_name', $params );. Here, 'method_name' is a (unique) identifier that will be used to compute the variable (it's recommended to prefix it with the name of your extension). To register the method, you should add a handler for the AbuseFilter-computeVariable hook; therein, you should check if the $method passed matches your 'method_name', and if so, compute the variable. Lastly, $params is an array of parameters that you'll need to compute the variable; these are passed to the computeVariable hook handler. For an example of this, you can check out CentralAuth's global_user_groups.


Adding rule groups

You can also add extra rule groups, which can be used to group existing abuse filters. Note that, at the moment, each filter can only be in a single group (T116642). Currently, the only known consumer of this feature is Flow. To do that, you should:

  • Append the name of the group to $wgAbuseFilterValidGroups
  • Add some code to run the filters with your group. Note that AbuseFilter won't do that on its own. To do that, you should construct an AbuseFilterRunner object, passing in the name of your group.

See also