tor-project June 2018

tor-project@lists.torproject.org

26 participants
30 discussions

Job Openings at Tor Project
by Erin Wyatt 20 Jun '18

20 Jun '18

Hey, everyone! Isa taking over as ED is a real thing (!!!) so we’re ready to recruit her replacement(s). We’ve posted two new PM job openings — please help us spread the word! :) * Project Manager for Network Projects: https://www.torproject.org/about/jobs-projectmanager-network.html.en <https://www.torproject.org/about/jobs-projectmanager-network.html.en> * Project Manager with Product Experience: https://www.torproject.org/about/jobs-projectmanager-product.html.en <https://www.torproject.org/about/jobs-projectmanager-product.html.en> We are also still looking for a Fundraising Director, which is a crucial position that can be tough to fill. Please continue to share the post: https://www.torproject.org/about/jobs-fundraising-director.html.en <https://www.torproject.org/about/jobs-fundraising-director.html.en> Thank you all! Cheers, Erin Wyatt HR Manager ewyatt(a)torproject.org GPG Fingerprint: 35E7 2A9F 6655 45F9 2CB6 6624 BA0C 9400 F80F 91CE

1 0

UX Team Report - May 2018
by Antonela Debiasi 20 Jun '18

20 Jun '18

Hello Tor! The Community and the UX Team visited the beautiful Kampala last month. We met old and new Tor users from all over Uganda. Our experience with local communities allowed us to spread Tor's world there and helped us to talk directly with users to improve our product's usability. We ran Tor trainings, threat modeling, a user needs discovery activities and conducted user testing for the new browser's improvements. Thanks to our awesome community members who provided critical logistics and translation support. Juliet, Tayfor, Karen, Neema, and Robert thanks for making it possible! We were working hard with the Application Team for our next Tor Browser release both for desktop and mobile. Thanks to the development team, we have nightly builds running again. It will help us to start testing our collaborative user testing workflow where the people in our community can test specific UX improvements and report them directly to the UX team. We were at Mozilla All Hands last week. We are collaborating to offer a better, private and safe browsing experience. On infra side, we started migrating the newsletter to Lektor and styleguide so it can be static. Also, the new support portal is about to launch at support.torproject.org, so stay tuned! On behalf of the Tor UX team, Antonela *Cool Things* - Hiro wrote about how you can browse the internet privately without corporate trackers lurking around you -> https://blog.torproject.org/dont-let-facebook-or-any-tracker-follow-you-web - We are preparing ourselves for Mexico Dev Meeting with a bunch of cool activities for Product, UX and UI designers who are going to be there! - "A lack of information often equates to a lack of control". Excellent article about system's feedback from NNGroup → https://www.nngroup.com/articles/visibility-system-status

4 3

Tor Browser team meeting notes, 18 June 2018
by Georg Koppen 19 Jun '18

19 Jun '18

Hello! Status updates and news from Tor Browser land after the Mozilla All Hands meeting got discussed yesterday at our weekly meeting. The chat log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-06-18-18.01.log… The notes from our pad are: Tor Browser Meeting Notes Monday, June 18, 2018 Discussion: -"status:" update -Quo vadis sandboxing? [GeKo: sysrqb is updating the sandbox plans he had and we get together on IRC to hammer out details] -Tracking issues in Trac -release preparations (blocker 1) and 2) from last week got solved, no new ones showed up, only 3) is left for the alpha) -which UX features need to get into the first alpha - .onion padlock indicator - circuit display - Tor Browser icon update - about:tor without onboarding? -next meeting - sysrqb: Confirming, we should base TBA on 60ESR, yes? [GeKo: yes] - igt0: Thinking about TBA, are we going to release a new orbot version as well? [GeKo: No, that's still the GuardianProject's job] - igt0: Service workers added lot of new APIs, I was not able to find out tickets about it (a master ticket), Is someone taking a look? [GeKo: We don't need that for now as service worksers are still disabled in the ESR60, we have #15563 for general service workers related work] sukhe: Last Week: - Finalized #26203, #26326, #26204, #25837 (Windows build issues; merged) and prepared #23561 (NSIS 64bit) for review - Attended Summer Institute This Week: - Work on #26319 (Don't package up the whole Tor Browser in the `mach package` step), #26251 (Adapt macOS snowflake compilation to new toolchain) - I am offline on Wed June 20 mcs and brade: Last week: - Triage some new/incoming tickets: - #26346 (Update prompt from 7.5.5 to the same version) - #26350 (MacOS Tor Browser cannot bind to port) - #26375 (On Mac, cannot have Tor Browser and Tor Browser Alpha side by side) - #26381 (about:tor page does not load on first start in localized Windows bundle) - Helped with #26045 (Create a new MAR signing key for ESR60) - Helped with #26355 (Make sure only Windows users on Windows7+ are trying to use Tor Browser based on ESR60 - Completed review for #23247 (Communicating security expectations for .onion). - Continued with #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). This week: - Continue with #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). - This is going slowly, so we are trying to find a way to speed up the review. - #26381 (about:tor page does not load on first start in localized Windows bundle) GeKo: Do you want us to work on this ticket? [Please go ahead, I probably won't get to it, GeKo] sysrqb: Last week: - At Mozilla All-Hands - Participated in conversations about Firefox sandboxing - Learned about Mozilla's plans for Firefox/Gecko on Android - Many more things This week: - Push Tor Browser 60ESR branch with TBA patches for review - Work on cross-platform Tor Browser sandboxing plan - Begin auditing code for proxy-safety (#21863) GeKo: Last week: -made progress on the network audit (#22176) -help with the Windows nightly builds (we seem to be good here now as well) -went over the UX tickets relevant for tor browser 8 -fixed up my rustc ticket (#26329) and some other small stuff (#23231, #26304) -reviews (#26329, #25837, #26203, #23247, #26396) This week: -fix for #26362 (create old-style MAR files) -test Mozilla fixes for bug 1413868 and 1421081, possible backport of a crash bug fix -continuing network audit (#22176) -reviews -release preparations and building/signing releases igt0: Last week: - Tested torbutton with FF60 - started investigating strategies to detect APK tampering. (Since we are going to allow the user to install from different places #26242). This week: - Define and implement update strategy(ies) for TBA (#26242) - Consider different installation methods (#26318) boklm: Last week: - reviewed some patches: - #26329: Fix Rust cross-compilation for 32bit Windows - #26203: Adapt tor-browser-build firefox and tor-browser project for ESR 60 Windows build - #26304: Update zlib to latest version - #23231: Error in STL wrappers when building Firefox 64-bit for Windows - #26250: Bump Rust version to 1.26.1 - #23561: Fix nsis builds for Windows 64 - made patches for: - #26354: Make sure only Linux users with SSE2 support are trying to use Tor Browser based on ESR60 - #26370: Don't copy msvcr100.dll and libssp-0.dll twice - #26206: Ship pthread related dll with tor - #26396: libwinpthread we ship in Windows builds is not built reproducible This week: - help building the new releases - doing some reviews - plan travel for mexico meeting - continue investigating build issue with #12968 (HEASLR) - fill upstream binutils ticket for #26148 - continue work on some ansible roles for testsuite VMs setup (#26149) pospeselr: Last week: - Mozilla All-Hands - patch for #26039 (extension-overrides.js no long being a thing in ESR60) This week: - fix up #23247 (onion lock icons) with final bits of feedback - verify #26039 fix works - go through the outreachy intern's issues spreadsheet - #26355 arthuredelstein: Last week: - Mozilla all hands meeting - Worked on reviewing HTTP/2 code including origin frames and AltSvc This week (as described last time): - Help with build as needed - Finish a patch for https://trac.torproject.org/25555 (reimplement optimistic socks) - HTTP/2, https://trac.torproject.org/14952 - Other needed alpha/ff60-esr tickets: https://trac.torproject.org/21785, https://trac.torproject.org/26321, https://trac.torproject.org/26322 Georg

1 0

Network team meeting notes, 18 June 2018
by Nick Mathewson 19 Jun '18

19 Jun '18

Hi! You can see the chat logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-06-18-16.59.html Our weekly meeting notes are below. = Network team meeting pad, 18 Jun 2018 = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) == Previous notes == 23 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001747.html 30 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001750.html 7 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001760.html 14 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001769.html 21 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001806.html 11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! == Announcements == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next release! * The git master branch is now 0.3.5! == Discussion == l * From last week: Rust build tickets- #25895 needs review/testing (Catalyst is reviewing again), and #25386 now doesn't have an owner but is high priority. (NM is taking it on for a bit.) * How aggressive should we be with our code-movement refactoring stuff? == Updates == Nick: Last week: - Released new 0.3.4 and 0.3.3 versions - Opened the 0.3.5 branch - Wrote up plan for refactoring Tor's layout, in a first step towards modularity: https://pad.riseup.net/p/cJUbdx0c7IzM-keep - Made a little progress on fixing up Rust testing issues, thereby making our CI fail. :) - Did a big branch to split (most of) our structures out of or.h, as a first step in the refactoring thing. (#26383) This week: - Work on #25386 (rust test linking thing) - Try to advance "big patches" thing w/ Taylor. - Revise refactoring plan based on comments, and (I hope) begin splitting src/common - Try to learn the state of wtf-pad - Try to learn the state of wide create work. Maybe code some? - 0.3.5 ticket triage - Community friend rotation ahf: Last week: - Went to Mozilla all hands meeting in SF. - Looked at some s4 documents we wrote at the end of the sponsor period for Isa. - Looked at MacOS sandboxing after meeting the Mozilla sandbox people (created #26374) This week: Sponsor 8: - Flesh out plan for PT error reporting. Talk with the application team and the guardian project if the plan sounds good to them. Misc: - Catch up on review backlog. - Do post-travel expenses after Seattle and Mozilla all hands - CI and Coverity duty (switched with asn last week) Mike: Last week: - vacation This week: - Figure out PETS travel - Catch up on email - Catch up on trac tickets? - Vanguard performance experiments - Vanguard packagaing dgoulet: Last week: - Reviewed #20700. I'm not done, pretty big ticket (HSv3 client auth). - Started review on nickm refactoring (#26383). I should be done soon. - Mostly reviewed 034 tickets. - Discussed with asn the #24977 solution. We had a back and forth review/revision already on it. This week: - Continue ticket assigned to me in 034. But as a priority, #26383 since it is a BIG refactoring. #20700 review for early 035 merge. Then outstanding HSv3 open bugs (#24977 and #25552) - Authenticated SENDMEs (#26288 - prop289), I would like to go over the proposal to see if it is ready to be implemented (in theory it is I believe). Ideally, we get an early merge on that as well. - I'm not on any rotation this week. catalyst: last week (2018-W24): - looked over the or.h refactoring proposal a little - tried to fix the rust tests (#26245, #25386, #25378) - reviewed #25895 (Rust cross compilation) this week (2018-W25): - code review - #25507 (big contributions) with Nick - more work on #25386/#26378 (rust test linking) -- maybe we want to disable the problem test for now? komlo (offline): - Last Week - Continued to investiage #24249 (automated mechanism for type syncing), working on a comparison of our options for this week - Reviewed #26220. I will create a ticket for a community wiki page where we can track infrastructure community projects such as this per discussion with Roger. - Chatted with ahf and sysrqb about looking at libcontainer as an option for sandboxing across platforms. More investigation about current/future support for Windows is needed. - This week: - See above about todos from last week asn: [Currently travelling. Won't be at meeting today! :)] Last weeks: - Wrote code for #24977 (034 ticket) - Wrote code for #25552 (035 ticket). - Fixed small 034 ticket #26358. - Did code reviews (#26283, #26272). - Continued communication with large onion provider. This week: - Finalize any other 034 tickets under my name (i don't think there are any) - Do #26379. - Do reviews. isis: last week: - mozilla all hands & meetings with rust people - did some hackerone and trac triage - reviewed #24249 #26378 #26245 #26152 #25269 - fixed some minor rust issues #26245 #26267 this week: - going back to the large create cell mine #25651 - traveling all day tuesday, mostly working offline - taking friday afternoon off to attend a wedding

1 0

May Communications Report
by Stephanie A. Whited 18 Jun '18

18 Jun '18

Hello, Tor! In May, we continued our campaign to onionize the web, and in addition to our digital presence, we also had a successful booth at RightsCon. Thanks to Kat, Sukhbir, Sina, and Jon for the help! Written or edited posts https://blog.torproject.org/privacy-international-protects-partners-its-oni… https://blog.torproject.org/get-help-running-your-relay-our-new-advocate https://blog.torproject.org/tor-tails-ux-identifying-user-needs-cryptorave-… https://blog.torproject.org/domain-fronting-critical-open-web Twitter Avg 3 posts/weekday Tweets: 99 New followers: 2,382 Top tweets: https://twitter.com/torproject/status/992388549013012485 https://twitter.com/torproject/status/996103057946632192 https://twitter.com/torproject/status/1002213999310721024 Mastodon At least 1-2 posts/wk New followers: ~200 LinkedIn At least 1 post/wk New followers: 47 FB 1 post/weekday New followers: 142 Newsletter 1/month https://newsletter.torproject.org/archive/2018-05-31-domain-fronting-relay-… Notable press http://www.cbc.ca/news/technology/ooni-tor-information-controls-measurement… https://www.zdnet.com/article/technology-that-changed-us-the-2000s/ o/ - comms -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Key ID: 39A876AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

Monthly spreadsheet - User queries, issues, demands...
by cy63113 17 Jun '18

17 Jun '18

Hi everyone, I am the new user advocate intern (and I'm loving it!), I'm working gathering users queries, issues, demands... in many Tor channels. This is the first time sending this spreadsheet out, so if there are any suggestions to improve it, please let me know! You can reach me by email or IRC: cy63113 I'm basing on the methodology of the former intern and using the identification of "Power users" and "Regular users" (https://trac.torproject.org/projects/tor/wiki/UserIssuesResearch). This is the overall description of the channels: - *f**rontdesk@*: most of the issues and queries are from beginner users (“regular users”), about installation and connection problems, these problems are usually solved by uninstalling and reinstalling, correcting the system clock, and disabling the antivirus/ firewall. In this channel I *suggest*, if feasible, in Tor contact page - email, make it clear that when writing an email, the subject must be objective, e.g. "Connection failure", "I need a bridge", etc., because there are several emails without subject and many that look like and are marked as spam. And in addition something like " In order to get a faster response, if possible, please write in English, Spanish, and/or Portuguese” - or any language you are comfortable to answer. This would facilitate for those who respond and therefore, the response would be faster. - *IRC:* #tor: some interactions, mostly of “heavy users”, some nonsense, grievances and hate speech #tor-offtopic: very few interactions, some nonsense, grievances and hate speech #tor-project: interactions of more experienced users - *Tor blog*: there are more comments than issues, queries and grievances - *Twitter*: there are lots of comments, very few issues and queries - *Facebook*: very few comments, some reactions and shares, and so far, 1 query (Can’t install in Win 10) - *StockExchange and Tor subreddit*:a mix of tech-savvy and beginner users. Mostly are general questions that need more instructions, frequently because they don't read Tor’s documentation (too extensive). Here you can constantly notice the use of Tor and deep / dark web as synonyms. You can check the May spreadsheet here: *https://ethercalc.org/may_2018** * Cheers, Cybelle

2 1

Damian's Status Report - May 2018
by Damian Johnson 15 Jun '18

15 Jun '18

Hi all, here's my status update for this last month! https://blog.atagar.com/may2018/

1 0

Notes from June 14 2018 Vegas team meeting
by Karsten Loesing 15 Jun '18

15 Jun '18

Notes for June 14 2018 meeting: Nick: 1) Might be late/absent depending on morning schedule; will try to read and respond to backlog and notes. 2) New releases out; 0.3.4 is on its way to stabilizing 3) If there's something you need the network team to do this year, please make sure we know about it! (Getting Isa involved would be wise). Shari: 1) Lots of personnel stuff. We're about to make an offer to a new localization coordinator, job posting is up for fundraising director, job postings are about to go up for 2 project managers, looking at possible grant writers. Busy time! 2) Working on 2018-2019 budget for next week's board meeting. 3) Planning continues for the Mexico City meeting. We're trying to be more careful with our spending, so I'm the first step in all travel approval. Trying not to be a bottleneck. 4) Grant proposals move along. Submitted for Ford/Sloan research grant, asked for full proposal from OTF, interesting support possibilities for anti-censorship work. Alison: 1) Mexico City planning! 2) LFI is underway! 3) Colin is planning the PETS meetup! 4) Gus is working on lots of outreach including more sponsor9 planning! Georg: 1) We did emergency releases over the weekend (Tor Browser 7.5.5 and 8.0a8) 2) We have working Windows Tor Browser builds based on Firefox ESR60, and sorting the last things out to get the nightly builds for them going as well; we are still on track for the first alpha based on ESR60 in less than two weeks 3) Coordination with other teams for the Tor Browser 8 and Tor Browser for Android launch 4) Shari: Where are we with the IRC coordination plan for the domain fronting follow-ups? [Georg: This got postponed a bit due to other high-prio stuff but it's still planned to get to it]

1 0

[TSoP] stem.client - status report #2
by Dave Rolek 13 Jun '18

13 Jun '18

Hey everyone! This is my second status report for the stem.client TSoP project [1]. My previous report was posted to the tor-project ml last month. [2] This report comes a few days late - sorry about that! # Updates ## stem.client The last few weeks I focused heavily on code review [3], and a bit on stem.client architecture [4]. The outputs of the code review are comments in the Trac ticket [5][6] and stem's first pull request on GitHub [7], including various bug fixes [8][9][10][11][12][13][14] and other improvements [just see 7 for all other commits]. The outputs from the architecture task are currently on a private pad. They'll be shared more widely after some discussion with atagar and teor. These two tasks have taken more time than I anticipated, so there hasn't been much else I've done. ## tor protocol, general For stem.client, I looked at leveraging existing binary serialization/deserialization libraries. At this time, I've decided none of them fit well in the scope of stem.client, but I've taken some notes on them to share later. They may be useful to the wider tor dev community. Kaitai Struct [15] looked the most promising, having a YAML-based language that helps produce deserialization code in a number of programming languages. Unfortunately it doesn't presently support serialization, but it does seem to be a goal of that project. If time allows for this TSoP project, I'll write up a .ksy definition just to try it out. (I also looked a bit at trunnel. Cool stuff!) # What's next ## stem.client I'll be waiting on atagar for a bit of feedback, but then probably implementing some of the architectural changes. I'm excited to do them! In the interim, I'll be taking care of some of the not-so-architecture-dependent changes. I'll also be filing and fixing a few 'dev' tickets, to make development easier. ## tor-spec, readability updates I started this project work (pre-proposal) diving into the tor-spec [16] but admittedly didn't read the tor-design paper [17][18][19] beyond a glance in the past. So some of the higher-level organization of communication designs was lost on me. When I finally realized from the spec that all of a RELAY_CELL payload is encrypted, not just the data portion, I noted this in IRC, and Roger pointed me to the paper. Oops! I should've read that long ago. So I'll be catching up on that while doing further stem.client implementation. Because of this roundabout intro to the communication protocol, I have some insight into how various tor-spec sections could be improved so that high-level context is clearer when someone jumps into reading specific sections of the spec. I'll be collecting this feedback and submitting clarification patches for review. (As a side note, you can see I've done this sort of readability improvements on Wikipedia in the past [20].) Pre-project, Roger suggested I collect spec updates and submit them for review en-batch, so I'll plan to do that over the course of the project. # Other Tor things Cryptoparty Ann Arbor held a workshop at the local library on Saturday [21]. It went pretty well! I'm participating in the community meeting today (happening now in #tor-meeting), so more specific updates will be therein. I've also welcomed a few new developers to the community, mostly within #tor-dev. One of them posted to the tor-dev list [22], so I encourage you to check it out, if you haven't gotten in touch with Simon off-list already. # Closing As with before, I've been active and reachable over IRC, where my nick is dmr. Please don't hesitate to reach out to me via IRC or email! Thanks, Dave [1] https://lists.torproject.org/pipermail/tor-dev/2018-April/013090.html [2] https://lists.torproject.org/pipermail/tor-project/2018-May/001811.html [3] https://trac.torproject.org/projects/tor/ticket/26227 [4] https://trac.torproject.org/projects/tor/ticket/26226 [5] https://trac.torproject.org/projects/tor/ticket/26227#comment:4 [6] https://trac.torproject.org/projects/tor/ticket/26227#comment:5 [7] https://github.com/torproject/stem/pull/1 [8] https://github.com/torproject/stem/pull/1/commits/9ce64fc2baf0f5032e9fb76d9… [9] https://github.com/torproject/stem/pull/1/commits/3afe3c1b8ae49275e2586f76f… [10] https://github.com/torproject/stem/pull/1/commits/912769c4c1e5bd14e6f053aba… [11] https://github.com/torproject/stem/pull/1/commits/3fa2d718147c761375d3b21dc… [12] https://github.com/torproject/stem/pull/1/commits/e899aae0eea7ff39f67a62cf0… [13] https://github.com/torproject/stem/pull/1/commits/ba275219bd50dfc408befca81… [14] https://github.com/torproject/stem/pull/1/commits/476b57a5aabf0c0d31998a088… [15] https://kaitai.io/ [16] https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt [17] https://www.torproject.org/docs/documentation.html.en#DesignDoc [18] https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf [19] https://svn.torproject.org/svn/projects/design-paper/tor-design.html [20] https://en.wikipedia.org/wiki/Special:Contributions/David_Rolek [21] https://aadl.org/node/372209 [22] https://lists.torproject.org/pipermail/tor-dev/2018-June/013205.html p.s. I get quite a chuckle out of this commit - gotta have some fun while developing: https://github.com/dmr-x/stem/commit/ba275219bd50dfc408befca81ef4d3116008db…

1 0

Network team meeting notes, 11 June 2018
by Nick Mathewson 12 Jun '18

12 Jun '18

Hi! Our logs from yesterday's meeting are at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-06-11-16.58.html Our notes follow below: -------- = Network team meeting pad, 11 Jun 2018 = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) == Previous notes == 23 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001747.html 30 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001750.html 7 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001760.html 14 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001769.html 21 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001806.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Community guides, it's time to hand off to the next guide! == Announcements == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next release! * Important dates: 15 Jun -- 0.3.5 merge window opens. == Discussion == * Finalizing plan to repurpose patch-party time. -nm * Ratifying some EU/AUS meetup time, to be used as needed? The best choice for now seems to me like 0700 UTC (== 9am Berlin, 5pm Brisbane), but maybe I shouldn't be driving this process. -nm * New rotation to advance proposals via discussions, to replace the Coverity rotation? -nm * Are there any wiki notes pages, or pads, that we haven't opened our tickets for? -nm * Shall we discuss proposed tickets for the milestone each week? * Rust build tickets- #25895 needs review/testing, and #25386 now doesn't have an owner but is high priority. == Updates == komlo: (offline) Last week: - Put up an initial POC for #24249 which currently only autogenerates C constants from a Rust constants file, but can be extended to structs, enums, etc. I have some questions for others on it, such as whether this should be an internal or external tool, etc. - Added clarification to #24265 about what is needed for that ticket so new people interested in contributing in Rust can pick it up, please update with any further detail. This week: - Will soon start on #26296 which is the refactoring work required prior to assessing approaches to implementing multi threaded crypto ($1749) ahf (will be traveling during the meeting time, so offline, please highlight me if you need anything from me) Last week: Misc: - Returned from Seattle: backlog of email/irc Sponsor 8: - Began working on a design for PT error reporting. Talked shortly with mcs and geko about some expectations from the browser team. - Wrote a patch for #26270 This week: - At the Mozilla All Hands in SF. asn: Last weeks: - Debugged #24977 (034 bug) and wrote two different patches for it. Feedback might be needed from Nick to help decide which approach to take (see comment:24). - Revised my test OPE branch for #25552 in a way that I think now works fine. I've been testing it for the past weeks and it's now working without any interruptions. I've been getting more familiar and more comfortable with the OPE approach. I heard Roger has some concerns here, but he did not comment on the ticket. Please comment on the ticket if so, because we are hoping for an early merge on the 035 timeline. I still need to fix some broken unittests and do some improvements on the branch before it's actually reviewable. The current iteration can be seen in my (ope_hax_dev) branch. - Coordinated with big provider about potential use of onion services. - Did weekly reviews as needed. - Did some review and testing of the vanguards script. Made a few PRs and opened issues. This week: - Finalize relevant open 034 tickets (e.g. #24977). - Finalize #25552 ticket so that it's ready for early inclusion in 035. - Weekly reviews as needed etc. Nick: Last week: - Post-Seattle followup - Small review and merging - Open/close tickets - Jetlag recovery :/ This week: - Release 0.3.3.7 and 0.3.4.2-alpha - Initial refactoring batch for 0.3.5. Mostly movements in common, splitting or.h. Any objections? Should I go smaller? Larger? [dgoulet: +1, related, see #26270] - Prepare for 0.3.5 merge-window opening - Informal meetings with 0.3.5 collaborators - Proposal scheduling rotation dgoulet: Last week: - Post-Seattle which included recovery. - Reviewed my assigned tickets for 034. - Not much else to report. This week: - Focusing on 034 tickets. Tight follow up on my review tickets. - Preparing for the 034 merge window, I'll go over #20700 with my notes. Ideally, we can get that in early in the merge window. - Will also try to start preparing big 035 roadmap items, break them down, prepare the work and synchronize with others assigned to them. - No rotation for me this week! haxxpop: Last week: - Nothing This week: - Will read the spec of prop279 naming layer api. - If the UX of client auth is ready, I will revise my PR. catalyst: last week (2018-W23): - travel - recovery from travel - started to review #3569 (refactor SOCKS parsing) -- this one might take a while this week (2018-W24): - code review - bookkeeping - #25507 (big patches guidelines) - #25601 (prevent non-origin connection errors from failing relay bootstrap) - maybe more health insurance annoyances dmr last last week - filed #26228 to get clarity in the tor-spec on how to do padding / make terminology a bit more consistent - would like to move this forward; not sure who else might want to provide input (nickm, teor, arma provided input so far; dgoulet un-cc'd) - worked on stem.client code review and architecture notes (#26227, #26226 respectively) last week - worked on stem.client code review and architecture notes (#26227, #26226 respectively) - submitted several commits resulting from code review (#26227, see GH pull request) - ran through most of the Seattle meeting notes; have some feedback to provide on... - mobile CI => "device farm" testing options, e.g. https://aws.amazon.com/device-farm/ https://firebase.google.com/docs/test-lab/ - macOS CI, if on own hardware, e.g. (so probably not for travis) https://github.com/kholia/OSX-KVM - LTS - relay-op friend mentioned that Debian stable packaging was out of date for a while, so switched to TPO repo - question for catalyst regarding modularisation notes from Seattle meeting: - who do we know is downstream from tor? - TB, debian, ubuntu (sorta), tails, gentoo, whonix, invizvox, arch, guardian project, freebsd, ... ? -nm - got some spec clarifications from teor and asn (thanks!) - tor-spec and pt-spec respectively this week - finish #26227, #26226 - work on transitioning stem.client to new architecture as per discussions in #26226 - so file tickets and whatnot - file various 'dev' tickets for stem; fix a few isis: last two weeks: - seattle - took a couple days off after getting back - worked a bit on ed25519-dalek integration on the plane #23886 - so much email piled up by the time i got back :/ - prep for all hands meetings this week, making various moz accounts, signing forms - added support for rust linting tools #22156 - reviewed #26152 #24891 #26259 - began helping a new contributor with their first patches this week: - expenses for seattle - all hands tonight through saturday morning - doing other small tasks in between all hands meetings, hopefully

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project June 2018