- ooni-dev - lists.torproject.org

Reminder for weekly OONI IRC meeting: Monday 2017-01-23, 16:00 UTC in #ooni
by Vasilis 23 Jan '17

23 Jan '17

Hello, This is a reminder for today's weekly OONI IRC meeting. It will happen as usual on the #ooni IRC channel (irc.oftc.net) at 16:00 UTC. *Watch out if you live in an area affected by the daylight saving time!* Meeting times around the world: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170123T16 In case that you have no IRC client you can join via the web from: https://kiwiirc.com/client/irc.oftc.net/ooni Everybody is welcome to join us and bring their questions and feedback. Please use the meeting agenda pad if you want to propose any topics: https://pad.riseup.net/p/ooni-irc-pad You can always find previous meeting logs at: http://meetbot.debian.net/ooni/ ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

New OONI measurements is now online
by Arturo Filastò 13 Jan '17

13 Jan '17

Hello Oonitarians! We are happy to announce the release of the new OONI measurements interface. This will replace the old raw archive of OONI measurements living at https://measurements.ooni.torproject.org/. Amongst the new features: * Ability to filter report files using an API: https://measurements.ooni.torproject.org/api/ * Support for browing raw reports by country and date: https://measurements.ooni.torproject.org/files/by_country, https://measurements.ooni.torproject.org/files/by_date * Some basic statistics on number of OONI measurements collected by month All old links to the reports are mapped to the new URL scheme, so there is no need to update links to raw reports (they are mapped in the sense that when accessed they return a 302 redirect to the new location). The files are now hosted on amazon s3 for faster download. If you have any questions or comments regarding the new measurements interface feel free to reply to this email! - The OONI team

2 1

tcp_connect tests sanitizing wisctorbridge02 bridge's address
by David Fifield 15 Dec '16

15 Dec '16

I mentioned this in #ooni IRC and Arturo explained what was going on. I'm making a post so I have something to link to in code comments. The tcp_connect nettest is now reporting reachability of Tor Browser default bridges and directory authorities. One of these bridges, host:128.105.214.161 port:8080 nickname:wisctorbridge02 protocol:fte is being sanitized in published reports (its address is removed and replaced with its hashed fingerprint). For example, see https://s3.amazonaws.com/ooni-public/sanitised/2016-12-14/20161213T003954Z-… There is only one line that starts with {"test_keys":{"bridge_hashed_fingerprint":... For all the other targets, the "input" key looks something like "fte 128.105.214.161:8080", but for this one it is the bridge's hashed fingerprint "626ec5e8b39dbc1d1b853529cdc80d21bf4c20e1" (which is the correct hashed fingerprint of the wisctorbridge02 bridge). Arturo says this is happening as an effect of the data pipeline sanitization. For some reason, this one bridge is in the list of bridges to be sanitized. As a workaround, I'm looking for this hashed fingerprint and mapping it back to the bridge's address and port in code.

1 0

A first look at tor_bridge_reachability
by David Fifield 15 Dec '16

15 Dec '16

Since https://github.com/TheTorProject/ooni-probe/issues/652 was merged, there have been about five days of tcp_connect tests for Tor bridges and directory authorities. I've posted some preliminary code and analysis here: https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… Interesting results so far: * Probes from 21 countries have contributed: BR, CZ, FI, GB, GR, ID, IN, IS, IT, KR, MM, MX, NL, NO, PK, TH, TR, TW, UG, US, VN. * The probes in ID and TH are reporting spurious reachability from destinations on port 80 (the destinations are down but the probes report connection success). * The probes in KR and MX are blocking some of the directory authorities. Here is a big illustration, with one page per probe destination. Blue dots are successful connection, gray dots are timeouts, and other colors indicate other connection errors. The pages are sorted alphabetically by nickname, so at the top you will see the bridge Azadi. Azadi has been down for a few days, so its recent dots are gray. https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… These pages show spurious reachability from ID and TH to Azadi:80 (obfs4) and fdctorbridge:80 (fte). These two bridges are both down: Azadi:80 is having a temporary outage and fdctorbridge:80 was decommissioned a long time ago. But two probe sites report them as reachable. https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… The next listed pages show potential blocking of certain directory authorities from KR and MX. Blocked only in MX: dannenberg:80 (dir_port) dannenberg:443 (or_port) gabelmoo:80 (dir_port) gabelmoo:443 (or_port) maatuska:80 (dir_port) maatuska:443 (or_port) Blocked in KR and MX: dizum:80 (dir_port) dizum:443 (or_port) moria1:9101 (dir_port) moria1:9131 (or_port) tor26:80 (dir_port) tor26:443 (or_port) Additionally, moria1:9101 and moria1:9131 are blocked for the probe identified as "ooni-ZZ-AS0". https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016… https://people.torproject.org/~dcf/graphs/ooni_tor_bridge_reachability/2016…

1 0

Reminder for weekly OONI IRC meeting: Monday 2016-11-21, 16:00 UTC in #ooni
by Vasilis 21 Nov '16

21 Nov '16

Hello everyone, This is a reminder for today's weekly OONI IRC meeting. It will happen as usual on the #ooni IRC channel (irc.oftc.net) at 16:00 UTC. *Watch out if you live in an area affected by the daylight saving time!* Meeting times around the world: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20161121T16 In case that you have no IRC client you can join via the web from: https://kiwiirc.com/client/irc.oftc.net/ooni Everybody is welcome to join us and bring their questions and feedback. Please use the meeting agenda pad if you want to propose any topics: https://pad.riseup.net/p/ooni-irc-pad You can always find previous meeting logs at: http://meetbot.debian.net/ooni/ ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

come and make a presentation
by dodonald＠i2pmail.org 21 Nov '16

21 Nov '16

Hello, I am here for the first time. I might make code to the Onii project. Before I would like to make a tour of Onii. Can you make a global and technical presentation of Onii? Present yourself. Best regards.

1 0

Egypt Blocking with Tor 0.2.8
by teor 01 Nov '16

01 Nov '16

Hi, I was reading about blocking in Egypt: https://ooni.torproject.org/post/egypt-network-interference/ And noticed that you were still using Tor 0.2.7: https://explorer.ooni.torproject.org/measurement/20161026T162218Z_AS36935_k… which Egypt blocks by blocking connections to the directory authorities. You say: "In our testing we found 7 out of 9 directory authority consensus file requests to be blocked:" Tor Browser uses Tor 0.2.8, which: * bootstraps using Fallback Directory mirrors as well as Authorities https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors * tries 5 fallbacks and 2 authorities before giving up https://trac.torproject.org/projects/tor/ticket/4483 * only bootstraps over the ORPort https://trac.torproject.org/projects/tor/ticket/18483 I think these changes make Tor harder to block, except perhaps for the ORPort bootstrap change, which means tor can be blocked using only the SSL handshake. (But it secures the HTTP headers from interference.) Can you repeat the Egypt tests with Tor 0.2.8? We've heard from users in Mexico that it evades some of their ISP blocks. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------

1 0

Reminder for weekly OONI IRC meeting: Monday 2016-10-31, 16:00 UTC in #ooni
by Vasilis 31 Oct '16

31 Oct '16

Hello everyone, This is a reminder for today's weekly OONI IRC meeting. It will happen as usual on the #ooni IRC channel (irc.oftc.net) at 16:00 UTC. *Watch out if you live in an area affected by the daylight saving time!* Meeting times around the world: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20161031T16 In case that you have no IRC client you can join via the web from: https://kiwiirc.com/client/irc.oftc.net/ooni Everybody is welcome to join us and bring their questions and feedback. Please use the meeting agenda pad if you want to propose any topics: https://pad.riseup.net/p/ooni-irc-pad You can always find previous meeting logs at: http://meetbot.debian.net/ooni/ ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

Bugs in Lepidopter install guide
by David Fifield 30 Oct '16

30 Oct '16

I followed the instructions at https://ooni.torproject.org/install/lepidopter and found a few errors. It tells you how to gpg-verify the image, but not how to download the .asc signature itself. The xz command has a .zip filename, not .xz: xz --decompress --verbose --no-sparse lepidopter-alpha-armel.img.zip It says the login credentials are lepidopter/lepidopter, but doesn't say what to do with them. I guess there should be a hint at the bottom that the next thing to do is go to http://lepidopter.local/ The README.md file at https://github.com/TheTorProject/lepidopter also has a little bug, an extra "of=" in the bmaptool command: bmaptool copy --nobmap lepidopter-alpha-armel.img.xz of=/dev/diskX After booting, my Raspberry Pi doesn't have a web interface (only port 22 is open).

2 5

ooniprobe failed on fresh lepidopter
by David Fifield 28 Oct '16

28 Oct '16

I installed lepidopter on a Raspberry Pi yesterday. It looks like it crashed during its first round of ooniprobe this morning. Would you like me to send you logs or something, to help debug it? /var/log/ooni/cronjobs.log contains 2 lines: /opt/ooni/run-ooniprobe.sh: line 13: 1434 Killed ooniprobe --annotations=platform:lepidopter --configfile=${OONI_CONFIG} --testdeck=${OONI_DECK} 27-10-16 06:29 error in "/opt/ooni/run-ooniprobe.sh" at line 12 /var/log/ooni/ooniprobe.log contains 1124129 lines. The last 10 are: 2016-10-27 14:37:39+0000 [-] Testing resolver: 65.77.164.5 2016-10-27 14:37:40+0000 [-] test resolver: 64.13.48.12 2016-10-27 14:37:40+0000 [-] experiment answers: ['81.171.123.200'] 2016-10-27 14:37:40+0000 [-] control answers: ['81.171.123.200'] 2016-10-27 14:37:40+0000 [-] tampering: false 2016-10-27 14:37:40+0000 [-] Testing resolver: 65.77.164.5 2016-10-27 14:37:40+0000 [-] [!] Got no response, perhaps the DNS resolver is down? 2016-10-27 14:37:40+0000 [-] Testing resolver: 93.188.161.190 2016-10-27 14:37:42+0000 [-] [!] Got no response, perhaps the DNS resolver is down? 2016-10-27 14:38:23+0000 [-] Testing resolver: 209.51.182.1 It looks like it managed to upload 3 reports before crashing: # grep 'Report ID:' /var/log/ooni/ooniprobe.log 2016-10-27 06:31:12+0000 [-] Report ID: 20161027T062733Z_AS25_5uN7bmBVwP1xmYbFlH1M1jgh8GZ6Vkl4Ezv03DfSohA27CDkjZ 2016-10-27 06:31:15+0000 [-] Report ID: 20161027T062741Z_AS25_pCY6HirAKR4TfFwLxrile74GETTZnBpZPLxd22McdrQqaatYXu 2016-10-27 08:32:41+0000 [-] Report ID: 20161027T062744Z_AS25_Yixcbst0TUWg7cQSIzDF6ufF9c2v6C6AoVoAL1t4Yab40fxXw5 I think these are the reports: https://measurements.ooni.torproject.org/2016-10-27/20161026T144325Z-US-AS2… https://measurements.ooni.torproject.org/2016-10-27/20161026T144335Z-US-AS2… https://measurements.ooni.torproject.org/2016-10-27/20161026T144338Z-US-AS2…

2 1