Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T00:46:43Zhttps://gitlab.torproject.org/legacy/trac/-/issues/26261Error building openssl for macOS2020-06-16T00:46:43ZboklmError building openssl for macOSWhen building openssl for macOS with the current master branch, I get the following error:
```
x86_64-apple-darwin10-ar r ../libcrypto.a cryptlib.o mem.o mem_dbg.o cversion.o ex_data.o cpt_err.o ebcdic.o uid.o o_time.o o_str.o o_dir.o o...When building openssl for macOS with the current master branch, I get the following error:
```
x86_64-apple-darwin10-ar r ../libcrypto.a cryptlib.o mem.o mem_dbg.o cversion.o ex_data.o cpt_err.o ebcdic.o uid.o o_time.o o_str.o o_dir.o o_fips.o o_init.o fips_ers.o x86_64cpuid.o
x86_64-apple-darwin10-ar: creating archive ../libcrypto.a
/var/tmp/dist/macosx-toolchain/cctools/bin/x86_64-apple-darwin10-ranlib: object: ../libcrypto.a(mem_dbg.o) malformed object (unknown load command 2)
x86_64-apple-darwin10-ar: internal ranlib command failed
make[1]: *** [../libcrypto.a] Error 1
Makefile:104: recipe for target '../libcrypto.a' failed
make[1]: Leaving directory '/var/tmp/build/openssl-1.0.2o/crypto'
make: *** [build_crypto] Error 1
Makefile:288: recipe for target 'build_crypto' failed
```
I think it might be related to the llvm update that was done as part of #26073.https://gitlab.torproject.org/legacy/trac/-/issues/26098remove meek-amazon from the Tor Browser2020-06-16T00:46:13ZSina Rabbaniremove meek-amazon from the Tor Browser-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please remove the meek-amazon bridge from the Tor Browser. Amazon is no longer supporting 'domain-fronting' and has effectively asked us to stop this CDN end-point.
Patch file is attached ...-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please remove the meek-amazon bridge from the Tor Browser. Amazon is no longer supporting 'domain-fronting' and has effectively asked us to stop this CDN end-point.
Patch file is attached to this ticket.
Some more details here:
https://blog.torproject.org/domain-fronting-critical-open-web
- --Sina
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJa+dysAAoJEMeylP64yITypVQP/R3KYgX0Xvm2AjmoDb2ltQ5m
2iupbfV1PPmVBIOPbM9bCPAETo9F4ANol5PjUNPSQClfp+qicpCLbcLCVAXxwovA
Ul2Rfq92/Ib3ZFTyfJJh7jxxnE744VIQ5S/x/S3ra5DcmletG1aaFViHQs0+S2Qa
hsrcpGioktLV88kC2XwJYAAiTTZ3qvZgc44xV2kG4eGIVWUWBvXEqsvICqCbxxqa
c7CBX0bSDW+/nV78+een56FXIxcmEK4hTdpsL2KfVjbf0cRCnEkY1lyhBtzL+KqM
R73o+aG3Ab/gqFVHKHW0ie3cuo3frvbjF9DJf2OoBmmHo+r/HzoU5dnlFMdM/8PN
oOvkWT2bHpFjfB+ir/253Bbtg9CNdUIgGNwJ3/mrbATZ35W5bILe68IQtFHnObVn
V0ecXhnFJWhhtyawmbjc4cY2eDNfmeulNFJIPgDRrhmRrS/Guaqqj6RPWgLZ8Fd5
CaZf/DHShLlsJNhu/l3kMLgvVbUrbOZIGR3L1mgL3tTGAsIEG89EJH0Ge0KNDLvQ
2qcD5wH+/ZmzMzsPbHOw+IsjGlpIH49IZzrsJKMxEsw4JfYQTHh/Ws2Y6VCIvT+R
adOOSO+lyCgyUbXd7FS+hw+Yq3xUS4U9V2O4c/yinzI2vkS8paoXnPN0Qf5Brn/6
s/eBNqcBbYHSKuiKGfYU
=G0Bu
-----END PGP SIGNATURE-----https://gitlab.torproject.org/legacy/trac/-/issues/26044Create a new Tor Browser signing subkey2020-06-16T00:46:03ZGeorg KoppenCreate a new Tor Browser signing subkeyThe currently used Tor Browser signing subkey expires in August. We should get a fresh one and use it in the next alpha.The currently used Tor Browser signing subkey expires in August. We should get a fresh one and use it in the next alpha.https://gitlab.torproject.org/legacy/trac/-/issues/25909disable updater telemetry2020-06-16T00:45:49ZMark Smithdisable updater telemetryBetween Firefox ESR 52 and ESR 60, Mozilla added telemetry pings to the updater codepaths. Unfortunately, some pings are not correctly disabled when telemetry is disabled.Between Firefox ESR 52 and ESR 60, Mozilla added telemetry pings to the updater codepaths. Unfortunately, some pings are not correctly disabled when telemetry is disabled.https://gitlab.torproject.org/legacy/trac/-/issues/25220Look into rust (cross-)compilation on all supported platforms2020-06-16T00:43:58ZboklmLook into rust (cross-)compilation on all supported platformsFirefox 60 will include some parts in Rust, so we should be able to (cross-)compile rust, with reproducible builds, on all our supported platforms.Firefox 60 will include some parts in Rust, so we should be able to (cross-)compile rust, with reproducible builds, on all our supported platforms.https://gitlab.torproject.org/legacy/trac/-/issues/24476make_full_update.sh and make_incremental_update.sh should do a "set -e"2020-06-16T00:42:38Zboklmmake_full_update.sh and make_incremental_update.sh should do a "set -e"The scripts `make_full_update.sh` and `make_incremental_update.sh` from the directory `tor-browser.git/tools/update-packaging` are missing a `set -e`, which would make it easier to detect failures. Currently if there is an error in the s...The scripts `make_full_update.sh` and `make_incremental_update.sh` from the directory `tor-browser.git/tools/update-packaging` are missing a `set -e`, which would make it easier to detect failures. Currently if there is an error in the script, an error is printed in the logs, but the script still exits with 0.https://gitlab.torproject.org/legacy/trac/-/issues/23930Tor Browser 7.x for Mac crashes at startup2020-06-16T13:40:38ZTracTor Browser 7.x for Mac crashes at startupRunning OS X El Capitan (10.11.6) on a MacBook Pro (17 inch, Mid 2009)
Tor Browser up to 6.x was running fine.
Tor Browser 7.x for Mac always crashes at start. I tried the stable and experimental versions. No luck.
Error message: Tor Br...Running OS X El Capitan (10.11.6) on a MacBook Pro (17 inch, Mid 2009)
Tor Browser up to 6.x was running fine.
Tor Browser 7.x for Mac always crashes at start. I tried the stable and experimental versions. No luck.
Error message: Tor Browser quit unexpectedly.
I can run Firefox ESR 52.4.1 (64 bit) without problems on my Mac.
**Trac**:
**Username**: wgahttps://gitlab.torproject.org/legacy/trac/-/issues/22564Hide firefox sync2020-06-15T23:44:54ZTracHide firefox syncTor browser bundle has filefox sync under the menu button and then click sync'ed tabs. and it should be removed to protect users form accidentally enabling it and revealing there search history.
**Trac**:
**Username**: DbryrtfbcbhgfTor browser bundle has filefox sync under the menu button and then click sync'ed tabs. and it should be removed to protect users form accidentally enabling it and revealing there search history.
**Trac**:
**Username**: Dbryrtfbcbhgfhttps://gitlab.torproject.org/legacy/trac/-/issues/22451about:cache is not useful anymore in ESR52-based Tor Browser (only wyciwyg-UR...2020-06-15T23:44:23ZGeorg Koppenabout:cache is not useful anymore in ESR52-based Tor Browser (only wyciwyg-URIs if at all any)I wanted to investigate #21689 and started to look at `about:cache` output to check for isolation keys. But to my surprise there is only garbage in it (in e10s mode), meaning all URLs start with the wyciwyg scheme, or nothing at all (in ...I wanted to investigate #21689 and started to look at `about:cache` output to check for isolation keys. But to my surprise there is only garbage in it (in e10s mode), meaning all URLs start with the wyciwyg scheme, or nothing at all (in non-e10s-mode).
After re-reading #9336 I suspect the cached elements are basically not showing up in e10s mode either but instead some weird wyciwyg incarnations.
Now, I tested manually that things are still cached and that cache isolation seems to be working which is a good thing. But we should investigate and fix this issue as it is highly confusing and might conceal bugs we would otherwise see.https://gitlab.torproject.org/legacy/trac/-/issues/22125Unit test for js locale2020-06-15T23:43:23ZArthur EdelsteinUnit test for js localeLet's introduce an automated regression test to ensure that the `javascript.use_us_english_locale` pref is applied to
* members of `window.Date` objects
* Intl API
* toLocaleString
* `DateTimeFormat.formatToParts`
I can work on this at ...Let's introduce an automated regression test to ensure that the `javascript.use_us_english_locale` pref is applied to
* members of `window.Date` objects
* Intl API
* toLocaleString
* `DateTimeFormat.formatToParts`
I can work on this at some point. The problem is that we need to set the LANG variable to de_DE or another non-en_US locale before starting Firefox. Maybe boklm's testing framework can do this? Or maybe it's possible in Mozilla's automated testing system, but I don't know a way yet.https://gitlab.torproject.org/legacy/trac/-/issues/21851Revert some of #18915 changes (search box)2020-06-15T23:42:29ZArthur EdelsteinRevert some of #18915 changes (search box)Following #21309, we may be able to revert some of the #18915 changes.Following #21309, we may be able to revert some of the #18915 changes.https://gitlab.torproject.org/legacy/trac/-/issues/21727Investigate network ID feature in ESR 522020-06-15T23:41:43ZGeorg KoppenInvestigate network ID feature in ESR 52Mozilla landed a network identification ID feature in Firefox 49 (https://bugzilla.mozilla.org/show_bug.cgi?id=1240932). We probably don't want that. At least we should investigate it closer and maybe don't let an ID get computed at leas...Mozilla landed a network identification ID feature in Firefox 49 (https://bugzilla.mozilla.org/show_bug.cgi?id=1240932). We probably don't want that. At least we should investigate it closer and maybe don't let an ID get computed at least when Telemetry is disabled.
Note: this has probably consequences for (Linux) sandboxing at least as it needs access to /proc/net/arp.https://gitlab.torproject.org/legacy/trac/-/issues/21689RequestCache from the Fetch API is available, make sure it adheres to our cac...2020-06-15T23:44:23ZGeorg KoppenRequestCache from the Fetch API is available, make sure it adheres to our cache isolationRequestCache from the Fetch API got implemented (https://bugzilla.mozilla.org/show_bug.cgi?id=1120715). We should make sure it does not interfere with our concept of isolated cache entries.RequestCache from the Fetch API got implemented (https://bugzilla.mozilla.org/show_bug.cgi?id=1120715). We should make sure it does not interfere with our concept of isolated cache entries.https://gitlab.torproject.org/legacy/trac/-/issues/21657Test to make sure we isolate or disable all speculative connects2020-07-19T04:47:39ZArthur EdelsteinTest to make sure we isolate or disable all speculative connectsThere are a variety of "resource hint" features in Tor Browser that we want to make sure are isolated by first-party or disabled. These include
```
link rel=preconnect
link rel=prefetch
link rel=prerender
```
and possibly more.
We ...There are a variety of "resource hint" features in Tor Browser that we want to make sure are isolated by first-party or disabled. These include
```
link rel=preconnect
link rel=prefetch
link rel=prerender
```
and possibly more.
We should test this for the ESR45 and ESR52 versions of Tor Browser, because isolation will have different mechanisms.
See https://w3c.github.io/resource-hints/
We should also look into "SpeculativeConnect" code in Firefox to make sure there aren't any other cases of non-first-party isolated connections.https://gitlab.torproject.org/legacy/trac/-/issues/21542use Subprocess.jsm to launch tor2020-06-13T17:43:33ZMark Smithuse Subprocess.jsm to launch torIn Firefox 49, Mozilla added a new Subprocess.jsm module (they use it to implement the WebExtensions Native Messaging API). Kathy and I have not looked at it closely yet, but this module may provide a better way for Tor Launcher to start...In Firefox 49, Mozilla added a new Subprocess.jsm module (they use it to implement the WebExtensions Native Messaging API). Kathy and I have not looked at it closely yet, but this module may provide a better way for Tor Launcher to start and manage the tor process. In particular, Subprocess.jsm provides access to stderr which would allow Tor Launcher to capture all output produced by tor.
Docs:
http://gecko.readthedocs.io/en/latest/toolkit/modules/subprocess/toolkit_modules/subprocess/Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/18287Use SHA-2 signature for Tor Browser setup executables2020-06-15T23:33:13ZGeorg KoppenUse SHA-2 signature for Tor Browser setup executablesAs tjr mentioned in #17870 we only use SHA-1 when signing our Windows setup executables and should switch to SHA-2 or, better, provide both SHA-1 for older systems and SHA-2 for newer ones. Mozilla tried to deal with it in https://bugzil...As tjr mentioned in #17870 we only use SHA-1 when signing our Windows setup executables and should switch to SHA-2 or, better, provide both SHA-1 for older systems and SHA-2 for newer ones. Mozilla tried to deal with it in https://bugzilla.mozilla.org/show_bug.cgi?id=1079858 which might be a good starting point for solving this bug.https://gitlab.torproject.org/legacy/trac/-/issues/16341Investigate fingerprinting potential of CanvasRenderingContext2D.filter2020-06-15T23:26:46ZGeorg KoppenInvestigate fingerprinting potential of CanvasRenderingContext2D.filterhttps://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/filter got added in Firefox 35. We should investigate its fingerprinting potential. This can at least wait until we prepare an ESR 45 based release as this feature...https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/filter got added in Firefox 35. We should investigate its fingerprinting potential. This can at least wait until we prepare an ESR 45 based release as this feature is still behind a preference in ESR 38 (`canvas.filters.enabled` is set to `false`)https://gitlab.torproject.org/legacy/trac/-/issues/14205Closely review all uses of IsCallerChrome() for e10s2020-06-15T23:27:59ZMike PerryClosely review all uses of IsCallerChrome() for e10sA lot of our fingerprinting patches depend upon the accuracy is nsContentUtils::IsCallerChrome() to determine if it is content window or browser chrome accessing fingerprinting information.
IsCallerChrome() kind of scares me, and has h...A lot of our fingerprinting patches depend upon the accuracy is nsContentUtils::IsCallerChrome() to determine if it is content window or browser chrome accessing fingerprinting information.
IsCallerChrome() kind of scares me, and has had issues for unexpected contexts like WebWorkers (See #13027).
We should keep a close eye on this as we transition to e10s support post FF38, as who knows that the child/parent context relationship changes may do to various codepaths.Mark SmithMark Smith