Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tcp_connect tests for Tor directory authorities and Tor Browser bridges #802

Closed
akwizgran opened this issue Oct 29, 2018 · 6 comments
Closed

Comments

Projects
No open projects
OONI-Verse
  
Icebox
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@akwizgran
Copy link

@akwizgran akwizgran commented Oct 29, 2018

It would be useful to have data about which networks block TCP connections to the Tor directory authorities and well-known bridges, such as those bundled with the Tor Browser.

The output from these tests would help the Briar project to maintain lists of countries where different methods of connecting to the Tor network (e.g. direct connection, vanilla bridges, obfs4 bridges) are likely to succeed. The Briar app uses these lists to choose a default connection method based on the user's location. The Briar devs are hoping to find volunteers to collect this data in censored countries and contribute it to OONI, and since our users are Android users it would be great if the Ooniprobe Android app supported these tests.

If I understand right, the tcp_connect test already exists in the version of Measurement Kit used by the Android app, and the data for these tests will be made available from the orchestrator (ooni/orchestra#51).

@hellais
Copy link
Member

@hellais hellais commented Nov 23, 2018

Thanks for reporting this!

I am migrating this to ooni/probe as it's not an android specific issue.

@hellais hellais transferred this issue from ooni/probe-android Nov 23, 2018
@hellais hellais changed the title Feature request: Add tcp_connect tests for Tor directory authorities and Tor Browser bridges Add tcp_connect tests for Tor directory authorities and Tor Browser bridges Nov 23, 2018
@hellais
Copy link
Member

@hellais hellais commented Nov 23, 2018

What would need to happen to make this become a reality is the following (these don't necessarily have to be done in this order):

  • The UX items in #804 are done
  • ooni/orchestra supports giving out bridge addresses: ooni/orchestra#51
  • either a new test or some adaptation of tcp_connect is done which speaks to ooni/orchestra to retrieve bridge addresses to test and runs the test
  • The rest of the items listed in #804 specific to new test development

@hellais
Copy link
Member

@hellais hellais commented Jan 16, 2020

I suspect this may be a duplicate of other existing issues. We are getting very close to being able to do this.

@bassosimone
Copy link
Member

@bassosimone bassosimone commented Jan 16, 2020

Correct, this is what the new tor experiment is enabling us to do: ooni/probe-engine#226

@bassosimone bassosimone self-assigned this Feb 17, 2020
@bassosimone
Copy link
Member

@bassosimone bassosimone commented Feb 17, 2020

@hellais I would like to close this issue, any objections?

@hellais
Copy link
Member

@hellais hellais commented Feb 17, 2020

This has been completed as part of: ooni/orchestra#82

@hellais hellais closed this Feb 17, 2020
@bassosimone bassosimone removed this from the Sprint 7 - Crown Jellyfish milestone Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment