Last modified: 2008-07-02 15:01:29 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 T15918, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 13918 - Make CAPTCHA less obtrusive
Make CAPTCHA less obtrusive
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ConfirmEdit (CAPTCHA extension) (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: accessibility, easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-01 16:40 UTC by Eugene N
Modified: 2008-07-02 15:01 UTC (History)
1 user (show)

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


Attachments

Description Eugene N 2008-05-01 16:40:38 UTC
Currently, if a user enters a wrong password, s/he is required to do a CAPTCHA on the next try, or wait some amount of time.  I propose doing it not after one failed attempt, but only after 2 or 3 attempts. 

This wouldn't affect security very much, but will make logging on more convenient. Mistyping one's password is a very natural thing, for those who don't memorize their password in their browser. 

Besides, I believe this change will greatly decrease the number of captchas processed per day, which can be useful in terms of CPU spent. Also it will improve accessibility to people with poor sight.

Possible downsides: 

It will very slightly make guessing passwords easier.

Required changes:

To have a counter instead of a binary flag, which seems simple.
Comment 1 Chad H. 2008-07-02 15:01:29 UTC
$wgCaptchaBadLoginAttempts implemented in r36918. This can be set to allow 1 (or more) bad login attempts before triggering the captcha.

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


Navigation
Links