The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-27T14:42:12Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11774Refactor common gitian bash functions into a library script2020-06-27T14:42:12ZMike PerryRefactor common gitian bash functions into a library scriptWe're starting to duplicate gitian functions in multiple scripts. This is bad form. We should refactor all common functions into a single library script that gets sourced from each Makefile-invoked script.We're starting to duplicate gitian functions in multiple scripts. This is bad form. We should refactor all common functions into a single library script that gets sourced from each Makefile-invoked script.Mike PerryMike Perryhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11517Ukrainian Tor Browser Bundle2022-07-15T11:08:06ZColin ChildsUkrainian Tor Browser BundleA few users have contacted RT requesting a Ukrainian Tor Browser Bundle. These strings have been translated by our Ukrainian translators on Transifex.A few users have contacted RT requesting a Ukrainian Tor Browser Bundle. These strings have been translated by our Ukrainian translators on Transifex.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11511Investigate why TorLauncher is sometimes not loaded when starting TBB2022-01-11T19:33:18ZGeorg KoppenInvestigate why TorLauncher is sometimes not loaded when starting TBBNot sure how to frame this but it seems there is the possibility that the Tor Browser Bundle is not proper working at least on some Linux machines: on #tor on Saturday there was a user, aurel, who extracted a fresh 64bit TBB 3.5.4 but co...Not sure how to frame this but it seems there is the possibility that the Tor Browser Bundle is not proper working at least on some Linux machines: on #tor on Saturday there was a user, aurel, who extracted a fresh 64bit TBB 3.5.4 but could not start browsing. The reason was that about:addons showed a missing TorLauncher. We should investigate how this can happen.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11466Only blank PNG files are visible in thumbnails folder after disabling private...2020-06-27T14:42:12ZGeorg KoppenOnly blank PNG files are visible in thumbnails folder after disabling private browsing modeInstead of thumbnails of previously visited sites only blank PNG files are visible after disabling private browsing mode. The expected behavior is probably to see the real thumbnails.Instead of thumbnails of previously visited sites only blank PNG files are visible after disabling private browsing mode. The expected behavior is probably to see the real thumbnails.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11459libfaketime causes the build system to report being not sane2020-06-27T14:42:12ZGeorg Koppenlibfaketime causes the build system to report being not sanelibfaketime causes build systems to report that they are not sane which can easily lead to an endless loop or at least to a much longer build time. This is only an issue if more than one core is used for building the TBBs.libfaketime causes build systems to report that they are not sane which can easily lead to an endless loop or at least to a much longer build time. This is only an issue if more than one core is used for building the TBBs.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11449Torbutton New Identity error with regard to NoScript2020-06-27T14:42:13ZTracTorbutton New Identity error with regard to NoScriptError reads:
Torbutton: Error clearing NoScript Temporary Permissions: TypeError: Components.classes['@maone.net/noscript-service;1'] is undefined
I'll be monitoring this bug to give feedback as needed.
I think I'm running 3.6 but I m...Error reads:
Torbutton: Error clearing NoScript Temporary Permissions: TypeError: Components.classes['@maone.net/noscript-service;1'] is undefined
I'll be monitoring this bug to give feedback as needed.
I think I'm running 3.6 but I might be running the latest PT bundle. Hard to tell! Filing another bug about that :/
Thanks!
**Trac**:
**Username**: Cypherpunkshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11439Vertical monitor leads to fingerprintable default screen size2020-06-27T14:42:13ZcypherpunksVertical monitor leads to fingerprintable default screen sizeWhen starting TBB 3.5.3 with a vertically oriented monitor, my default window size is highly identifiable - even though it is rounded to 100px. (size is 1000x1700x24)
Deleting the tor_browser directory and extracting a new version did n...When starting TBB 3.5.3 with a vertically oriented monitor, my default window size is highly identifiable - even though it is rounded to 100px. (size is 1000x1700x24)
Deleting the tor_browser directory and extracting a new version did not fix this issue.
Attempting to resize the window manually leads to odd (not round) values that are also identifiable.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11425Tor cannot be used to watch netflix on 64bit windows2020-06-27T14:42:13ZTracTor cannot be used to watch netflix on 64bit windowsI'm away at a conference and thought I could protect my netflix account by using TOR to watch.
Unfortunately Netflix complains that Silverlight is not installed. The link netflix provides within tor is for a 32 bit silverlight which ref...I'm away at a conference and thought I could protect my netflix account by using TOR to watch.
Unfortunately Netflix complains that Silverlight is not installed. The link netflix provides within tor is for a 32 bit silverlight which refuses to install because a 64 bit is already installed.
I'm using Tor Browser Bundle 3.5.3 -- Mar 19 2014
**Trac**:
**Username**: kwgagelhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11420Expand gitian/check-prerequisites.sh tests2020-06-27T14:42:13ZTracExpand gitian/check-prerequisites.sh testscheck-prerequisites.sh should include logic to test for known build requirements:
AMD64 architecture
Enough RAM memory
Enough disk storage
Assuming that builds on IA32 VMs (using LXC) and bare metal build environments fail due to the c...check-prerequisites.sh should include logic to test for known build requirements:
AMD64 architecture
Enough RAM memory
Enough disk storage
Assuming that builds on IA32 VMs (using LXC) and bare metal build environments fail due to the current OSX cross-compile toolchain and/or linking of libxul.so, check-prerequisites.sh should include (pseudocode):
uname -m | grep -q x86_64 ~|~| echo 'Wrong CPU arch!'
Assuming a minimum 4Go RAM build requirement, check-prerequisites.sh should include (pseudocode):
free -g | grep Mem | sed(1)/awk(1)
Assuming a minumum 48Go disk storage requirement, check-prerequisites.sh should include (pseudcode):
pwd(1)/mount(1)/df(1) script code to determine max storage in current path.
NOTE: These requirements depend on other variables, at the very least whether KVM or LXC is in use (already determined by check-prerequisites.sh.
Lastly, once these requirements are sorted out they should be documented (separate ticket) in or near [1] for human consumption.
[1] https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking/
**Trac**:
**Username**: michaelhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11383TBB says it is not updated when it is2020-06-27T14:42:13ZTracTBB says it is not updated when it isTor Browser Bundle 3.5.3 for Windows in Spanish is the latest available (at the moment) non-beta version. But the user on ticket RT.23442 reports its TBB says it must be updated.
**Trac**:
**Username**: EnviteTor Browser Bundle 3.5.3 for Windows in Spanish is the latest available (at the moment) non-beta version. But the user on ticket RT.23442 reports its TBB says it must be updated.
**Trac**:
**Username**: Envitehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11371Tor Browser doesn't work on OSX 10.8.5 - Mountain Lion2020-06-27T14:42:13ZcypherpunksTor Browser doesn't work on OSX 10.8.5 - Mountain LionInteresting that an older Tor Browser works, but the latest one doesn't. Would you please open a new bug ticket on bugs.torproject.org describing the details of your experiment?
I am using OSX 10.8.5 - Mountain Lion (not Mavericks for p...Interesting that an older Tor Browser works, but the latest one doesn't. Would you please open a new bug ticket on bugs.torproject.org describing the details of your experiment?
I am using OSX 10.8.5 - Mountain Lion (not Mavericks for performance reasons) with my OSX firewall on AND with Sophos antivirus 9.0.8. I do not want to relax these settings for security reasons.
I am successfully playing with Vidalia 0.2.21 & TOR 0.2.4.9-alpha (git-23dd7c901287d7d8) Qt 4.8.1 (TorBrowser-2.4.9-alpha-1-osx-i386-en-US.zip) -- which DOES work. This is the old version with separate Vidalia and the old Firefox browser.
However, when today I installed the CURRENT version of TOR (TorBrowserBundle-3.5.3-osx32_en-US.zip), it would not work. The TorButton onion turns green but I am not actually making any kind of network connection:
Here are the logs:
3/29/14 19:26:05.157 [NOTICE] Opening Socks listener on 127.0.0.1:9150
3/29/14 19:26:05.157 [NOTICE] Renaming old configuration file to "/Applications/Privacy/TorBrowserBundle_en-US.app/Data/Tor/torrc.orig.1"
3/29/14 19:26:05.490 [NOTICE] Bootstrapped 5%: Connecting to directory server.
3/29/14 19:26:05.490 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server.
3/29/14 19:26:05.621 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection.
3/29/14 19:26:05.741 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus.
3/29/14 19:26:05.790 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus.
3/29/14 19:26:06.306 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
3/29/14 19:26:07.110 [NOTICE] Bootstrapped 40%: Loading authority key certs.
3/29/14 19:26:07.587 [NOTICE] Bootstrapped 45%: Asking for relay descriptors.
3/29/14 19:26:07.588 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/5570, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw.)
3/29/14 19:26:08.655 [NOTICE] Bootstrapped 50%: Loading relay descriptors.
3/29/14 19:26:09.320 [NOTICE] Bootstrapped 51%: Loading relay descriptors.
3/29/14 19:26:09.155 [NOTICE] Bootstrapped 53%: Loading relay descriptors.
3/29/14 19:26:09.269 [NOTICE] Bootstrapped 55%: Loading relay descriptors.
3/29/14 19:26:09.332 [NOTICE] Bootstrapped 57%: Loading relay descriptors.
3/29/14 19:26:09.332 [NOTICE] Bootstrapped 59%: Loading relay descriptors.
3/29/14 19:26:09.388 [NOTICE] Bootstrapped 61%: Loading relay descriptors.
3/29/14 19:26:09.443 [NOTICE] Bootstrapped 63%: Loading relay descriptors.
3/29/14 19:26:09.444 [NOTICE] Bootstrapped 65%: Loading relay descriptors.
3/29/14 19:26:09.504 [NOTICE] Bootstrapped 67%: Loading relay descriptors.
3/29/14 19:26:09.546 [NOTICE] Bootstrapped 68%: Loading relay descriptors.
3/29/14 19:26:09.546 [NOTICE] Bootstrapped 70%: Loading relay descriptors.
3/29/14 19:26:09.560 [NOTICE] Bootstrapped 72%: Loading relay descriptors.
3/29/14 19:26:09.593 [NOTICE] Bootstrapped 74%: Loading relay descriptors.
3/29/14 19:26:09.620 [NOTICE] Bootstrapped 76%: Loading relay descriptors.
3/29/14 19:26:09.653 [NOTICE] Bootstrapped 78%: Loading relay descriptors.
3/29/14 19:26:36.449 [NOTICE] We now have enough directory information to build circuits.
3/29/14 19:26:36.449 [NOTICE] Bootstrapped 80%: Connecting to the Tor network.
3/29/14 19:26:36.449 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit.
3/29/14 19:26:39.255 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
3/29/14 19:26:39.255 [NOTICE] Bootstrapped 100%: Done.
3/29/14 19:26:40.988 [NOTICE] New control connection opened.
3/29/14 19:28:40.438 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
3/29/14 19:28:43.435 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11362"amd64 lucid VM creation failed" with virtualized LXC build on Ubuntu 12.04.42020-06-27T14:42:13ZDavid Fifielddcf@torproject.org"amd64 lucid VM creation failed" with virtualized LXC build on Ubuntu 12.04.4I got an error with [gitian-builder tor-browser-builder-3.x-5](https://gitweb.torproject.org/builders/gitian-builder.git/tag/refs/tags/tor-browser-builder-3.x-5) and [tor-browser-bundle tbb-3.5.3-build1](https://gitweb.torproject.org/bui...I got an error with [gitian-builder tor-browser-builder-3.x-5](https://gitweb.torproject.org/builders/gitian-builder.git/tag/refs/tags/tor-browser-builder-3.x-5) and [tor-browser-bundle tbb-3.5.3-build1](https://gitweb.torproject.org/builders/tor-browser-bundle.git/tag/refs/tags/tbb-3.5.3-build1) when I tried an LXC build inside KVM. The i386 linux VM image built okay, but then there was a failure in building the amd64 linux image:
```
lxc-start: failed to spawn 'gitian'
amd64 lucid VM creation failed
```
(See full log in comment:1.)
I was running inside a KVM-virtualized installation of ubuntu-12.04.4-server-amd64.iso.
```
$ uname -a
Linux ubuntu 3.11.0-18-generic #32~precise1-Ubuntu SMP Thu Feb 20 17:52:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
```
boklm on IRC reported that they had built using virtualized LXC within the last week. They are using ubuntu-12.04.4-desktop.iso with 3.11.0-15-generic!legacy/trac#25~precise1-Ubuntu. Perhaps my use of "server" rather than "desktop" makes the difference; I didn't try the "desktop" ISO. boklm said that they didn't have the `Cgroup namespace: required` error below.
Some web searching led me to check the output of the lxc-checkconfig command. The line that stands out as erroneous is `Cgroup namespace: required`. It appears red in the terminal and is the only line that appears red.
```
$ lxc-checkconfig
Kernel config /proc/config.gz not found, looking in other places...
Found kernel config file /boot/config-3.11.0-18-generic
--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: missing
Network namespace: enabled
Multiple /dev/pts instances: enabled
--- Control groups ---
Cgroup: enabled
Cgroup namespace: required
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: missing
Cgroup cpuset: enabled
--- Misc ---
Veth pair device: enabled
Macvlan: enabled
Vlan: enabled
File capabilities: enabled
Note : Before booting a new kernel, you can check its configuration
usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
```
These links may be relevant:
* [Bug #1191600 User namespace is not enabled in raring kernel](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600)
* [Question #223671 lxc-checkconfig / Cgroup namespace: required](https://answers.launchpad.net/ubuntu/+source/lxc/+question/223671)
* [Example fails on today's Ubuntu 13.04 daily](https://lwn.net/Articles/541787/)
The lxc-checkconfig output may be a red herring, because after all I was able to make the i386 image. (Then again, boklm didn't have the same lxc-checkconfig error.) I tried commenting out the building of the i386 image so that the amd64 would be built first, and it still failed.
Some time back we had a problem that was resolved by removing linux-generic-lts-saucy (backported kernel from a newer Ubuntu, installed by default in 12.04.4) and replacing it with linux-generic-lts-quantal. I tried that and it didn't work.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11298Login button on weather.yahoo.com is only visible if browser window gets resized2020-06-27T14:42:14ZGeorg KoppenLogin button on weather.yahoo.com is only visible if browser window gets resizedIf one loads weather.yahoo.com the login button is shortly visible but vanishes quickly. It turns out that the width of 1000px is not enough to display the portion of the page where the login button is. Resizing on the other hand destroy...If one loads weather.yahoo.com the login button is shortly visible but vanishes quickly. It turns out that the width of 1000px is not enough to display the portion of the page where the login button is. Resizing on the other hand destroys the window size fingerprinting defense we currently have.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11295Users cannot log into LycosMail2020-06-27T14:42:14ZGeorg KoppenUsers cannot log into LycosMailWe got a report that logging into LycosMail is not working: https://blog.torproject.org/blog/tor-browser-bundle-35-released?page=1#comment-43008We got a report that logging into LycosMail is not working: https://blog.torproject.org/blog/tor-browser-bundle-35-released?page=1#comment-43008https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11294Users are not able to log into https://unseen.is2020-06-27T14:42:14ZGeorg KoppenUsers are not able to log into https://unseen.isThere are reports that users are not able to log into unseen.is (see legacy/trac#10569 for some comments).There are reports that users are not able to log into unseen.is (see legacy/trac#10569 for some comments).https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11293Users are not able to log into http://www.bouyguestelecom.fr/mon-compte/2020-06-27T14:42:14ZGeorg KoppenUsers are not able to log into http://www.bouyguestelecom.fr/mon-compte/Quoting Lunar From the original bug entry (legacy/trac#10569):
```
The user told me they were unable to login. They got an error message mentioning a bad cookie. I told them to deactivate Private Browsing Mode and then they were successf...Quoting Lunar From the original bug entry (legacy/trac#10569):
```
The user told me they were unable to login. They got an error message mentioning a bad cookie. I told them to deactivate Private Browsing Mode and then they were successfully able to login.
I unfortunately don't have credentials for that site.
```https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11287Torbutton preferences not saving changes.2020-06-27T14:42:14ZTracTorbutton preferences not saving changes.Using browser bundle 3.5.3-Windows
In the preferences menu of the Torbutton, under Security Settings:
The "Disable Browser plugins (such as Flash)" does not remain unchecked.
The other options work as intended.
The issue was encounte...Using browser bundle 3.5.3-Windows
In the preferences menu of the Torbutton, under Security Settings:
The "Disable Browser plugins (such as Flash)" does not remain unchecked.
The other options work as intended.
The issue was encountered while modifying the bundle for bbc iplayer access.
**Trac**:
**Username**: pyritehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11268Encourage webroot antivirus to scan TBB releases2020-06-27T14:42:14ZRoger DingledineEncourage webroot antivirus to scan TBB releasesEvery time we put out a new TBB, it seems like there are a pile of Webroot users who show up with cryptic complaints like "Couldn't load XPCOM."
Skruffy is pretty sure that showing our TBB releases to Virustotal (legacy/trac#11263) isn'...Every time we put out a new TBB, it seems like there are a pile of Webroot users who show up with cryptic complaints like "Couldn't load XPCOM."
Skruffy is pretty sure that showing our TBB releases to Virustotal (legacy/trac#11263) isn't going to influence Webroot in any way.
We should find a contact at Webroot and encourage them to integrate "check TBB releases" into whatever internal process they have.
(This would be a great task for a volunteer.)boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11258Toggling permissions.memory_only causes crash of Tor Browser2020-06-27T14:42:14ZGeorg KoppenToggling permissions.memory_only causes crash of Tor BrowserWhile investigating legacy/trac#9531 I run into an other reason for crashing when hitting New Identity:
```
WARNING: NS_ENSURE_TRUE(asyncCloseWasCalled) failed: file /home/firefox/tor-browser/storage/src/mozStorageConnection.cpp, line 94...While investigating legacy/trac#9531 I run into an other reason for crashing when hitting New Identity:
```
WARNING: NS_ENSURE_TRUE(asyncCloseWasCalled) failed: file /home/firefox/tor-browser/storage/src/mozStorageConnection.cpp, line 943
Assertion failure: !mAsyncExecutionThread, at /home/firefox/tor-browser/storage/src/mozStorageConnection.cpp:415
Program ./Browser/firefox (pid = 30485) received signal 11.
```
Commenting out the code toggling "permissions.memory_only" seems to help.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11254Tor Browser bundle v3.5 fails to clean up cancelled downloads in Temp folder2020-06-27T14:42:15ZTracTor Browser bundle v3.5 fails to clean up cancelled downloads in Temp folder1. Run TBB v3.5.3
2. Click on a link to download an archive or any file type not natively handled by the browser
3. Wait for the download to complete
4. Observe that <random>.ext.part file is created containing entire file contents in th...1. Run TBB v3.5.3
2. Click on a link to download an archive or any file type not natively handled by the browser
3. Wait for the download to complete
4. Observe that <random>.ext.part file is created containing entire file contents in the system's %temp% folder.
4. In the Open/Save dialog box click Cancel.
5. Observe that the temp-created file is not removed.
6. Close Firefox/TBB.
7. Observe that the temp-created file is not removed.
Firefox 28's Private Mode does not have this bug.
I observed this bug in TBB v2.x as well.
**Trac**:
**Username**: ericlaw