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

feat: mechanism compile and embed tor #1052

Merged
merged 51 commits into from
Jan 25, 2023
Merged

feat: mechanism compile and embed tor #1052

merged 51 commits into from
Jan 25, 2023

Conversation

bassosimone
Copy link
Contributor

@bassosimone bassosimone commented Jan 25, 2023

This diff introduces a mechanism to compile and embed tor. We plan on using this functionality on Android and iOS but we have not finished working on updating the build yet. In the meanwhile, here's an interim result. We're committing the code to run unit and integration testing of this new functionality on linux/amd64.

The reference issue is ooni/probe#2365.

The Go based build was sketched out in ooni/probe#2401.

@bassosimone bassosimone changed the title Issue/2365e feat: mechanism compile and embed tor Jan 25, 2023
@bassosimone bassosimone marked this pull request as ready for review January 25, 2023 22:36
@bassosimone bassosimone merged commit 95d23c7 into master Jan 25, 2023
@bassosimone bassosimone deleted the issue/2365e branch January 25, 2023 22:40
bassosimone added a commit that referenced this pull request Feb 3, 2023
I want to understand why we did not see this error previously. My
initial hypothesis is that the code at ooni/go-libtor behaved behaved
differently than #1052.

To understand whether this is the case, in this patch I have copied
the code at libtor/libtor.go and adapted it such that we can use
it inside the current tree.

Part of ooni/probe#2405.
bassosimone added a commit that referenced this pull request Feb 3, 2023
It turns out previously we were not using the control conn. Using
such a conn is not the default and needs to be configured.

However, the code at #1052
tries to be immutable and hence has a different algorithm than the
one inside go-libtor. In particular, this new code always creates
a control connection and then closes it. So, definitely the new
code I wrote is such that it triggers the tor issue.

On the other end, to hope to see the issue with go-libtor we must
enable using the control conn. Let us do that and see.

Part of ooni/probe#2405.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant