Page MenuHomePhabricator

Global IP block exemption does not override local blocks
Closed, DeclinedPublic

Event Timeline

saper raised the priority of this task from to Medium.
saper updated the task description. (Show Details)
saper subscribed.
Glaisher subscribed.

This is not specific to local rangeblocks but applies to single IP blocks as well. AFAIK, this is intentional and not a bug in the code. Technically, this is correct as the globalblock exemption right should only exempt from global blocks not local blocks as there is a right specifically for local ip block exemptions. Also from what I've seen, stewards have also been declining requests to add users to the global IPBE group for just overriding local blocks so this needs community consensus as well. If there is consensus to do so, it can simply be solved by adding ipblock-exempt right to the group.

Glaisher claimed this task.

Technically, this is correct as the globalblock exemption right should only exempt from global blocks not local blocks as there is a right specifically for local ip block exemptions.

Declining this per above as the right works as expected.

Agree with everything that @Glaisher said. By design global block and global IPBE are paired.

In an WMF context, stewards should not be overriding local blocks. So a steward is essentially only unblocking global blocks, and system blocks like Tor.

If that is to change at WMF then that should be a social discussion at Meta, not a technical discussion at Phabricator.

Thank you for confirming this is intended behaviour.

I think the problem is caused by en.wikipedia additionally blocking Tor IP address using the automated process, which duplicates Tor blocking done by the extension already.

I have appealed to the en.wiki block to resolve the particular en.wiki case and will take it to the meta, thanks!

saper renamed this task from Global IP block exemption should override local range blocks to Global IP block exemption does not override local blocks.Nov 16 2015, 1:09 PM