This is really fantastic. 



Le 12 juin 2015 21:22:26 CET, Juliet Barbara <> a écrit :
>The Wikimedia Foundation is pleased to announce that we have begun the
>transition of the Wikimedia projects and sites to the secure HTTPS
>protocol. You may have seen our blog post from this morning; it has
>been posted to relevant Village Pumps (Technical).
>This post is available online here:
>Securing access to Wikimedia sites with HTTPS
>To be truly free, access to knowledge must be secure and uncensored. At
>Wikimedia Foundation, we believe that you should be able to use
>and the Wikimedia sites without sacrificing privacy or safety.
>Today, we’re happy to announce that we are in the process of
>HTTPS <> to encrypt all Wikimedia
>traffic. We will also use HTTP Strict Transport Security
><> (HSTS)
>protect against efforts to ‘break’ HTTPS and intercept traffic. With
>change, the nearly half a billion people who rely on Wikipedia and its
>sister projects every month will be able to share in the world’s
>more securely.
>The HTTPS protocol creates an encrypted connection between your
>and Wikimedia sites to ensure the security and integrity of data you
>transmit. Encryption makes it more difficult for governments and other
>third parties to monitor your traffic. It also makes it harder for
>Service Providers (ISPs) to censor access to specific Wikipedia
>and other information.
>HTTPS is not new to Wikimedia sites. Since 2011, we have been working
>establishing the infrastructure and technical requirements, and
>understanding the policy and community implications of HTTPS for all
>Wikimedia traffic, with the ultimate goal of making it available to all
>users. In fact, for the past four years
>Wikimedia users could access our sites with HTTPS manually, through
>Everywhere <>, and when directed to
>sites from major search engines. Additionally, all logged in users
>have been accessing via HTTPS since 2013.
>Over the last few years, increasing concerns about government
>prompted members of the Wikimedia community to push
>for more broad protection through HTTPS. We agreed, and made this
>transition a priority for our policy and engineering teams.
>We believe encryption makes the web stronger for everyone. In a world
>mass surveillance has become a serious threat to intellectual freedom,
>secure connections are essential for protecting users around the world.
>Without encryption, governments can more easily surveil sensitive
>information, creating a chilling effect, and deterring participation,
>or in
>extreme cases they can isolate or discipline citizens. Accounts may
>also be
>hijacked, pages may be censored, other security flaws could expose
>sensitive user information and communications. Because of these
>circumstances, we believe that the time for HTTPS for all Wikimedia
>is now. We encourage others to join us as we move forward with this
>The technical challenges of migrating to HTTPS
>HTTPS migration for one of the world’s most popular websites can be
>complicated. For us, this process began years ago and involved teams
>across the Wikimedia Foundation. Our engineering team has been driving
>transition, working hard to improve our sites’ HTTPS performance,
>our infrastructure to handle the transition, and ultimately manage the
>Our first steps involved improving our infrastructure and code base so
>could support HTTPS. We also significantly expanded and updated our
>hardware. Since we don’t employ third party content delivery systems,
>had to manage this process for our entire infrastructure stack
>HTTPS may also have performance implications for users, particularly
>many users accessing Wikimedia sites from countries or networks with
>technical infrastructure. We’ve been carefully calibrating our HTTPS
>configuration to minimize negative impacts related to latency, page
>times, and user experience. This was an iterative process that relied
>industry standards, a large amount of testing, and our own experience
>running the Wikimedia sites.
>Throughout this process, we have carefully considered how HTTPS affects
>of our users. People around the world access Wikimedia sites from a
>diversity of devices, with varying levels of connectivity and freedom
>information. Although we have optimized the experience as much as
>with this challenge in mind, this change could affect access for some
>Wikimedia traffic in certain parts of the world.
>In the last year leading up to this roll-out, we’ve ramped up our
>and optimization efforts to make sure our sites and infrastructure can
>support this migration. Our focus is now on completing the
>of HTTPS and HSTS for all Wikimedia sites. We look forward to sharing a
>more detailed account of this unique engineering accomplishment once
>through the full transition.
>Today, we are happy to start the final steps of this transition, and we
>expect completion within a couple of weeks.
>Yana Welinder
>Senior Legal Counsel, Wikimedia Foundation
>Victoria Baranetsky
><>, Legal
>Counsel, Wikimedia Foundation
>Brandon Black <>,
>Engineer, Wikimedia Foundation
>*Juliet Barbara*
>Senior Communications Manager I Wikimedia Foundation
>149 New Montgomery Street I San Francisco, CA 94105
> I +1 (512) 750-5677
>Please note: all replies sent to this mailing list will be immediately
>directed to Wikimedia-l, the public mailing list of the Wikimedia
>community. For more information about Wikimedia-l:
>WikimediaAnnounce-l mailing list
>Wikimedia-l mailing list, guidelines at:

Habib M'henni
Ingénieur civil et technologue à l'Iset de Nabeul
Membre fondateur de CLibre et Wikimedia TN User Group
Téléphone : +216 52232190
[K9.Andro ]
Wikimedia-l mailing list, guidelines at:

Reply via email to