Help:Login notifications/nb

Don't worry!
Hei der! Er du her fordi du fikk et varsel om et innloggingsforsøk til brukeren din? Ikke bekymre deg! Brukeren din er ennå sikker.

Hvorfor fikk jeg varselet?
Du fikk et varsel fordi noen prøvde (og feilet) å logge inn på brukeren din. Hvis innloggingsforsøket var på en enhet eller nettleser du ikke har brukt før, fikk du et varsel etter det første feilede forsøket. Hvis det var på en kjent enhet eller nettleser, var varselet sendt etter fem forsøk.

Varselet var laget av $LoginNotify, som ble innført i 2017.

Hva bør du gjøre?
Du bør ha et sterkt og unikt passord til brukeren din. Hvis du ikke har det, burde du endre passordet ditt så tidlig som mulig. Ifølge en studie av lekkende passord, har 17% av 10 millioner internettbrukere «123456» som deres passord.

Don't be one of them! Even if you do have a strong password, you may want to change your password anyway, if you suspect that someone else has tried to access your account.

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 browsers by placing an HTTP 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 compliances 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 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: "".

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 and email notifications are on for everyone. This is configurable in the notification preferences.

Successful logins
The extension allows you to get an email when a user logs in successfully to your account from an unfamiliar device and IP. This is especially helpful for admins or other functionaries who are concerned that their rights might be misused. This notification is on by default. Note that the web notifications are disabled for this feature. The email text says: "" You can disable this in your preferences.

Have a strong password
There is a lot of advice available online about making a strong password. Here is some general advice about passwords:


 * "Select strong passwords – eight or more characters long, and containing letters, digits, and punctuation". (Source: Security/Password reset on Meta). Know more about passwords and security.
 * "As a rule of thumb, a password that is reasonably long, with a mixture of upper and lowercase letters and numbers, and not mostly made up of dictionary words or names or personal information (date of birth, cat's name, etc.) is likely to be reasonably strong for everyday use. Passwords that consist of just lowercase letters can also be reasonably strong, but they must be significantly longer". (Source: User account security on English Wikipedia).