Last modified: 2014-05-05 13:55:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65946, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63946 - Block of login not reported
Block of login not reported
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
1.22.2
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-15 17:20 UTC by Matt Copperwaite
Modified: 2014-05-05 13:55 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
The 5 minute warning when being locked out (18.69 KB, image/png)
2014-04-15 17:20 UTC, Matt Copperwaite
Details

Description Matt Copperwaite 2014-04-15 17:20:00 UTC
Created attachment 15104 [details]
The 5 minute warning when being locked out

When a user fails their password 5 times, they are automatically blocked by default. The message returned suggests trying again in 5 minutes but the block is enforced for longer than 5 minutes (maybe indefinitely).

The block is also stored in memory rather than in the block list so it does not appear in the usual block pages and the login attempts cannot be unblocked. The way I resolved it was to restart the service, flushing the block from memory.

Is there a way to disable this block or have more control over it?

It looks to me like the returned error message will need updating, and the blocks to be stored on the block list rather than in memory where it can't be controlled.
Comment 1 Andre Klapper 2014-05-05 13:14:29 UTC
Matt: Unrelated, but are you really still using old 1.22.0?
Comment 2 Matt Copperwaite 2014-05-05 13:55:53 UTC
Ah, no, I just couldn't find the minor release version I was on at the time. I've changed that now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links