19:00:12 #startmeeting tor-browser-dev 19:00:12 Meeting started Mon Jan 18 19:00:12 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:31 welcome to our weekly tor browser meeting 19:00:44 who wants to go first today for the status updates? 19:01:58 hi everyone 19:02:10 I can go if nobody else wants to ;) 19:02:26 This week I finished patches for #17965. 19:02:34 And I opened #18087. 19:02:46 I wrote a patch for #18030. 19:02:54 I worked on some manual tests for the font fingerprinting patch. 19:03:09 And I had a preliminary look at Kathy and Mark's patch for #18019. 19:03:20 This week I will post my font fingerprinting test results, 19:03:26 finish reviewing #18019, 19:03:31 and write a revised patch for #17790. 19:03:41 If there's time I will work on rebasing patches to ESR45. 19:04:08 that's it for me 19:05:00 could you get those fingerprinting test results assembled by tomorrow/wednesday? 19:05:25 that's probably when we finally need to decide what to do with the font fingerprinting defense 19:06:31 Yes, I think by Wednesday should be doable 19:06:56 Is there a specific thing you are concerned about regarding the font defense? 19:08:27 not a specific thing. i'd like to make sure that it works against the different attacks out there 19:08:38 on all platforms we support 19:09:22 OK. The main attack it defends against currently is font enumeration, which is what my test is checking. 19:09:36 i am particularly interested how we handle dcf's idea 19:10:10 what's the main font defense? reporting the fonts found on windows xp? 19:10:19 or some subset of fonts taht everybody has? 19:11:27 there isn't, because of the stupid fucking UI font issue >.> 19:11:46 sorry, windows makes me really mad 19:11:51 (me too) 19:11:59 * huseby can go 19:12:22 last week, i finished filing bugs for all of the remaining callsites for the origin attributes work i'm/we're doing 19:12:23 huseby: The font defense (patch from #13133) which we may apply to stable, restricts the allowed fonts for each platform. 19:12:31 Sorry, #13313 19:12:39 thx 19:12:44 And bundles some fonts, especially for Linux 19:12:45 problem is, there isn't a common set on certain windows locales that doesn't result in a fucked up UI 19:12:59 because the windows UI font has changed, basically every release 19:13:18 Yawning is correct. So we whitelist all needed UI fonts for now. 19:13:18 we're going through the process of writing patches for all of the callsites that create codebase principals 19:14:54 making sure that the origin attributes are handled correctly 19:15:02 making user contexts work properly 19:15:16 which will also make 1st/3rd party isolation work correctly when we uplift the patches from tor 19:15:30 that's it for me. 19:15:58 GeKo: Which of dcf's ideas do you mean? 19:17:36 the font glyph paper 2015 19:17:54 Fingerprinting Web Users through Font Metrics 19:18:58 okay, here is what i did last week: 19:19:36 i mainly tried to collect things for 5.5 some succesfully some not 19:20:22 in the latter category were #11506 and #13893 19:20:46 the latter was quite a timesink but we know now that EMET does not like mingw-w64 optimized code 19:21:12 i've written jacek an email and hope he is able to help us with this one and #9145 19:21:40 i've reviewed and merged some smaller patches 19:21:58 and am almost ready to post one for #18008 19:22:12 i am currently testing it and this should go into 5.5 as well 19:22:47 then i try to get #16322 into it as well 19:23:31 apart from that i am probably busy with reviews for 5.5 and 6.0a1 + the usual release related stuff 19:23:38 that's it for me 19:24:17 * mcs will go next 19:24:29 Last week, Kathy and I created patches for #17917, #18019, and #18064. 19:24:41 We reviewed patches for #18017 and #17428. 19:24:50 We triaged some Tor Browser bugs (the Trac “inflow” seems high lately). 19:24:56 We also posted our patch for #11773 (too late for TB 5.5 though). 19:25:02 We added a comment to the following Mozilla bug where they are thinking about just using plain HTTP to retrieve the updater XML manifest file in Firefox: 19:25:07 https://bugzilla.mozilla.org/show_bug.cgi?id=1239545 19:25:12 mikeperry added some even better comments to that bug report. 19:25:16 This week we will continue working on TB 5.5 issues and help get everything done for the release. 19:25:21 That’s all for us. 19:26:19 GeKo: Let us know if there is anything we need to do to help with #18008 19:26:24 mcs: if you could have a look at #17965 this week that would rock 19:26:27 i'll do 19:26:46 this way we could test that isolation in 6.0a1 19:27:59 We can take a look, but do we need to make a 6.0a1 release right away? 19:28:50 you mean using 5.5 for alpha as well? 19:29:32 we probably already have stuff that won't make it into 5.5 we might want to test 19:29:37 I mean alpha channel users would get the same TB 5.5 stable bits as release channel users for a little while. Maybe that is confusing to alpha testers? 19:29:44 OK; makes sense. 19:29:50 Just thought I would ask ;) 19:30:14 like #11773 19:30:42 It would be good to get #11773 merged so localizatiion can start for new strings. 19:30:55 its on my ToDo list for tomorrow 19:31:02 it's even 19:31:04 Thanks. 19:32:01 so, yes, i think 6.0a1 makes sense and then having such a big thing like #17965 in it would be good 19:32:22 We will review the #17965 patches. 19:32:48 thanks 19:33:06 thanks! :) 19:36:12 who else is here? do we have a boklm? 19:36:17 * boklm will go next 19:36:22 ah 19:36:30 This week I fixed #17325 and #17128. I made a build with #15578 patches and tried it on Centos6. 19:36:34 This week I'm planning to work on #16009, help with #15578 and the release. 19:36:50 That's it for me. 19:39:18 boklm: do you think you could do the release things for the alpha from the signed bundles on people-tpo on? 19:39:33 meaning i upload them to people-tpo and you would do the remaining things? 19:39:54 GeKo: ok 19:39:55 long-term plan here is to share the release load a bit and avoid me being a new bottleneck 19:40:03 (and avoid roping mikeperry in again) 19:40:06 cool 19:40:28 GeKo: for the 6.0a1 ? 19:40:44 yes and the hardened one 19:40:49 ok 19:41:07 i'll be around in case issues pop up or you have questions 19:42:04 alright, do we have anything else to discuss or is anyone else here for the meeting? 19:43:30 GeKo: It might be useful for me to discuss fonts with you a little further, either before or after the end of the meeting (if you have time). 19:44:36 yeah, after the meeting sounds fine 19:44:43 cool 19:46:27 thanks everybody then *baf* 19:46:31 #endmeeting