The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-09-09T07:34:27Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40116Investigate LOAD_FLAGS_BYPASS_PROXY usage2020-09-09T07:34:27ZGeorg KoppenInvestigate LOAD_FLAGS_BYPASS_PROXY usageMike flagged `LOAD_FLAGS_BYPASS_PROXY` usage in his [proxy
audit](https://gitlab.torproject.org/tpo/applications/fenix/-/issues/34177),
so we should look at it closer.
I _think_ this is just a way to indicate that proxy caches should be...Mike flagged `LOAD_FLAGS_BYPASS_PROXY` usage in his [proxy
audit](https://gitlab.torproject.org/tpo/applications/fenix/-/issues/34177),
so we should look at it closer.
I _think_ this is just a way to indicate that proxy caches should be
bypassed and does not mean that suddenly connections bypass the network
proxy settings, see the
[MDN](https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIWebNavigation)
explanation of that flag:
```
This flag specifies that any intermediate proxy caches should be
bypassed (That is, that the content should be loaded from the origin
server).
```
We'll see whether my basic understanding is right here...Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40090Disable v3 extension blocklist for 10.0a62020-09-09T15:44:35ZGeorg KoppenDisable v3 extension blocklist for 10.0a6https://bugzilla.mozilla.org/show_bug.cgi?id=1631018 landed and is
enabling the v3 extension blocklist mechanism.
We are not sure how this effects our HTTPS-Everywhere extension. So, we
disable that mechanism for now.https://bugzilla.mozilla.org/show_bug.cgi?id=1631018 landed and is
enabling the v3 extension blocklist mechanism.
We are not sure how this effects our HTTPS-Everywhere extension. So, we
disable that mechanism for now.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/33935Fenix's classes5.dex files are not reproducible2020-09-10T15:02:12ZGeorg 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.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40072Tor libraries are missing in final .apk after switch to 81.1.0b12020-09-10T15:21:26ZGeorg KoppenTor libraries are missing in final .apk after switch to 81.1.0b1While preparing patches for #40055 and #40068 I realized that suddenly the Tor related artifacts do not seem to get picked up during build anymore and are therefore missing in the final .apk.
I double-checked that the `tor-onion-service...While preparing patches for #40055 and #40068 I realized that suddenly the Tor related artifacts do not seem to get picked up during build anymore and are therefore missing in the final .apk.
I double-checked that the `tor-onion-service-library` and `tor-android-service` artifacts included are a) still properly copied over to the /app directory and b) that they still contain the dependencies we need for the final .apk.Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://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/android-components/-/issues/34338Disable mozilla_lib_crash2020-09-11T08:33:37ZMatthew FinkelDisable mozilla_lib_crash> # A generic crash reporter component that can report crashes to multiple services
> mozilla_lib_crash -> org.mozilla.components:lib-crash
https://github.com/mozilla-mobile/android-components/tree/master/components/lib/crash> # A generic crash reporter component that can report crashes to multiple services
> mozilla_lib_crash -> org.mozilla.components:lib-crash
https://github.com/mozilla-mobile/android-components/tree/master/components/lib/crashhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40112Check that caching stylesheets per document group adheres to FPI2020-09-11T12:26:37ZGeorg KoppenCheck that caching stylesheets per document group adheres to FPIFirefox 80 comes with [caching stylesheets per document
group](https://bugzilla.mozilla.org/show_bug.cgi?id=1599160). Mozilla
thinks that
[needs](https://bugzilla.mozilla.org/show_bug.cgi?id=1646640)
[partitioning](https://bugzilla.mozil...Firefox 80 comes with [caching stylesheets per document
group](https://bugzilla.mozilla.org/show_bug.cgi?id=1599160). Mozilla
thinks that
[needs](https://bugzilla.mozilla.org/show_bug.cgi?id=1646640)
[partitioning](https://bugzilla.mozilla.org/show_bug.cgi?id=1645987) for
their [top-level site
partitioning](https://bugzilla.mozilla.org/show_bug.cgi?id=1590107),
which is roughly equivalent to first-party isolation. The relevant check
implemented is
```
nsIPrincipal* Loader::PartitionedPrincipal() const {
if (mDocument && StaticPrefs::privacy_partition_network_state()) {
return mDocument->PartitionedPrincipal();
}
return LoaderPrincipal();
}
```
which is not checking the FPI pref. So, I guess we need to investigate
what the FPI story is.Tor 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/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/tpa/team/-/issues/34424backport invoke and fabric to debian buster and update invoke in debian testing2020-09-14T16:21:43Zanarcatbackport invoke and fabric to debian buster and update invoke in debian testingWe rely on newer features of Fabric in our configuration that are not present in Debian buster. upload a backport to the official Debian backports.We rely on newer features of Fabric in our configuration that are not present in Debian buster. upload a backport to the official Debian backports.anarcatanarcathttps://gitlab.torproject.org/tpo/core/team/-/issues/11Release 0.4.4 stable (on time?)2020-09-15T13:45:24ZNick MathewsonRelease 0.4.4 stable (on time?)This is a tracking ticket for our 0.4.4 stable release, which is scheduled for 15 September. We can, of course, defer if needed.
Here are some things we should do before 0.4.4 is stable:
* [x] Ensure that every ~044-must ticket is fi...This is a tracking ticket for our 0.4.4 stable release, which is scheduled for 15 September. We can, of course, defer if needed.
Here are some things we should do before 0.4.4 is stable:
* [x] Ensure that every ~044-must ticket is fixed, or relabeled as not truly being must-fix for 0.4.4.
* [ ] Review all remaining ~044-should tickets and make sure that we are okay releasing without fixing any that remain. Fix all of the ones that are necessary, reclassifying them as ~044-must if needed.
* [x] Put out a release candidate in late August or early September, if there are significant changes since 0.4.4.4-rc
* [x] Write a changelog and releasenotes. (Nick is happy to do this when he's back.)Nick MathewsonNick Mathewsonhttps://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/-/issues/40095Review Mozilla developer notes for 79-81 (including)2020-09-17T10:47:04ZGeorg KoppenReview Mozilla developer notes for 79-81 (including)For mobile we need to review the Mozilla developer notes between 79-81
(including) watching out for proxy, linkability, and fingerprinting issues.
(There will be an own ticket for proxy bypass audit, though)For mobile we need to review the Mozilla developer notes between 79-81
(including) watching out for proxy, linkability, and fingerprinting issues.
(There will be an own ticket for proxy bypass audit, though)Tor Browser: 10.0Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/android-components/-/issues/40004Investigate Intents for launching external apps2020-09-18T09:57:30ZAlex CatarineuInvestigate Intents for launching external appsFrom https://gitlab.torproject.org/tpo/applications/fenix/-/issues/34177#note_2707927.
We should investigate these items:
* components/feature/app-links/src/main/java/mozilla/components/feature/app/links/AppLinksUseCases.kt
* component...From https://gitlab.torproject.org/tpo/applications/fenix/-/issues/34177#note_2707927.
We should investigate these items:
* components/feature/app-links/src/main/java/mozilla/components/feature/app/links/AppLinksUseCases.kt
* components/feature/contextmenu/src/main/java/mozilla/components/feature/contextmenu/ContextMenuCandidate.kt
* components/feature/downloads/src/main/java/mozilla/components/feature/downloads/AbstractFetchDownloadService.kt
* components/feature/downloads/src/main/java/mozilla/components/feature/downloads/DownloadsFeature.kt
* components/feature/prompts/src/main/java/mozilla/components/feature/prompts/PromptContainer.kt
* components/feature/prompts/src/main/java/mozilla/components/feature/prompts/file/FilePicker.kt
* components/feature/pwa/src/main/java/mozilla/components/feature/pwa/WebAppInterceptor.kt
* components/feature/app-links/src/main/java/mozilla/components/feature/app/links/AppLinksInterceptor.kt
And make sure we ask the user before launching, or block the intent if it's too dangerous (e.g. proxy bypass).Tor Browser: 10.0https://gitlab.torproject.org/tpo/web/support/-/issues/120Incorrect GPGTools link2020-09-18T15:53:54ZGusIncorrect GPGTools linkFrom frontdesk:
Hello! This weblink (https://www.gpgtools.org) leads to a security risk site. I believe it needs to link to this site instead: https://gpgtools.org/From frontdesk:
Hello! This weblink (https://www.gpgtools.org) leads to a security risk site. I believe it needs to link to this site instead: https://gpgtools.org/GusGushttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40041Remove Centos 6 support for Tor Browser 10.52020-09-18T20:37:38ZGeorg KoppenRemove Centos 6 support for Tor Browser 10.5There are CentOS 6 bits in our tor-browser-build parts that we should
remove (there is at least the one in `start-firefox`) for 10.5.There are CentOS 6 bits in our tor-browser-build parts that we should
remove (there is at least the one in `start-firefox`) for 10.5.Tor Browser: 10.5Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/core/tor/-/issues/2178We launch dummy descriptor fetches more often than needed2020-09-22T15:11:40ZNick MathewsonWe launch dummy descriptor fetches more often than neededRight now, we have code in update_router_descriptor_downloads() to launch a fetch for authority.z if we want to learn our IP from a directory fetch. We do this if:
* We're a server
* We don't have the Address option set
* At le...Right now, we have code in update_router_descriptor_downloads() to launch a fetch for authority.z if we want to learn our IP from a directory fetch. We do this if:
* We're a server
* We don't have the Address option set
* At least 20 minutes have passed since we last launched a router descriptor download
* At least 20 minutes have passed since we last launched a
Per discussion in bug legacy/trac#652, we could be even more quiet about launching these fetches. We could also require that
* At least 20 minutes have passed since we last launched *any* appropriate directory op.
* At least 20 minutes have passed since we got a new incoming connection on what we think our IP is.
* At least 20 minutes have passed since we got confirmation of our current IP in a NETINFO cell
We could also make the "20 minutes" value configurable by a networkstatus parameter.
This is a minor issue, since the current behavior is inelegant, but not actually hurting anything.Tor: 0.4.5.x-freezeDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://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.0