Merge Orfox patches into tor-browser

We want to have Tor Browser mobile patches in our tree to make it easier keeping track on all things Tor Browser.

added TorBrowserTeam201803 component::applications/tor browser ff52-esr owner::igt0 parent::5709 priority::medium resolution::fixed severity::normal status::closed tbb-mobile type::task labels

Trac:
Cc: amoghbl1 to amoghbl1, brade, mcs

Trac:
Cc: amoghbl1, brade, mcs to amoghbl1, brade, mcs, arthuredelstein

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

Trac:
Username: tokotoko
Cc: amoghbl1, brade, mcs, arthuredelstein to amoghbl1, brade, mcs, arthuredelstein, fdsfgs@krutt.org

Removing parent ID because this shouldn't block TBB/ESR52.

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

Trac:
Keywords: N/A deleted, ff52-esr added

Trac:
Keywords: N/A deleted, TorBrowserTeam201712 added

Trac:
Status: new to assigned
Owner: tbb-team to igt0

I rebased the Orfox commits on tor-browser-52.5.2esr-7.5-2. This includes all commits from orfox-tor-browser-52.2.0esr-7.0-1, but with some modifications.

1. Rename .mozconfig-orfox as .mozconfig-android
2. Align .mozconfig-android configuration with .mozconfig configuration
3. Add comments on non-obvious configuration changes
4. Bump Java JDK version from openjdk-7 to openjdk-8 (openjdk-7 is EOL)
5. Bump Android NDK version from r11b to r11c (hash of r11c is published on the Android website, r11b's hash is not available)
6. Verify sha256sum hash of downloaded SDK and NDK files match expected/published value

There are a few outstanding changes that are needed:

1. Compiling with tests enabled fails
2. App crashes when running in an Android emulator (it does not crash when running on a device)
3. Change the app name from Orfox to Tor Browser(?)
4. We need more unit tests
5. c823adc2da01ee47d50e03f1a5a4f14e661e8a2c adds a third-party extension, we need integrate its changes instead
6. Audit mobile.js and confirm it matches browser.js
7. Some of the commits add whitespace, we should clean before merging

branch is tor-browser-52.5.2esr-7.5-2_attempt0_1 at https://github.com/sysrqb/tor-browser/tree/tor-browser-52.5.2esr-7.5-2_attempt0_1

I have some more notes from my review, I will add them here after I think about them some more.

Trac:
Cc: amoghbl1, brade, mcs, arthuredelstein, fdsfgs@krutt.org to amoghbl1, brade, mcs, arthuredelstein, fdsfgs@krutt.org, igt0
Status: assigned to needs_revision

Nice stuff! I am making comments straight in the github.

I am not sure if it is related to this merge however we need to sync the: https://github.com/sysrqb/tor-browser/blob/tor-browser-52.5.2esr-7.5-2_attempt0_1/mobile/android/app/mobile.js

with the

https://gitweb.torproject.org/tor-browser.git/tree/modules/libpref/init/all.js?h=tor-browser-52.5.2esr-7.5-2

Replying to sysrqb:

I rebased the Orfox commits on tor-browser-52.5.2esr-7.5-2. This includes all commits from orfox-tor-browser-52.2.0esr-7.0-1, but with some modifications.

1. Rename .mozconfig-orfox as .mozconfig-android
2. Align .mozconfig-android configuration with .mozconfig configuration
3. Add comments on non-obvious configuration changes
4. Bump Java JDK version from openjdk-7 to openjdk-8 (openjdk-7 is EOL)
5. Bump Android NDK version from r11b to r11c (hash of r11c is published on the Android website, r11b's hash is not available)
6. Verify sha256sum hash of downloaded SDK and NDK files match expected/published value

There are a few outstanding changes that are needed:

1. Compiling with tests enabled fails
2. App crashes when running in an Android emulator (it does not crash when running on a device)
3. Change the app name from Orfox to Tor Browser(?)
4. We need more unit tests
5. c823adc2da01ee47d50e03f1a5a4f14e661e8a2c adds a third-party extension, we need integrate its changes instead
6. Audit mobile.js and confirm it matches browser.js
7. Some of the commits add whitespace, we should clean before merging

branch is tor-browser-52.5.2esr-7.5-2_attempt0_1 at https://github.com/sysrqb/tor-browser/tree/tor-browser-52.5.2esr-7.5-2_attempt0_1

I have some more notes from my review, I will add them here after I think about them some more.

Moving tickets to 2018.

Trac:
Keywords: TorBrowserTeam201712 deleted, TorBrowserTeam201801 added

Moving tickets to Feb

Trac:
Keywords: TorBrowserTeam201801 deleted, TorBrowserTeam201802 added

Trac:
Parent: N/A to 5709

Trac:
Parent: 5709 to #5709 (moved)

Okay, we decided we'll take a different path with this. I rebased the current Orfox patches onto tor-browser-52.6.0esr-8.0-2, there weren't any merge conflicts. Instead of fixing the current patches so we're comfortable calling mobile/android "Tor Browser for Android", we'll take the patches as-is and mark this task as complete. We'll fixup these commits as we rebase them onto mozilla-central.

I already have a few changes, but getting these patches in-tree is higher priority. We're keeping the Orfox branding because this is not a Tor Browser for Android, yet. I'll open some tickets that cover the changes I think we should make.

I did fixup one commit where symlinks were used for icons at different screen resolutions. Mach try does not like symlinks anywhere in the commit history, so I scrubbed that before we merged it.

Branch bug19675_orfox_patches on https://git.torproject.org/user/sysrqb/tor-browser.git

Trac:
Status: needs_revision to needs_review

Trac:
Keywords: TorBrowserTeam201802 deleted, TorBrowserTeam201802R added

I am not overly thrilled to add .xpi files to our tree in commit 4553e490317622677475d0d63ba169074df2f085, especially as they are outdated (there is HTTPS-E 5.2.21 available instead of 5.2.20 if the requirement is a non-WebExtension Add-On). But I guess we can iterate from that. :)

Could you provide an updated branch without b27b64b540cd81a895a289e09d611a50255de3c1 as it does not seem to do anything?

Trac:
Status: needs_review to needs_revision
Keywords: TorBrowserTeam201802R deleted, TorBrowserTeam201803 added

Replying to gk:

I am not overly thrilled to add .xpi files to our tree in commit 4553e490317622677475d0d63ba169074df2f085, especially as they are outdated (there is HTTPS-E 5.2.21 available instead of 5.2.20 if the requirement is a non-WebExtension Add-On). But I guess we can iterate from that. :)

Yes, I can follow up with a new ticket for updating these.

Could you provide an updated branch without b27b64b540cd81a895a289e09d611a50255de3c1 as it does not seem to do anything?

Sure thing, I pushed branch bug19675_orfox_patches_1 with that commit deleted https://gitweb.torproject.org/user/sysrqb/tor-browser.git/log/?h=bug19675_orfox_patches_1

For reference:

$ git status
On branch bug19675_orfox_patches_1
nothing to commit, working tree clean

$ git diff bug19675_orfox_patches  
diff --git a/mobile/android/base/AndroidManifest.xml.in b/mobile/android/base/AndroidManifest.xml.in
index 1d6730d13ff4..1aa50a08463d 100644
--- a/mobile/android/base/AndroidManifest.xml.in
+++ b/mobile/android/base/AndroidManifest.xml.in
@@ -22,7 +22,6 @@
      fileincluded here, so that they can be referenced by both APKs. -->
 #include FennecManifest_permissions.xml.in
 
-
     <application android:label="@string/moz_app_displayname"
                  android:icon="@drawable/icon"
                  android:logo="@drawable/logo"

Alright, we are done here, finally. I did:

1. Run a build for all supported platforms/architectures to make sure the patches don't affect the desktop build
2. Reviewed the patches
3. Checked that they are indeed the same patches as in the Orfox repository
4. Built Orfox and ran it successfully on my test phone \o/.

sysrqb: I wonder if we should amend the "Building Orfox" part on our Hacking document a bit to reflect the new situation. FWIW: I needed to spent quite some time to get the Android SDK thing to do what it was supposed to do, even after calling ./mach bootstrap. It seems to be the case that the bootstrap thing is downloading the r24 SDK, however at the end the build-tools r23.0.3 are missing. Trying to install them fails even with the SDK manager because I only got offered r23.0.1 and the build system is insisting that it needs r23.0.3. So, I ended up just sim-linking 23.0.1 -> 23.0.3 and that worked smoothly. :) I wonder though whether there is something more straightforward we can suggest on the doc...

Trac:
Status: needs_revision to closed
Resolution: N/A to fixed

Excellent! Opened #25562 (moved) for additional discussion.

We might want to have this backported to make Orfox releases easier.

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

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

closed

mentioned in issue #21863 (moved)

mentioned in issue #22059 (moved)

mentioned in issue #22059 (moved)

mentioned in issue #22170 (moved)

mentioned in issue #22171 (moved)

mentioned in issue #22171 (moved)

mentioned in issue #23144 (closed)

mentioned in issue #24796 (moved)

mentioned in issue #24919 (moved)

mentioned in issue #24920 (moved)

mentioned in issue #24926 (moved)

mentioned in issue #24957 (moved)

mentioned in issue #25164 (moved)

mentioned in issue #25562 (moved)

mentioned in issue #25603 (moved)

moved to tpo/applications/tor-browser#19675 (closed)

mentioned in issue tpo/applications/tor-browser#25562 (closed)

mentioned in issue tpo/applications/tor-browser#25603 (closed)