[tor-project] Notes from network-team meeting, 4 Sep 2018
Nick Mathewson
nickm at torproject.org
Tue Sep 4 17:52:49 UTC 2018
Hi!
Our meeting logs are at:
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-09-04-16.59.html
Below are the contents of this meeting's pad.
= Network team meeting pad! =
Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC.
This week we're meeting on Tuesday 4 September, because Monday 3
September is a US holiday.
(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.html
for background.)
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 ==
11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html
18 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001835.html
25 June: https://lists.torproject.org/pipermail/tor-project/2018-July/001863.html
2 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001866.html
9 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001884.html
16 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001888.html
23 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001926.html
30 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001928.html
6 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001936.html
13 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001947.html
20 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001954.html
27 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001963.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/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrriaYfUBQ/edit#gid=856122210yy
* Check reviewer assignments at
https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrriaYfUBQ/edit#gid=95993070
* 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/TeamRotations
* Community guides, it's time to hand off to the next guide!
* Let's look at proposed tickets! [but see discussion]
https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~035-roadmap-proposed&max=200&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority
== 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
-------------------------------
---- 4 September 2018
-------------------------------
== Announcements ==
== Discussion ==
(teor: I put some CI questions here. But let's talk about CI at the
Tor Meeting in a few weeks time.)
teor: We have some very productive volunteers.
How can we balance reviewing their code, and our other tasks?
Here's what I think we can do:
* run their code on CI before reviewing
* ask them to open pull requests on GitHub, or push their branches ourselves
* ask them to write unit tests
* let them know that some reviews will be delayed until mid-September
* ask them to review each others' code?
== Updates ==
Nick:
Last week:
* Drafted a sidechannels-and-datagrams whitepaper; got fast
feedback from Mike
* Backend for memory reduction via more efficient family storage
* Tracked down a memory leak in my NSS code. (This took way
more time than you'd think.)
* Made new rotations.
* Reviewed and merged a bunch of stuff.
* Released 0.3.4.
This week:
* Revise and expand sidechannels-and-datagrams whitepaper.
* Further revisions to NSS code TBD
* more memory hacking as needed
* more review, possibly even on non-sponsored stuff, time permitting.
* Start working on next stable releases.
* More tests for TLS code?
* Revise code based on reviews
teor (offline):
last week (+ Monday this week):
- Worked on fixing failures in chutney due to 0.3.4 changes
(#27146 and children)
- Reviewed the fixes to the vanguards patch (#25573)
- Bwauth work (#27107, #27341, #27398)
- Emailed Travis CI to fix startup hangs and network failures (#27366)
- Reviewed some UTF-8 patches (#27367)
- Windows CI is broken (#27389)
- Other fast fixes, reviews, and ticket triage
- Helped purge old trac admin accounts
this week:
0.3.4:
- Get chuntney working in mixed 0.3.3/0.3.4 networks (#27146)
- maybe we should run chutney in travis CI? (#20647)
- our macOS time API seems to return weird results on i386 (#26987)
- Create an updated list of fallback directory mirrors (#24786)
0.3.5:
- bwauth work (#27135)
dgoulet:
Last week:
- HS ticket triage and work on some.
- Finalized for upstream merge #20700. nickm: This is rather
large... if you want, you can defer this to me and asn for upstream
merge? (no, I'm cool with it -nick)
- Started working on #27359 using nickm's backend code.
- Bad relays activity was high last week so spent some time there.
This week:
- Finalize #27359.
- Hunt around for tickets needed to be completed pre-freeze.
catalyst:
last week (2018-W35):
- proof of concept of deferring directory bootstrap status (#22266)
this week (2018-W36):
- community guide rotation
- clean up #22266 work a little (mostly improving tests)
- add connection tracking abstraction for bootstrap reporting (#22266)
- make some progress on #25502 (PT progress in bootstrap
reporting) ahf, i left a rough sketch of an incremental piece i plan
to work on in a comment at
https://trac.torproject.org/projects/tor/ticket/27100#comment:2
ahf:
Last week:
Sponsor 8:
- Looked at Nick's NSS RSA and TLS code (#26819). Wrapped
my head arouns the NSS API's.
- Looked shortly at #27255 (mmap of cached consensus),
gonna postpone that until my other S8
tasks are done (#25502).
- Back to #25502 (PT bootstrap error handling)
Misc:
- Looked at Marionette status.
- Got through my review queue from before vacation
(#24104, #17873, and #24204)
- Some discussion about DEFCON badges with Steph.
This week:
Sponsor 8:
- Follow up on NSS-TLS reviews.
- Focus on #25502.
Misc:
- Bug triage role.
asn:
Last week:
- Wrote a draft of the "onion services open issues" blog post based on Mike's
README_SECURITY document. Circulated it to David and Mike. We need some more
thinking on the right way to publish it, so that it does not sound alarmist
but still informs people of the open issues with onion services.
- Review #26818.
- Tested onionshare's onion v3 support.
- Updated v3 wiki page to bring it more up to date.
- Started debug on another HSv3 descriptor upload fail (the only one
around atm): #27436
This week:
- Think more of the way we should publish the "onion services open issues"
blog post. Talk more with Steph, David and other people who might have
feedback.
- Do reviews.
- Help with open v3 issues
Mike:
Last week:
- Updated #25573 based on review, made a merge branch on master.
- Reviewed #27241; have some questions there
- Vanguards bug fixes + v0.2.2 release
- Reviewed asn's onion services post; updated README_SECURITY
- Reviewed and commented on Nick's side channels paper
- Replied to teor's sbws tor-dev thread.
- Failed at CI; really hate digging through jenkins. Kept putting it
off until it was too late :/
This week:
- WTF-PAD/Sponsor2 work
More information about the tor-project
mailing list