Last modified: 2013-04-22 16:14:14 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 T44018, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42018 - Find common range box doesn't work with IPs starting with octet 2.
Find common range box doesn't work with IPs starting with octet 2.
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Huji
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-11 16:42 UTC by Huji
Modified: 2013-04-22 16:14 UTC (History)
2 users (show)

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


Attachments

Description Huji 2012-11-11 16:42:19 UTC
The updateCIDRresult function doesn't work when you have IP addresses in the "find common range" box that all belong to 2.x.x.x range
Comment 1 Huji 2012-11-11 17:09:21 UTC
I realized I should've been more detailed with my bug report. Currently checkuser.js assumes that ranges 1.0.0.0/8 & 2.0.0.0/8 belong to IANA and should be ignored.

This is problem because some parts of 2.0.0.0/8 range are actually not reserved addresses; e.g. 2.178.0.0 - 2.178.253.255 is owned by Iran's telecommunication company.

More importantly, there are other ranges which are reserved too, and the JS is disregarding those. IMHO, the JS should NOT restrict any ranges, reserved or not. It's the user's responsibility to understand the nature of IP addresses; additionally, reserved addresses should never occur on CU log.

As a result, I submitted Gerrit change #32922 which removes the lines of code from checkuser.js that restrict the use of this tool to certain ranges.

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


Navigation
Links