18:58:15 #startmeeting Tor Browser meeting 7 December 2020 18:58:15 Meeting started Mon Dec 7 18:58:15 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:58:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:58:19 Hello! 18:58:30 Pad, as usual: https://pad.riseup.net/p/tor-tbb-2020-keep 19:00:07 o/ 19:00:40 o/ 19:02:41 hi! 19:02:54 hello! 19:03:07 * gaba removing the old discussion items from the pad 19:03:54 hi! 19:04:51 Weekly reminder to update your boards (as needed): https://gitlab.torproject.org/groups/tpo/applications/-/boards 19:04:59 tpdcl: hello! 19:05:52 okay 19:05:59 sorry for ebing late 19:06:53 o/ 19:07:42 GeKo: i've mostly ignored your work on the root-less builds 19:07:59 can you summarize how well that is going? 19:08:00 is there anyway of logging this meeting so I can view the messages later? 19:08:10 sorry for interrupting 19:08:11 tpdcl: they are already logged 19:08:25 sysrqb: it's boklm who has mainly worked on them 19:08:25 where can I view the logs? 19:08:26 you'll see it at https://gitlab.torproject.org/groups/tpo/applications/-/boards 19:08:32 thanks! 19:08:33 err 19:08:34 they are working as far as i see 19:08:36 http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-12-07-16.59.txt 19:08:39 and my testing showede 19:08:41 *showd 19:08:43 *showed 19:09:04 i am waiting for a final round of review to test the patches on our tpo build machines 19:09:13 i heard hiro might work on that this week 19:09:31 i expect no issues but we should make sure things are working on thiose machines 19:09:37 *before* the patches land 19:09:47 so we are good i actually think 19:09:53 nice 19:12:51 acat: GeKo: i never pinged you about holiday planning 19:13:01 are you available after this meeting or should i ping youtomorrow morning? 19:13:16 i'm available 19:13:29 acat: thanks for your mail 19:13:35 we can do it today 19:13:41 okay 19:14:00 i dont haveany significant discussion items now 19:14:29 10.5a5 is uploaded on Google Play and approved, and it is synced on the web servers 19:14:50 so i'm just writing the blog post and updating the download page 19:15:06 GeKo: i'm not sure if you wanted to do the publishing 19:15:11 i forgot about the new arrangement 19:15:19 :) 19:15:21 so sorry for taking over 19:15:30 it's cool 19:15:57 i can do the next alpha 19:16:11 (and review your related MRs while doing so) 19:16:22 GeKo: i also built -build2 and it matched (again), so we are good there 19:16:28 yep, sounds good 19:16:59 not including the changelog in the android builds has some benefits :) 19:17:08 yeah ;) 19:17:35 re the publishing/signing arragement: we can discuss that once the process updates landed 19:17:48 wfm 19:18:08 because getting that updated was one of the goals for taking some publishing work over 19:18:44 yeah 19:19:38 we have 10.0.6 for all platforms, and 10.5a6 for desktop scheduled for next tuesday 19:19:55 meanwhile we have tpo/anti-censorship/pluggable-transports/meek#40001, as well 19:20:30 losing meek for an entire week is not a good situation 19:20:55 so we'll probably discuss building an emergency release when the obfs4proxy update becomes available 19:21:12 (stable only) 19:21:24 can't we just grep the patch and get the building going? 19:21:50 we could 19:21:52 if we want to get a emergency release out let's do it fast 19:21:57 *an 19:22:48 i think the total build-time should be fast because we don't need to rebuild firefox/geckoview 19:22:56 so we could release it tomorrow night, in theory 19:23:00 yes 19:23:39 phw: are you comfortable with your patch that we shouls just pick it and strat our build? 19:23:42 *start 19:24:12 (re cert pinning) 19:24:42 sysrqb: you said 10.5a6 next week for desktop. why not mobile? 19:25:14 sysrqb: i'm 90% comfortable. i don't think i have write access to the repo that your builds are pulling from though 19:25:16 GeKo: what would mobile be based on? 84.0? 19:25:35 yes 19:25:43 phw: that's okay, we could use a patch file in the short-term 19:26:01 sysrqb: okay, the patch file is here: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek/-/issues/40001#note_2718149 19:26:24 GeKo: i wasn't planning on it, but that doesn't hurt 19:26:54 it feels weird that alpha users don't get all the updates 19:27:01 phw: yep 19:27:11 or not the latest stuff at least 19:27:52 there might even be last minute sec bugs landing 19:28:10 or stability fixes for geckoview 19:28:53 i mean we could decide that on code review between 84.0b7 and 84.0 19:29:14 but... 19:29:15 GeKo: true, and if there are sec bugs then we should definitely include it 19:29:38 i felt that updating twice every month semed unnecessary unless there was a security driver 19:29:54 but the overhead is not very large 19:30:04 i think that's true for stable 19:30:14 i am not sure whether that's true for alpha 19:30:32 in particular as we should try to get as much alpha testing as we reasonably can 19:30:52 as our stabilization time for stable is pretty...low 19:31:16 but 84.0 will be available for alpha after 84.0 for stable 19:31:27 so i didn't feel like that provided much insight 19:31:39 yes but it contains a bunch of additional code not being in stable 19:31:59 so it might not help for the current stable 19:32:04 i see, and there could be unexpected interactoin between the new code 19:32:11 yes 19:32:11 okay, that's a good point 19:32:24 and we would catch that earlier that way 19:32:51 1 month :) but yes, that's fair 19:33:11 okay, then i'll plan on including android in 10.5a6 19:33:42 i am fine if we feel the overhead is not worth it 19:34:03 so, i am not pushing too hard here :) 19:34:21 (and less releases means less release work) 19:35:09 it increases the overall build-time by 5 or 6 hours, but that is not generally a big problem 19:35:17 unless we are days behind schedule 19:35:27 yeah 19:35:53 the additional signing is not a problem for me 19:36:00 only adding some minutes 19:36:07 so, the overhead seemed small to me compared to the small benefit we might get 19:36:44 yeah 19:36:49 and we would not need to do all the extra work to *not* build mobile 19:37:07 (like extra code review, exclusion and explanation in blog post etc.) 19:37:15 i just considered it "unnecessary", but is is helpful 19:37:18 true 19:38:17 okaythen this is the new plan 19:39:31 and i'll tag 10.0.6 today with the obfs4proxy patch, and then 10.0.7/10.5a6 are next week's versions 19:40:54 acat: GeKo: gaba: Jeremy_Rand_Talos: anything ele you want to discuss today? 19:41:00 not from me 19:41:04 i'm good 19:41:21 We will have to check on s58 work in the next last meetings. 19:41:42 sysrqb, I don't have much to discuss, unless anyone is curious about the TLS onion thingy I came up with 19:41:59 gaba: mmm 19:42:05 yes, let's discuss that next week 19:42:19 yes 19:42:28 Jeremy_Rand_Talos: yes, I am, but maybe next week 19:42:31 sysrqb: we should not forget tickets with the Bacport label 19:42:37 *Backport 19:42:42 ok, next week is fine 19:42:49 there are a bunch that pile more and more up 19:43:15 that's for 10.0.7 19:43:26 but we don't need to go through them now 19:44:00 good point, yes 19:45:12 okay, if there aren't any other topics then I'll close this meeting 19:45:14 thanks everyone 19:45:19 and have a good week 19:45:21 o/ 19:45:24 #endmeeting