I do not really enjoy the way the mandatory-for-editors HTTPS was
introduced, mainly for time frame and communications (still) reasons,
although I’m globally really enthousiastic about a better security and
particularly the activation of HTTPS. Generally speaking I do _hope_ in
the future WMF will give more time and more discussion space to handle
History: (I concede I may lack some readings, but I think I have the big
After the PRISM scandal in June (2.5 months ago) everybody condemned that
program and the Internet security became a major concern for Internet
users. HTTPS is in important means to improve the security (although
concerns about the protocol and the way it is implemented appear) and
since it was a matter of time before it could be globally activated the
blog post published on August 1st announced HTTPS will be activated for
logged-in users 20 days after, with solutions about the blocked China
HTTPS to be found , after a discussion on wikitech-l .
Some Chinese editors made petitions  (starting on 08/08) and Iranian
users raised a similar problem  (on 14/08). In parallel these last two
weeks there were discussions on wikitech-l about some way to opt-out by
user and/or geographically. And in parallel the last two weeks there were
discussions on wikitech-l whether some opt-out mechanism should be
implemented with two opposed points of view:
1/ this security about the protection of the password must be for everyone
else it is unuseful (which is true in a perfect world), no matter if China
and other HTTPS-unlucky people cannot login (and hence must edit under IP
or not edit);
2/ although security is very important, not to allow HTTP logins in China
(and other HTTPS-unlucky people) will destroy etablished parts of the
community and should be avoided, so implementation of work-arounds is
And this last discussion had not to be on wikitech-l because it is
political, and was only a few raised elsewhere (where HTTPS is technical
and should be discussed on wikitech-l.)
Finally some work-arounds were implemented; first it was a list of wikis
where HTTP login will be allowed (this decision became public on Monday
) and yesterday (sic) it was announced a geolocalised solution .
Secondly there will be a preference for the users, although until
yesterday it was not clear for everybody how exactly it was implemented.
In parallel the central notice was set up two days ago with an
English-only page, pywikipediabot was announced to be ready some hours
ago. And in some hours there should be the deployment target.
I know the fact we now know we are spied is disturbing, but…
Why the hell HTTPS is so truly *urgent* we cannot spent more than three
weeks (at all) to think about the problem, investigate related problems
(including political and communitical here), think about solutions and
user interfaces/interactions, implement solutions, widely avertize the
problem and solutions, and peacefully deploy the patches?
I would have loved some RFC and some discussion elsewhere than on
wikitech-l with structured problems and solutions, and more time allowed
for discussing all that with the community -- because I guess it was
widely discussed internally in technical and operations teams, but the
community discovered these plans and had to report potential problems in a
time frame of 3 weeks.
More generally speaking, I would love the WMF share more their internal
plans long before rollout -- even if I concede writing and discussion is
more time-consuming than oral speak and introduce latencies -- and
probably in some digest and expanded forms (I know there are already both,
it’s probably to be improved and perhaps more targeted to avoid everyone’s
burnout). And perhaps slow the rhythm of the technical changes to have a
more stable environment (I understand this is personal and there are other
Le Wed, 21 Aug 2013 11:37:35 +0200, Pierre-Selim <pierre-se...@huard.info>
First of all, I'm sorry If my tone was not appropriate (keep in mind I'm
not a native speaker).
2013/8/21 Terry Chay <tc...@wikimedia.org>
On Aug 21, 2013, at 1:39 AM, Pierre-Selim <pierre-se...@huard.info>
> Just a question: Why imposing HTTPS ? Really, it will be damaging
The reason why is outlined in Ryan's blog post as well as his previous
post and the Wikipedia entry on https linked from that post.
The short answer is the current state is known to present a number of
privacy and security vulnerabilities further emphasized by the now-known
existence of software designed to deliberaty target these
in Wikipedia specifically.
I just think the user should be informed of this and should have the
(so the user can make an enlightened choice). And that is mostly my
All the explanation you have given are good, and the work of the WMF is
> Thank you for all the time you spent on this feature, however I'm not
> convinced at all.
Luckily, the standard for the Movement is consensus, not catering to
extremist view with 100% buy-in. The latter standard is impossible as
people would be affected either way. The technical component is
the decision and helps to hash out some of the details, but this is a
where parts of the Vision are being compromised today, and a different
(hopefully better) compromise is being reached through this rollout.
Off course, I was just giving my opinion, I'm one user and do not
more than that. We will see how it works out, and I would be happy to owe
you a drink if everything goes smooth.
Thank you for your answer and have a nice roll out.
> 2013/8/21 Ryan Lane <rl...@wikimedia.org>
>> On Wed, Aug 21, 2013 at 4:38 AM, Brion Vibber <bvib...@wikimedia.org>
>>> On Tue, Aug 20, 2013 at 1:33 PM, Nathan <nawr...@gmail.com> wrote:
>>>> Hi, context please?
>>> Continuation of this thread from wikitech-l:
>>> tl;dr summary:
>>> * ops plans to switch logins to HTTPS
>>> * switching all logins to HTTPS is known to break access for
>>> users in countries where Wikimedia's HTTPS servers are blocked by
>>> government censorship
>>> * there are some plans to mitigate this by excluding some languages
>>> the requirement
>>> * this is controversial for several reasons, one of which is that it
>>> break access for users in those countries on language projects that
>>> excepted (eg English Wikipedia in mainland China)
>> The last point isn't accurate. The original plan was to exempt
>> languages from the login redirection, and those projects would be
>> wikis. When someone logged-in there, they'd also be logged-in
>> else via central auth. The current plan is to disable the HTTPS
>> using geolocation for countries that have a > 5% error rate for HTTPS
>> This discussion is technical, so I'm going to move back to
>> - Ryan
>> Wikimedia-l mailing list
> Wikimedia-l mailing list
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
Wikimedia-l mailing list
Wikimedia-l mailing list