Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T01:26:15Zhttps://gitlab.torproject.org/legacy/trac/-/issues/33935Fenix's classes5.dex files are not reproducible2020-06-16T01:26:15ZGeorg KoppenFenix's classes5.dex files are not reproducibleWhen building .apk files with the https://gitweb.torproject.org/user/gk/tor-browser-build.git/commit/?h=bug_33927_v2&id=a9eca52f63d049f0cb1a03c14971c8743d79a2b1 it turns out the `classes5.dex` files are not getting built deterministicall...When building .apk files with the https://gitweb.torproject.org/user/gk/tor-browser-build.git/commit/?h=bug_33927_v2&id=a9eca52f63d049f0cb1a03c14971c8743d79a2b1 it turns out the `classes5.dex` files are not getting built deterministically for all 4 architectures. Looking at the diff for armv7 (attached) there is at least a timestamp issues we need to fix, but maybe more.https://gitlab.torproject.org/legacy/trac/-/issues/33934Fix Fenix reproducibility issues2020-06-16T01:26:15ZGeorg KoppenFix Fenix reproducibility issuesFenix has reproducibility issues it seems. We should collect them in child tickets and address them.Fenix has reproducibility issues it seems. We should collect them in child tickets and address them.https://gitlab.torproject.org/legacy/trac/-/issues/33931obfs4 bridges are used instead of meek if meek is selected in Tor Browser for...2020-06-16T01:12:35ZGeorg Koppenobfs4 bridges are used instead of meek if meek is selected in Tor Browser for Android alphaIn the 9.5 alpha series `meek` is not used anymore even if `meek` is selected as pluggable transport. Instead Tor Browser tries to use some `obfs4` bridge from the bridge list coming with Tor Browser. That's happening on 9.5a11. 9.0.9 is...In the 9.5 alpha series `meek` is not used anymore even if `meek` is selected as pluggable transport. Instead Tor Browser tries to use some `obfs4` bridge from the bridge list coming with Tor Browser. That's happening on 9.5a11. 9.0.9 is not affected.https://gitlab.torproject.org/legacy/trac/-/issues/33930Tor binary we build seems to not getting picked up in nightly builds2020-06-15T23:02:06ZGeorg KoppenTor binary we build seems to not getting picked up in nightly buildsWe build Tor for Android now ourselves thanks to the fix for #28766. But unfortunately it seems at least as it is not picked up yet, despite #32993 claiming so. I stumbled across this when testing a fix for #32027. The branch has all pat...We build Tor for Android now ourselves thanks to the fix for #28766. But unfortunately it seems at least as it is not picked up yet, despite #32993 claiming so. I stumbled across this when testing a fix for #32027. The branch has all patches for #28704 and children but it's still shown that we use the Tor we've been bundling so far but not the one we compile.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33927Add tor-browser-build project for fenix2020-06-16T01:26:13ZGeorg KoppenAdd tor-browser-build project for fenixWe need an own project for FenixWe need an own project for FenixGeorg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33904tba: tabs sometimes fail to rerender2020-06-16T01:12:34Ztraumschuletba: tabs sometimes fail to rerenderVersion: 68.7.0
This appeared several times in irregular intervals. STR aren't known yet. Will add a trace when it happens again.
Symptoms:
- page content suddenly goes blank
- every tab is blank when attached to
- rest of Tor Browser ...Version: 68.7.0
This appeared several times in irregular intervals. STR aren't known yet. Will add a trace when it happens again.
Symptoms:
- page content suddenly goes blank
- every tab is blank when attached to
- rest of Tor Browser keeps responsive and tab list still shows correct previewshttps://gitlab.torproject.org/legacy/trac/-/issues/33903avc: denied { ioctl } for comm="libTor.so"2020-06-16T01:12:34Ztraumschuleavc: denied { ioctl } for comm="libTor.so"This shows up in the log a lot:
```
659 E audit : type=1400 audit(1586853418.578:86987): avc: denied { ioctl } for pid=31144 comm="libTor.so" path="socket:[4954704]" dev="sockfs" ino=4954704 ioctlcmd=894b scontext=u:r:untrusted_app...This shows up in the log a lot:
```
659 E audit : type=1400 audit(1586853418.578:86987): avc: denied { ioctl } for pid=31144 comm="libTor.so" path="socket:[4954704]" dev="sockfs" ino=4954704 ioctlcmd=894b scontext=u:r:untrusted_app:s0:c78,c257,c512,c768 tcontext=u:r:untrusted_app:s0:c78,c257,c512,c768 tclass=tcp_socket permissive=0 audit_filtered
```
top:
```
31144 u0_a334 20 0 41M 13M 5.9M S 1.0 1846 21:15.61 libTor.so -f /data/user/0/org.torproject.torbrowser_alpha/app_torservice/torrc __OwningControllerProcess 30950`
30950 u0_a334 20 0 2.2G 252M 87M S 9.3 36721 66:23.37 org.torproject.torbrowser_alpha
```
Possibly related:
[Further restrict socket ioctls available to apps](https://android.googlesource.com/platform/external/sepolicy/+/556bb0f55324e8839d7b735a0de9bc31028e839e)https://gitlab.torproject.org/legacy/trac/-/issues/33876Back Button on Tor Browser Android Closes App When Log is Open2020-06-16T01:12:29ZTracBack Button on Tor Browser Android Closes App When Log is OpenThis is a small UX quirk that can frustrate/confuse new users, especially those who are unfamiliar with Tor and are curious about the log. When you open the log in Tor Browser on Android it fills up the entire screen and if the user pres...This is a small UX quirk that can frustrate/confuse new users, especially those who are unfamiliar with Tor and are curious about the log. When you open the log in Tor Browser on Android it fills up the entire screen and if the user presses the back button on their device the app will close. Generally when a screen is filled on Android pressing back takes you to the previous screen. I think little things could instill distrust in newer users.
This issue used to exist in Orbot a few years ago https://github.com/guardianproject/orbot/pull/139
I apologize if this isn't the correct spot to report this. I'm new to trac, and am open to feedback if there's a better spot to file this :) Also, I've implemented a fix and I'm still figuring out where to push my code and put it up for review... <3
**Trac**:
**Username**: bimhttps://gitlab.torproject.org/legacy/trac/-/issues/33833Upgrade Rust To Use Android NDK 202020-06-16T01:26:12ZShane IsbellUpgrade Rust To Use Android NDK 20Upgrade rust to use latest toolchainUpgrade rust to use latest toolchainGeorg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33801Upgrade Go Project to use new Android Toolchain2020-06-16T01:26:11ZShane IsbellUpgrade Go Project to use new Android ToolchainGo needs to use new NDK pathGo needs to use new NDK pathhttps://gitlab.torproject.org/legacy/trac/-/issues/33760Update rbm.conf to match NDK 202020-06-16T01:26:11ZShane IsbellUpdate rbm.conf to match NDK 20the configure_host field no longer matches the correct clang in the lasted NDK. The new NDK requires that we also update the platform version number.the configure_host field no longer matches the correct clang in the lasted NDK. The new NDK requires that we also update the platform version number.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33685Add Support for Building zlib for Android2020-06-16T01:11:58ZShane IsbellAdd Support for Building zlib for AndroidAdd android build support for zlibAdd android build support for zlibhttps://gitlab.torproject.org/legacy/trac/-/issues/33683Fenix fingerprinting2020-06-15T23:01:20ZThorinFenix fingerprintingAs I come across Fenix-only items I will add them here for consideration: sysrqb & gk know how to get hold of me if you need a PoC
- toolbar location can be detected
- Settings > Customize > Toolbar > Top/Bottom
- font inflation can ...As I come across Fenix-only items I will add them here for consideration: sysrqb & gk know how to get hold of me if you need a PoC
- toolbar location can be detected
- Settings > Customize > Toolbar > Top/Bottom
- font inflation can be detected
- Settings > Accessibility > Automatic Font Sizing
Feel free to add more itemshttps://gitlab.torproject.org/legacy/trac/-/issues/33626Add TBB project for GeckoView2020-10-02T06:25:04ZShane IsbellAdd TBB project for GeckoViewFenix and android-components have dependencies on GeckoView. Need to setup environment to build this for production, beta and nightly. Involves rust and clang setup.Fenix and android-components have dependencies on GeckoView. Need to setup environment to build this for production, beta and nightly. Involves rust and clang setup.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33594Fenix Use of Glean2020-06-15T23:01:19ZShane IsbellFenix Use of GleanGlean is the telemetry library that Fenix uses, which I think we don't want to add to the final apk.
There two ways to handle this
1. Create a TBB project for glean and include it as a compile time dependency in android-components. Th...Glean is the telemetry library that Fenix uses, which I think we don't want to add to the final apk.
There two ways to handle this
1. Create a TBB project for glean and include it as a compile time dependency in android-components. Then we just don't include the aar in the final project, which disables the feature.
2. Patch the Fenix project to not use glean
I'm not that keen on (1) since we have to pull in and configure rust. (2) also seems a bit of a pain because the android-components is going through heavy development would require redoing the patches each time.
I have pref for (2). Thoughts?
Remark from components/browser/engine-gecko-nightly/build.gradle
```
// We only compile against Glean. It's up to the app to add those dependencies
// if it wants to collect GeckoView telemetry through the Glean SDK.
```
Project: https://github.com/mozilla/gleanhttps://gitlab.torproject.org/legacy/trac/-/issues/33565Upgrade LZMA to use Android NDK 202020-06-16T01:11:43ZShane IsbellUpgrade LZMA to use Android NDK 20This is based of the current work done in branch for android support. We need to upgrade to build with NDK 20.
Make standalone toolchain is not longer supported in NDK 20 so need to configure to use new locationsThis is based of the current work done in branch for android support. We need to upgrade to build with NDK 20.
Make standalone toolchain is not longer supported in NDK 20 so need to configure to use new locationshttps://gitlab.torproject.org/legacy/trac/-/issues/33564Upgrade ZSTD to use Android NDK 202020-06-16T01:26:09ZShane IsbellUpgrade ZSTD to use Android NDK 20This is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locationsThis is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locationshttps://gitlab.torproject.org/legacy/trac/-/issues/33563Upgrade Tor To Use Android NDK 202020-06-16T01:26:08ZShane IsbellUpgrade Tor To Use Android NDK 20This is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locationsThis is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locationsGeorg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33562Upgrade libevent to use NDK 202020-06-16T01:11:42ZShane IsbellUpgrade libevent to use NDK 20This is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locations.This is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locations.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/33561Upgrade openssl to use Android NDK 202020-06-16T01:26:07ZShane IsbellUpgrade openssl to use Android NDK 20This is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locations.This is based of the current work done in branch for android support. We need to upgrade to build with NDK 21.
Make standalone toolchain is not longer supported in NDK 21 so need to configure to use new locations.Georg KoppenGeorg Koppen