Create Tor-Android Project

The tor-android repo contains a TorResourceInstaller. This is an !Android/Java library that Orbot uses. We need this.

The tor-android repo also contains the native Tor libraries. We don't want to use these. So the Tor-Android project will need to depend on our own versions of these native libraries.

!https://github.com/n8fr8/tor-android

added TorBrowserTeam202004 component::applications/tor browser owner::sisbell parent::28704 points::.5 priority::medium resolution::wontfix severity::normal status::closed tbb-mobile tbb-parity tbb-rbm type::defect labels

The projects that tor-android is dependent on are:

1. libevent (included patch)
2. openssl
3. tor
4. zstd -!https://github.com/facebook/zstd (not sure how the project is using this)
5. lzma (not sure how the project is using this)

The first 3 we already have tor-browser-build projects for.

!https://github.com/n8fr8/tor-android/tree/master/external

Replying to sisbell:

The projects that tor-android is dependent on are:

1. libevent (included patch)
2. openssl
3. tor
4. zstd -!https://github.com/facebook/zstd (not sure how the project is using this)
5. lzma (not sure how the project is using this)

We have the last two on our radar for desktop platforms, see #22341 (moved). But there has not been done any work to tackle that bug. As I said in that ticket starting with zstd sounds good. I am fine supporting lzma right from the beginning, too. (What about zlib support which we currently have on desktop?)

Moving tickets to Jan 2019.

Trac:
Keywords: TorBrowserTeam201812 deleted, TorBrowserTeam201901 added

tbb-parity items.

Trac:
Keywords: N/A deleted, tbb-parity added

Trac:
Points: N/A to .5

I highly recommend getting rid of all the asset unpacking code from Orbot. It is ancient and long unneeded, and indeed problematic. The libtor.so created by https://github.com/guardianproject/tor-android/pull/21 can be directly included in the TBB APKs by putting them in the right place on the file system before building. In tor-android, this is done in tor-android-binary/src/main/libs with tor-android-binary/src/main/jniLibs a symlink to that.

Then Android will automatically handle all the unpacking in a much more secure way. And it can be either loaded as a shared library without setting any paths, e.g. System.load("tor") or directly executed as a daemon from /data/data/org.torproject.torbrowser/lib/libtor.so.

If you still need to unpack other assets like torrc, geoip, etc., those should be put into the projects assets/ folder, then there is a standard Android method for getting those asset files. I think Orbot was already doing that.

Then TBB will need nothing from the https://github.com/guardianproject/tor-android project anymore.

Trac:
Keywords: TorBrowserTeam201901 deleted, TorBrowserTeam201911 added
Status: new to assigned
Owner: tbb-team to sisbell

Trac:
Cc: sisbell to sisbell, tbb-team

Moving tickets to December

Trac:
Keywords: TorBrowserTeam201911 deleted, TorBrowserTeam201912 added

Trac:
Keywords: TorBrowserTeam201912 deleted, TorBrowserTeam202001 added

Moving tickets to February

Trac:
Keywords: TorBrowserTeam202001 deleted, TorBrowserTeam202002 added

We are no longer in February, moving tickets

Trac:
Keywords: TorBrowserTeam202002 deleted, TorBrowserTeam202003 added

Trac:
Sponsor: N/A to Sponsor58

We are no longer in March

Trac:
Keywords: TorBrowserTeam202003 deleted, TorBrowserTeam202004 added

This is not a blocker of #28704 (moved)

Trac:
Parent: #28704 (moved) to N/A

Wrong ticket. But as eighthave said, we don't need this piece, so closing.

Trac:
Status: assigned to closed
Resolution: N/A to wontfix
Parent: N/A to #28704 (moved)

Trac:
Sponsor: Sponsor58 to N/A

closed

changed time estimate to 4h