Last modified: 2012-09-06 16:27: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 T41980, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39980 - Block XFF
Block XFF
Status: RESOLVED DUPLICATE of bug 23343
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-04 17:37 UTC by Ole Palnatoke Andersen
Modified: 2012-09-06 16:27 UTC (History)
4 users (show)

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


Attachments

Description Ole Palnatoke Andersen 2012-09-04 17:37:56 UTC
Some vandals are smart enough to change their IP address, but we can find the originating IP address in XFF headers. It would be good to be able to block based on XFF header.
Comment 1 Liangent 2012-09-04 17:41:54 UTC
Then vandals can forge their XFF to claim they're coming from somewhere else.

If you have a list of trusted proxy servers, please check out [[mw:Extension:TrustedXFF]].
Comment 2 Liangent 2012-09-04 17:49:40 UTC
Should be WFM, my fault.

This function is built-in and configurable with $wgSquidServersNoPurge and the above extension is just a list.

If you want to open it to every IP, write in your LocalSettings.php:

$wgHooks['IsTrustedProxy'][] = function( &$ip, &$trusted ) { return $trusted = true; }
Comment 3 Kåre Thor Olsen 2012-09-04 18:27:02 UTC
This request is due to vandalism seen in Wikipedia; we can't just change the setup ourselves as we see fit.

Sometimes you have other means to verify the validity of an XFF address, and when you know for a fact that the vandalism is coming from said XFF address, it would save a lot of combined time and effort if the checkusers were able to stop the vandalism at the origin rather than the administrators having to chase after open proxies and revert vandalism.

Thus, I'm re-opening as the requested feature isn't implemented.
Comment 4 Marcin Cieślak 2012-09-04 18:33:16 UTC

*** This bug has been marked as a duplicate of bug 23343 ***

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


Navigation
Links