18:03:41 <GeKo> #startmeeting tor browser 18:03:41 <MeetBot> Meeting started Mon Sep 11 18:03:41 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:03:41 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic. 18:03:44 <GeKo> sorry all 18:03:48 <arthuredelstein> hi! 18:03:50 <GeKo> i had some network issues 18:03:56 <mcs> I was about to ask if we were meeting today :) 18:03:59 <mcs> and hi 18:04:00 <isabela> ! 18:04:07 <GeKo> alright, let's start with the updates 18:04:11 <GeKo> who is first today? 18:04:17 <boklm> hi 18:04:18 * isabela is around for this meeting and have a couple of items :) 18:05:09 <GeKo> okay, then i'll go 18:05:39 <GeKo> last week i tracked down the issue for #16010 18:05:58 <GeKo> i hope someone from mozilla can help me understand what's going on 18:06:07 <GeKo> if not i'll try to find someone 18:06:23 <GeKo> then we switched to rbm for development 18:06:33 <GeKo> i went over almost all of the tbb-gitian 18:06:40 <GeKo> tickets and moved them over or closed them 18:06:49 <GeKo> i'll take care of the remaining ones this week 18:06:58 <GeKo> the plan is still to build the next alphas with rbm 18:07:30 <GeKo> i spent a considerable amount of time reviewing #18101 and #23228 18:07:48 <GeKo> actually the testing was quite involved in both cases 18:07:55 <GeKo> and i refined my patch for #22692 18:08:06 <GeKo> then i tried to move the hiring forward 18:08:23 <GeKo> this week i'll do more reviews and look over the remaining tbb-gitian items 18:08:33 <GeKo> then i hope to work further on #16010 18:08:40 <asn> dgoulet: ack ack 18:08:41 <GeKo> and get back to updating the design doc 18:08:45 <asn> dgoulet: checkin and then making unity 18:09:05 <GeKo> i'll start with the review for the sec slider update as well 18:09:29 <GeKo> that's it from me 18:10:10 <tjr> I'm here (although double booked with another meeting) 18:10:22 <tjr> Don't have much to say other than slowly working on mingw patches and trying to get them all r+ed 18:10:36 <tjr> (And eventually will need to debug why the browser doesn't run...) 18:11:48 <GeKo> who is next? 18:12:01 * arthuredelstein can go 18:12:12 <arthuredelstein> This past week I wrote patches for #23404 and #22564. 18:12:23 <arthuredelstein> I started work on revising my patch for #18101 (thanks for the review GeKo!). 18:12:31 <arthuredelstein> I reviewed https://bugzilla.mozilla.org/1372073 18:12:34 <arthuredelstein> and wrote a demo of evil fingerprinting via navigator.mediaDevices. 18:12:52 <arthuredelstein> (https://arthuredelstein.github.io/tordemos/mediaDevices.html) 18:13:01 <arthuredelstein> And I reviewed some other fingerprinting uplift tickets on bugzilla and met with the Mozilla/Tor uplift team. 18:13:30 <arthuredelstein> This week I want to finally get #18101 working properly 18:13:41 <arthuredelstein> and work on more tbb-usability. I'm looking at #22985 and #21394. 18:13:45 <GeKo> arthuredelstein: are there actually meeting notes of those meetings somewhere available? 18:14:16 <arthuredelstein> GeKo: Yes. I will mail it to you as it's on an etherpad. 18:14:21 <GeKo> cool 18:14:24 <arthuredelstein> (and to the rest of the tbb-dev team) 18:14:43 <GeKo> where are you with respect to your hardening work? 18:14:47 <GeKo> like ubsan support 18:14:56 <GeKo> STACK support etc.? 18:15:11 <GeKo> i am asking because that's actually a deliverable we have 18:15:31 <GeKo> and we have kind of 2 1/2 months left 18:15:49 <GeKo> do we have something we can show? 18:16:05 <GeKo> or somethin where we explain why we can't show something? 18:16:10 <GeKo> *something 18:17:05 <arthuredelstein> yes, I have some stuff for ubsan but it was pretty tricky and I was focusing on other things. But I can make it high priority again. 18:17:33 <arthuredelstein> STACK I haven't really started but I did some reading. 18:18:04 <GeKo> for the ubsan part the plan was to test things e.g. whether we could use it for q&a 18:18:27 <GeKo> i think the point is not necessarily to get every part of firefox compiled with ubsan 18:18:50 <GeKo> i think a good start could be to take care of the js engine first 18:19:00 <GeKo> and/or just some part of undefined behavior 18:19:17 <GeKo> if that is not working for some reason i think we can try to sell that to otf, too 18:19:18 <isabela> arthuredelstein: can i have the notes from the moss meetings too? 18:19:29 <arthuredelstein> Yeah, I was focusing on trying to fix some types of undefined behavior. As a proof of principle I fixed all of the enum behaviors 18:20:04 <arthuredelstein> But that particular issue is not as helpful for security as integer overflow 18:20:12 <GeKo> yep 18:20:26 <GeKo> oh, another buzz thing on our list is #16352 18:20:39 <GeKo> if you want to test that as well 18:20:56 <GeKo> so, yes, if you could spend some time on those things too, that would be neat 18:21:04 <arthuredelstein> OK, well, as we have 2.5 months for that deliverable I should probably put those at the top of my list 18:21:16 <tjr> I am working on https://bugzilla.mozilla.org/show_bug.cgi?id=1376819 right now 18:21:19 <GeKo> well, at least not drop them :) 18:21:21 <tjr> it should be usable in 2.5 months 18:21:38 <GeKo> neat 18:21:41 <arthuredelstein> tjr: nice! 18:21:46 <arthuredelstein> isabela: Will do 18:21:59 <isabela> tx 18:22:20 <arthuredelstein> GeKo: thanks for the reminder! I will try to get those moving 18:22:27 <GeKo> arthuredelstein: so, if you could keep the hardening stuff on your plate with the knowledge that we have to have something in about 2 months that would be great 18:22:30 <GeKo> sure 18:22:34 <arthuredelstein> yup 18:22:45 <GeKo> alriiiiiight 18:22:48 <GeKo> who is next? 18:22:52 * boklm can go next 18:23:03 <boklm> This past week I worked on some Windows 64 issues: #23436, #23231, #23442, #23456 18:23:13 <boklm> I also fixed some tbb-rbm tickets: #21286, #23425, #23403, #23417, #23382, #23454 18:23:23 <boklm> This week I'm planning to work on #23458 and try to fix hardening of the Win64 toolchain for #23228. 18:23:38 <boklm> Try building a Win64 bundle to check if it's running. 18:23:54 <boklm> Then try to finish the FPCentral things, setup the Windows QA machine (#23386) and work on #23039 or other tbb-rbm tickets. 18:24:08 <boklm> That's it for me. 18:24:26 * mcs will go next 18:24:44 <mcs> During the first half of last week, Kathy and I made more progress on #23262. 18:24:49 <mcs> Then we were out of the office part of Thursday and all of Friday. 18:24:53 <mcs> This week we plan to continue working on #23262 and help with code reviews. 18:25:05 <mcs> From reading the backlog on this channel, it also sounds like we will have one or more meetings this week with the Network Team to discuss Tor Launcher tasks (progress and moat integration). 18:25:06 <mcs> That's all for now. 18:25:23 * isabela can tell her 2 things :) 18:25:31 <GeKo> go ahead! 18:25:34 <isabela> ok 18:26:05 <isabela> 1. is about tor launcher, i wanted to see if pearl crescente could meet w catalyst isis and nick to chat about it 18:27:12 <isabela> maybe tomorrow if not today? 18:27:34 <isabela> should be quick - i can also send an email to coordinate this off meeting 18:27:45 <mcs> isabela: tomorrow would be better for Kathy and me but we are flexible 18:27:53 <isabela> cool 18:27:58 <isabela> i will send an email too 18:28:07 <nickm> (we could probably do it in <30 min, and today would probably help us be productive sooner) 18:28:09 <isabela> i think network team folks can share sstuff prior to the meeting 18:28:20 <nickm> (or we can just make reasonable guesses and run with them) 18:28:21 <isabela> aha 18:28:24 <mcs> nickm: after this meeting then? 18:28:32 <nickm> works for me if it works for you and catalyst 18:28:34 <isabela> isis catalyst ^^^ 18:28:42 * catalyst is back from lunch 18:28:53 <isabela> maybe chat with mcs in like 30min? 18:29:05 <catalyst> that works for me 18:29:08 <isabela> cool 18:29:14 <isabela> ok that was 1. :) 18:29:45 <isabela> 2. is that i will be emailing the team this week to start a discussion about the roadmap planning in montreal or a.k.a. life after sponsor4 18:30:05 <isabela> just a heads up 18:31:23 <isabela> thats it for me 18:31:30 <GeKo> thanks 18:31:39 <GeKo> who else is here for a status update? 18:33:39 <GeKo> okay, discussion time 18:33:45 <GeKo> do we have something for today? 18:34:25 <GeKo> i have one item 18:34:28 <msvb-lab> Not much status, but I had my build system bugs closed, due to migration to RBS, whatever that is. 18:34:33 <msvb-lab> ...I mean RBM. 18:34:56 <GeKo> there is currently planning going on when the next meeter after montreal will be 18:35:14 <GeKo> we got asked whether mar 10-14 would work for us 18:35:31 <GeKo> the issue is that pwn2own will be on mar 14-16 18:35:46 <GeKo> and chances are quite high we need to make an emergency release 18:36:04 <GeKo> (although this time we were lucky and dodged that bullet) 18:36:30 <GeKo> so, do we thinkg we could have a productive meeting during that time with pwn2own looming? 18:37:57 <GeKo> okay, seems this is up to me to decide :) 18:38:01 <GeKo> works for me 18:38:01 <mcs> It seems like bad timing to me. 18:38:10 <mcs> But it might work out fine. 18:38:49 <GeKo> yeah, a week earlier is a regular firefox release which would be bad timing as well 18:38:49 <mcs> usually, being at a dev meeting means getting behind in other areas which means no time to recover before pwn2own 18:38:58 <GeKo> indeed 18:39:32 <GeKo> anything else for today? 18:40:13 <GeKo> thanks everyone one then *baf* 18:40:16 <GeKo> #endmeeting