Extension:ConfirmEdit/fr

L'extension ConfirmEdit vous permet d'utiliser différentes techniques CAPTCHA, pour essayer d'empêcher les spambots et d'autres outils automatisés de modifier votre wiki, ainsi que pour déjouer les tentatives de connexion automatisées qui tentent de deviner les mots de passe.

ConfirmEdit est livré avec plusieurs techniques/modules pour générer captcha.

Certains de ces modules nécessitent un travail d'installation supplémentaire :


 * MathCaptcha nécessite à la fois la présence de TeX et, pour les versions de MediaWiki après 1.17, l'extension ;
 * FancyCaptcha nécessite l'exécution d'un script de configuration préliminaire en Python.

Inconvénients
Les CAPTCHA réduisent l'accessibilité et causent des inconvénients aux utilisateurs humains.

Ils ne sont pas non plus 100% efficaces contre les robots, et ils ne protégeront pas votre wiki des spammeurs qui sont prêts et capables d'utiliser le travail humain pour passer par les CAPTCHA. Vous pouvez utiliser ConfirmEdit avec d'autres fonctionnalités anti-spam. Quelle que soit la solution que vous utilisez, si vous avez un wiki publiquement modifiable, il est important de continuer à surveiller la page "Modifications récentes".

Installation


Types de CAPTCHA
Il existe beaucoup de types différents de CAPTCHA inclus dans ConfirmEdit.

QuestyCaptcha
Ce module pose une question et l'utilisateur doit fournir la réponse. Vous fournissez la question dans la configuration. Ce module a montré qu'il offrait un mécanisme fiable contre les spambots; il présente également l'avantage d'une meilleure accessibilité car les questions textuelles peuvent être lues par les logiciels de lecture d'écran ce qui permet aux utilisateurs qui ont des problèmes de lecture (mais pas aux robots), de répondre correctement aux questions. Ajoutez ceci à  pour activer ce CAPTCHA, en mettant à jour la question-réponse :

Vous pouvez également configurer les drapeaux de ConfirmEdit et les autres options. Si le Captcha ne s'affiche pas, ajoutez ceci sous le code de l'extension. En initialisant chacune des options individuelles à, le Captcha s'activera à chaque fois que l'action nommée sera réalisée. Sinon vous pouvez mettre  pour désactiver le Captcha sur cette action.

Cela va choisir aléatoirement une question dans la liste fournie.

Le minimum est un.
 * QuestyCaptcha n'est pas sensible à la casse. Cela fonctionne quand même lorsque la réponse est « Paris » et que l'utilisateur écrit « paris » ou si la réponse est « paris » et que l'utilisateur écrit « Paris ».
 * If the answer has a special character like "ó", you may write an answer with "ó" and another without, just in case. Par exemple si la réponse est « canción » vous pouvez utiliser  dans le cas où l'utilisateur écrit « cancion ».
 * La réponse doit être facile à deviner par un humain concerné par votre wiki mais pas par un programme automatique. Ideally, it should not be contained in the text of the question; you can try and edit the captcha help messages and provide the solution to the captcha response there.
 * Just change the questions when/if they start proving ineffective; this may never happen if your wiki is not specifically targeted.
 * Don't ever reuse questions already used by you or others in the past: spambots are known to remember a question and its answer forever once they broke it.
 * You can even dynamically generate questy captchas in the configuration. DO NOT use an exact copy of the dynamic questions from the link, they've been cracked by spammers. However, other dynamic questions in the style of the questions presented are highly effective.
 * There is a separate extension to ConfirmEdit called QuestyCaptchaEditor which provides an on-wiki special page for managing QuestyCaptcha question+answer(s) pairings. You may wish to consider installing it if it's desirable to reduce sysadmin intervention when it comes to managing the CAPTCHA questions and their answers.

ReCaptcha (NoCaptcha)
The new generation of ReCaptcha, called NoCaptcha, was introduced by Google back in December 2014 and reduces the need for humans to solve a CAPTCHA. Based on a user-side JavaScript (which can't be controlled by the user the administrator), reCaptcha tries to identify the site user as a human by analyzing their browsing behavior on the page. The user then has to click an "I'm not a robot" checkbox and (in the best case) doesn't have to do anything further to prove they're a human. Néanmoins dans certains cas, l'utilisateur doit encore résoudre une image CAPTCHA.

Ce module implémente la nouvelle solution ReCaptcha NoCaptcha dans ConfirmEdit.

You still need a public and a secret key (which you can retrieve from the ReCaptcha admin panel – change v2, v3 not work) and install the plugin with:

There is an additional configuration option for this module, (default: ), which, if set to, sends the IP address of the current user to a server from Google while verifying the CAPTCHA. Vous pouvez améliorer la confidentialité de vos utilisateurs si vous gardez l'initialisation à. However, remember, that this module adds a client side JavaScript code, directly loaded from a server from Google, which already can collect the IP address of the user (combined with other data, too) and can not be limited by a configuration option. This will only work on standard MediaWiki editor.

reCAPTCHA v3
Currently there is no official way to implement version 3 of Google reCAPTCHA.



SimpleCaptcha (calculs)
C'est le CAPTCHA par défaut.

Ce module demande à l'utilisateur le résultat d'une simple addition ou soustraction.

Ajoutez les lignes suivantes dans  à la racine de votre installation MediaWiki pour activer ce CAPTCHA :

Note that the display of a trivial maths problem as plaintext yields a captcha which can be trivially solved by automated means; as of 2012, sites using SimpleCaptcha are receiving significant amounts of spam and many automated registrations of spurious new accounts. Wikis currently using this as the default should therefore migrate to one of the other CAPTCHAs.

FancyCaptcha
Ce module affiche une image stylisée d'un ensemble de caractères.

Pillow must be installed in order to create the set of images initially, but isn't needed after that (can be installed with  in most environments).


 * 1) Ajoutez les lignes suivantes dans   du répertoire racine de votre installation MediaWiki.
 * 2) In , set the variable  to the directory where you will store Captcha images. Ci-dessous  est initialisé avec votre phrase secrète.
 * 3) Créez les images en exécutant ceci où :
 * 4) * font est un chemin vers une fonte donnée, par exemple AriBlk.TTF.
 * 5) * wordlist est un chemin vers une liste de mots, par exemple . ( Note: on Debian/Ubuntu, the 'wbritish' and 'wamerican' packages provide such lists. Sous Fedora, utiliser le paquet 'words')
 * 6) * key est la phrase secrète utilisée pour initialiser . Utilisez les guillemets si nécessaire.
 * 7) * output is the path to where the images should be stored (defined in ).
 * 8) * count indique le nombre d'images à générer.
 * 9) * An example, assuming you're in the  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.
 * 11) Put the images you get into   directory in your installation.
 * 12) Edit your wiki's : specify full path to your captcha directory in  and secret key you've been using while generating captures in.
 * 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.
 * 2) Put the images you get into   directory in your installation.
 * 3) Edit your wiki's : specify full path to your captcha directory in  and secret key you've been using while generating captures in.

See also Generating CAPTCHAs for how Wikimedia Foundation does it.


 * How to avoid common problems running Python on Windows


 * 1) Installez la version la plus récente de Pillow.
 * 2) Make the installation of Python on a short folder name, like C:\Python\
 * 3) Create a folder like C:\Ex and place files CAPTCHA.py / FONT.ttf / LIST.txt into the folder.
 * 4) To execute easily, run the following example as a batch file:

 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

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

Initialisez les valeurs suivantes pour activer ce CAPTCHA : See the  file in the math folder to install this captcha.

hCaptcha
Voir https://www.hcaptcha.com/

La configuration est similaire à ReCaptcha : is also available.

Configuration
ConfirmEdit introduces a  permission type to. This lets you set certain groups to never see CAPTCHAs. All of the following can be added to. Defaults from : To skip captchas for users that confirmed their email, you need to set both: 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. Requires to be set to something other than   in your , if in doubt the following will always work. Note that   does not trigger captchas on API login, but instead blocks them outright until  expires.

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.



Listes blanches d'URL et d'adresses IP
It is possible to define a whitelist of known good sites for which the CAPTCHA should not kick in, when the  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 on OpenStreetMap.

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

Some other variables you can add to : These are described more thoroughly in the code comments
 * $wgCaptchaWhitelistIP - List of IP ranges to allow to skip the CAPTCHA (you can also use MediaWiki:Captcha-ip-whitelist; see below for details).
 * $ceAllowConfirmedEmail - Allow users who have confirmed their e-mail addresses to post URL links

MediaWiki:Captcha-ip-whitelist can be used to change the whitelisted IP addresses and IP ranges on wiki.

They should be separated by newlines.

If any other character (apart from a valid IP address or range) is found on a line, it will be ignored but leading and trailing whitespace characters are allowed.

For example, a line with only  is considered valid but   will be ignored.



Expressions régulières
The global variable wgCaptchaRegexes accepts an array of regexes to be tested against the page text and will trigger the CAPTCHA in case of a match.



Approche Wikimedia
For example, wikis use FancyCaptcha with a custom set of images and the default configuration, modified by what follows. This means only unregistered and newly registered users have to pass the CAPTCHA.



Mode EmergencyCaptcha
Additionally the shortcut named is designed for use in a limited number of emergency situations, for instance in case of massive vandalism or spam attacks: it changes the default trigger values (see above) into the following: So all anonymous and new users have to solve a CAPTCHA also before being able to save an edit or create a new page, in addition to the normal situation.

Limite du taux
ConfirmEdit supports rate limiting for false CAPTCHA.

For more information about and how to set it up, read, the action key is.

Auteurs
The basic framework was designed largely by Brion Vibber, who also wrote the SimpleCaptcha and FancyCaptcha modules.

Le module MathCaptcha a été écrit par Rob Church.

Le module QuestyCaptcha a été écrit par Benjamin Lees.

Le travail supplémentaire de maintenance a été fait par Yaron Koren.

Références
