Last modified: 2014-09-29 10:31:31 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 T56496, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54496 - Local Special:GlobalBlockStatus does not work at all
Local Special:GlobalBlockStatus does not work at all
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
GlobalBlocking (Other open bugs)
unspecified
All All
: High critical (vote)
: ---
Assigned To: Nobody - You can work on this!
: ipv6
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-24 09:37 UTC by Bartosz Dziewoński
Modified: 2014-09-29 10:31 UTC (History)
8 users (show)

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


Attachments

Description Bartosz Dziewoński 2013-09-24 09:37:52 UTC
When trying to locally unblock 2001:41D0:0:0:0:0:0:0/40 (globally blocked) at pl.wp (https://pl.wikipedia.org/wiki/Specjalna:Lokalny_status_globalnych_blokad) I get the following error:

Your change to the local status of a global block was unsuccessful, for the following reason: 
You made no change to the local status of this block. Return to the global block list.

I can confirm the block by unchecking the checkbox – this works, but when trying to unblock again I get the same message. The block itself is not being lifted, of course.

IPv6-related?
Comment 1 Chris Steipp 2013-10-18 23:10:54 UTC
I can confirm the listing is in the DB

mysql:wikiadmin@db1036 [plwiki]> select * from global_block_whitelist where gbw_address like '2001%';
+--------+--------------------------+--------+-------------+------------+----------------+
| gbw_id | gbw_address              | gbw_by | gbw_by_text | gbw_reason | gbw_expiry     |
+--------+--------------------------+--------+-------------+------------+----------------+
|  25682 | 2001:41D0:0:0:0:0:0:0/40 |  77940 | Masti       | Toolserver | 20140530153054 |
+--------+--------------------------+--------+-------------+------------+----------------+
1 row in set (0.00 sec)


But IP's are still being blocked from that range?
Comment 2 Andre Klapper 2013-11-04 16:35:46 UTC
(In reply to comment #1)
> But IP's are still being blocked from that range?

I wonder if that was a question to MatmaRex...
Comment 3 Chris Steipp 2013-11-04 16:59:20 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > But IP's are still being blocked from that range?
> 
> I wonder if that was a question to MatmaRex...

Sorry, yeah. MatmaRex, can you confirm that ipv6 addresses in that range were still being blocked?
Comment 4 Chris Steipp 2013-11-04 17:01:56 UTC
Oh, and again for MatmaRex, could you check that if the blocked users are coming from those addresses directly, or if it's an XFF block?
Comment 5 Bartosz Dziewoński 2013-11-04 18:45:33 UTC
(In reply to comment #3)
> Sorry, yeah. MatmaRex, can you confirm that ipv6 addresses in that range were
> still being blocked?

Editing from that IP range was still not possible after I tried to unblock it, yes.


(In reply to comment #4)
> Oh, and again for MatmaRex, could you check that if the blocked users are
> coming from those addresses directly, or if it's an XFF block?

No idea how I could check that. (I am not a checkuser nor a global sysop.)
Comment 6 Bartosz Dziewoński 2013-11-04 18:56:03 UTC
(The range includes the Wikimedia Poland Toolserver – tools.wikimedia.pl, which is where I was trying to edit from when I encountered this. Not sure if this answers your question.)
Comment 7 Chris Steipp 2013-11-05 02:59:06 UTC
I was trying to reproduce this on a dev instance, but I'm unable to do that. The whitelist seems to be working just fine for ipv6.

Is the affected user a bot, since this is on a tools server? Can you give any more details? A capture of the headers? Or of the actual error message, which would verify if this is the IP or an xff block?
Comment 8 Bartosz Dziewoński 2013-11-05 11:32:02 UTC
(In reply to comment #7)
> Is the affected user a bot, since this is on a tools server?

When I filed this bug, the block affected logged-in users as well; this was since changed to just anonymous, so this is not troublesome.

I just tried again:

* Visit https://pl.wikipedia.org/wiki/Specjalna:Lokalny_status_globalnych_blokad
* Input "2001:41D0:0:0:0:0:0:0/40", no reason, checkbox checked, and submit

I get the following red error:

  Your change to the local status of a global block was unsuccessful, for
  the following reason:

  You made no change to the local status of this block. Return to the global
  block list.

It is still not possible to anonymously edit pl.wp from tools.wikimedia.pl
(I tried via Lynx while being SSH-d there) – it's in English, even though the wiki language is Polish:

  Your IP address has been blocked on all wikis.

  The block was made by Matanya (meta.wikimedia.org). The reason given is
  abused web hosting. ovh.com.
    * Start of block: 10:32, 24 wrz 2013            // == 2013-09-24
    * Expiry of block: 20:40, 22 mar 2014           // == 2014-03-22

  Your current IP address is 2001:41d0:2:7530::2000. Please include all
  above details in any queries you make.


We could probably get you an account on the toolserver if you're interested in testing yourself :) (CC-ing Saper who is an admin there.)
Comment 9 Andre Klapper 2013-11-22 15:30:16 UTC
csteipp: Is the information in comment 8 sufficient, or do you need more?
Comment 10 Chris Steipp 2013-11-22 17:15:58 UTC
I think I'll need to actually play with it a bit, I'm not able to reproduce this locally.

Saper, is it possible to get an account there that I can bounce through to see what's happening?
Comment 11 Marcin Cieślak 2013-11-22 19:09:23 UTC
Chris, I just need your public SSH key.
Comment 12 Chris Steipp 2013-11-22 21:40:08 UTC
Hopefully we can trust that my bugzilla account is me:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDOjXk3AOCJUGvRwZcnFxCKHZqxkwpr53ZX4atkFzeB7uBnGoyyhYHstD5X56THqF4o3Mg5y7kK1YrdbFyKAenHPXh06AAIck5FecLVoc9HPyUbnicuC7kelQHgzox/41RzfmnFyAjoelOgXG/rFj6iFy3+WCbFL9RdGXcbUPK457u8IMgJS/Bvsze5x0KTVyU464aAHfkuWNepAaWinUgJAjJZ0aM8iJS2/dC3wfZMNHS2+k1oqKNhR0E+G87YcHtobyXZ6Qke0XR5fpP0ncUZCelYXtUNHrkqEk2h2NS93eUuku5vgSiio6UCoRgBDPKwnf1/jnxKuCe0RzFaaDAd csteipp@linux-hv06.site
Comment 13 Marcin Cieślak 2013-11-22 22:04:56 UTC
We're interested in a person posing as csteipp online, not some real Chris :)
Comment 14 Chris Steipp 2013-11-22 23:15:43 UTC
Ok, so the root of the issue is that the block whitelist is linked to a non-existent block. The whitelisting is mostly based on block id numbers.

The whitelist prevents global block 25682 from applying, which doesn't exist. The block by Matanya was gb_id 30986.

So deleting and re-issuing the whitelist should work. I'm guessing the global block was issued, the whitelist was created, and then someone re created the global block, so it got a new id number.

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


Navigation
Links