19:00:57 <GeKo> #startmeeting tor-browser
19:00:57 <MeetBot> Meeting started Mon Dec 12 19:00:57 2016 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:57 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:01:01 <GeKo> hi all!
19:01:06 <boklm> hi!
19:01:08 <GeKo> time for another weekly tor browser meeting
19:01:09 <mcs> hi
19:01:13 <legind> hello
19:01:14 <Yawning> hi
19:01:27 <GeKo> let's start, as usual, with a status update
19:01:32 <GeKo> who wants to go first today?
19:01:40 <arthuredelstein> hi everyone
19:01:44 <Yawning> I tagged
19:02:14 <Yawning> will work on improving things unless someone tells me I should do something different, or I get overcome by existential nhilism and spend the days in bed instead
19:02:17 <Yawning> >.>
19:02:30 <Yawning> done
19:03:42 <GeKo> hm, so i realized we are calling the sandbox just "sandbox-0.0.2-linux$$.zip" and not "sandboxed-tor-browser-0.0.2-linux$$.zip"
19:04:00 <GeKo> my first impression was to not give the user the idea they download a whole sandboxed browser
19:04:11 <GeKo> and name the things what it is: a sandbox
19:04:19 <GeKo> but i am not sure anymore
19:04:46 <zeroise> "Tor Browser with a Diaper"
19:04:57 <GeKo> maybe it might be a more helpful thing for a user to have a "sandboxed-tor-browser" dir than
19:05:17 <GeKo> a plain "sandbox" one (with a sandboxed-tor-browser binary)
19:05:38 <GeKo> but, anyway, that is a thing we can figure out for the next release i guess
19:06:10 <GeKo> i can go next:
19:06:30 <mcs> For what its worth, I think it would be better to use "sandboxed-tor-browser" as the name
19:06:48 <GeKo> i was mainly busy with preparing the releases and waiting anxiously for mozilla to tag their stuff
19:07:10 <GeKo> they finally did late on friday so that we were able to start building on the weekend
19:07:27 <GeKo> and it seems we are done with it having matching builds in all series (yay!)
19:07:55 <GeKo> i found a bit time to work on the design documentation and helped with the DRL proposal
19:08:56 <GeKo> this week i plan to get the releases out and work the design doc as much as possible and seems to be time to tackle #18925
19:09:05 <GeKo> that's it for me.
19:09:16 <GeKo> mcs: yes, i tend to agree meanwhile
19:09:36 <arthuredelstein> So that zip does not contain the tor-browser itself, correct?
19:10:10 <mcs> maybe “tor-browser-sandbox-…” ?
19:10:18 <arthuredelstein> Or "sandbox-for-tor-browser"?
19:10:56 <GeKo> yes, correct
19:11:15 <GeKo> i'll open a ticket afterwards for the bikeshedding (and fixing)
19:11:48 * arthuredelstein can give a status report
19:11:58 <arthuredelstein> Last week I worked on #10281 and started working on #20680.
19:12:05 <arthuredelstein> Also I wrote a patch for #20947.
19:12:23 <arthuredelstein> This week I will continue on the rebasing.
19:12:40 <GeKo> please have a look at #20941
19:12:47 <arthuredelstein> Will do.
19:13:05 <GeKo> chances are that this is due to the resizing code living in firefox itself now
19:13:22 <GeKo> ok
19:13:43 <arthuredelstein> interesting.
19:14:03 <arthuredelstein> And I will continue to work with the DieHarder author to see if it's possible to get that working.
19:14:22 <arthuredelstein> That's it for me.
19:14:37 * boklm can go next
19:15:11 <boklm> This past week I worked on #17380 and I reproduced builds of the new releases.
19:15:19 <boklm> This week I'm going to be at the reproducible build meeting during the next 3 days. Then I'm planning to fix #20949 and continue working on #17380.
19:15:26 <boklm> That's it for me.
19:15:42 * mcs will go next
19:15:50 <mcs> Last week Kathy and I revised our patch for #20121.
19:15:55 <mcs> We also created a patch for #20761 (but that is on hold for now).
19:16:01 <mcs> We also completed some code reviews.
19:16:05 <mcs> This week we will mostly be working on some non-Tor projects.
19:16:10 <mcs> We do plan to help with the TB sandbox blog post and we will be available if any issues come up with the releases.
19:16:15 <mcs> That’s all for us.
19:16:47 <legind> From the HTTPS Everywhere side, most likely there will be a release made this week, 5.2.9
19:17:01 <GeKo> hi legind!
19:17:07 <legind> hey GeKo! :)
19:17:38 <legind> That's it for me
19:18:03 <GeKo> alright, anybody else here for a status update?
19:18:54 <GeKo> mcs: before i forget it: i might bug you wrt #20784 which is another of those extremely weird OS X bugs
19:19:12 <GeKo> i hope i get the profile sent and answers to my questions
19:19:13 <mcs> right; we saw that and are still puzzled.
19:19:52 <GeKo> okay, do we have anything for discussion today?
19:20:31 <Yawning> do I need to help drafting the blog post
19:20:45 <Yawning> or can I just disappear and work on making the sandbox stuff better
19:20:53 <GeKo> the stuff you sent is good, thanks
19:21:08 <Yawning> k
19:21:15 <GeKo> i'll ping you probably tomorrow for feedback
19:21:22 <GeKo> once i have the draft up
19:21:24 <Yawning> the trac page I have going for the thing has more details I think
19:21:26 <Yawning> ok
19:21:33 <GeKo> good
19:22:18 <Yawning> should #20954's patch also fix the thing for windows?
19:22:25 <GeKo> no
19:22:26 <Yawning> people complain about everything but linux
19:22:36 <GeKo> we have instructions for windows which are working
19:22:43 <Yawning> ah ok
19:23:36 <arthuredelstein> I posted my notes on memory hardening options here: https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hardening. Hoping to keep working on this in the coming months.
19:23:58 <Yawning> we should rename the sha256 sum file to "these-are-not-the-sha256-hashes-you-are-looking-for-use-gpg"
19:24:23 <GeKo> yeah, lol
19:24:35 <arthuredelstein> :)
19:24:58 <GeKo> but frankly if folks are going to the advanced section and are not able to read then renaming would not help either i guess
19:25:10 <GeKo> arthuredelstein: good stuff
19:25:30 <GeKo> i was wondering whether you could sum up your investigation and add that to #10281
19:25:34 <GeKo> to get that beast closed
19:25:44 <arthuredelstein> Will do.
19:25:45 <GeKo> (maybe pointing to that wiki page)
19:25:55 <GeKo> and we open new tickets for stuff we want to work on
19:25:59 <GeKo> like the dieharder thing
19:26:07 <GeKo> or the partitioning work
19:26:22 <arthuredelstein> Yeah. I was thinking about opening a parent ticket for all memory hardening work.
19:26:36 <arthuredelstein> redzones are definitely not the final answer
19:26:44 <GeKo> indeed
19:27:38 <arthuredelstein> So much academic vaporware in the field :(
19:27:45 <GeKo> yeah
19:28:24 <GeKo> that is a good summary for the meeting i guess, thanks all *baf*
19:28:28 <GeKo> #endmeeting