Last modified: 2008-06-05 15:12:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8504 - Automatically block Tor exit nodes
Automatically block Tor exit nodes
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-06 13:38 UTC by Invalid Account
Modified: 2008-06-05 15:12 UTC (History)
2 users (show)

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


Attachments

Description Invalid Account 2007-01-06 13:38:53 UTC
I find Tor gives this script out to auto-block Tor in something called Python, which I don't believe any 
webhosts run: http://tor.eff.org/svn/trunk/contrib/exitlist

Then there's a DNSbl that is supposed to lookup Tor http://www.ahbl.org/docs/torbl.php

So maybe MediaWiki could integrate code to do either a regular check and update of a tor list like once 
a day. Or have some kind of custom DNSbl (aside from SORBS) that one can inpute any DNSbl to use for 
blocking.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-01-06 23:39:23 UTC
1) The script appears to only work if you have Tor installed, although I don't
claim to know much about Tor and could be wrong.

2) There's already code to use arbitrary DNSBLs, IIRC, just it's not used by the
WMF because there's no way to override false positives.  There was some talk of
maintaining our own DNSBL and updating it in real time, but it never got anywhere.
Comment 2 Invalid Account 2007-01-07 02:33:12 UTC
Where is the code for "code to use arbitrary DNSBLs"? No mention in defaultsettings.php

An extension?
Comment 3 Andrew Garrett 2007-01-07 02:34:34 UTC
Working on it as an extension.
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-01-07 02:41:47 UTC
(In reply to comment #2)
> Where is the code for "code to use arbitrary DNSBLs"? No mention in
defaultsettings.php
> 
> An extension?

Just change $wgSorbsUrl to some non-SORBS DNSBL, I suppose.  I can't see why
that wouldn't work.  Maybe those variables should be named better?
Comment 5 Invalid Account 2007-01-08 14:25:30 UTC
wgSorbsUrl is not in defaultsettings.php

The only thing with sorbs in its variable name is a true or false variable.
Comment 6 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-01-08 16:36:22 UTC
Check trunk, or version 1.9 that's about to be released.  It's not in 1.8, I
don't think.
Comment 7 Invalid Account 2007-01-13 00:37:53 UTC
Okay I found http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_9_0/phase3/RELEASE-NOTES

$wgSorbsUrl will replace the SORBS DNSBL. But I'd prefer to still be able to use SORBS. So 2 or 3 
DNSBLs would be a good option to have.

Comment 8 Invalid Account 2007-01-20 12:37:31 UTC
Well basically the needed enhancement is the ability to use multiple DNSBLs.


Comment 9 Andrew Garrett 2008-05-10 01:14:36 UTC
Given the concerns above about using the existing functionality, I now intend to do some work on a dedicated extension with a local whitelisting interface.
Comment 10 Chad H. 2008-06-05 15:12:46 UTC
Resolved by [[mw:Extension:TorBlock]]

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


Navigation
Links