Extension:ConfirmEdit

The ConfirmEdit extension lets you use various different CAPTCHA techniques, to try to prevent spambots and other automated tools from editing your wiki, as well as to foil automated login attempts that try to guess passwords.

ConfirmEdit ships with several techniques/modules to generate captcha.

Some of these modules require additional setup work:
 * MathCaptcha requires both the presence of TeX and, for versions of MediaWiki after 1.17, the Math extension;
 * FancyCaptcha requires running a preliminary setup script in Python; and reCAPTCHA requires obtaining API keys.

Caveats: CAPTCHAs reduce accessibility and cause inconvenience to human users. In addition, they are not 100% effective against bots, and they will not protect your wiki in any way from human spammers. You may wish to use ConfirmEdit in conjunction with other anti-spam features. Regardless of the solution you use, if you have a publicly-editable wiki it's important to keep monitoring the "Recent changes" page.

Installation
The ConfirmEdit extension requires MediaWiki 1.11.0 or higher and PHP5 (but revisions on SVN before 21970 are PHP4-compatible).


 * Download the latest version and save it to your computer
 * Create a folder in the extensions folder named ConfirmEdit
 * Move the files to the extensions/ConfirmEdit/ folder
 * Edit LocalSettings.php in the root of your MediaWiki installation, and add the following line near the bottom:

Note: ConfirmEdit may not work if used with a MediaWiki version different from the one specified when downloading via the "Extension distributor".

CAPTCHA types
There are numerous different CAPTCHA types included with ConfirmEdit.

SimpleCaptcha (calculation)
This is the default CAPTCHA. This module provides a simple addition or subtraction question for the user.

Set the following to enable this CAPTCHA:

FancyCaptcha
This module displays a stylized image of a set of characters. The Python Imaging Library must be installed in order to create the set of images initially, but isn't needed after that.


 * 1) Add the following lines to LocalSettings.php in the root of your MediaWiki installation:
 * 2) In LocalSettings.php, set the variable $wgCaptchaDirectory to the directory where you will store Captcha images.  Below it set $wgCaptchaSecret to your passphrase.
 * 3) Create the images by running the following, where:
 * 4) * font is a path to some font, for instance AriBlk.TTF.
 * 5) * wordlist is a path to some word list, for instance /usr/share/dict/words. (Note: on Debian/Ubuntu, the 'wbritish' and 'wamerican' packages provide such lists. On Fedora, use the 'words' package).
 * 6) * key is the the exact passphrase you set $wgCaptchaSecret to. Use quotes if necessary.
 * 7) * output is the path to where the images should be stored (defined in $wgCaptchaDirectory).
 * 8) * count is how many images to generate.
 * 9) * An example, assuming you're in the extensions/ConfirmEdit directory (font location from Ubuntu 6.06, probably different on other operating systems):
 * 10) * If you are not satisfied with the results of the words you've generated you can simply remove the images and create a new set. Comic_Sans_MS_Bold.ttf seems to generate relatively legible words, and you could also edit the last line of captcha.py to increase the font size from the default of 40.
 * 1) * An example, assuming you're in the extensions/ConfirmEdit directory (font location from Ubuntu 6.06, probably different on other operating systems):
 * 2) * If you are not satisfied with the results of the words you've generated you can simply remove the images and create a new set. Comic_Sans_MS_Bold.ttf seems to generate relatively legible words, and you could also edit the last line of captcha.py to increase the font size from the default of 40.
 * 1) * If you are not satisfied with the results of the words you've generated you can simply remove the images and create a new set. Comic_Sans_MS_Bold.ttf seems to generate relatively legible words, and you could also edit the last line of captcha.py to increase the font size from the default of 40.

How to avoid common problems running Python
C:\python\python.exe C:\Ex\CAPTCHA.py --font C:\Ex\FONT.ttf --wordlist C:\Ex\LIST.txt --key=YOURPASSWORD --output C:\Ex\ --count=20
 * 1) The captcha.py version 29357 is not supported on newer versions of Python - this is due to deprecated md5, although you can use 2.4x.
 * 2) Install the proper version of Python Imaging Library (PIL) 1.5 for Python 2.4.
 * 3) Make the installation of Python on a short folder name. Like C:\Python\
 * 4) Create a folder like C:\Ex and place files CAPTCHA.py / FONT.ttf / LIST.txt into the folder.
 * 5) To execute easily, run the following example as a batch file:

MathCaptcha
This module generates an image using TeX to ask a basic math question.

Set the following to enable this CAPTCHA:

See the readme file in the math folder to install this captcha.

QuestyCaptcha
This module presents a question and the user supplies the answer. You provide the questions in the configuration. This module has proven to offer a strong mechanism against spam bots.

Set the following to enable this CAPTCHA:

It will randomly choose a question from those supplied. The minimum is one.

Asirra

 * NOTE: The Asirra module is currently not included. Until version 1.0 arrives, you can still use the standalone Extension at Extension:Asirra

This module displays the Asirra (Animal Species Image Recognition for Restricting Access) widget, created by Microsoft Research. The widget shows 12 random images from the Petfinder pet-adoption website, all of which are of either a cat or a dog, and asks the user to select only the images of cats.

Image recognition is an inherently more difficult task for computers than character recognition; and the use of Petfinder's massive, and ever-changing, database of millions of images makes it seemingly impossible for spammers to attempt to beat the system via some shortcut. It should be noted, though, that some research exists showing that image-recognition software can beat Asirra at least 10% of the time. Still, Asirra may possibly be the most secure of the modules within ConfirmEdit.

Note: in order to use Asirra, you will need to download the latest/trunk version of ConfirmEdit.

Add the following to LocalSettings.php to enable this CAPTCHA:

In addition, you can add any of the following configuration parameters:
 * $wgAsirraEnlargedPosition: Can be one of top</tt>, bottom</tt>, left</tt>, right</tt>. Defaults to bottom</tt>.
 * $wgAsirraCellsPerRow</tt>: Number of images per row. Defaults to 6</tt>.
 * $wgAsirraScriptPath</tt>: If your extensions directory is outside the document root, or not accessible for any reason, you can set an alternative path to this module's JavaScript scripts here.

ReCaptcha
This module uses the "reCAPTCHA" widget/service. In addition to providing a CAPTCHA, it performs a valuable service because it helps to digitize old books (read more here.)

To use this module, first go here and obtain a public and private key for your wiki.

Add the following to LocalSettings.php, below the inclusion of ConfirmEdit:


 * Recaptcha is only in the latest 1.18 version of ConfirmEdit. Earlier version do not have the ReCaptcha php files.
 * Unfortunately, as of 2011, some spammers appear to have figured out a way to bypass it, either through character recognition or by using humans. For that reason, it is not necessarily recommended.
 * Part of the weakness of the ReCaptcha module is that ConfirmEdit doesn't include any penalty mechanism, so spam bots can simply keep trying to bypass the CAPTCHA until they get through. This is an issue that is strongly worth addressing in some way.

VisualMathCaptcha
The extension VisualMathCaptcha can also be used, in conjunction with ConfirmEdit. See that extension's documentation for how to install and configure it.

Configuration
ConfirmEdit introduces a 'skipcaptcha' permission type to wgGroupPermissions. This lets you set certain groups to never see CAPTCHAs. All of the following can be added to localsettings.php.

Defaults from ConfirmEdit.php:

To skip captchas for users that confirmed their email, you need to both set:

There are five "triggers" on which CAPTCHAs can be displayed:
 * 'edit' - triggered on every attempted page save
 * 'create' - triggered on page creation
 * 'addurl' - triggered on a page save that would add one or more URLs to the page
 * 'createaccount' - triggered on creation of a new account
 * 'badlogin' - triggered on the next login attempt after a failed one

The default values for these are:

The triggers,   and   can be configured per namespace using the   setting. If there is no  for the current namespace, the normal   apply. So suppose that in addition to the above  defaults we configure the following:

Then the CAPTCHA will not trigger when adding URLs to a talk page, but on the other hand user will need to solve a CAPTCHA any time they try to edit a page in the project namespace, even if they aren't adding a link.

A common alternate setting is to have a CAPTCHA only for unregistered users, on every edit. This can be accomplished by:

URL and IP whitelists
It is possible to define a whitelist of known "good" sites for which the CAPTCHA should not kick in, when the 'addurl' action is triggered.

Sysop users can do this by editing the system message page called MediaWiki:captcha-addurl-whitelist. The expected format is a set of regex's one per line. Comments can be added with # prefix. You can see an example of this usage here, on OpenStreetMap.

This set of whitelist regexes can also be defined using the $wgCaptchaWhitelist config variable in LocalSettings.php, to keep the value(s) a secret.

Some other variables you can add to LocalSettings.php: These are described more thoroughly in the code comments
 * $wgCaptchaWhitelistIP - List of IP ranges to allow to skip the CAPTCHA
 * $ceAllowConfirmedEmail - Allow users who have confirmed their e-mail addresses to post URL links

Test plan
See ConfirmEdit Test Plan.

Authors
The basic framework was designed largely by Brion Vibber, who also wrote the SimpleCaptcha and FancyCaptcha modules. The Asirra module was written by Bachsau. The MathCaptcha module was written by Rob Church. The QuestyCaptcha module was written by Benjamin Lees. The reCAPTCHA module was written by Mike Crawford and Ben Maurer. Additional maintenance work was done by Yaron Koren.