Last modified: 2013-10-06 22:57:23 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 T25310, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23310 - CentralAuth: global suppression does not suppress very well
CentralAuth: global suppression does not suppress very well
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
All All
: Low critical with 10 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: revdel SWMT
  Show dependency treegraph
Reported: 2010-04-24 17:45 UTC by MA
Modified: 2013-10-06 22:57 UTC (History)
13 users (show)

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


Description MA 2010-04-24 17:45:21 UTC
Dear developers. Sorry to bother again but when an account is suppressed via CentralAuth it should be [removed/hidden/grayed out] too from [[Special:ListUsers]] and, if previously blocked, from [[Special:IPBlockList]] too (like it happens when you manually block an account using the 'hideuser' option). This is not happenning now and leaks usernames with libellous or private information exposed to the public as well so we have to manually reblock the user again across the projects. Thank you.
Comment 1 MA 2010-09-29 09:29:36 UTC
Hello. Any updates on this? This is potentially causing privacy leaks as explained above. Scaling up to critical and CC'd Tim. Sorry for bothering but this needs urgent fixing. Thanks.
Comment 2 Victor Vasiliev 2011-03-22 08:36:02 UTC
I'm not sure about that. It should remove users from user list, and it did when I commited it.
Comment 3 MA 2011-03-24 17:39:02 UTC
(In reply to comment #2)
> I'm not sure about that. It should remove users from user list, and it did when
> I commited it.

Not when the user is previously blocked before we can globally suppress it. Regards.
Comment 4 Mark A. Hershberger 2011-05-23 19:45:50 UTC
(lowered priority as carry over from old bug triage)
Comment 5 Andre Klapper 2013-01-09 13:34:12 UTC
This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED.
In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help!

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