tbb-dev September 2016

tbb-dev@lists.torproject.org

9 participants
8 discussions

Re: [tbb-dev] Let's organize a team meeting in Seattle!
by Nathan Freitas 27 Sep '16

27 Sep '16

On Sun, Sep 25, 2016, at 08:13 PM, isabela(a)riseup.net wrote: > On 9/25/16 10:31 AM, isabela(a)riseup.net wrote: > >> I am proposing either 10:15am (it should be a 30min meeting) or at noon > >> - what is a good time? > > Ok we picked 10:15am for our sync! We can find each other at the event > place and sit in a corner or go to a place where we can chat. I hope/plan to join to represent the small, but growing, Tor Browser mobile efforts, though I am happy just to listen in and absorb knowledge. +n

2 1

Let's organize a team meeting in Seattle!
by isabela＠riseup.net 26 Sep '16

26 Sep '16

Hi there! Me and Geko were talking about organizing a team meeting for Seattle outside of the 'gunner days' so we can meet as a team and discuss topics that affects the team day to day life. I will help organize and facilitate this meeting since Geko won't be coming to Seattle #sadface. To prepare for this meeting, we thought of us having a quick chat as a team on Monday morning - during the hacking hours prior to the community meeting (which starts at 1:30pm). I am proposing either 10:15am (it should be a 30min meeting) or at noon - what is a good time? Then we would decide on a time on Thursday where we could actually have a longer meeting (around 1 to 1:30 hrs) to discuss roadmap (new deliverables from proposals we sent out), new hiring, team retrospective and so on. Here is a place where we can organize the discussion topics for the team meeting: https://trac.torproject.org/projects/tor/wiki/org/teams/ApplicationsTeam/Te… (ps: more items will be added in the wiki for the roadmap part of it) Cheers, Isabela

1 2

TBB 6.0.5 / screen resolution and color depth
by scar 25 Sep '16

25 Sep '16

if javascript is allowed, according to http://www.whatismyscreenresolution.com/ and https://panopticlick.eff.org/ the size of the TBB window is reported back. if the size of the window is changed, the new size is reported to the test sites, making the browser fingerprint more unique. if i maximize the TBB window, i receive a warning about tracking, but again the size reported back to the test sites isn't the screen's resolution but still the window size. seems to me this value should be spoofed to some common value like 1024x768 no matter what size the TBB window is

3 5

No meeting on Monday, September 26
by Georg Koppen 22 Sep '16

22 Sep '16

Hi, due to the dev meeting next week in Seattle, we will cancel the Tor Browser meeting. The next regular Tor Browser meeting will be on October 3, 18:00 UTC in #tor-dev. Georg

1 0

Please come help us
by Dave Huseby 16 Sep '16

16 Sep '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi TBB devs, I have a favor to ask. We at Mozilla are trying to uplift as many of the TBB patches into the Mozilla central repo before we fork the next ESR on, or around, November 7th, 2016. The Mozilla engineers currently working on this are focused on implementing and debugging our new first party isolation mechanism. That leaves another 18 bugs that need to be uplifted that aren't related to first party isolation. That's where you come in. We would really appreciate any help you can give us in uplifting the patches. The list of bugs is here: https://is.gd/tbT10I Here's the general "how to": 0) (optional) if you don't have one, create a bugzilla account. if you don't want to do that, you may just email me the patches for review and landing. 1) assign the bug to yourself and mark it as "assigned". 2) go to https://torpat.ch/<tor trac number> to get the diffs. the trac numbers are in most of the bugs. (if you're using git with moz central you can directly cherry pick the revisions from the tbb repo). 3) add a new pref to firefox and set it to disabled by default. we've been putting them under privacy.* mostly. 4) refactor the patch so that the new functionality only works when the pref is enabled. the one exception is if it is a bug fix, then a pref is probably not needed. 5) submit the updated patch for review and landing. That's it! Thank you ahead of time for any of you that jump in to help. The more patches we get uplifted, the smaller, and quicker, the next Tor Browser rebase will be. - --dave -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJX3GqeAAoJEJ7v31qiCP4gBCcP/RKfCi2QYiUAfI7g+dherVQS +imTY+P2uopN/BbLYEntFTJe/lRhmboq/BoQau714mIVatCnnhATyWF+Jt9JIeAn m23Hcu0lDusL0N1pfmMlnrKyZFuWpCl5RVh+iIeGNdDF2kcRCGHM+YG3waXA7DfQ Mj3jwFk00YlSw8MbmFTbhqPAjZmLM5zzVzG/TXmj0eiZZmvD1q/1LEST5tqxcnfn LbtYYtqu5p6fGFaCdzZdY3GqzJIHVr2FieBEEekoJDWwVX16Aq/7qA+WDH38vBUy oaRpYHNCnXDXXiNNKbLwNVcxPEeDNJl3NuKM2nlnZzuufMxTa2SCjJUotTAUR9Vz Jr5m7ViNmiKEIf6tNGXRlQo5vxZ2irh3z2bVE6QtOdO5fM1WHG38Pm+9KoE7KVoI HAcmNDncvRaFSqY7mlE5zmAtPyyN+f1gTKo68+Vk89uO8t5m4hpFLRobRtvBrDoI Fvt597F+Kjp6Xui7LcSdPTFLB+4KUHFh1Y2FhoQDLy2Op8eoB1x5jf4R7eEydd7f m1yY9yJQeKaVRyk+eTJpuvgTl+pQlgaOTMAfDvfWPlbnY8cISjf17XCLqHu+51l1 kKRqnshhjJcvPmrTJXWZEqEm/71Ko+PoC2R905S5YLEw5z/71r8lZvLvH2DSaUgg i+Cgh/9zmaC2ze3jJGVF =ds05 -----END PGP SIGNATURE-----

1 0

nightly failure
by Linus Nordberg 12 Sep '16

12 Sep '16

Hi, The 'nightly' build has been failing for me the last couple of days. Due to a bug in the continous-build-hack we haven't recevied any emails with the contents of any log files as we used to. Here's one failure. I don't know if there are others too. --8<---------------cut here---------------start------------->8--- make[1]: Leaving directory `/home/debian/build/libevent' + cd .. + tar xzf openssl.tar.gz + cd openssl-1.0.2h openssl-Make-build-reproducible.patch + patch -p1 patching file crypto/cversion.c Hunk #1 FAILED at 68. 1 out of 1 hunk FAILED -- saving rejects to file crypto/cversion.c.rej --8<---------------cut here---------------end--------------->8--- Looking into fixing the mail issue later at some point.

2 1

How Tor Browser interacts with Tor source code
by Liu, Zhuotao 11 Sep '16

11 Sep '16

Hi Folks, This is Zhuotao from University of Illinois. I have a problem of understanding how Tor browser interacts with the Tor source code. My understanding is that in order to use Tor, there much be a Tor client instance running locally. But when using Tor browser, I did not notice the existence of Tor client at all (which is good for usability). However, I do not understand how the Tor browser interacts with Tor client in background? Any idea is greatly appreciated. :) Thanks, Zhuotao

2 2

pseudo-hosts for first party isolation?
by Arthur D. Edelstein 06 Sep '16

06 Sep '16

Hi Everyone, Yoshi asked me about first-party isolation of various kinds of top-level content, including: data:, chrome:, resource:, about:, javascript: URLs. Should Mozilla generate first-party "pseudo-hosts" for these as we have in Tor Browser? What are the pros and cons? Here's the bug -- feel free to comment directly: https://bugzilla.mozilla.org/show_bug.cgi?id=1300671 Thanks, Arthur

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

tbb-dev September 2016