Last modified: 2011-04-14 15:13:01 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 T20447, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18447 - AntiSpoof confused by users differing only in capitalisation (mysql case-insensitivity)
AntiSpoof confused by users differing only in capitalisation (mysql case-inse...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AntiSpoof (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-13 08:23 UTC by OverlordQ
Modified: 2011-04-14 15:13 UTC (History)
1 user (show)

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


Attachments

Description OverlordQ 2009-04-13 08:23:23 UTC
Say there's an existing user named Sriniw8z in the wiki. This get's normalized to: v2:5R1N1W8Z

Say this user has been gone for many many years so you override AntiSpoof to create a user named:

SRINIW8Z, which also gets normalized into v2:5R1N1W8Z.

Now in the spoofusers table, you'd expect to see both entries?

However in MySQL's case insenitive nature, it clobbers the old entry since the query in batchRecord uses a replace call, and you just get the second one listed.  This throws off later AntiSpoof checks as they'll only show one similar user, instead of multiple.

Seems to work as intended with PG, I dont know if this is an artifact of the old DB style WMF uses, I dont have a new UTF-8 MySQL to test on.
Comment 1 Andrew Garrett 2009-04-13 08:27:01 UTC
Updated summary to vaguely reflect the problem.

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


Navigation
Links