Last modified: 2013-09-09 23:58:21 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 T54846, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52846 - HTTPS only Wikimedia problem for Iran Language related Wikipedias
HTTPS only Wikimedia problem for Iran Language related Wikipedias
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
SSL related (Other open bugs)
wmf-deployment
All All
: High normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
https1308
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-14 14:02 UTC by pouyan
Modified: 2013-09-09 23:58 UTC (History)
10 users (show)

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


Attachments

Description pouyan 2013-08-14 14:02:26 UTC
As was declared here:
https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/
and also said in Wikimania, wikimedia Websites are going to be HTTPS by default from 21 Aug.

Wikimedia Websites are not accessible in Iran through HTTPS and Ryan Lane told me that there would be an exception for fa* websites which are mostly edited and used in Iran.

After discussion with community, there were also another languages that are mostly used in Iran and wanted the same exception, I hereby enlist them here:

fa*
cbk*
mzn*
glk*
ku*
Comment 1 Calak 2013-08-14 14:51:04 UTC
Hello. I am sysop of ckb.wiki and I confirm Pouyan statements. We can not access to wikimedia projects via HTTPS. All sysops of ckb.wiki are from Iran and this is very bad. Now what are we suppose to do?
(Correction: Pouyan's purpose was "ckb" not "cbk" wikipedia)
Comment 2 pouyan 2013-08-14 14:53:24 UTC
(In reply to comment #1)
> Hello. I am sysop of ckb.wiki and I confirm Pouyan statements. We can not
> access to wikimedia projects via HTTPS. All sysops of ckb.wiki are from Iran
> and this is very bad. Now what are we suppose to do?
> (Correction: Pouyan's purpose was "ckb" not "cbk" wikipedia)

sorry for the typo (not enough sleep after long distance travel :D).
Comment 3 Andre Klapper 2013-08-14 15:15:32 UTC
Some other countries have similar problems and Wikimedia Foundation's Engineering Team is well aware of these problems. Very likely a number of Wikimedia sites (like Wikipedia) will be excluded from HTTPS login by default.

We will keep you updated, please have a little bit of patience while sorting out plans here. Thanks! :)
Comment 4 Greg Grossmeier 2013-08-20 15:51:06 UTC
Thanks for the added list, we'll confirm on the https://meta.wikimedia.org/wiki/HTTPS#List_of_excluded_language_wikis page before launch.
Comment 5 Calak 2013-08-20 20:10:00 UTC
Now all WM projects are out of access except Meta, Commons, Incubator, Bugzilla, MediaWiki and Wikidata projects.
Comment 6 Brion Vibber 2013-08-20 20:11:12 UTC
There really should be no excluded languages; exposing our contributors to MITM attacks and government spying is a disservice.
Comment 7 Andre Klapper 2013-08-20 20:23:03 UTC
(In reply to comment #5 by Calak)
> Now all WM projects are out of access except Meta, Commons, Incubator,
> Bugzilla, MediaWiki and Wikidata projects.

Uh? The SecureLogin deployment handled in this bug report is scheduled to take place in 22 hours, see https://wikitech.wikimedia.org/wiki/Deployments#Week_of_August_19th . If there are issues *now* for you then they are unrelated and a different problem. Please elaborate.
Comment 8 Calak 2013-08-20 20:30:10 UTC
(In reply to comment #7)
>If there are issues *now* for you then they are unrelated and a different problem.
> Please elaborate.

I don't know what is the problem but now I can not open any page on all Wikimedia projects; I only reported it.
Comment 9 Stefan2 2013-08-20 20:42:26 UTC
(In reply to comment #6)
> There really should be no excluded languages; exposing our contributors to
> MITM attacks and government spying is a disservice.

I agree that HTTP is a problem, but isn't it worse if several projects lose most of their contributors?
Comment 10 Calak 2013-08-20 21:02:15 UTC
(In reply to comment #6)
> There really should be no excluded languages; exposing our contributors to
> MITM attacks and government spying is a disservice.
What does "MITM attacks and government spying" mean when we can not contribute?
Comment 11 Greg Grossmeier 2013-08-20 21:25:46 UTC
Updated list of initially excluded language wikis at:
https://meta.wikimedia.org/wiki/HTTPS#List_of_excluded_language_wikis
Comment 12 Stefan2 2013-08-20 21:38:52 UTC
(In reply to comment #11)
> Updated list of initially excluded language wikis at:
> https://meta.wikimedia.org/wiki/HTTPS#List_of_excluded_language_wikis

What about other languages predominantly spoken in China? There is a list at [[m:Talk:HTTPS#Excluded language]] but I can't tell if the list is complete.
Comment 13 Stefan2 2013-08-20 23:32:31 UTC
See also [[m:Talk:HTTPS#List of Chinese Wikipedia]].
Comment 14 Calak 2013-08-21 07:50:09 UTC
Now all thing in order.
Comment 15 Andre Klapper 2013-08-21 08:51:11 UTC
(In reply to comment #12 by Stefan2)
> What about other languages predominantly spoken in China? There is a list at
> [[m:Talk:HTTPS#Excluded language]] but I can't tell if the list is complete.

Please ask on that talk page instead. I prefer to see such discussion and questions on the public talk page instead of a technical bugtracker.
Comment 16 Andre Klapper 2013-08-29 11:09:52 UTC
This change took place yesterday, and Iran has been excluded as per https://meta.wikimedia.org/wiki/HTTPS#Excluded_Countries .

CLosing as FIXED.
Comment 17 Andre Klapper 2013-08-29 11:17:35 UTC
(In reply to comment #0)
> After discussion with community, there were also another languages that are
> mostly used in Iran and wanted the same exception, I hereby enlist them here:

For your information: An IRC user stated that excluding Iran would not be needed.
I myself do not have enough information to judge (plus I am not involved in the SecureLogin deployment).

Only __if__ Farsi (or any other language community in Iran) would like to see a change to the current policy of excluding the wiki from SecureLogin, please discuss with the community on your wiki, and see https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes for more information. 
Thanks for your understanding.
Comment 18 reza1615 2013-08-29 12:31:17 UTC
Now in Iran https links  for wikipedia works
Comment 19 Calak 2013-08-29 13:54:41 UTC
Yes, it works.
Comment 20 Amir Ladsgroup 2013-08-29 17:27:01 UTC
It seems Iran has opened SSL of WMF but there is no guarantee that Iran won't block it again. I think we need to wait for a while and see what will happen
Comment 21 Ryan Lane 2013-08-29 17:59:26 UTC
I'd say if it's allowed, let's enable it now. If that changes, let us know and we'll immediately disable it.
Comment 22 Chris Steipp 2013-08-29 18:21:35 UTC
I agree. No sense in throwing cleartext passwords if ssl is allowed. Should we make than config change and deploy during the 4pm window?
Comment 23 Ryan Lane 2013-08-29 18:29:41 UTC
Works for me.
Comment 24 pouyan 2013-08-29 18:32:42 UTC
I agree with Ryan on this, when they open the gates why not use it. I hope it last long. when not we need to add the exception.
Comment 25 Amir Ladsgroup 2013-08-29 19:11:14 UTC
Problem is sometimes this opening and closing doesn't last more than three hours. So When I say please wait, I mean one day or two at the most
Comment 26 Calak 2013-08-29 21:41:15 UTC
Please don't enable it, today it works, but we can't guarantee tomorrow.
Beside it, I can't guarantee other areas of Iran.
Comment 27 Ryan Lane 2013-08-29 21:49:02 UTC
We'd only re-enable it for iran specifically. We'll wait a couple days to make sure it isn't a short fluke.
Comment 28 Calak 2013-08-29 21:58:58 UTC
I am not bullish. In Iran, anything is possible.
Comment 29 Amir Ladsgroup 2013-08-30 04:16:14 UTC
I checked two ISPs and they both blocked SSL now. :|

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


Navigation
Links