Last modified: 2012-09-18 14:09:05 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 T42122, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40122 - Remove OTRS from global block list
Remove OTRS from global block list
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-09 20:35 UTC by Tiptoety
Modified: 2012-09-18 14:09 UTC (History)
11 users (show)

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


Attachments

Description Tiptoety 2012-09-09 20:35:53 UTC
For some reason OTRS-wiki is affected by global blocks. Given that the wiki is private there is no need for global blocks. Please remove OTRS-wiki from the list of wiki's affected by such blocks.
Comment 1 Pine 2012-09-09 20:38:51 UTC
Maybe I'm missing something here, but why would you want globally blocked users to have access to OTRS-wiki?
Comment 2 Snowolf 2012-09-09 20:41:32 UTC
Some users who have access to the otrs wiki are obviously caught in global blocks.
Comment 3 Thehelpfulone 2012-09-09 20:41:48 UTC
Users aren't globally blocked Pine, they are globally locked.

Global blocking is done on IPs, please see https://meta.wikimedia.org/wiki/Global_blocks for more information.
Comment 4 Tiptoety 2012-09-09 20:42:37 UTC
(In reply to comment #1)
> Maybe I'm missing something here, but why would you want globally blocked users
> to have access to OTRS-wiki?

Global *blocks*, not global locks. Global blocks affect IPs. We recently had an issue where a legit established OTRS user was attempting to edit the wiki, but was doing so through a globally blocked IP and therefore could not. While giving them IPBE solves the issue, there is no reason that we should even have the issue in the first place give everyone on OTRS-wiki is trusted.
Comment 5 Pine 2012-09-09 20:48:31 UTC
What concerns me is the thought that when true global blocks of usernames are implemented, then a user who is globally blocked would still have access to OTRS-wiki if this wiki gets an exception. I don't think we'd want a user who has been globally blocked to continue to have access to OTRS-wiki.
Comment 6 Betacommand 2012-09-09 20:50:34 UTC
No, lock != Block
Comment 7 Tiptoety 2012-09-09 20:50:50 UTC
Try reading the responses again before saying the same thing twice.
Comment 8 Pine 2012-09-09 20:52:53 UTC
I would think that IPBE would be the appropriate thing to do.
Comment 9 Betacommand 2012-09-09 20:56:38 UTC
/facepalm IPBE shouldnt be needed as global IP blocks shouldn't effect this wiki
Comment 10 Pine 2012-09-09 21:00:11 UTC
Now discussing this in IRC on #mediawiki
Comment 11 Pine 2012-09-09 21:05:41 UTC
I withdraw my objection *for now* since global blocks for users are still hypothetical and making someone IPBE exposes their IP.
Comment 12 jeremyb 2012-09-09 21:08:52 UTC
I'm thinking this should be changed for all fishbowls and privates. Looked at the list of all such current wikis and saw no obvious issues. The one caveat is that this would also (I think?) effect whether or not blocked IPs could trigger password reset emails.

I've sent a proposed change: I13b3be3aa77b58ef072
Comment 13 Dereckson 2012-09-10 08:10:18 UTC
[ Raising priority to high, as it's a trivial issue to fix and blocks the regular work from one legit user on this wiki. ]
Comment 14 jeremyb 2012-09-10 13:31:42 UTC
(In reply to comment #13)
> blocks the
> regular work from one legit user on this wiki.

I don't think so? As far as I know this has been addressed with IPBE for any currently affected users.
Comment 15 Antoine "hashar" Musso (WMF) 2012-09-18 14:09:05 UTC
Deployed live at Tue, 18 Sep 2012 14:08:38 +0000

Thanks for the patch!

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


Navigation
Links