- tor-project - lists.torproject.org

Network team meeting notes, 24 June 2019
by Nick Mathewson 25 Jun '19

25 Jun '19

Hello! You can read the logs from yesterday's meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-24-17.00.html Below are the contents of our meeting pad. = Network team meeting pad! = This week's team meeting is at Monday 24 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 24 June at 1700 UTC July schedule: * Wednesday 3 July 2300 UTC * Monday 8 July at 1700 UTC * (In-person meeting 12-14 July) * Monday 22 July 1700 UTC * Monday 29 July 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) 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! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 28 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002338.html 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html 10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html 17 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002365.html == Stuff to do every week = * How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… * Let's check the 0.4.1 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… Click on 'all boards' and then the network team one. Filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Any blocker from last week? == Reminders == * 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 releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. When you are overloaded, it is ok to say "no" to things. And it is ok to reschedule things. ------------------------------- ---- 24 June 2019 ------------------------------- == Announcements == [REMINDER] WIP Schedule for Tor meeting https://nc.riseup.net/s/FFkikRBmKDZyLw9 The master branch is now 0.4.2.x. 0.4.1.x development continues on maint-0.4.1 and release-0.4.1. 0.3.4.x is now end-of-life. Summary the mail thread on proposal from Dgoulet https://nc.riseup.net/s/gQGT8kjNgt3C6cd == Discussion == Retrospective on Thursday. How people want to do the retrospective? (please vote) jitsi +1 +1 irc other? #29697 Anybody up to team with boklm to coordinate archive.tpo Please update https://pad.riseup.net/p/network-team-draft-CI-role and vote yes/no on the change into a permanent role for CI. Can we start soon? Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity ahf -> catalyst coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) Looking at coverity -- it seems our builds may have been stuck. I've cancelled the stuck builds. Also, they say they are going to have a planned outage to upgrade their backend, starting today and lasting about 3-4 days. Friday would be a good day to have another look. -nm jenkins Travis teor did some work on stem failures, we need to add a control message trace to tor to diagnose (#30901) waiting for catalyst's advice, because they are refactoring this code Appveyor Bug triage teor -> ahf Everything seems ok, I might have missed some patches and things earlier in the week. == Recommended links == == Updates == NOTE NEW FORMAT! Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: Last week (actual): . gitlab This week (planned): . sponsor 31 adjustment with new tickets . more gitlab Help with: teor: (offline at the usual meeting time) Week of 17 June (planned): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fix existing open tickets where I have added the sponsor - Fallback directory mirror list rebuild (#28793) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - merge chutney pull requests - disown or quick fix tickets: I should only be owner on tickets I will work on in the next month - bug triage rotation Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Low-Priority: - backlog: router_have_consensus_path() logs an incorrect "no exits in consensus" (#27448) - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Week of 17 June (actual): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fixed some existing open tickets where I have added the sponsor - some code reviews - merged some chutney pull requests - Fallback directory mirror list rebuild (#28793) - draft list - need to work out why the list is so short this time (#30952) - some bug triage - sbws triage and fixes - Fixed PT extra-info bugs introduced in 0.4.1.1-alpha and 0.2.7.2-alpha (#30956, #30958) - disowned some tickets, more next week Important: - reviews of new onion service DoS code - designed API for pool abstraction - work on proposal/questions for possible trac migration - travel prep - process changes Week of 24 June (planned): Urgent: - fix existing open tickets where I have added the sponsor - Continue fallback directory mirror list rebuild (#28793) - need to work out why the list is so short this time (#30952) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - disown or quick fix the rest of my tickets: - I should only be owner on tickets I will work on in the next month - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Week of 24 June (actual): Urgent: - Important: - Low Priority: - Help needed: - catalyst, do you have advice on: - add tor controller trace logging to diagnose stem hangs (#30901) [catalyst: i'll try to look at it this week] Nick: Week of 17 June (planned): - Summarize employee feedback - PETS review - 0.4.0.6 release, maybe. - Reply to proposals 303 through 305, maybe. - Reviews and merges - 29211 -- refactor configuration code. - 29280 -- needs_revision, chutney in ci code - 27801 -- review proposed API for launching sockets with embedded tor - 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Week of 17 June (actual): - Code reviews - PETS review - Work on various 29211 subtickets. (configuration refactoring) - Start summarizing employee feedback. (4/6 done) - Defer 0406 release; start 0413 release - try to catch up with backlog Week of 24 June (planned): - Retrospective on Thursday - More 29211 work - 0413 release - attempt: Reply to proposals 303 through 305, maybe. - attempt: review 27801 api - attempt: 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Mike: Week of 6/17 (planned): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/17 (actual): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/24 (planned): - Bitcoin conference - code reviews - Catch up on mail catalyst: week of 06/17 (2019-W25) (planned): - reviews - control.c refactoring week of 06/17 (2019-W25) (actual): - chatted with ahf re #28930 (msybe reorder some PT/proxy bootstrap phases) - bureaucracy - wrote up #30911 to document some inbound email problems - cleaned up my owned tickets a little week of 06/24 (2019-W26) (planned): - CI+Coverity rotation - reviews - take a closer look at dgoulet's "radical changes" email thread - help teor with #30901 (control port trace logging for debugging test-stem hangs) - more bureaucracy - starting Stockholm trip prep - hopefully have time to work on control.c refactor asn: Week of 06/03 (planned): - Finalize s27 o2a1. - Help organize our AllHands experience. - Fix #30578 circpadding bug (041-must). - Do more work on HS DoS. - Some more travel prep for allhands. Week of 06/03 (actual): - Finally managed to get #30381 in needs_review. - Wrote some scaling emails. - Worked on #30578 (041-must). - Did some work on HS DoS: https://lists.torproject.org/pipermail/tor-dev/2019-June/013873.html - Cleaned most of my review backlog, but there is still more. - Merged prop304 to torpec. Week of 06/10 (planned): - #30381 is now in needs_revision. Need to do that. - More prepping for AllHands. Flying out on Sunday. - Try to do some work on s27 #26294 (intro point rotation dos) - Still got reviews hanging. In particular #30382. - I also got lots of hanging merges... Help needed: - teor, I still have troubles mapping all the pieces of #22029 in my brain. Perhaps at some point you can take over the review of that ticket, and I can take one big review from you? I don't see you having any big reviews this week, so perhaps we can wait until next week. teor says: I assigned myself as reviewer on this ticket. neel is still working on it, when he finishes, I will split off some of the small features so other people can review them. ahf Week of 17/6 (planned): Network team: - Finish off patches for #29736 so we can discuss the big changes at the Thursday meeting. - Continue with #28930. Misc: - Figure out what needs to be doing on some of the PT spec tickets I have. Week of 17/6 (actually): Network team: - Discussed #29736 and authentication patches during anti-censorship team meeting. - Rebased and discussed current changes for #28930 with catalyst and decided next step. - Wrote patches for CI build failures for Stem and Chutney in #30928. - Figured out next steps for #5304 Week of 24/6 (planned): Network team: - Continue iteration of #28930 and discuss progress with catalyst. - Write Tor patch for #5304 (spec is OK) - Bug Triage duty. - Work a little bit on 'untrac' (a small tool to import Trac tickets into Gitlab that Gaba and I talked about during my 1:1 last Friday). juga(offline): Week of 05/20 (planned) - Add Tor version to the bandwidth file (#30196) Week of 05/20 (actual) Week of 06/03 (plan) - Continue with #30406: Refactor header constants in sbws to use Stem's one dgoulet: (might be offline, getting sleep has been very rough in the last days...) Week of 06/10 (actual): - Tested and experimented with #15516. Had to wait a bit to get new machines from a friend at a hosting provider in order to start limited bw relays. Thanks to ahf for providing assistance with his fast relays. - Wrote prop305 (on tor-dev@) about ESTABLISH_INTRO parameters. See #30790. Thanks from teor/asn for early feedbacks! - Merges and reviews as always. Week of 06/17 (planned): - Finalize #30382 from asn's review. - Continue work on #15516. I'm hoping to drop the experimental results on the ticket, finzlie the branch for upstream merge. And then move on to prop305.

1 0

S27: Onion Services meeting this week: Tuesday 18th June
by Pili Guerra 25 Jun '19

25 Jun '19

Hi everyone, This is a reminder of our fortnightly S27: Onion Services project meeting happening this Tuesday 18th June at 15UTC on #tor-meeting. Please join us if you’d like to participate or feel free to just lurk :) Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

2 4

Anti-censorship meeting notes, 20 June 2019
by Philipp Winter 20 Jun '19

20 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-20-17.00.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 20th 17:00 UTC Weekly meetings, every Thursday at 17:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == * Our anti-censorship roadmap: https://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Our roadmap consists of a subset of trac tickets. * Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team" * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 20th June 2019 ---- --------------------------- == Announcements == * Sponsor 28 (RACE) next meeting will be on June 27th 1800 UTC at #tor-meeting == Discussion == * do we want to move to gitlab for snowflake? (try only with one component for now) --> we are going to wait until the issue of "guests filling tickets in gitlab" is resolved. * gaba created https://dip.torproject.org/anti-censorship/pluggable-transports/snowflake/b… * Let's test our obfs4 setup guide by asking people on tor-relays@ to set up new obfs4 bridges? * WebSocket in Snowflake: next steps. (ahf) * trac management: can we 'own' tickets only when we are working on them? if you are interested in a ticket then add yourself to cc. * is #23888 going to be able to happen on time? do we need to take it? == Actions == * == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. hiro: (gettor days are Thursday) This week: Next week: Past week: phw: This week (2019-06-20): * Reviewed #21315 (publish some realtime stats from the broker?) * Mostly implemented #9316 (BridgeDB should export statistics) * Got a frontdesk account and had a look at bridge-related tickets * With Cecylia's help compiled summary of what we know about the GFW and active probing * Pinged ICLab team again to see if they can periodically scan at least our default bridges * Sent more emails to PT implementers * So far only one response * Tested #23888 (Creating a Snowflake WebExtension addon) and left feedback * Went through old tor-dev@ threads to compile feedback on improving the PT spec Next week: * More work on moving forward with PT spec * More thinking about improving obfs4 * Get #9316 reviewed * Create a blog post for our sponsor 19 report #2. Help with: * Brainstorming features of obfs4 successor, and how to improve PT spec Gaba: (updated 2019-06-20) Last week: * playing with gitlab for snowflake: https://dip.torproject.org/anti-censorship/pluggable-transports/snowflake/b… * prepare tor meeting schedule This week (05/30): * ahf Last week: - Talked with Cecylia about WebSocket + authentication patches in https://github.com/ahf/snowflake/tree/features/websocket_r5 and what we should do next. (#29736 and friends) - Hack on #28930 This week: - Work on #28930 kat5: Last week (May 20): This week (May 27): dcf: 2019-06-20 Last week: - brainstormed some problems with the PT spec (https://bugs.torproject.org/29285#comment:5 ) - wrote ideas about protocol versioning and backward compatibility (#30704) - reviewed sequencing layer (#29206) - added meek-azure bridge, meek-azure CDN, and snowflake-broker CDN to the infrastructure survey Next week: - will be mostly offline next week, will miss 2019-06-27 meeting - look at WebExtension changes in https://bugs.torproject.org/23888#comment:24 - publish post-sanitization broker logs (#30731) Help with: cecylia (cohosh): last updated 2019-06-13 Last week: - submitted some PR's for pion/webrtc - starting modifying our snowflake code to use pion/webrtc as the library (#28942) - started familiarizing myself with Chutney - took a look at the snowflake webextension changes (#23888) Next week: (AFK on Friday) - update default STUN configuration (#26348) - address dcf's feedback on the sequencing layer (#29206) - continue work with integrating/evaluating pion/webrtc (#28942) - familiarize self with PT spec Help with: - broker stats (#21315) need a metrics team review (should we deploy what we have and store the output locally?) - browser team help for mingw toolchain (#25483) catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 arlolra: 2019-06-20 Last week: - nothing This week: - a bit of snowflake webextension Help with: - getting the webextension published (#30931)

1 0

CANVAS talk on ethical Internet measurement
by Philipp Winter 20 Jun '19

20 Jun '19

A few months ago, while still affiliated with CAIDA, I gave a talk on "Ethical Internet measurement: From outages to anonymity" at the CANVAS workshop in Bamberg, Germany. Part of my talk covered ethical research on the Tor network. The recordings are now online: <https://canvas-project.eu/videos/Workshop-Bamberg-Philipp-Winter.html> My slides are available here: <https://nymity.ch/pdf/canvas19-slides.pdf> Cheers, Philipp

1 0

S28: Resilient Anonymous Communication for Everyone
by Gaba 20 Jun '19

20 Jun '19

Hi people! We are going to start meeting monthly related to the new sponsor on obfuscated communications [0]. The goals for this periodic meetings are: 1. share what is happening with the rest of organizations in the project 2. share progress on Tor side 3. get the monthly report started Our first meeting will be on June 27th 1800 UTC at #tor-meeting in irc.oftc.net Please join us if you want to check how this project goes. [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 -- Project Manager: Network, Anti-Censorship and Metrics teams and OONI support gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Notes from June 13 2019 Vegas team meeting
by Karsten Loesing 20 Jun '19

20 Jun '19

Notes for June 13 2019 meeting: Roger: 0) Ola and Chelsea are still in jail. 1) We kicked off the RACE project, and this week Cecylia is meeting with the integration team to teach them that there is a pluggable transports API. 1b) Micah has a job posting up for a censorship circumvention developer / researcher to work for Georgetown in the DC area, on building better pluggable transports, on the theory of obfuscation, and (maybe less fun) on staying coordinated with all the other teams working on RACE. Think about whether you know a good person! https://georgetown.wd1.myworkdayjobs.com/en-US/Georgetown_Admin_Careers/job… 2) Our NSF CCRI proposal, for Rob to improve Shadow, has been recommended for funding. We'll be hiring a Shadow developer (managed by Rob) sometime this fall. Micah will be hiring one at Georgetown too. When that gets going, I'll be looking for volunteers on the Tor side to help steer the project to be most useful to Tor too. 3) I met with Prateek and Aaron Johnson this week to start revamping our NSF Medium proposal (with plans to submit it at the end of June). 4) I'm exploring the idea of getting phw and cohosh to work with the Tapdance folks on an NSF TTP proposal, or a Tapdance integration with Tor Browser, or both. 5) I went with Isa and Sue and Sarah last week to the MDF meeting to discuss strengthening our foundation connections. 6) I spent this past weekend at a local hacker con, reconnecting to the organizers of other American hacker cons and doing general outreach. 7) This week is the program committee discussion phase for putting together the FOCI program. 8) Next week a pile of us are going to Whistler for Mozilla All Hands. I'm going to lead some brainstorming to help us remember, and then sort and triage, all the things we ought to do to make Tor faster for browser users, with a focus on things that we already at-least-kind-of understand and just need to buckle down and do. 9) I'd like to call attention to Moritz's post about the future of torservers.net, since wherever it goes from here could be a big deal. 10) Pili, what news on the frontdesk@rt investigation? pili: I've been too busy with the community portal to look into it, once it's in a better shape I can look into it 11) I still owe people some peer reviews. :/ 12) We should build a plan for tea time and the Whistlers Sarah: 1) Productive meeting with MDF, Isa, Roger, and Sue last week. 2) Working on stewardship plans for major donors and foundations. 3) Pushing monthly giving program along and next set of invites will go out once we have a sample patch from the vendor. 4) Helping Isa set up and prepare for major donor meetings. 5) Preparing for a crowdfunding campaign BTCPayServer has offered to conduct for us. 6) Helping with MDF proposal. 7) Will be afk June 14, and June 19-24 but available on email and Signal. 8) Working on finding connectors to foundations and major donors we'd like to connect with. Nick: 1) Team got 0.4.1 out; master branch is now 0.4.2 2) What should I do about people with missing feedback? Gaba: 1) drafted scheduled from proposed sessions 2) helped MDF grant proposal 3) helped anarcat draft an evaluation to email and options going forward to discuss (next week?) here 4) started looking at report sponsor V 5) moz/tor meeting & helping with all hands corodination 6) RACE meeting and trying to keep up with it 7) gettor organizing is happening in gitlab 8) other tasks like roadmaps update/checking Mike: 1) Working on metrics; meeting scheduling; tuning and R&D items for Mozilla all hands 2) Considering topics for Tor meeting 3) Working on peer feedback 4) Feeling a little ill Steph: 1) getting situated after holiday, going through a lot of emails 2) will submit for def con ama w roger this week. plans for a badge are moving fwd - thanks to anto for the design help! 3) community portal feedback Pili: 1) Still trying to get community portal ready 2) Helping out with dev meeting schedule 3) Reviewing media.tpo and trying to come up with a plan to unify with https://github.com/TheTorProject/tor-media as well as UX content 4) Still haven't got around to looking at Frontdesk :( 5) Season of Docs enquiries 6) Started working on updating S9 Phase 3 workplan comments 7) usual roadmap and ticket gardening Karsten: 1) Preparing for All Hands. 2) Reprocessing OnionPerf logs to include more detailed error codes in results. Sue: 1) Meeting with Isa, Sarah, Roger and MDF 2) General Accounting Stuff Georg: 1) We finally got all our point releases out, yay! 2) HackerOne bug triage 3) slowly prepping for Whistler 4) toolchain work and reviews for Firefox 68 ESR transition Antonela: 1) testing OONI Probe for desktop, opening some issues, working in OONI Explorer 2) working with fundraising on a monthly donors campaign 3) working with s27 onions, review #30024, meeting stakeholders 4) TBA - worked on #30540 and #24920 5) TB - reviewing acat proposal for ESR68 and scoping ux work for it 6) organizing user research material, syncing with Narriral about the latest Uganda trip, organizing next Kenia visit 7) organizing sessions for the dev meeting isabela: 1) Met with MDF last week 2) Board meeting this week 3) Working on follow ups from the MDF meeting 4) Reviewing MDF proposal and Sida anarcat: 1) hardware survey in progress 2) worked on an evaluation for the email hosting and alternatives, still in progress, expect more discussion next week 3) started looking at trac to gitlab migration, might be controversial but so far so good https://trac.torproject.org/projects/tor/ticket/30857 4) almost done with huge internal puppet project, very satisfying but less shiny than the prometheus stuff

1 0

Software developer to work on Tor Pluggable Transport ecosystem and censorship circumvention
by Gaba 18 Jun '19

18 Jun '19

Hi! In one of the projects we are working on right now, one of our partners (Georgetown University) is looking for a programmer/software developer. Please apply or share it with people that may be interested in it. Position: https://georgetown.wd1.myworkdayjobs.com/en-US/Georgetown_Admin_Careers/job… thanks gaba -- Project Manager: Network, Anti-Censorship and Metrics teams and OONI support gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network team meeting notes, 17 Jun 2019
by Nick Mathewson 17 Jun '19

17 Jun '19

Hello! You can find our meeting log at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-17-17.01.html . Below are the contents of our meeting pad. = Network team meeting pad! = This week's team meeting is at Monday 17 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 17 June at 1700 UTC * Monday 24 June at 1700 UTC July schedule: * Wednesday 3 July 2300 UTC * Monday 8 July at 1700 UTC * (In-person meeting 12-14 July) * Monday 22 July 1700 UTC * Monday 29 July 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) 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! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 20 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002335.html 28 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002338.html 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html 10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html == Stuff to do every week = * How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… * Let's check the 0.4.1 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… Click on 'all boards' and then the network team one. Filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Any blocker from last week? == Reminders == * 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 releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. When you are overloaded, it is ok to say "no" to things. And it is ok to reschedule things. ------------------------------- ---- 10 June 2019 ------------------------------- == Announcements == [REMINDER] WIP Schedule for Tor meeting https://nc.riseup.net/s/FFkikRBmKDZyLw9 [INFRA] Do you have problems with email? Please report any problem (or not) that you may have here: https://trac.torproject.org/projects/tor/ticket/30608 (also https://help.torproject.org/tsa/doc/reporting-email-problems/) The master branch is now 0.4.2.x. 0.4.1.x development continues on maint-0.4.1 and release-0.4.1. 0.3.4.x is now end-of-life. == Discussion == Please comment on the draft meeting agenda, see the tor-meeting list for details Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity ahf -> ahf (ahf takes another week here after having talked with asn who is at mozilla all hands). coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) ^ is from last week, what happened this week? Looking at coverity -- it seems our builds may have been stuck. I've cancelled the stuck builds. Also, they say they are going to have a planned outage to upgrade their backend, starting today and lasting about 3-4 days. Friday would be a good day to have another look. -nm jenkins Travis teor did some work on stem failures, we need to add a control message trace to tor to diagnose (#30901) waiting for catalyst's advice, because they are refactoring this code Appveyor Bug triage nickm -> teor I think I'm up-to-date, but please let me know if there are any unhandled piles of tickets that you think I should go back to -nm. == Recommended links == == Updates == NOTE NEW FORMAT! Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: Last week (actual): . stockholm meeting planning . scalability meeting This week (planned): . sponsor v and 2 . sponsor 31 adjustment with new tickets . more gitlab Help with: teor: (offline at the usual meeting time) Week of 10 June (planned): Urgent: - More HR stuff - Fallback directory mirror list rebuild (#28793) - Get gus access to the fallback-scripts repository - Get gus an LDAP account - Help close Sponsor 19? - code reviews - work on stem CI hangs? - do end of life tasks for 0.3.4 Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - revise reject bridge descriptors on authorities (#16564) - waiting for an initial review - still need to do another review of #29280 - work out which roadmapped work to do next: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - off-by-default module practices (#29224) - remove unneeded dependencies for tor roles: client, relay, etc. (#29227) - merge add chutney to tor's CI (blocked on stable Tor CI) - backport backlog (blocked on stable Tor CI) Low-Priority: - document disabled CI (#30745) - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? - revise tor_addr_port_lookup() is overly permissive (#30721) - improve documentation for chutney warnings in make test-network-all (#30455) Week of 10 June (actual): Urgent: - code reviews - Fallback directory mirror list rebuild (#28793) - Get gus access to the fallback-scripts repository - Get gus an LDAP account - did end of life tasks for 0.3.4 - made progress on stem hangs, turns out tor needs more logging to diagnose them (#30901) Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - made progress on add chutney to tor's CI (#29280) - merged chutney pull requests - merged CI backport backlog, still need to triage the rest of the backlog - try to work out how to write a pool abstraction, to help us solve bootstrap issues - helped fix some critical sbws issues - triaged some of the tickets where I am the owner on trac Low-Priority: - Fix Tor's address parsing so it's more consistent (#30721), turned out harder than I thought - improve documentation for chutney warnings in make test-network-all (#30455) Week of 17 June (planned): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - Fallback directory mirror list rebuild (#28793) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Low-Priority: - backlog: router_have_consensus_path() logs an incorrect "no exits in consensus" (#27448) - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Nick: Week of 10 June (planned): - Open 0.4.2. - Deprecate 0.3.4. - More analysis for walking onions, time permitting - Review and merge - Revise chutney/CI improvements: - 29280 (Use Chutney in Tor's CI) - 29024 (chutney and PTs) - 30459 (Let chutney tell Tor whether a network is supported) - Finish handle refactoring and cleanup (29218) - Plan configuration refactoring - More modularization? Week of 10 June (actual): - Started on 29211 (refactoring config code): planning, testing, initial refactoring. - Revisions on chutney-ci 29280 - Unrecommend a big pile of versions. - Revise 29024 and 30459 (chutney related) - Triage rotation Week of 17 June (planned): - Summarize employee feedback - PETS review - 0.4.0.6 release, maybe. - Reply to proposals 303 through 305, maybe. - Reviews and merges - 29211 -- refactor configuration code. - 29280 -- needs_revision, chutney in ci code - 27801 -- review proposed API for launching sockets with embedded tor - 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Mike (not at meeting; travel to Mozilla): Week of 6/10 (planned): - Mozilla all hands planning/discussion - Scalability metrics review/page reorg - Peer feedback - Register for PETs - Circpad documentation? Week of 6/10 (actual): - Mozilla all hands planning/discussion - Scalability metrics review/page reorg - Peer feedback - Register for PETs Week of 6/17 (planned): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization catalyst: week of 06/10 (2019-W24) (planned): - reviews - some sponsor31 tickets week of 06/10 (2019-W24) (actual): - reviews - bureaucracy - some control.c refactoring - figured out some mysteries about code that coccinelle has trouble looking at - chatted with nickm week of 06/17 (2019-W25) (planned): - reviews - control.c refactoring asn: Week of 06/03 (planned): - Finalize s27 o2a1. - Help organize our AllHands experience. - Fix #30578 circpadding bug (041-must). - Do more work on HS DoS. - Some more travel prep for allhands. Week of 06/03 (actual): - Finally managed to get #30381 in needs_review. - Wrote some scaling emails. - Worked on #30578 (041-must). - Did some work on HS DoS: https://lists.torproject.org/pipermail/tor-dev/2019-June/013873.html - Cleaned most of my review backlog, but there is still more. - Merged prop304 to torpec. Week of 06/10 (planned): - #30381 is now in needs_revision. Need to do that. - More prepping for AllHands. Flying out on Sunday. - Try to do some work on s27 #26294 (intro point rotation dos) - Still got reviews hanging. In particular #30382. - I also got lots of hanging merges... Help needed: - teor, I still have troubles mapping all the pieces of #22029 in my brain. Perhaps at some point you can take over the review of that ticket, and I can take one big review from you? I don't see you having any big reviews this week, so perhaps we can wait until next week. ahf Week of 10/6 (planned): Network team: - Finish #28930. - Talk with traffic-obfuscation list people about #28849 - Talk to Cecylia and DCF about patches for #29736 and friends. Misc: - Presentation Thursday evening at the local union about Tor. - CI/Coverity role. Week of 10/6 (actually): Network team: - Went over #29736 and friends with Cecylia. We decided to ignore the proxy authentication part for now and continue with the rest, but in a way where it can be disabled on the broker side in case of a problem. It is a very big change to the Snowflake codebase, so that seems reasonable. - Hacked a bit on the Snowflake changes for #29736 after the conversation with Cecylia. - Hacked on #28930. - Some relay setup for asn and david for some experiments they are doing. Misc: - Did presentation on Tor at the union's youth department in Odense. Went well. - CI/Coverity wasn't bad. - Some conversations about upcoming CC election. Week of 17/6 (planned): Network team: - Finish off patches for #29736 so we can discuss the big changes at the Thursday meeting. - Continue with #28930. Misc: - Figure out what needs to be doing on some of the PT spec tickets I have. juga(offline): Week of 05/20 (planned) - Add Tor version to the bandwidth file (#30196) Week of 05/20 (actual) Week of 06/03 (plan) - Continue with #30406: Refactor header constants in sbws to use Stem's one dgoulet: (might be offline, getting sleep has been very rough in the last days...) Week of 06/10 (actual): - Tested and experimented with #15516. Had to wait a bit to get new machines from a friend at a hosting provider in order to start limited bw relays. Thanks to ahf for providing assistance with his fast relays. - Wrote prop305 (on tor-dev@) about ESTABLISH_INTRO parameters. See #30790. Thanks from teor/asn for early feedbacks! - Merges and reviews as always. Week of 06/17 (planned): - Finalize #30382 from asn's review. - Continue work on #15516. I'm hoping to drop the experimental results on the ticket, finzlie the branch for upstream merge. And then move on to prop305.

1 0

Tor Browser team meeting notes 17 June 2019
by Pili Guerra 17 Jun '19

17 Jun '19

Hi, Here is the IRC log from our weekly meeting: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-17-17.31.l… and here are the items from our pad: Discussion: - Please review the list of dev meeting sessions and identify any gaps: https://nc.riseup.net/apps/onlyoffice/s/FFkikRBmKDZyLw9 - Is there any infrastructure that people in the tor browser team is using? Please fill in the spreadsheet: https://nc.riseup.net/apps/onlyoffice/s/QEM4MNBA8MmWW4x pili: Last week: - not very productive in Tor Browser terms, was afk for a public holiday on Monday and tonsilitis on Friday - Some general roadmap cleaning + work planning - dev meeting schedule - This week: - Dev meeting schedule - Helping GSoD candidates with their proposals - Tor Browser release meeting this week mcs and brade: Last week: - Worked on #30000 (Integrating client-side authorization to onion services v3). - Continued to work on the Onion Services client auth prompt (#30237). - Commented in #29285 (Improve the PT spec and how PTs interface with Tor). This week: - Review for #18101 (IP leak from Windows/macOS UI dialog with URI). - at the same time, test Snowflake on macOS 10.9.x. - More work on the Onion Services client auth prompt (#30237). - Soon: #29197 (remove use of overlays from Tor Launcher) - Soon: #30429 (ESR 68 Rebase — updater patches). acat: Last week: - Progress on DTD locale leak issue (https://bugzilla.mozilla.org/show_bug.cgi?id=467035) - Investigated why theme extensions were not enabled in ESR68 rebased branch (#30845). - Addressed GeKo's review comments on torbutton integration patch (#10760) - Some work on torbutton cleanup/refactor (#28745) This week: - Address review requested changes for https://bugzilla.mozilla.org/show_bug.cgi?id=467035. - torbutton cleanup/refactor (#28745) - maybe "Properties in dom/locales/$lang/chrome/ allow detecting user locale" (#30683). boklm: Last week: - helped with publishing 9.0a2 - made small patch for #30863 (Fix tor-android-service and tor-onion-proxy-library filenames) - finished patch for #28672 (Android reproducible build of Snowflake), now ready for review - updated patch for #30549 (Add script to remove expired sub-keys from a keyring file) - reviewed #30334 (build_go_lib for executables) - started reviewing #30585 (Provide standalone clang 8 project usable across all platforms) This week: - look at remaining failing testsuite tests - work on #30320 (Adapt Tor Browser toolchains for Firefox 68 ESR) child tickets. Not sure which yet. - fill infrastructure spreadsheet antonela: This week: - Looking at https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~Tor… issues - TBA - what we will do with #24920? and #30540? Any updates on #29955? [matt is out today, will keep it here for next week -A] - TB - ESR68 - reviewing acat proposal - TB - #30577 - pili: could we sync with sstevenson/steph to have some content for it? If we use the same code, is just text replacing. [for release meeting this week -A] - S27 - reviewing #30024, met stakeholders - Collecting/listing user problems for prioritization during the dev meeting pospeselr: Last week: - tracked down the cause of the reason for the accessibility crash of 32 and 64 bit tor browser on 64 bit windows (#27503) - caused by fix introduced by one of the wine devs to fix another of our crashes This week: - working with wine devs to fix this last crash - introduce the widl fix into tor-browser-build - babysit the fix submissions into wine tree Thanks, Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

Tor Browser Release Meeting this week: Wednesday 19th June
by Pili Guerra 17 Jun '19

17 Jun '19

Hi everyone, It’s that time again :) Please join us for the Tor Browser Release meeting this week on Wednesday 9th June at 18:00UTC on #tor-meeting. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0