tbb-dev July 2014

tbb-dev@lists.torproject.org

5 participants
7 discussions

Tor Browser self-updater vs. sandboxing
by intrigeri 22 Sep '14

22 Sep '14

Hi, while discussing opportunities for increased cooperation between Tails and Freepto [1] recently, I've mentioned the upcoming Tor Browser's self-updater, and one of the Freepto developers rightly noted that there may be a fundamental incompatibility between this updater, and the desire to confine the browser in a sandbox. Indeed, it seems quite clear to me that one of the important tasks such a sandbox should fulfill would be... to avoid the confined program from modifying itself. It seems that supporting such sandboxes is part of your plans ([2], [3]), so I'm curious: what's the TBB team's take on this problem? [1] http://www.freepto.mx/ [2] https://trac.torproject.org/projects/tor/wiki/org/sponsors/SponsorP [3] https://trac.torproject.org/projects/tor/ticket/5791 Cheers, -- intrigeri

2 2

stopgap fix for ticket #9516 (Show log in Tor Browser)
by Mark Smith 01 Aug '14

01 Aug '14

Is it is too late to include a small but possibly important Tor Launcher improvement in TB 3.6.4? Please take a look at: https://trac.torproject.org/projects/tor/ticket/9516#comment:7 If Mike and others think the change is useful, it would be trivial to merge this fix into Tor Launcher's maint-0.2.5 branch (for TB 3.6.4). -- Mark Smith Pearl Crescent http://pearlcrescent.com/

2 1

Missing the meeting today
by Nicolas Vigier 25 Jul '14

25 Jul '14

Hello, I will be travelling this afternoon (unfortunately, to go to the funeral of my grandmother), so I won't be able to attend the meeting today. On the weekly update, the main thing I have been doing this week is the setup of the rebuild of all tor browser commits for xpcshell testing: https://lists.torproject.org/pipermail/tbb-dev/2014-July/000096.html Nicolas

1 0

Running xpcshell tests
by Nicolas Vigier 25 Jul '14

25 Jul '14

Hello, I am currently investigating how we can run the Mozilla xpcshell tests on our version of firefox, and the other unit tests. The xpcshell tests are included on the firefox source tree, and require a complete build tree, built without the '--disable-tests' option. So we cannot run those tests on the version that is shipped in the bundle. To run those tests, I can see different options: 1. Run the tests as part of the gitian build process and save the output in a file that can be analyzed later. The bundle build process is already very long, and we probably don't want to make it even longer. Running the xpcshell tests on my laptop (i5-2520M CPU @ 2.50GHz) took 2.5 hours. So this is probably not a good idea. 2. Save the build tree in a tarball at the end of the build, and make it available with the bundle files. We can then use it to run the tests as part of our test suite. The main problem with this is that the obj directory at the end of the build is taking 6GB. It's possible to reduce it to a 888MB tar.xz file, but it takes 50 minutes to create it on my laptop. 3. Build the browser separatly, in the VM that we use for running the tests. We enough test VMs to be able to do that. This also allow us to run those tests on any commit. The main problem with this is that we are not running the tests on the same binaries that are shipped in the bundle. So I'm thinking about doing 3. Does anybody have any other idea or comment about this ? Nicolas

3 6

weekly update from Pearl Crescent
by Mark Smith 17 Jul '14

17 Jul '14

I assume there will be a TBB dev meeting tomorrow... unfortunately, neither member of the Pearl Crescent team (Kathy Brade and myself) will be able to attend. Here is a brief update from us: * Related to #4234 (Firefox updater), we commented in child bugs #12622 and #12623, we looked at what it will take to rebase our patches onto the TBB 4.0a1 builder and browser code, and we researched symlink support for the Firefox updater (and filed #12647). https://trac.torproject.org/projects/tor/ticket/12622 "Automate update package distribution for TBB updater" https://trac.torproject.org/projects/tor/ticket/12623 "Deploy our TBB update archives on a secure machine" https://trac.torproject.org/projects/tor/ticket/12647 "updater needs to support use of symlinks" * For Tor Launcher and Torbutton, we fixed the Tor Launcher portion of #11193 (new logo in the config wizard that omits the word "Bundle"), we debugged #12264 and handed it to Isis for a fix, and we spent a bit of time fixing #11472. https://trac.torproject.org/projects/tor/ticket/11193 "Change Tor Browser Bundle to Tor Browser in package strings, download pages, and docs" https://trac.torproject.org/projects/tor/ticket/12624 "tbb-nightly-2014-07-13 chokes with 'Bad password or authentication cookie on controller.'" https://trac.torproject.org/projects/tor/ticket/11472 "Onion logo and text on about:tor page may overlap in non en-US TBBs" We also tried to help test the patches for #12391 and we triaged several miscellaneous bugs. https://trac.torproject.org/projects/tor/ticket/12391 "Building mingw-w64 is failing intermittently" * Next week we plan to focus on #12647 (symlink support for the updater) and rebasing of our updater patches. If we are overlooking anything that is of higher priority, let us know, -- Mark Smith Pearl Crescent http://pearlcrescent.com/

1 0

Feedback from help desk
by Matt Pagan 14 Jul '14

14 Jul '14

We've gotten some angry emails from users who have installed Tor for Windows (expert bundle) and been unable to uninstall it. I can confirm that although this package seems to keep up with the stable Tor releases pretty well, it definitely needs some love. For example, shortcuts (including a shortcut to an uninstaller) on Desktop and Start Menu are dead links. C:\Program Files(x86)\Tor appears never to have been created, although the shortcuts do get created. I can understand why getting a "Windows is searching for Uninstall.exe" message would be frustrating. It's not even clear for me how this package is created. Where is the source code?

1 1

Missing the meeting today
by Mike Perry 11 Jul '14

11 Jul '14

Hello everyone, Sorry for the short notice, but I won't be able to make the meeting today. I spent most of the week following up on dev meeting items and traveling, so not much to report from me anyway. I should be able to read the backlog, but i suspect a few others (gk, erinn?) are also traveling/will be absent, so it may be a short meeting. -- Mike Perry

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

tbb-dev July 2014