Hi David,
Apologies for not replying sooner more extensively.
Unfortunately the machines on which we had those probes running were shut down due to some unpaid bills and poor sysadmin management on my side. We talked a bit about this during this Tor Measurement meeting: http://meetbot.debian.net/tor-project/2015/tor-project.2015-07-15-14.00.log....
At the moment OONI does not have enough resources to dedicate time to making this a priority at the moment, but anybody that considers this to be a priority should absolutely hack on this! To be clear I am not saying that we don't want to do this, it's just that we want to do so many other things (run a hackathon at the Italian Parliament, implement exploratory tools to ALL the OONI data with the help from Brennan Novak, get more stable general purpose ooni-probe in many more countries with lepidopter, setup our big data cluster in Humboldt university, etc.) and have finite resources.
Getting them running is basically a matter of having time. If somebody wants to take this up I can send them the information I sent to Jens about setting them back again (logins, accounts, etc.), but I will need to be pinged otherwise it will slide to the bottom of my todo list.
ciao!
~ Arturo
On 21 Sep 2015, at 09:58, David Fifield david@bamsoftware.com wrote:
I would love to have some ongoing measurement of the default TB obfs4 bridges.
However, it seems that there are no bridge_reachability tests since May 2015 at http://api.ooni.nu/.
Are these test results being stored somewhere else, or are they not running? What would it take to get them running again, even on a small number of ooniprobe installations?
On Mon, Sep 21, 2015 at 12:25:46PM +0200, Arturo Filastò wrote:
Hi David,
Apologies for not replying sooner more extensively.
Unfortunately the machines on which we had those probes running were shut down due to some unpaid bills and poor sysadmin management on my side. We talked a bit about this during this Tor Measurement meeting: http://meetbot.debian.net/tor-project/2015/tor-project.2015-07-15-14.00.log....
At the moment OONI does not have enough resources to dedicate time to making this a priority at the moment, but anybody that considers this to be a priority should absolutely hack on this! To be clear I am not saying that we don't want to do this, it's just that we want to do so many other things (run a hackathon at the Italian Parliament, implement exploratory tools to ALL the OONI data with the help from Brennan Novak, get more stable general purpose ooni-probe in many more countries with lepidopter, setup our big data cluster in Humboldt university, etc.) and have finite resources.
What does it take for a volunteer to run the bridge_reachability tests? The default deck does not include them. Is there a document you can point me to so that I can try setting it up myself?
I can understand why limited resources would cause you to have to shut down probes. I thought, though, that there were at least some volunteer ooniprobes doing bridge reachability tests, and it turns out that there are not any.
P.S. I just tried this to run the bridge_reachability test myself. If I just make sure obfs4proxy and fteproxy are installed, it should work? How would someone make it part of the default system test deck?
~$ awk -F, '{print $1}' /var/lib/ooni/resources/citizenlab-test-lists/test-lists-master/lists/services/tor/bridges.csv | sed 1d > bridges.list ~$ ooniprobe -n blocking/bridge_reachability -f bridges.list
Connecting to obfs3 83.212.101.3:80 A09D536DD1752D542E1FBB3C9CE4449D51298239 with tor 0.2.6.10 Spawning tor process with DataDirectory /tmp/tmpPKjx7j Connecting to obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9 with tor 0.2.6.10 Spawning tor process with DataDirectory /tmp/tmpJrlHUq ... Connecting to flashproxy 0.0.1.0:1 with tor 0.2.6.10 [!] Unable to test bridge because we don't recognize the flashproxy transport ... Connecting to fte 192.240.101.106:80 B629B0B607C8AC9349B5646C24E9D242184F5B6E with tor 0.2.6.10 [!] Unable to test bridge because fteproxy is not installed ... Connecting to scramblesuit 188.226.213.208:54278 AA5A86C1490296EF4FACA946CC5A182FCD1C5B1E password=MD2VRP7WXAMSG7MKIGMHI4CB4BMSNO7T with tor 0.2.6.10 Spawning tor process with DataDirectory /tmp/tmprGvled ... Connecting to obfs4 178.209.52.110:443 67E72FF33D7D41BF11C569646A0A7B4B188340DF cert=Z+cv8z19Qb8RxWlkagp7SxiDQN++b7D2Tntowhf+j4D15/kLuj3EoSSGvuREGPc3h60Ofw iat-mode=0 with tor 0.2.6.10 [!] Unable to test bridge because obfs4proxy is not installed ... Connecting to meek 0.0.2.0:1 url=https://meek-reflect.appspot.com/ front=www.google.com with tor 0.2.6.10 [!] Unable to test bridge because we don't recognize the meek transport ... Successfully connected to obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9 ... Successfully connected to scramblesuit 83.212.101.3:443 A09D536DD1752D542E1FBB3C9CE4449D51298239 password=XTCXLG2JAMJKZW2POLBAOWOQETQSMASH ... Failed to connect to obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9 ... Failed to connect to obfs3 109.105.109.163:38980 1E05F577A0EC0213F971D81BF4D86A9E4E8229ED ... Failed to connect to obfs3 109.105.109.163:47779 4C331FA9B3D1D6D8FB0D8FBBF0C259C360D97E6A ... Failed to connect to scramblesuit 188.226.213.208:54278 AA5A86C1490296EF4FACA946CC5A182FCD1C5B1E password=MD2VRP7WXAMSG7MKIGMHI4CB4BMSNO7T ... Summary for bridge_reachability ------------------------------- Total successes: 3 Total failures: 23 Obfs3 successes: 2 Scramblesuit successes: 1 Obfs3 failures: 3 Meek failures: 3 Obfs4 failures: 3 Flashproxy failures: 5 Fte failures: 8 Scramblesuit failures: 1 Working bridges: obfs3 169.229.59.75:46328, obfs3 83.212.101.3:80, scramblesuit 83.212.101.3:443 Failing bridges: flashproxy 0.0.1.0:1 (at 0%), flashproxy 0.0.1.0:2 (at 0%), flashproxy 0.0.1.0:3 (at 0%), flashproxy 0.0.1.0:4 (at 0%), flashproxy 0.0.1.0:5 (at 0%), fte 192.240.101.106:80 (at 0%), fte 50.7.176.114:80 (at 0%), fte 131.252.210.150:8080 (at 0%), fte 128.105.214.161:8080 (at 0%), fte 128.105.214.162:8080 (at 0%), fte 128.105.214.163:8080 (at 0%), fte [2001:49f0:d002:1::2]:80 (at 0%), fte [2001:49f0:d00a:1::c]:80 (at 0%), obfs4 178.209.52.110:443 (at 0%), obfs4 83.212.101.3:41213 (at 0%), obfs4 104.131.108.182:56880 (at 0%), meek 0.0.2.0:1 (at 0%), meek 0.0.2.0:2 (at 0%), meek 0.0.2.0:3 (at 0%), obfs3 169.229.59.74:31493 (at 10%), obfs3 109.105.109.163:38980 (at 10%), obfs3 109.105.109.163:47779 (at 10%), scramblesuit 188.226.213.208:54278 (at 10%)
-
Arturo Filastò -
David Fifield