18:01:19 <GeKo> #startmeeting tor browser
18:01:19 <MeetBot> Meeting started Mon Jul 24 18:01:19 2017 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:19 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:01:23 <GeKo> hi all!
18:01:35 <GeKo> welcome to monday 1800 UTC and a tor browser meeting
18:01:48 <mcs> hi
18:01:51 <GeKo> let's start with the weekly status update
18:02:19 <GeKo> who wants to go first today?
18:03:40 <GeKo> okay. then i am first it seems
18:03:48 <arthuredelstein> hi all!
18:04:10 <GeKo> last week i wrote patches for #21321, #20848 and #22699
18:04:26 <GeKo> the latter is not pushed yet
18:04:51 <GeKo> i spent quite some time on the design doc update and made good progress
18:05:10 <GeKo> i got dragged into the hackerone public launch and follow up stuff
18:05:40 <GeKo> i reviewed #22884
18:06:22 <GeKo> this week i want to look at #22692
18:06:33 <GeKo> and work further on the design doc update and #16010
18:06:40 <GeKo> and i plan to do a bunch of reviews
18:06:46 <GeKo> that's it from me
18:07:07 * mcs will go next
18:07:23 <mcs> Last week, Kathy and I posted patches for #22884 and for the download warning prompt bug collection (the patch is in #22618).
18:07:29 <mcs> We reviewed the API proposal in #15967 and provided some input.
18:07:35 <mcs> We reopened #22434 but need to do some more testing for that issue.
18:07:43 <mcs> This week, we plan to help with code reviews.
18:07:48 <mcs> We will also do some testing for #22434 to confirm whether there really is a problem or not.
18:07:59 <mcs> Then we plan to start looking at some Tor Launcher tickets in preparation for the redesign work, probably starting with #21542 and #22592.
18:08:09 <mcs> That's all for now.
18:08:50 <GeKo> sounds good, thanks
18:09:08 * arthuredelstein can go
18:09:17 <arthuredelstein> This past week I posted new patches for #23024, #23025, and #22563.
18:09:24 <arthuredelstein> I participated in a UX discussion and opened #22985, #22982, #22981 and #22980.
18:09:46 <arthuredelstein> I reviewed #21830 and some bugs for the Mozilla tor uplift team.
18:10:30 <arthuredelstein> This week I want to help with code reviews, and look into more hardening options, including memory allocators and possibly ubsan
18:10:37 <arthuredelstein> That's it for me.
18:11:02 <tjr> Any chance you can cc me on the bugs you filed? I won't make the wens meeting this week
18:11:21 <GeKo> arthuredelstein: did you go systematically over our (new) patches in tor-browser.git
18:11:29 <arthuredelstein> tjr: the ux bugs?
18:11:35 <GeKo> and filed tickets as needed?
18:11:41 <GeKo> (i mean upstream ones)
18:11:53 <tjr> oh sorry i thought you said you filed more bugs for the uplift, nevermind
18:11:54 <GeKo> or did you focus on fingerprinting stuff
18:12:17 <arthuredelstein> GeKo: Yes, actually this week I systematically filed anti-fingerprinting tickets
18:12:43 <arthuredelstein> Since the tor team is focused on that category right now
18:13:10 <arthuredelstein> But I should also go through and file any others I can. I can do that this week
18:13:35 <GeKo> okay. it just occurred to me we have a bunch of other things as well we might want to upstream
18:13:47 <GeKo> like the one for #21792 for instance
18:13:54 <GeKo> err
18:13:58 <GeKo> #21972
18:14:54 <GeKo> who is next?
18:15:01 * boklm can go next
18:15:05 <arthuredelstein> Yes, good point. I'll file that one and similar
18:15:17 <boklm> This past week I fixed #22959, did the linux part of #22499 and started the windows part.
18:15:26 <boklm> This week I'm planning to finish #22499, compare the result of rbm and gitian builds, and do some reviews
18:15:34 <boklm> That's it for me.
18:16:25 <GeKo> boklm: we need to move forward with the panopticlick thing as well. so
18:16:38 <GeKo> if you'd fine some time to look at remaining issues this week that would rock
18:16:44 <boklm> ok
18:17:11 <GeKo> anyone else here today for a status update?
18:18:37 <GeKo> okay. do we have something to discuss this week?
18:18:53 <GeKo> (i have nothing fwiw)
18:19:29 <arthuredelstein> I'm curious about #16010 -- what happens if you remove all __try and __except statements?
18:19:46 <arthuredelstein> Does the content process crash a lot then?
18:20:31 <GeKo> i have a build which does this
18:20:49 <GeKo> there are errors in the error console indicating that something goes wrong
18:21:08 <GeKo> the browser is not really usable but i still have to figure out why
18:21:46 <mcs> I have a quick question: when will we start builds for the next Tor Browser release (approximate date)?
18:22:01 <mcs> Mozilla’s release date is August 8th
18:22:03 <arthuredelstein> GeKo: thanks, that's interesting
18:22:11 <GeKo> next thursday i guess
18:22:19 <mcs> GeKo: sounds good; thx
18:22:20 <GeKo> aug 3
18:22:33 <GeKo> at least i hope so
18:22:59 <GeKo> arthuredelstein: indeed. i had hoped it would somewhat work out-of-the box but crash from time to time
18:23:19 <GeKo> but i suspect there is an underlying different bug causing this weird bnehavior
18:23:22 <GeKo> but we
18:23:25 <GeKo> 'll see
18:23:32 <arthuredelstein> The use of __try and __except in the sandboxing code seems questionable to me anyhow
18:24:08 <GeKo> try to convince the chromium people and we got rid of a big problem :)
18:24:14 <arthuredelstein> yeah! :)
18:24:26 <arthuredelstein> I mean, I would just worry you are relying on undefined behavior
18:24:42 <arthuredelstein> but maybe those cases are safe. I don't know.
18:25:06 <GeKo> i did not have time to look that close yet, maybe
18:25:21 <GeKo> anyway, thanks for the  meeting and happy tor-browser-fixing *baf*
18:25:24 <GeKo> #endmeeting