The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-09-10T15:54:24Zhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40078Bump Gradle version for Fenix to 6.5.12020-09-10T15:54:24ZGeorg KoppenBump Gradle version for Fenix to 6.5.1While we did not look did Mozilla bump Fenix's Gradle version to 6.5.1.
We should do the same.
Thanks, cypherpunk!While we did not look did Mozilla bump Fenix's Gradle version to 6.5.1.
We should do the same.
Thanks, cypherpunk!Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40082Fenix reproducibility issues2020-10-03T07:24:06ZGeorg KoppenFenix reproducibility issuesThis is the parent ticket for tracking Fenix reproducibility issues.
- [x] #33935
- [x] android-components#40013
- [x] fenix#40042
- [x] #40084
- [x] #40085
- [x] #40086
- [x] #40088
- [x] #40117This is the parent ticket for tracking Fenix reproducibility issues.
- [x] #33935
- [x] android-components#40013
- [x] fenix#40042
- [x] #40084
- [x] #40085
- [x] #40086
- [x] #40088
- [x] #40117Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40083Timestamp is embedded in extension manifest files2020-09-14T07:33:29ZGeorg KoppenTimestamp is embedded in extension manifest filesInspecting two Fenix .apk files one can see:
```
diff -r 1/test/assets/extensions/ads/manifest.json
2/test/assets/extensions/ads/manifest.json
9c9
< "version": "57.0.0.0910095351",
---
> "version": "57.0.0.0910102701",
diff -r 1/test...Inspecting two Fenix .apk files one can see:
```
diff -r 1/test/assets/extensions/ads/manifest.json
2/test/assets/extensions/ads/manifest.json
9c9
< "version": "57.0.0.0910095351",
---
> "version": "57.0.0.0910102701",
diff -r 1/test/assets/extensions/cookies/manifest.json
2/test/assets/extensions/cookies/manifest.json
9c9
< "version": "57.0.0.0910095351",
---
> "version": "57.0.0.0910102701",
```
The versions stem from a respective `manifest.template.json` which gets
processed in `app/build.gradle` like
```
def values = ['version': AndroidComponents.VERSION + "." + new
Date().format('MMddHHmmss')]
```Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40084Generation of AndroidManifest.xml is not reproducible2023-08-17T16:20:24ZGeorg KoppenGeneration of AndroidManifest.xml is not reproducibleWhen building Fenix twice the decompiled `AndroidManifest.xml` is the
same, yet the compiled one, not:
```
< 000046e0: 0800 0010 891a 2678 a800 0000 2d00 0000 ......&x....-...
---
> 000046e0: 0800 0010 911a 2678 a800 0000 2d00 0000 ......When building Fenix twice the decompiled `AndroidManifest.xml` is the
same, yet the compiled one, not:
```
< 000046e0: 0800 0010 891a 2678 a800 0000 2d00 0000 ......&x....-...
---
> 000046e0: 0800 0010 911a 2678 a800 0000 2d00 0000 ......&x....-...
```Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40085classes.dex is not reproducible in Fenix2022-05-06T16:29:04ZGeorg Koppenclasses.dex is not reproducible in Fenix```
--- diff1 2020-09-10 12:56:41.420435344 +0000
+++ diff2 2020-09-10 12:56:45.944473534 +0000
@@ -1,10 +1,10 @@
-00000000: 6465 780a 3033 3500 91ac 4818 cccd df98 dex.035...H.....
-00000010: e66f c93a 13c9 5794 c7d6 5c9e 7675 0e06 .o...```
--- diff1 2020-09-10 12:56:41.420435344 +0000
+++ diff2 2020-09-10 12:56:45.944473534 +0000
@@ -1,10 +1,10 @@
-00000000: 6465 780a 3033 3500 91ac 4818 cccd df98 dex.035...H.....
-00000010: e66f c93a 13c9 5794 c7d6 5c9e 7675 0e06 .o.:..W...\.vu..
+00000000: 6465 780a 3033 3500 2caa 318d 2cde 4f25 dex.035.,.1.,.O%
+00000010: 1f36 9bd8 6008 46ce a75a 692c 3fce f46b .6..`.F..Zi,?..k
00000020: a475 8100 7000 0000 7856 3412 0000 0000 .u..p...xV4.....
00000030: 0000 0000 c874 8100 8aef 0000 7000 0000 .....t......p...
00000040: 5d27 0000 98be 0300 9f33 0000 0c5c 0400 ]'.......3...\..
00000050: 2bf9 0000 80c7 0600 94d9 0000 d890 0e00 +...............
00000060: fb20 0000 785d 1500 ccf8 6700 d87c 1900 . ..x]....g..|..
00000070: e06a 5700 e26a 5700 256b 5700 906b 5700 .jW..jW.%kW..kW.
00000080: 936b 5700 a56b 5700 b76b 5700 c96b 5700 .kW..kW..kW..kW.
00000090: dd6b 5700 f46b 5700 0c6c 5700 246c 5700 .kW..kW..lW.$lW.
@@ -466021,17 +466021,17 @@
0071c640: 7c5f 5f00 017d 0002 7d0a 000d 7d20 4672 |__..}..}...} Fr
0071c650: 6167 6d65 6e74 7320 2800 137d 2056 6965 agments (..} Vie
0071c660: 774d 6f64 656c 5374 6f72 6573 2028 0003 wModelStores (..
0071c670: 7d2c 2000 027d 4000 027d 5b00 027d 5d00 }, ..}@..}[..}].
0071c680: 027d 7d00 017e 0058 7e7e 5238 7b22 636f .}}..~.X~~R8{"co
0071c690: 6d70 696c 6174 696f 6e2d 6d6f 6465 223a mpilation-mode":
0071c6a0: 2272 656c 6561 7365 222c 226d 696e 2d61 "release","min-a
0071c6b0: 7069 223a 3231 2c22 7067 2d6d 6170 2d69 pi":21,"pg-map-i
-0071c6c0: 6422 3a22 6130 6538 3738 6122 2c22 7665 d":"a0e878a","ve
+0071c6c0: 6422 3a22 3430 3436 3266 3422 2c22 7665 d":"40462f4","ve
0071c6d0: 7273 696f 6e22 3a22 312e 352e 3638 227d rsion":"1.5.68"}
0071c6e0: 0001 7f00 01c2 a300 3fc3 80c3 81c3 82c3 ........?.......
0071c6f0: 83c3 84c3 85c3 86c3 87c3 88c3 89c3 8ac3 ................
0071c700: 8bc3 8cc3 8dc3 8ec3 8fc3 90c3 91c3 92c3 ................
0071c710: 93c3 94c3 95c3 96c3 97c3 98c3 99c3 9aef ................
0071c720: bfba 1c1d 1ec3 9bc3 9cc3 9dc3 9ec3 9fc2 ................
0071c730: aac2 acc2 b1c2 b2c2 b3c2 b5c2 b9c2 bac2 ................
0071c740: bcc2 bdc2 bec2 80c2 81c2 82c2 83c2 84c2 ................
```Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40086classes2.dex is not reproducible in Fenix2020-10-02T17:23:02ZGeorg Koppenclasses2.dex is not reproducible in FenixThere is a big diff between `classes2.dex` for two Fenix builds. It is
attached.
[diff.bz2](/uploads/2246bee9e5d293f065ff1822e77d91f7/diff.bz2)There is a big diff between `classes2.dex` for two Fenix builds. It is
attached.
[diff.bz2](/uploads/2246bee9e5d293f065ff1822e77d91f7/diff.bz2)Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40088Use MOZ_BUILD_DATE for extension manifest timestamps2020-09-14T12:15:14ZGeorg KoppenUse MOZ_BUILD_DATE for extension manifest timestampsIn fenix#40042 we add the option to overwrite the `Date()` call with
some generated build date making use of `MOZ_BUILD_DATE`. We need to
actually set that env variable in our build script, though.In fenix#40042 we add the option to overwrite the `Date()` call with
some generated build date making use of `MOZ_BUILD_DATE`. We need to
actually set that env variable in our build script, though.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40090NSIS 3.06.1 based builds are not reproducible anymore2020-09-14T14:25:18ZGeorg KoppenNSIS 3.06.1 based builds are not reproducible anymoreWhile building 10.0a7 we realized that Windows builds were not matching
anymore. Extracting 32bit .exe files (with `7z x`) it turns out the NSIS
.dlls in the `PLUGINSDIR` were different. Inspecting them with `xxd`
(`diff -u <(xxd 1/\$PLU...While building 10.0a7 we realized that Windows builds were not matching
anymore. Extracting 32bit .exe files (with `7z x`) it turns out the NSIS
.dlls in the `PLUGINSDIR` were different. Inspecting them with `xxd`
(`diff -u <(xxd 1/\$PLUGINSDIR/System.dll) <(xxd
2/\$PLUGINSDIR/System.dll)`) showed the following:
```
--- /dev/fd/63 2020-09-14 13:36:43.586345952 +0000
+++ /dev/fd/62 2020-09-14 13:36:43.590345980 +0000
@@ -6,7 +6,7 @@
00000050: 6973 2070 726f 6772 616d 2063 616e 6e6f is program canno
00000060: 7420 6265 2072 756e 2069 6e20 444f 5320 t be run in DOS
00000070: 6d6f 6465 2e0d 0d0a 2400 0000 0000 0000 mode....$.......
-00000080: 5045 0000 4c01 0900 3076 5c5f 0000 0000 PE..L...0v\_....
+00000080: 5045 0000 4c01 0900 acc6 5c5f 0000 0000 PE..L.....\_....
00000090: 0000 0000 e000 2e23 0b01 021f 0046 0000 .......#.....F..
000000a0: 0064 0000 0004 0000 a633 0000 0010 0000 .d.......3......
000000b0: 0060 0000 0000 6c63 0010 0000 0002 0000 .`....lc........
@@ -1342,7 +1342,7 @@
000053d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000053e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000053f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
-00005400: 0000 0000 3076 5c5f 0000 0000 7890 0000 ....0v\_....x...
+00005400: 0000 0000 acc6 5c5f 0000 0000 7890 0000 ......\_....x...
00005410: 0100 0000 0800 0000 0800 0000 2890 0000 ............(...
00005420: 4890 0000 6890 0000 7514 0000 c831 0000 H...h...u....1..
00005430: a114 0000 c71b 0000 3d29 0000 441c 0000 ........=)..D...
```
After the PE header ends with `\0\0` The COFF header starts with 2 bytes
for the `Machine` attribute and 2 bytes for the `NumberOfSections`.
Immediately after those the differences begin in the `TimeDateStamp`
part. The same timestamps seem to show up later again.
I am not sure why I did not see those, though when redoing the build. I
probably recreated only the .exe files assuming the issue was solely in
those and not in binaries coming with NSIS itself.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40094Aarch64 fenix rust cross-compilation fails2020-09-17T07:14:47ZMatthew FinkelAarch64 fenix rust cross-compilation failsWhile building `fenix-rust-android-aarch64`:
```
= note: /var/tmp/build/rustc-1.43.0-src/build/build/x86_64-unknown-linux-gnu/stage2-std/armv7-linux-androideabi/release/deps/std-0c290f22c43402b2.std.e84jh5q4-cgu.0.rcgu.o: error adding...While building `fenix-rust-android-aarch64`:
```
= note: /var/tmp/build/rustc-1.43.0-src/build/build/x86_64-unknown-linux-gnu/stage2-std/armv7-linux-androideabi/release/deps/std-0c290f22c43402b2.std.e84jh5q4-cgu.0.rcgu.o: error adding symbols: File in wrong format
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: aborting due to previous error
error: could not compile `std`.
To learn more, run the command again with --verbose.
command did not execute successfully: "/var/tmp/dist/fenix-rust-rust-old/bin/cargo" "build" "-Zconfig-profile" "--target" "armv7-linux-androideabi" "-Zbinary-dep-depinfo" "-j" "8" "--release" "--frozen" "--features" "panic-unwind backtrace compiler-builtins-c" "--manifest-path" "/var/tmp/build/rustc-1.43.0-src/src/libtest/Cargo.toml" "--message-format" "json-render-diagnostics"
expected success, got: exit code: 101
failed to run: /var/tmp/build/rustc-1.43.0-src/build/build/bootstrap/debug/bootstrap build
```
And, this seems to be a result of a mismatch in the configured toolchain (in the container's `build` script):
```
mkdir build
cd build
../configure --prefix=$distdir --enable-local-rust --enable-vendor --enable-extended --release-channel=stable --sysconfdir=etc --target=armv7-linux-androideabi --set=target.armv7-linux-androideabi.cc=aarch64-linux-android21-clang --set=target.armv7-linux-androideabi.ar=aarch64-linux-android-ar
```
We should be building for `aarch64`, but we're targetting `armv7` and using the `aarch64` toolchain.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40095The pattern for the apk variable in build.android is matching too much2020-09-17T08:00:44ZGeorg KoppenThe pattern for the apk variable in build.android is matching too much`[% c("var/abi") %]*` is matching both `x86` and `x86_64` which results
in busted Android `x86` builds.`[% c("var/abi") %]*` is matching both `x86` and `x86_64` which results
in busted Android `x86` builds.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40097Update toolchain for Fenix 822020-10-21T21:18:23ZGeorg KoppenUpdate toolchain for Fenix 82Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40101Pick up Fenix 81.1.12020-09-23T13:00:05ZMatthew FinkelPick up Fenix 81.1.1Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/34080Avoid double delays from ReconnectTimeout2022-07-09T04:20:16ZDavid Fifielddcf@torproject.orgAvoid double delays from ReconnectTimeout[ReconnectTimeout](https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/client/lib/snowflake.go?id=72cfb96edeb7c9a3c93d38539bc31a51e30dbe8d#n18) is used in 2 places:
* In [exchangeSDP](https://gitweb.torproject.org/plug...[ReconnectTimeout](https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/client/lib/snowflake.go?id=72cfb96edeb7c9a3c93d38539bc31a51e30dbe8d#n18) is used in 2 places:
* In [exchangeSDP](https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/client/lib/webrtc.go?id=72cfb96edeb7c9a3c93d38539bc31a51e30dbe8d#n223), where it is a delay inserted between calls to `broker.Negotiate` until one of them succeeds.
`Failed to retrieve answer. Retrying in 10s`
* In the main [ConnectLoop](https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/client/snowflake.go?id=72cfb96edeb7c9a3c93d38539bc31a51e30dbe8d#n27), where it is a delay inserted between every check for getting a new snowflake.
```
WebRTC: <errmsg> Retrying in 10s...
```
The broker itself also terminates requests after 10s when the chosen proxy doesn't respond: `BrokerChannel Response: 504 Gateway Timeout`.
This situation sometimes results in double delays. Here are two cases I've identified.
* The client requests a proxy, the broker responds immediately with an answer, but the proxy doesn't work. After waiting the `DataChannelTimeout` to decide that the proxy doesn't work, the client waits an _additional_ `ReconnectTimeout` in `ConnectLoop`.
Here, I've set `DataChannelTimeout` to 10s. Notice that between `DataChannel created` and `Collecting a new Snowflake` there are 20s (which is `DataChannelTimeout` + `ReconnectTimeout`), when it really should only be 10s.
```
2020/04/30 22:38:29 Received Answer.
2020/04/30 22:38:29 WebRTC: DataChannel created.
2020/04/30 22:38:39 establishDataChannel: timeout waiting for DataChannel.OnOpen
2020/04/30 22:38:39 WebRTC: closing PeerConnection
2020/04/30 22:38:39 WebRTC: Closing
2020/04/30 22:38:39 WebRTC: WebRTC: Could not establish DataChannel Retrying in 10s...
2020/04/30 22:38:49 WebRTC: Collecting a new Snowflake. Currently at [0/1]
```
* The client requests a proxy, and the broker waits for 10s to respond with a 504 Gateway Timeout (indicating that the chosen proxy did not return an answer to the broker in time). The client waits 10s for the broker to respond, then waits another `ReconnectTimeout` in exchangeSDP before trying the broker again.
```
2020/04/30 22:39:30 Negotiating via BrokerChannel...
2020/04/30 22:39:41 BrokerChannel Response: 504 Gateway Timeout
2020/04/30 22:39:41 BrokerChannel Error: Unexpected error, no answer.
2020/04/30 22:39:41 Failed to retrieve answer. Retrying in 10s
2020/04/30 22:39:51 Negotiating via BrokerChannel...
```
Both these cases can probably be fixed by running the timer in parallel with the periodic operation they are rate limiting. That is, instead of
```
for {
operation()
<-time.After(ReconnectTimeout)
}
```
it can be
```
for {
timer := time.After(ReconnectTimeout)
operation()
<-timer
}
```
That way, if the operation itself takes more than 10s, `ReconnectTimeout` doesn't impose any additional delay.Sponsor 28: Reliable Anonymous Communication Evading Censors and Repressors (RACECAR)Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40104Generating incremental .mar files does not fully adhere to using specified tm...2020-10-16T19:51:26ZGeorg KoppenGenerating incremental .mar files does not fully adhere to using specified tmp directoryBack then in #23899 we made our incremental .mar files creation setup
adhere to a custom temporary directory as `/tmp` might just be too small
for handling large .mar files (diffs).
However, while I can see we still use that custom temp...Back then in #23899 we made our incremental .mar files creation setup
adhere to a custom temporary directory as `/tmp` might just be too small
for handling large .mar files (diffs).
However, while I can see we still use that custom temporary directory I
can see *too* that /tmp is used. In particular, when dealing with large
incremental files due to a major Firefox ESR update this can still cause
incrementals generation to fail.
I suspect there is another switch needed deeper down in the incrementals
generation stack, that is in Mozilla's scripts.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40105Enhance Gradle dependency script (sort deterministically and exclude .module ...2020-09-23T13:00:05ZGeorg KoppenEnhance Gradle dependency script (sort deterministically and exclude .module files)In #33932 we added the `gen_gradle_deps_file.sh` to help with the
generation of Gradle dependencies. We should enhance it so it sorts the
entries on different machines in the same way. This makes it easier to
ensure the proposed changes ...In #33932 we added the `gen_gradle_deps_file.sh` to help with the
generation of Gradle dependencies. We should enhance it so it sorts the
entries on different machines in the same way. This makes it easier to
ensure the proposed changes are correct.
Additionally, Gradle module files are not needed. We should ignore them when generating our dependencies list.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40106Support using geckoview as well2020-10-01T07:52:38ZGeorg KoppenSupport using geckoview as wellRight now we only support using our `geckoview-beta` in
`android-components` and `fenix`. We want to make sure that the
downloaded `geckoview` is replaced by our `geckoview` when building
release builds.Right now we only support using our `geckoview-beta` in
`android-components` and `fenix`. We want to make sure that the
downloaded `geckoview` is replaced by our `geckoview` when building
release builds.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4010710.5a1-build2 linux32 incrementals differ2020-09-22T19:31:58ZMatthew Finkel10.5a1-build2 linux32 incrementals differThe complete/full packages matched, but three linux32 incremental mars differ:
```
--- 10.5a1-build2-gk-sha256sums-unsigned-build.incrementals.txt 2020-09-22 13:26:19.463125161 +0000
+++ 10.5a1-build2-sy-sha256sums-unsigned-build.incr...The complete/full packages matched, but three linux32 incremental mars differ:
```
--- 10.5a1-build2-gk-sha256sums-unsigned-build.incrementals.txt 2020-09-22 13:26:19.463125161 +0000
+++ 10.5a1-build2-sy-sha256sums-unsigned-build.incrementals.txt 2020-09-22 12:44:24.817295530 +0000
@@ -1,5 +1,5 @@
1b77a0f956118978eda903282b0b7751ab00b4b0ac9b7569a56f400d2236d263 tor-browser-linux32-10.0a7-10.5a1_ar.incremental.mar
-ed56e7d2ef49a5cbcf7a3a979a09b3d4882b5229267f935a7caddae323e2477b tor-browser-linux32-10.0a7-10.5a1_ca.incremental.mar
+f915ba71d47c165e7a39c20cc071a409ec10c8d952a9a3258c9f25e853487d59 tor-browser-linux32-10.0a7-10.5a1_ca.incremental.mar
474989dc6eded1014e79e19c74af3c10a89f3ccb9b75cbea15731ab7afda4167 tor-browser-linux32-10.0a7-10.5a1_cs.incremental.mar
936bbae8e31796db8d8fe0b5b883752426d2ada24f6383797383c5dbd157269d tor-browser-linux32-10.0a7-10.5a1_da.incremental.mar
f8e215c1dee2ebe2d9c1a1ef598857f91d20e614665c70640b8c8c5ffa123d9b tor-browser-linux32-10.0a7-10.5a1_de.incremental.mar
@@ -10,7 +10,7 @@
a9b43840103ce41553aa1e97a22785be484abb2edcb07d08c9d8583b9e811786 tor-browser-linux32-10.0a7-10.5a1_fa.incremental.mar
e5d8ca07657f4b6e83ff622a5854f661b96be3ed475cdb0404e669022525dfa9 tor-browser-linux32-10.0a7-10.5a1_fr.incremental.mar
d48f4040798f83dfe77d93eb1a271b6d80a994a77096e0e851739162b091fe2b tor-browser-linux32-10.0a7-10.5a1_ga-IE.incremental.mar
-6d9229c7ef11b06ff09578e416f15d607a968e51c4d2aeddb31cafd86df420ee tor-browser-linux32-10.0a7-10.5a1_he.incremental.mar
+400c06adc58dfdb78991e28fe382e2ba8d05d8e614293c874bd2a8d1849f4798 tor-browser-linux32-10.0a7-10.5a1_he.incremental.mar
8ae3a437dd29143e60229341b4695caf874189782ae80483febacb3770d763a3 tor-browser-linux32-10.0a7-10.5a1_hu.incremental.mar
c033aad437a8c34cfd0f546179ae3b318015aeac8d431029054e17e6baa34570 tor-browser-linux32-10.0a7-10.5a1_id.incremental.mar
3bb106fa33c66ca3fa442289c4b1cb0fb2d0658f7dc612da7eaea28d929b85a8 tor-browser-linux32-10.0a7-10.5a1_is.incremental.mar
@@ -24,7 +24,7 @@
5facbc51d00611e394cfd35f0b899d2c50c4505530803188d163db0fdbef37be tor-browser-linux32-10.0a7-10.5a1_nb-NO.incremental.mar
a9854d535f997f98721d47895fecb289b6f1ddb1d92053192ecc56ddc68e1bf9 tor-browser-linux32-10.0a7-10.5a1_nl.incremental.mar
e6028e3c22e58e63f92b318fe4501806e47dab90c41b2168033c1c1d17a4d506 tor-browser-linux32-10.0a7-10.5a1_pl.incremental.mar
-b32cb8329db20991ba02a6dfea1a54de4542c12477732c77cfbce5b41f25fdb8 tor-browser-linux32-10.0a7-10.5a1_pt-BR.incremental.mar
+4dd4f2aefeb37b8c621e7abb83893a517e58d9cd4aee4386482641197efb3fff tor-browser-linux32-10.0a7-10.5a1_pt-BR.incremental.mar
6aa11610ea0f1c97deb5d808a76bbcb91f1e276769ca00beb79cb7f53f9bdf08 tor-browser-linux32-10.0a7-10.5a1_ro.incremental.mar
d0752bdbe4b3a02195ff3d96e2913f648299c8c055e7f007a6ce19da1c2cbdc8 tor-browser-linux32-10.0a7-10.5a1_ru.incremental.mar
18f3d684830a84f5a324712c41fea820617fd84bc695147a74dc15cafa6e4073 tor-browser-linux32-10.0a7-10.5a1_sv-SE.incremental.mar
```
Comparing the archives shows additional differences (they don't all differ in the same way):
```
$ diff -u <(~/mar-tools/mar -t gk/ca/tor-browser-linux32-10.0a7-10.5a1_ca.incremental.mar) <(~/mar-tools/mar -t sy/ca/tor-browser-linux32-10.0a7-10.5a1_ca.incremental.mar)
--- /dev/fd/63 2020-09-22 14:41:09.792590868 +0000
+++ /dev/fd/62 2020-09-22 14:41:09.792590868 +0000
@@ -6,6 +6,7 @@
341540 0644 TorBrowser/Tor/libcrypto.so.1.1.patch
472 0644 TorBrowser/Docs/ChangeLog.txt.patch
116 0644 application.ini.patch
+3976660 0644 libxul.so.patch
1676 0644 abicheck.patch
590384 0644 TorBrowser/Data/Browser/profile.default/extensions/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
228840 0644 TorBrowser/Tor/tor.patch
@@ -26,7 +27,6 @@
89080 0644 TorBrowser/Tor/libssl.so.1.1.patch
7064 0644 libmozavcodec.so.patch
652 0644 updatev2.manifest
-32424068 0755 libxul.so
1176 0644 precomplete
7444 0644 libmozavutil.so.patch
972908 0644 browser/omni.ja.patch
@@ -39,7 +39,7 @@
348 0644 gtk2/libmozgtk.so.patch
824 0644 libplc4.so.patch
31652 0644 TorBrowser/Tor/PluggableTransports/obfs4proxy.patch
-700 0644 updatev3.manifest
+696 0644 updatev3.manifest
7400 0644 libfreeblpriv3.so.patch
9188 0644 updater.patch
12960 0644 libnspr4.so.patch
```
```
$ diff -u <(~/mar-tools/mar -t gk/he/tor-browser-linux32-10.0a7-10.5a1_he.incremental.mar) <(~/mar-tools/mar -t sy/he/tor-browser-linux32-10.0a7-10.5a1_he.incremental.mar)
--- /dev/fd/63 2020-09-22 14:46:02.433509835 +0000
+++ /dev/fd/62 2020-09-22 14:46:02.433509835 +0000
@@ -6,6 +6,7 @@
341540 0644 TorBrowser/Tor/libcrypto.so.1.1.patch
472 0644 TorBrowser/Docs/ChangeLog.txt.patch
116 0644 application.ini.patch
+3976660 0644 libxul.so.patch
1676 0644 abicheck.patch
590384 0644 TorBrowser/Data/Browser/profile.default/extensions/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
228840 0644 TorBrowser/Tor/tor.patch
@@ -27,7 +28,6 @@
89080 0644 TorBrowser/Tor/libssl.so.1.1.patch
7064 0644 libmozavcodec.so.patch
652 0644 updatev2.manifest
-32424068 0755 libxul.so
1176 0644 precomplete
7444 0644 libmozavutil.so.patch
972908 0644 browser/omni.ja.patch
@@ -39,7 +39,7 @@
348 0644 gtk2/libmozgtk.so.patch
824 0644 libplc4.so.patch
31652 0644 TorBrowser/Tor/PluggableTransports/obfs4proxy.patch
-700 0644 updatev3.manifest
+696 0644 updatev3.manifest
7400 0644 libfreeblpriv3.so.patch
9188 0644 updater.patch
12960 0644 libnspr4.so.patch
```
```
$ diff -u <(~/mar-tools/mar -t gk/pt-BR/tor-browser-linux32-10.0a7-10.5a1_pt-BR.incremental.mar) <(~/mar-tools/mar -t sy/pt-BR/tor-browser-linux32-10.0a7-10.5a1_pt-BR.incremental.mar)
--- /dev/fd/63 2020-09-22 14:46:43.893874307 +0000
+++ /dev/fd/62 2020-09-22 14:46:43.897874347 +0000
@@ -6,6 +6,7 @@
341540 0644 TorBrowser/Tor/libcrypto.so.1.1.patch
472 0644 TorBrowser/Docs/ChangeLog.txt.patch
116 0644 application.ini.patch
+3976660 0644 libxul.so.patch
1676 0644 abicheck.patch
590384 0644 TorBrowser/Data/Browser/profile.default/extensions/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
228840 0644 TorBrowser/Tor/tor.patch
@@ -27,7 +28,6 @@
7064 0644 libmozavcodec.so.patch
19040 0644 TorBrowser/Data/Browser/profile.default/extensions/langpack-pt-BR@firefox.mozilla.org.xpi.patch
656 0644 updatev2.manifest
-32424068 0755 libxul.so
1176 0644 precomplete
7444 0644 libmozavutil.so.patch
972896 0644 browser/omni.ja.patch
```Tor Browser: 10.0https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/issues/1Create a Tor PT client for conjure2022-06-30T16:27:34ZCecylia BocovichCreate a Tor PT client for conjureWe can import the [refraction networking client](https://github.com/refraction-networking/gotapdance) code as a library directly from our main program as described in the code snippet in their [README](https://github.com/refraction-netwo...We can import the [refraction networking client](https://github.com/refraction-networking/gotapdance) code as a library directly from our main program as described in the code snippet in their [README](https://github.com/refraction-networking/gotapdance#usage).
This will be done similarly to how the Snowflake client now calls the Snowflake client library from [the main Go package](https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/blob/0054cb2dec19e89e07b8c5a6d8b9d23589842deb/client/snowflake.go).Sponsor 30 - Objective 2.3Cecylia BocovichCecylia Bocovich2022-06-10https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40108android-components does not bundle tooling-glean-gradle archive, only .pom file2020-10-05T17:42:04ZGeorg Koppenandroid-components does not bundle tooling-glean-gradle archive, only .pom fileFor some reason our build of android-components only includes the .pom
file for the `tooling-glean-gradle` component but not archive. However,
that's needed otherwise the build breaks. We don't see issues right now
(or only by accident a...For some reason our build of android-components only includes the .pom
file for the `tooling-glean-gradle` component but not archive. However,
that's needed otherwise the build breaks. We don't see issues right now
(or only by accident as I did) because we silently use the one Mozilla
provides as we are only overwriting things with .aars and .poms we
actually provide.
So, we should a) fix this issue and b) make sure we don't have the
.pom-only situation with other components either.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/33150Allow to connect to an external control port2022-02-17T19:58:39ZjugaAllow to connect to an external control portTo be able to run integration tests with chutney.To be able to run integration tests with chutney.sbws: 1.1.x-finaljugajuga