Fact-check my understanding of ooniprobe URL testing lists
I'm working on a project where we're using OONI http_requests reports to find servers that block Tor users. I'd like you to check my understanding of where the URL lists for testing come from. I wrote: A single OONI report typically tests many URLs. For the most part, reports use the Citizen Lab URL testing lists (https://github.com/citizenlab/test-lists) which contain about 1,200 "global" URLs, plus up to about about 900 additional country-specific URLs that are tested depending on the country in which ooniprobe is run. Users may run ooniprobe with their own custom URL lists; the results are uploaded to the global report pool. (There are several one-off reports in the data that test a single URL.) Is this true? Has it always been like this? How do ooniprobe users get updates when the list changes?
On Jul 30, 2015, at 04:20, David Fifield <david@bamsoftware.com> wrote:
I'm working on a project where we're using OONI http_requests reports to find servers that block Tor users. I'd like you to check my understanding of where the URL lists for testing come from. I wrote: A single OONI report typically tests many URLs. For the most part, reports use the Citizen Lab URL testing lists (https://github.com/citizenlab/test-lists) which contain about 1,200 "global" URLs, plus up to about about 900 additional country-specific URLs that are tested depending on the country in which ooniprobe is run. Users may run ooniprobe with their own custom URL lists; the results are uploaded to the global report pool. (There are several one-off reports in the data that test a single URL.) Is this true? Has it always been like this? How do ooniprobe users get updates when the list changes?
The above paragraph is correct. Users will get updates to the URL list when they re-run the ooniresources —update-inputs commands or when they update their version of ooniprobe. There are plans to have a more dynamic mechanism of provisioning probes with URLs and you can read more about that in this ticket: https://trac.torproject.org/projects/tor/ticket/12551 Before v1.2.0 (Wed, 1 Oct 2014) we would have the default deck just run the alexa top 1k for every country. This still does not preclude users from using their own custom URL lists or single URLs when testing. Hope this helps, ~ Arturo
On Thu, Jul 30, 2015 at 11:36:48AM +0200, Arturo Filastò wrote:
On Jul 30, 2015, at 04:20, David Fifield <david@bamsoftware.com> wrote:
I'm working on a project where we're using OONI http_requests reports to find servers that block Tor users. I'd like you to check my understanding of where the URL lists for testing come from. I wrote: A single OONI report typically tests many URLs. For the most part, reports use the Citizen Lab URL testing lists (https://github.com/citizenlab/test-lists) which contain about 1,200 "global" URLs, plus up to about about 900 additional country-specific URLs that are tested depending on the country in which ooniprobe is run. Users may run ooniprobe with their own custom URL lists; the results are uploaded to the global report pool. (There are several one-off reports in the data that test a single URL.) Is this true? Has it always been like this? How do ooniprobe users get updates when the list changes?
The above paragraph is correct.
Users will get updates to the URL list when they re-run the ooniresources —update-inputs commands or when they update their version of ooniprobe.
Thanks. Help me understand what is going on with oonideckgen. I installed ooniprobe 1.3.1-2 from the Debian repository. I ran sudo ooniresources --update-inputs sudo ooniresources --update-geoip oonideckgen -o my_decks/ It created the files 0.1.0-us-user.deck citizenlab-urls-global.txt dns-server-us.txt The file citizenlab-urls-global.txt has 1226 lines. However I notice it does not include the new meek URLs from https://github.com/citizenlab/test-lists/commit/d4c82c825. Why is that? Do I need to run oonideckgen in another way?
Hi David, On Fri, 31 Jul 2015 18:20:14 -0700 David Fifield <david@bamsoftware.com> wrote: <snip>
Thanks. Help me understand what is going on with oonideckgen. I installed ooniprobe 1.3.1-2 from the Debian repository. I ran sudo ooniresources --update-inputs sudo ooniresources --update-geoip oonideckgen -o my_decks/ It created the files 0.1.0-us-user.deck citizenlab-urls-global.txt dns-server-us.txt The file citizenlab-urls-global.txt has 1226 lines. However I notice it does not include the new meek URLs from https://github.com/citizenlab/test-lists/commit/d4c82c825. Why is that? Do I need to run oonideckgen in another way?
Currently oonideckgen is not creating tests for pluggable transports. https://gitweb.torproject.org/ooni-probe.git/tree/ooni/deckgen/cli.py#n95 There are plans to include PT tests to the 'standard set' of decks. BTW, there is also a test for meek: https://gitweb.torproject.org/ooni-probe.git/tree/ooni/nettests/blocking/mee...
participants (3)
-
Arturo Filastò -
balooni＠espiv.net -
David Fifield