Extension:Lockdown/ja

Lockdown拡張機能は、特定の名前空間や特別なページへのアクセスを、指定された利用者グループの集合に制限する方法を実装しています. これにより、既定の 、 設定で提供されるセキュリティ モデルよりも、よりきめ細かいセキュリティ モデルが提供されます.

MediaWiki が既定で使用するセキュリティ モデルについての以下のページが、下記の説明を理解するのに役立つでしょう:

例
ロックダウンの使用


 * Special:Export へのアクセスをログイン済み利用者 (登録利用者) のみに制限する
 * プロジェクトの名前空間の編集をログイン利用者（登録利用者）に制限する.

以下によって実行します:

説明とその他の例は以下をご覧ください.

設定
Lockdown拡張機能はアクセスを制限するためにのみ使用でき、アクセスを許可するために使用できるわけではないことに注意してください. MediaWikiの組み込み設定によってアクセスが拒否される場合、Lockdownを使用してアクセスを許可することはできません.

$wgSpecialPageLockdown
では、各特別ページに対して、どのユーザーグループがアクセスできるかを指定することができます. 例えば、履歴ページの利用をログイン済み利用者に限定する場合は、Special:Export で以下を使用します:

なお、特殊なページの中には、「ネイティブ」に特定の権限が必要なものがあります. 例えば、ページの移動に使用できるSpecial:MovePageは、" "権限（デフォルトではログインしたユーザーにのみ付与されます）が必要です. This restriction can not be overridden using the Lockdown extension.

Some special page titles are not capitalized the way they appear on-wiki. For instance, Special:RecentChanges is Recentchanges internally, so to restrict it you need:

A full list of special page titles is available in the "" file ( array) or alternatively use the "siteinfo" API module like e.g. /api.php?action=query&meta=siteinfo&siprop=specialpagealiases in your wiki.

$wgActionLockdown
allows you to specify for each action which user groups have access to it. 例えば、履歴ページの利用をログイン済み利用者に限定する場合は、LocalSettings.php で以下を使用します:

Note that some actions can not be locked down this way. In particular, it will not work for the  action.

$wgNamespacePermissionLockdown
lets you restrict which user groups have which permissions on which namespace. For example, to grant only members of the sysop group write access to the project namespace, use this:

Wildcards for either the namespace or the permission (but not both at once) are supported. More specific definitions take precedence:

The first two lines restrict all permissions in the project namespace to members of the sysop group, but still allow reading to anyone. The third line limits page moves in all namespaces to members of the autoconfirmed group.

Note that this way, you cannot grant permissions that have not been allowed by the build-in $wgGroupPermissions setting. The following does not allow regular users to patrol edits in the main namespace:

Instead, you would have to grant this right in $wgGroupPermissions first, and then restrict it again using $wgNamespacePermissionLockdown:

Note that when restricting read-access to a namespace, the restriction can easily be circumvented if the user has read access to any other namespace: by including a read-protected page as a template, it can be made visible. To avoid this, you would have to forbid the use of pages from that namespace as templates, by adding the namespace's ID to :

You can of course also use Lockdown with custom namespaces defined using :

Note that custom namespaces should always be defined in pairs, the namespace proper (with an even id), and the associated talk namespace (with an odd id).

If you want to use constants to refer to your namespaces, you need to define them:

You could also use array_fill to restrict multiple namespaces at once, e.g. if you wanted to restrict namespaces 0 to 2009 to editing by sysops only:

$wgNamespacePermissionLockdown vs $wgActionLockdown
is checked considerably sooner (in the MediaWikiPerformAction hook) in the request-handling process than  (which is checked in the getUserPermissionsErrors hook).

If an action that  does not permit is attempted, a permission error is displayed. Likewise,  lets the end user know which groups are allowed to perform the action.

グループの一覧
You can control which user belongs to which groups with the page Special:Userrights. Only existing groups will be proposed, but you can "create" a new group by creating an entry for it in (even if you don't actually need to set a permission there, but it has to appear on the left hand side of the array). For example:

For more information, see Help:User rights, Manual:User rights, and Manual:User rights management.

追加情報

 * Images and other uploaded files

Images and other uploaded files still can be seen and included on any page. Protections on the Image namespace do not prevent that. See Manual:Image Authorisation for information on how to prevent unauthorized access to images. See also:

既知の問題点
Lockdown is known to be broken for MW 1.27.x to 1.30.x. Possible side-effects of using it include: A workaround may be to list all namespaces under, but success is not guaranteed. Another temporary solution is to use a version before the breaking commits, as detailed in Topic:Tr4xxpln3fnpz3eu.
 * Incomplete list of namespaces showing under the Advanced tab of Special:Search and on the special page for ReplaceText
 * Searchbox no longer offering autocompletion for certain namespaces

関連項目

 * Category:User rights extensions
 * (BlueSpice) - for adding, editing and deleting user groups
 * (BlueSpice) - for administering user rights to user groups
 * - Allows per-user per-right per-page protection
 * - Allows restricting access to specific pages and files
 * CategoryLockdown - Allows restricting access by category and group