-
Notifications
You must be signed in to change notification settings - Fork 142
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
experiment/tor in probe-engine #1657
Comments
I revisited this issue today as ooni/probe-cli#387 is landing. It turns out, as of today:
We didn't track very precisely the progress we made, but, still, it's important to say that, as of today, we are at 3/5 of the original follow-up points we wanted to cover to improve our tor testing support. |
it might be useful to look at how bine makes use of a embedded, static Tor binary: https://github.com/cretz/bine/blob/master/process/embedded/process.go |
@kalikaneko yeah, I agree, thanks! |
So, after ooni/probe-cli#718 has been merged, we have now addressed all the issues that were mentioned as todo items as part of this issue. As such, we can now close this issue. |
We have now finished all that was mentioned in this issue and transferred sub-issues to #1730. |
OONI users will be able to run the vanilla Tor test to determine whether Tor is blocked. This is about enabling them to do that here in probe-engine.
See measurement-kit/measurement-kit#86 for the original issue.
As of 2020-02-13, we have implemented the tor experiment to connect to a bunch of tor resources such as obfs4 bridges, as implemented, e.g., in ooni/probe-engine#226 and ooni/probe-engine#276. We can implement further improvements to this experiment, and some of them are listed below:
We will (hopfully) be disciplined enough to keep this issue up to date regarding everything that pertains to the experiment/tor implementation in the coming months.
The text was updated successfully, but these errors were encountered: