Help:Login notifications/fr

Bonjour ! Vous êtes ici parce que vous avez reçu une notification au sujet d’une tentative de connexion à votre compte ? Pas d’inquiétude ! Votre compte est toujours sécurisé.

Pourquoi ai-je reçu cette/ces notification(s) ?
Vous avez reçu une notification parce que quelqu’un a essayé (sans succès) de se connecter à votre compte. Si la tentative a été effectuée sur un appareil ou un navigateur que vous n’aviez pas utilisé auparavant, vous obtenez une notification après la première tentative échoué. Si c’était sur un appareil ou un navigateur connu, la notification apparait après cinq tentatives.

Les notifications ont été générées par LoginNotify, une fonctionnalité introduite en 2017.

What should I do?
You should have a strong and unique password for your account. If you don't think this is the case, you should go ahead and change your password as soon as possible. According to one study of leaked account passwords, nearly 17% of 10 million internet user accounts have "123456" as their password. Don't be one of them!

Also, it might be a good idea to associate an email address with your account in the event you lose access to your account and want to get back in. You can set your email on the first panel of your Preferences page. You might also want to glance through this essay on how to prevent account hijacking which has some general tips you should keep in mind when using the internet.

How does this feature work?
The extension keeps track of known devices (browsers really) by placing a cookie in the browser. This cookie automatically expires in 180 days. If a failed login attempt happens from a new browser, it generates an Echo notification alerting the user about the login attempt. The other way that we identify known devices is by checking the current IP address subnet against the IP addresses that have been used recently (as stored in a temporary server cache). None of the information is stored in a database and at no point is any private information revealed publicly, including the attacker’s IP address/location. The WMF Legal and Security teams have reviewed the implementation for both compliance with our Privacy Policy and security considerations.

For known devices/IPs, we allow up to 5 login attempts before alerting the user about the login attempt, since it's fairly common to mistype or forget a password. If there are 5 or more failed attempts, the notification will say: "There have been 5 failed attempts to log in to your account since the last time you logged in. If this wasn't you, please make sure your account has a strong password." There would be another notification at 10 attempts, 15 attempts and so on.

For unknown devices/IPs, we alert on every failed attempt. The extension bundles these notifications to avoid spamming users with too many notifications. For example, if there are 3 failed attempts from an unknown device, there will be a single notification, which says: "There have been 3 failed attempts to log in to your account from a new device since the last time you logged in. If this wasn't you, please make sure your account has a strong password." On further attempts, that notification would update to say "4 failed attempts," "5 failed attempts", and so on.

Things to note
There are two ways for users to get these notifications – either by web Echo notifications or by email. By default, the web notifications are on for everyone and email ones are turned off. This is configurable in the notification preferences.

This extension does not give you notifications when somebody successfully logs into your account from an unknown device or IP. It is technically possible to generate those, but if somebody else has logged in, they could just as easily see those notifications and do a password reset (which the notification encourages you to do). The ideal way to handle this is to issue email notifications for this case, but since most Wikipedia accounts do not have emails associated with them, this wouldn't be useful to majority of the users. So for the time being, we have settled for not issuing these notifications.