Last modified: 2014-11-16 19:23:29 UTC
Proxyunbannable is a userright granted to sysops by [[mw:Extension:AutoProxyBlock]]. But this extension is not used on WMF wikis, which instead use [[mw:Extension:TorBlock]], with torunblocked as equivalent. Torunblocked is not granted to sysop, so they cannot edit from tor. However, for some reason proxyunbannable appears in the listed rights of sysops, with the description "Bypass automatic blocks of proxies". This led to some confusion among users. Since it doesn't seem to have any use, it would be best to remove it.
I just checked wmf-config but I don't see anything about 'proxyunbannable' in there except for mlwikis and wikidata. I'm not sure but I think this is done by the TorBlock extension as all sysops on Wikimedia projects have 'proxyunbannable' by default but keeping this here for now.
The AutoProxyBlock extension seems to be an offshoot of the deprecated $wgBlockOpenProxies. Proxyunbannable was missed. *** This bug has been marked as a duplicate of bug 54597 ***
Not a duplicate; commented there.
Noted. [[mw:Manual:User_rights#List_of_permissions]] updated. $wgProxyList refers to mwblocker.log which does not exist in wmf-config, so this doesn't seem to be of any use. And $wgEnableDnsBlacklist is set to false by default but true on 'enwikinews', 'thwiki', 'thwiktionary', 'thwikiquote', 'thwikibooks' and 'thwikisource'. I'll fill the bugs.
I think I'll fill a bug asking to remove all proxy blocking from mediawiki, or move to an extension. This way, wikis can choose their preferred proxy blocking extension. And proxyunbannable can go (implying some extensions will have to declare it). The 'proxyunbannable' instances in wmf-config are just copy and paste from the list of sysop userrights, so it's no problem. But I've no idea why $wgEnableDnsBlacklist is set to true on the above 6 wikis and which DNS blacklist they use (if any). Is this necessary for those projects ?
