Last modified: 2013-06-18 15:44:55 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 T20540, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18540 - Change TorBlock configuration on WMF wikis
Change TorBlock configuration on WMF wikis
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-21 00:28 UTC by MZMcBride
Modified: 2013-06-18 15:44 UTC (History)
9 users (show)

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


Attachments

Description MZMcBride 2009-04-21 00:28:08 UTC
After discussion at http://techblog.wikimedia.org/2009/04/planning-to-tighten-torblock-restrictions/ and http://lists.wikimedia.org/pipermail/wikitech-l/2009-April/042434.html , there's nearly unanimous agreement to change the configuration of the TorBlock extension to make it more strict.

I believe what's needed is to set:
$wgGroupPermissions['user']['torunblocked'] = true;

This change should probably be made concurrently with bug 18337 ("Enable "IP block exemption" on all Wikimedia wikis").
Comment 1 Brion Vibber 2009-04-21 00:30:38 UTC
Tossing a bunch of CCs on and assigning. :D
Comment 2 Andrew Garrett 2009-04-21 02:29:24 UTC
(In reply to comment #1)
> Tossing a bunch of CCs on and assigning. :D

Do we want to do this concurrently with bug 18337?
Comment 3 Mike.lifeguard 2009-04-21 02:37:40 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Tossing a bunch of CCs on and assigning. :D
> 
> Do we want to do this concurrently with bug 18337?
> 

Yes, we do.
Comment 4 Andrew Garrett 2009-04-21 02:58:47 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Do we want to do this concurrently with bug 18337?
> > 
> Yes, we do.

Actually I was asking Brion :)
Comment 5 Chenzw 2009-05-04 09:44:53 UTC
Please refine the configuration. Tor-blocked users can't edit any page at all (which includes their user talk page), so it is almost impossible to get yourself unblocked (other than through off-wiki methods) if you are within range of an exit node.
Comment 6 Brion Vibber 2009-05-08 19:02:55 UTC
Ping Andrew -- what's the get-yourself-unblocked workflow look like? Do we need some on-wiki editing request or have we got someplace else we can clearly direct people to where their unblock request will get handled?
Comment 7 Andrew Garrett 2009-05-31 22:26:44 UTC
We can send people to unblock-en-l (a mailing listz). That seems like the most sensible thing to do for the moment.
Comment 8 Mike.lifeguard 2009-06-01 02:35:01 UTC
(In reply to comment #7)
> We can send people to unblock-en-l (a mailing listz). That seems like the most
> sensible thing to do for the moment.
> 

Even if unblock-en-l were properly functioning, how does that help the other >700 wikis?
Comment 9 Andrew Garrett 2009-07-03 14:22:13 UTC
Looking for suggestions to improve the "get yourself unblocked" workflow.

Does anybody have any thoughts?
Comment 10 Andrew Garrett 2009-07-16 17:04:36 UTC
(Batch change)

These are low-priority miniprojects that I can mop up at some point when I'm doing general code work as opposed to working on a specific projects.
Comment 11 Andrew Garrett 2009-08-14 12:37:57 UTC
[Batch change]

Removing Dave McCabe from CC, who I somehow managed to add to the CC list of 12 bugs assigned to me.
Comment 12 Mike.lifeguard 2010-04-26 07:25:40 UTC
(In reply to comment #9)
> Looking for suggestions to improve the "get yourself unblocked" workflow.
> 
> Does anybody have any thoughts?

Making a request on the user's talk page is fairly standard - that could be permitted for tor nodes. OTOH, the only problems we've had so far with TorBlock is when it doesn't block well enough, or doesn't block at all. I think we should go ahead and fix this problem already.
Comment 13 Sam Reed (reedy) 2011-07-08 01:20:33 UTC
Is there anything else to action here?

It doesn't seem to be a shell bug... More policy, that is, even if something actually needs doing

Help?
Comment 14 Sam Reed (reedy) 2011-10-20 05:00:29 UTC
Please reopen if there's anything else to still action here

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


Navigation
Links