Hello Oonitarians,
Today, in collaboration with ASL19, ARTICLE 19 and Small Media, the OONI
team released a new research report: *Internet Censorship in Iran:
Network Measurement Findings from 2014-2017.*
You can read the report here:
https://ooni.torproject.org/post/iran-internet-censorship/
We also published a summary of the report on the Tor blog:
https://blog.torproject.org/internet-censorship-iran-findings-2014-2017https://twitter.com/OpenObservatory/status/913454524450447365
This study involves the analysis of thousands of network measurements
collected from 60 networks across Iran over the last 3 years.
OONI data confirms the blocking of 886 domains (and 1,019 URLs overall),
most of which include news outlets and human rights sites. The breadth
and scale of internet censorship in Iran is pervasive, since we found a
wide range of different types of sites to be blocked, with the blocking
extending beyond a simple definition of legality.
Blocked domains include search engines (such as google.com and
duckduck.go), online social networks (e.g. facebook.com, twitter.com,
plus.google.com), media sharing platforms (e.g. instagram, flickr.com,
youtube.com), blogging platforms (e.g. wordpress.com, blogger.com), and
communication tool sites (such as viber.com and paltalk.com). We also
found Facebook Messenger to be blocked by means of DNS tampering.
But**blocked domains also include opposition sites, pro-democracy sites,
and even the sites of digital rights groups in our community, such as:
EFF, CDT, Freedom House, ASL19, ARTICLE 19, Global Voices, The Citizen
Lab, and Reporters Without Borders.
Iranian ISPs appear to have shifted their practices from applying "smart
filters" (only censoring specific webpages) to "blanket censorship"
(censoring entire sites). Previously, they used to limit their
censorship to specific webpages hosted on HTTP. But over the last years,
as more sites have adopted HTTPS, we found that most ISPs blocked access
to both the HTTP and HTTPS versions of sites (since it's not possible to
target specific webpages when a site is hosted on HTTPS).
What's interesting is that we found internet censorship in Iran to be
non-deterministic.**By this we mean that we found ISPs to be flipping
between blocking and unblocking sites over time, possibly in an attempt
to create uncertainty or to make the censorship more subtle.
Internet censorship in Iran is sophisticated because we found ISPs to be
serving blockpages by means of DNS injection and through the use of HTTP
transparent proxies. But another reason why it is sophisticated is
because it is reinforced through the blocking of multiple censorship
circumvention tools. We even found the Tor network to be blocked most of
the time across most networks, but on a positive note, Tor bridges were
partially accessible.
Iranian ISPs also appear to be taking extra steps to reinforce internet
censorship and limit circumvention. We found various online translators
to be blocked. Pasting a URL into an online translator will provide
access to the site's content, even if that site is blocked. Online
translators can therefore provide a form of censorship circumvention,
likely explaining why we found them to be blocked.
Political relations appear to influence how information controls are
implemented in Iran. This is strongly suggested by the fact that we
found multiple Israeli and U.S. domains to be blocked. Israeli domains
even appear to be blocked almost indiscriminately. US export laws and
regulations, on the other hand, restrict the use of services in Iran,
which is why we found Norton, Virus Total, and GraphicRiver to be
inaccessible in the country.
Internet censorship in Iran also appears to serve as a tool for the
reinforcement of geopolitical dynamics of power. This is strongly
suggested by the fact that we found multiple Kurdish sites to be blocked.
Much more can be said about this study....but this email is already
quite long. :)
We encourage you to explore the data we published!
Thanks for reading.
~ The OONI team.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E
Hello Oonitarians,
The OONI team is super excited to announce.... OONI Run!
OONI Run is a new OONI Probe mobile app feature linked to this site:
https://run.ooni.io/
Through this site, you can:
* Engage your friends (and the world) with censorship measurement tests!
* Monitor the blocking of your site (and other sites you care about)
around the world!
Heard of censorship events but would like to have data to verify them?
Suspecting that censorship may occur leading up to or during political
events?
*Our solution to this is OONI Run.*
We are excited about OONI Run because it can help build a *global
community that monitors and responds to censorship events around the world.*
Add sites to OONI Run, generate a link, and share it with your friends
and with the world! If they have the OONI Probe mobile app already
installed, it will automatically start running the tests (and testing
the sites) of your choice! If they don't have OONI Probe installed, in
will encourage them to first install the app (to then start running the
tests).
Has your site been censored by governments around the world (or do you
suspect that that may happen)? Through OONI Run (https://run.ooni.io/)
you can get OONI Probe widget code so that the global OONI Probe
community can test your site!
Learn more about OONI Run through our blog post:
https://ooni.torproject.org/post/ooni-run/https://blog.torproject.org/ooni-run-lets-fight-internet-censorship-togetherhttps://twitter.com/OpenObservatory/status/913063206855331845
Together, we can coordinate to fight internet censorship around the world.
Happy testing!
~ The OONI team.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E
Hello Oonitarians,
I am sending this email to share OONI data providing evidence of recent
censorship events in Spain and China.
*# Spain*
As of yesterday, OONI Probe users in Spain started testing the blocking
of sites associated to the upcoming Catalan Independence Referendum.
The sites that were added for testing can be found here:
https://github.com/citizenlab/test-lists/pull/222/files
If you know of other sites that should be added to this testing list,
please create a pull request or send them to me via email.
As of today, we have started collecting network measurements which
provide *evidence of the DNS blocking of sites related to the Catalan
Referendum*.
Below are some examples:
https://explorer.ooni.torproject.org/measurement/20170925T094539Z_AS12479_Y…https://explorer.ooni.torproject.org/measurement/20170925T094539Z_AS12479_Y…
To find more examples, please filter the measurements through the
following page: https://explorer.ooni.torproject.org/country/ES
You can filter the measurements through the following steps:
1. Click "Filter Results" in the Spanish OONI Explorer page:
https://explorer.ooni.torproject.org/country/ES
2. Add a domain in the "Test Input" section that already exists in the
Spanish test list:
https://github.com/citizenlab/test-lists/blob/master/lists/es.csv (if
it's not included in this list, then that URL hasn't been tested)
3. Click "Apply Filter".
This will now present you with all the measurements pertaining to the
domain that you selected. By clicking on each of those measurements, you
will be able to find evidence of the blocking at the bottom of each
"measurement page", by clicking on "object" (thus opening up the
technical details).
*# China*
We *confirm that the blocking of WhatsApp in the AS9808 network in China
started on 23rd September 2017.
*Network measurements collected from that network over the last days show:
WhatsApp blocked on 25th September 2017:
https://explorer.ooni.torproject.org/measurement/20170925T150818Z_AS9808_Ub…
WhatsApp blocked on 24th September 2017:
https://explorer.ooni.torproject.org/measurement/20170924T032827Z_AS9808_VE…
WhatsApp blocked on 23rd September 2017:
https://explorer.ooni.torproject.org/measurement/20170923T190041Z_AS9808_KV…
In contrast, WhatsApp was found to be accessible in that network on 22nd
September 2017 (and during all the previous dates):
https://explorer.ooni.torproject.org/measurement/20170922T161201Z_AS9808_Vv…
This strongly suggests that this ISP started blocking WhatsApp on 23rd
September 2017.
It's worth highlighting that, as of yesterday, we see this ISP
increasing the censorship of WhatsApp. During the previous dates (23rd &
24th September), they were only blocking TCP connections to WhatsApp's
endpoints.
But as of yesterday (25th September), they are *ALSO blocking access to
WhatsApp's registration service* -- therefore enhancing the censorship
of WhatsApp.
It's also worth noting that these measurements have only been collected
from one ISP (AS9808). Therefore, it remains unclear to us whether other
ISPs in China are blocking access to WhatsApp as well, or whether the
block is being implemented on a nation-wide level.
The measurements that we collect depend on the OONI Probe users in
China, and where they choose to run tests.
You can filter the WhatsApp measurements collected from China through
the following steps:
1. Access the China OONI Explorer page:
https://explorer.ooni.torproject.org/country/CN
2. Click "Filter Results".
3. Select "WhatsApp" in the drop-down menu of "Test Name".
4. Click "Apply Filter".
You will now be presented will all the OONI network measurements showing
the testing of WhatsApp in China. By clicking on each individual
measurement, you will be able to find more information by clicking
"object" (uncovering technical details).
We encourage you to use this data as part of policy and advocacy
efforts, as well as for recommending censorship circumvention advice.
All the best,
Maria.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E
Hi all,
The Spanish government is blocking websites that contain information about the referendum that will happen in Catalonia next 1st
October (along with other repressive measures) and is suing people that keeps publishing web mirrors.
Note that the .cat domains seem to be seized (last week Police raided the offices of the .cat domain registry, seized some
computers and arrested their head IT) while other TLDs are just DNS hijacked by the Spanish Internet providers.
I've made a pull request to include some of these urls in the list of domains checked by OONI.
You can read more about it in the following links:
- https://github.com/citizenlab/test-lists/issues/221
- https://www.eff.org/deeplinks/2017/09/cat-domain-casualty-catalonian-indepe…
- https://medium.com/@josepot/is-sensitive-voter-data-being-exposed-by-the-ca…
Thanks for your work!
Pablo
Hello,
Today the Open Observatory of Network Interference (OONI) project
published a new report, titled: "*Measuring Internet Censorship in
Cuba's ParkNets*"
You can read the report here:
https://ooni.torproject.org/post/cuba-internet-censorship-2017/https://twitter.com/OpenObservatory/status/902229490495053824
Last May we traveled to Cuba and performed a variety of network
measurement tests across eight vantage points in Havana, Santa Clara,
and Santiago de Cuba, with the aim of measuring internet censorship.
As part of our study, we were able to confirm the *blocking of 41
websites*. Many of these sites include news outlets and blogs, as well
as pro-democracy and human rights sites. Many of the blocked sites,
directly or indirectly, express criticism towards the Cuban government.
Interestingly enough though, various other international sites which
also express criticism were found to be accessible.
Web proxies, like Anonymouse, were amongst those found to be blocked,
potentially limiting Cubans' ability to circumvent censorship. The Tor
network though was found to be accessible across the country, likely
because Cuba has relatively few Tor users.
*Deep Packet Inspection (DPI) technology was found to be resetting
connections and serving (blank) block pages.* Through latency
measurements, we were able to confirm that the blocking server is most
likely located in Havana (and in any case, for sure in Cuba). Only the
HTTP version of sites was found to be blocked, potentially enabling
users to circumvent the censorship by merely accessing them over HTTPS.
Most blocked sites, however, do not support HTTPS.
*Skype was found to be blocked. *By examining packet traces, we were
able to determine that the DPI middlebox blocked Skype by means of RST
injection. Other popular communications tools, such as WhatsApp and
Facebook Messenger, were found to be accessible.
*Chinese vendor Huawei was also found to be supporting Cuba's internet
infrastructure.* The server header of blocked sites, for example,
pointed to Huawei equipent. It remains unclear though whether they are
actually implementing internet censorship in the country.
Lastly, we accidentally discovered that *Google is blocking Google App
Engine from Cuba (when trying to run NDT).*
Overall, internet censorship does not appear to be particularly
sophisticated in Cuba. The high cost of the internet and the limited
availability of public wifi hotspots across the country remain the main
barriers to accessing the internet. But as Cuba's internet landscape
evolves, so might techniques and practices around internet censorship.
Therefore, we think it's important to continue to measure networks with
ooniprobe in Cuba and elsewhere around the world.
Thanks for reading our latest report - happy to address any questions
you may have!
~ The OONI team.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E
Hi Oonitarians,
Two weeks ago we hosted the*first OONI Partner Gathering*! :)
The event was hosted at the University of Toronto on 10th & 11th July 2017.
The aim of this two-day event was to bring our international partners
together to share skills, knowledge, and research findings. We reflected
on our collaboration over the last year, and we brainstormed on future
goals and priorities to improve our collaboration on the study of
internet censorship.
Today we published a report which provides an overview of the event, its
sessions, partner challenges and needs, future goals and priorities, and
event outcomes.
*Read the report here:
https://ooni.torproject.org/post/ooni-partner-gathering-2017/*
You can also find the event's agenda and all of the session notes here:
https://github.com/OpenObservatory/gatherings/tree/master/partner-gathering…
All the best,
Maria.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E
Hello!
The OONI team warmly welcomes you to join us**for our *monthly
**community meeting tomorrow**on Tuesday, 25th July 2017, at 14:00 UTC.*
We'd love to hear your thoughts and suggestions on how to improve
research on internet censorship.
Please join us on *https://slack.openobservatory.org* and add topics
that you would like to discuss as part of the meeting in this pad:
https://pad.riseup.net/p/ooni-community-meeting
If you're not able to join us, please feel encouraged to join us on
slack any other day!
Looking forward to connecting with you soon!
All the best,
~ The OONI team.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E
Thank you so much for publishing an article on installing ooni-probe it’s great stuff!
I am moving this thread over to ooni-dev as ooni-operators is actually meant for just important communications to operators of ooniprobe instances.
What Vasilis says is mostly correct, just a couple of minor corrections.
On July 1, 2017 at 3:14:24 PM, Vasilis (andz(a)torproject.org) wrote:
Hi Snehan,
Snehan Kekre:
> Hello excellent ooni people,
>
> I've written a blog post (https://snehankekre.github.io/anti-censorCHIP)
> about installing ooniprobe on a $9 computer called CHIP that runs a flavor
> of Debian.
Thank you for your good words and publishing a blog post about
installing ooniprobe on CHIP.
> I would appreciate any feedback, suggestions, or comments. I'll
> use them to make necessary changes to reflect accurate delivery. I've used
> some images and a lot of lines from the ooni website.
The 4th step in the install section of the blog post
(https://snehankekre.github.io/anti-censorCHIP#installing-ooniprobe-on-chip)
is not needed since Step 3 will get all the available dependencies.
However given that are a number of bugs
(https://github.com/TheTorProject/ooni-probe/issues?q=label%3Adebian+is%3Aop…)
in the Debian ooniprobe packages, I will suggest you instead to install
ooniprobe with pip and use the following install guide:
https://github.com/TheTorProject/ooni-probe#unix-systems-with-pip
As Vasilis points out you don’t actually need to install those extra dependencies via pip and are already part of the package installation, however you should NOT install ooniprobe via pip as it’s not the best way to install packages that will run as root.
The issues with the debian package are being actively worked on and I have some sample debian packages if you would like to try them out (https://github.com/hellais/ooniprobe-fpm#debian) and as soon as they are ready the canonical torproject debian package will be updated and all the outstading issues should be resolved.
In the Step 5. you don’t actually need to run oonideckgen, but you can directly find the location of your decks by running ooniprobe --info ,it should be in /var/lib/ooni/decks.
Usually ooniprobe is more useful when it performs regular (scheduled)
network measurements, I will suggest you to add the following steps to
the install guide:
1. Configure ooniprobe
(https://github.com/TheTorProject/ooni-probe#configuring-ooniprobe),
either via the GUI (setup wizard) or from the shell (ooniprobe initialize)
2. Add ooniprobe system service
(https://github.com/TheTorProject/ooni-probe#run-ooniprobe-as-a-service-syst…)
Yes this is indeed the recommended way of running it, in theory that should already be setup for you by using the debian package (but due to the debian package bugs vasilis pointed out is currently not happening).
> Is there a standard format to provide credit to ooni devs?
Everything published on the website is licensed under a
Creative Commons Attribution 3.0 License (CC BY 3.0).
~ Arturo
Hello!
The OONI team warmly welcomes you to join us**for our *monthly
**community meeting**on Wednesday, 28th June 2017, at 13:00 UTC.*
We'd love to hear your thoughts and suggestions on how to improve
research on internet censorship.
Please join us on *https://slack.openobservatory.org* and add topics
that you would like to discuss as part of the meeting in this pad:
https://pad.riseup.net/p/ooni-community-meeting
If you're not able to join us, please feel encouraged to join us on
slack any other day!
Looking forward to connecting with you soon!
All the best,
~ The OONI team.
--
Maria Xynou
Research and Partnerships Coordinator
Open Observatory of Network Interference (OONI)
https://ooni.torproject.org/
PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E