Phabricator のプロジェクト名 #CheckUser

Extension:CheckUser

From MediaWiki.org
Jump to: navigation, search
This page is a translated version of the page Extension:CheckUser and the translation is 12% complete.

Other languages:
বাংলা • ‎Deutsch • ‎English • ‎español • ‎français • ‎magyar • ‎italiano • ‎日本語 • ‎한국어 • ‎Nederlands • ‎polski • ‎português do Brasil • ‎русский • ‎svenska • ‎中文
MediaWiki 拡張機能マニュアルManual:Extensions
Crystal Clear action run.png
CheckUser

リリースの状態:Extension status 安定

CheckUser1.png
実装Template:Extension#type Special page, User identity
説明Template:Extension#description CheckUser function allows a user with permissions to check which IPs are used by a given username and which usernames are used by a given IP, without having to run queries directly against the database by hand.
作者Template:Extension#username Tim Starling, Aaron Schulz
最新バージョンTemplate:Extension#version 2.4
MediaWikiTemplate:Extension#mediawiki 1.23+
データベースの変更Template:Extension#needs-updatephp はい
テーブルTemplate:Extension#table1 cu_changesExtension:CheckUser/cu_changes table
cu_logExtension:CheckUser/cu_log table
ライセンスTemplate:Extension#license GNU General Public License 2.0 or later
ダウンロード
追加する権限Template:Extension#rights

checkuser
checkuser-log

使用するフックTemplate:Extension#hook
RecentChange_saveManual:Hooks/RecentChange_save
EmailUserManual:Hooks/EmailUser
AuthPluginAutoCreateManual:Hooks/AuthPluginAutoCreate
ParserTestTablesManual:Hooks/ParserTestTables
LoadExtensionSchemaUpdatesManual:Hooks/LoadExtensionSchemaUpdates
ContributionsToolLinksManual:Hooks/ContributionsToolLinks
ArticleEditUpdatesDeleteFromRecentchangesManual:Hooks/ArticleEditUpdatesDeleteFromRecentchanges
LoggableUserIPDataManual:Hooks/LoggableUserIPData
AddNewAccountManual:Hooks/AddNewAccount

translatewiki.net で翻訳を利用できる場合は、CheckUser 拡張機能の翻訳にご協力ください

使用状況とバージョン マトリクスを確認してください。

問題点Phabricator

未解決のタスク · バグを報告
This page is about the extension itself. For the Wikimedia Foundation CheckUser policy, see m:CheckUser policy.

CheckUser is an extension that allows a user (with the checkuser permission) to check which IPs are used by a given username and which usernames are used by a given IP, without having to run queries directly against the database by hand. The extension is running live on all Wikimedia wikis.

ダウンロード[edit]

拡張機能は、Git から直接取得できる場合があります [?]:

  • コードを参照
  • 一部の拡張機能には安定版リリースのタグがあります。
    • タグを参照
    • タグを選択します
    • 「スナップショット」をクリックします
  • 各ブランチは過去の MediaWiki リリースと関連付けられています。 最新のアルファ バージョンを含む「master」ブランチもあります (MediaWiki のアルファ バージョンが必要な場合用)。

スナップショットを展開して、MediaWiki インストレーション内の extensions/CheckUser/ ディレクトリに配置します。

git に馴染みがあり、かつサーバーにシェルでアクセスできる場合は、拡張機能を以下のようにして取得することもできます:

cd extensions/
git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/CheckUser.git

インストール[edit]

The extension is released under the GNU General Public License 2.0 or later. The software is provided as-is. Updates will be made according to the needs of Wikimedia wikis; or where critical vulnerabilities are discovered.

On an existing wiki[edit]

Basic[edit]

  • If you have installed other extensions without running php maintenance/update.php, run that first.
  • ダウンロードして、ファイルを extensions/ フォルダー内の CheckUser という名前のディレクトリ内に配置します。
  • 以下のコードを LocalSettings.php の末尾に追加します:
    wfLoadExtension( 'CheckUser' );
    
  • To users running MediaWiki 1.27 or earlier:
Using a telnet/ssh client program such as PuTTY, navigate to the extensions/CheckUser folder and run php install.php. Ensure that you are running a PHP version 5.x install, otherwise this script will not run. If install.php is not present then run php maintenance/update.php again. The result will be something similar to this:
...cu_changes table added.
...doing rc_id from 368856 to 368955....
...
...cu_changes table added and populated.
...cu_log added
...logging disabled, skipping log import.
  • YesY 完了 - ウィキの「Special:Version」に移動して、拡張機能が正しくインストールされたことを確認します。

MediaWiki 1.24 以前を稼働させている利用者へ:

上記の手順では、wfLoadExtension() を使用してこの拡張機能をインストールする新しい方法を記載しています。 この拡張機能をこれらの過去のバージョン (MediaWiki 1.24 以前) にインストールする必要がある場合は、wfLoadExtension( 'CheckUser' ); の代わりに以下を使用する必要があります:

require_once "$IP/extensions/CheckUser/CheckUser.php";
Installing without command prompt access[edit]

Many hosting providers don't allow direct shell access, but allow creation of cron jobs (e.g. via cPanel web interface). For those hosting providers a temporary cron job can be used to run php /path/to/install.php (naturally /path/to should be replaced with real full path to install.php). If you are using a remote server and do not have command prompt access (nor cron job solution is suitable for you), but do have access through phpMyAdmin, substitute these steps for step #2 above:

  1. Download cu_changes.sql and cu_log.sql
  2. In phpMyAdmin, click the database you're using for mediawiki along the left side
  3. On the next screen, click the "Import" tab at the top.
  4. At "Location of the text file", choose one of the files, select compression "None", and click the bottom "Go" button.
    If your phpMyAdmin screen has only a text field and no text file chooser, click the "SQL" button in the left-side column, under the phpMyAdmin logo, and click the "import files" tab in the new window that opens.
  5. Repeat for the second file

On a new wiki[edit]

Follow step 1 as above, then run the MediaWiki installation. The MediaWiki installer will automatically perform the installation tasks if you select the checkbox for CheckUser when prompted for which extensions to install.

Configuration[edit]

This tool migrates recent changes data to a separate cu_changes table, and adds to that when new entries are added. If $wgPutIPinRCManual:$wgPutIPinRC was previously set to false, there will be no initial data to search but new edits will fill in as soon as the extension is set up.

After you run the queries, you can reduce $wgRCMaxAgeManual:$wgRCMaxAge to make recentchanges shorter, without affecting checkuser. Use $wgCUDMaxAge to set how far back checkuser data can go, in seconds.

In versions for MediaWiki 1.22 and later, the CheckUser-specific setting $wgCheckUserCIDRLimit determines the largest range that can be checked in a single check. Its format is the same as $wgBlockCIDRLimitManual:$wgBlockCIDRLimit. Otherwise, the default limit (for all versions) is /32 for IPv6 checks and /16 for IPv4 checks.

CheckUsers using Mozilla Firefox can add this JS script to their .js file. It makes retrieving IP WHOIS data easier. It requires applets.codebase.principle support (about:config) enabled. (This can be signed.applets.codebase_principle_support in Firefox 3)

Granting right to use CheckUser[edit]

To grant the right to use the Check User function, a user with user rights management must go to Special:UserRights and enter the user's name in the box, then select the option "Check User". Once this is done, the Check User option will show up on the Special pages page for that user.

To turn on user rights management for sysops, put the following into LocalSettings.php:

$wgGroupPermissions['sysop']['checkuser'] = true;

$wgGroupPermissions['sysop']['checkuser-log'] = true;

To only allow the adding and removing of the checkuser permission, use the following instead:

$wgAddGroups['sysop'][] = 'checkuser';
$wgRemoveGroups['sysop'][] = 'checkuser';

Configuration[edit]

Configuration settings in CheckUser.php
パラメーター 既定値 コメント
$wgCheckUserLog '/home/wikipedia/logs/checkuser.log' Legacy variable, no longer used. Used to point to a file in the server where CheckUser would log all queries done through Special:CheckUser. If this file exists, the installer will try to import data from this file to the 'cu_log' table in the database.
$wgCUDMaxAge 3 * 30 * 24 * 3600; // 3 months How long to keep CU data (in seconds)?
$wgCheckUserMaxBlocks 200; Mass block limits
$wgCheckUserForceSummary false Set this to true if you want to force checkusers into giving a reason for each check they do through Special:CheckUser. (Not very useful, given that checkusers could simply give a summary such as "they need to be checked" or "I feel like it" and the software would not know.)
$wgCheckUserCIDRLimit

$wgCheckUserCIDRLimit = array( 'IPv4' => 16, 'IPv6' => 32, );

Shortest CIDR limits that can be checked in any individual range check
$wgCUPublicKey <<<CUPUBLICKEY

CUPUBLICKEY;

Public key to encrypt private data that may need to be read later Generate a public key with something like:

`openssl genrsa -out cu.key 2048; openssl rsa -in cu.key -pubout > cu.pub` and paste the contents of cu.pub here

使用法[edit]

Basic interface[edit]

  1. Go to Special:CheckUser.
  2. In the user field, type in the username (without the 'user:' prefix), IP address, or CIDR range.
    • IP: any IPv4 or IPv6 address.
    • CIDR: you can check a range of IP addresses by appending the CIDR prefix (by default, up to /16 for IPv4 (65,536 addresses), up to /64 for IPv6 (~1.8446*1019 addresses) before revision 7352, up to /48 for IPv6 (~1.2089*1024 addresses or 65536 /64s - controlled by $wgCheckUserCIDRLimit in the latest version) after revision 7352, and up to /32 (65536 /48's) after revision rECHU9d7c239bf88866eca577f3241194d440f94fa014). For notation, see Range blocks.
    • XFF: you can check a client IP address provided by X-Forwarded-For headers by appending /xff (for example, 127.0.0.1/xff).
  3. Select the information you want to retrieve.
    • Get IPs: returns IP addresses used by a registered user.
    • Get edits from IP: returns all edits made by a user (registered or anonymous) from an IP address or range.
    • Get users: returns user accounts that have edited from an IP or range.
  4. In the reason field, type in the reason you are accessing the confidential data. Try to succinctly summarise the situation (for example, "cross-wiki spam"); this will be logged in a log visible only to users with the checkuser-log permission.

Information returned[edit]

A typical entry in the CheckUser results for a user summary ("get users") is as follows:

  • Example (Talk | contribs) (20:11, 20 9月 2017 -- 20:12, 20 9月 2017) [5]
    1. 127.0.0.37 XFF: 127.0.0.1, 127.0.0.5

This is formatted to fit a lot of information into a format that can very easily be listed and skimmed, but is difficult to read unless you know what the information provided is. The information is laid out as follows:

  • 利用者名 (利用者リンク群) (time period when they edited from the given IP or range) [number of edits from the IP or range]
    1. IP address edited from XFF: XFF information provided (can be spoofed)

Each IP/XFF combination used to edit is listed, in order of use.

The last ten user agents (browser, operating system, system language, and versions) for each user for edits made in the IP or range are listed afterwards.

XFF Format[edit]

XFF (X-Forwarded-For) headers indicate the series of IP addresses used from the user's computer (first) to the last proxy server. In case of Wikimedia, the last proxy server is one of the Wikimedia proxies (listed under $wgSquidServersNoPurge in the Wikimedia configuration file).

In this example:

aaa.aaa.aaa.aaa XFF: 10.4.46.42, 127.0.0.1, aaa.aaa.aaa.aaa, 208.80.152.46

  • the first two addresses (10.4.46.42, 127.0.0.1) are private to the originating network and can't be reached directly from the public Internet,
  • the third address (aaa.aaa.aaa.aaa) is the "public face" of the editor, usually a broadband or dialup ISP, a company gateway, (but possibly an anonymizer or a malware-compromised server),
  • the last address (208.80.152.46) is one of the Wikimedia squids (sq36.wikimedia.org).

MediaWiki configuration settings $wgUsePrivateIPs, $wgSquidServers, $wgSquidServersNoPurge and extensions using the IsTrustedProxy hook (such as Extension:TrustedXFF) change the way an actual IP address used to attribute edits is selected.

エラー メッセージ[edit]

database query syntax error

If you receive an error message like this when you try to save a page:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:

(SQL query hidden)

from within function "efUpdateCheckUserData". Database returned error "1146: Table 'cu_changes' doesn't exist (localhost)".

This means that CheckUser has not been installed correctly. In this case you forgot to create the necessary cu_changes table in your database.

API[edit]

CheckUser also provides an API.

api.php?action=query&list=checkuser&curequest=userips&cutarget=Jimbo_Wales
api.php?action=query&list=checkuser&curequest=edits&cutarget=127.0.0.1/16&xff=1&cureason=Some_check
api.php?action=query&list=checkuserlog&culuser=WikiSysop&cullimit=25
api.php?action=query&list=checkuserlog&cultarget=127.0.0.1&culfrom=20111015230000