[tor-project] Network team meeting notes, 20 Aug 2018
Nick Mathewson
nickm at torproject.org
Mon Aug 20 22:36:08 UTC 2018
Hi!
You can find our logs at
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-08-20-17.00.html
Below are the notes from our meeting today:
= Network team meeting pad! =
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.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
== 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
-------------------------------
---- 20 August 2018
-------------------------------
== Announcements ==
"""
Sponsor8 ends on Dec 31, and we have some deliverables that needs to
make 035. The 035 merge window closes on Sept 15. With that in mind,
we need to prioritize these deliverables, and ask some folks to step
out from rotations and most code reviews for the next month or so, so
we can get it all done.
Code reviews will also prioritize sponsor8 work, so, some reviews
might be delayed and not added to the weekly review spreadsheet.
For the rest of us, we don't intend that reviews and rotations should
take up your whole life. If you're spending more than 20% or so of
your week on reviews and rotations, then we might need to recalibrate.
Talk to Nick and Isa if that sounds like the situation you're in.
We will resume normal team operations once we get the sponsor8
deliverables done :) thank you for the understanding.
"""
If anyone has an opinion on bwauth scaling and how sbws needs to match
torflow, please contribute to:
* https://github.com/pastly/simple-bw-scanner/issues/182
* Trac #27135
We don't want to be making last-minute changes to the design.
== Discussion ==
Do these tickets block 0.3.4:
- our macOS time API seems to return weird results (#26987, #27139)
- did we break the consensus between 0.3.3.9 and master? (#27146)
[I've tried to opine on these tickets. -nm]
== Updates ==
Nick:
Last week:
- NSS TLS stuff. Got X509 working (?). Worked on TLS initialization.
- Worked on roadmap revision
- Met about congestion control alternatives
- Review & merge a bunch of patches
- Initial (messed up) bisecting on #27080
This week:
- Draft a whitepaper about datagram-related attacks
- NSS TLS: maybe finish the implementation?
- Help work on 034 blocker tickets.
teor (offline):
last week:
- PrivCount in Tor: blinding and encryption (#24629, #26972)
- bwauth mentoring (mainly
https://github.com/pastly/simple-bw-scanner/issues/182 and #27135)
- Reviewed the large vanguards patch (#25573), and other code
reviews (#23588, #15188, #22747, #27190 #27191)
- Worked on bridges are broken in 0.3.4 and master (#27080)
- our macOS time API seems to return weird results (#26987, #27139)
- did we break the consensus between 0.3.3.9 and master? (#27146)
- I was on leave for a local holiday on Wednesday
this week:
- Keep on trying to fix bridges are broken in 0.3.4 and master (#27080)
- PrivCount in Tor: blinding and encryption
- reviews, fixes, design meeting
- other reviews and revisions
rest of 0.3.5:
- work out the earliest rust version tor supports, and add CI for it
- Implement PrivCount in Tor noise generation (#26637, maybe #26398)
- Merge PrivCount in Tor
komlo (offline):
- Last week:
- Gave a talk about Rust, had a lot of conversations about how
to move forward with some existing Rust issues. Will be sending
updates/syncs this week
- This week:
- Finish writing a draft for a peer review checklist, will
work with Mike on adding his input/finalizing this
- Look over recently-opened Rust tickets (thank you to the
people opening these and adding improvements!)
haxxpop:
- Last week:
- The client auth code is ready for review and test. Even
thought the test still fails on Windows but I think we can review and
test the code while
I fix this issue. The code is in
https://github.com/torproject/tor/pull/36
- This week:
- One thing that we haven't discussed about yet is how clients
generate their keypairs (how the command will look like). After
discussing about this,
I think I will implement it.
catalyst:
- last week (2018-W33):
- CI/Coverity rotation
- reviewed some more of teor's CI changes
- PM candidate interviews
- more digging in bootstrap related code for #25502, #22266
- this week (2018-W34):
- design meeting organizer rotation
- #25502, #22266 (bootstrap progress reporting improvements)
Mike:
Last week:
- Continue discussions about congestion control
- Make sure Sponsor2 report is good for submission
- Chat with Tobias Pulls about adaptive padding implementation variants
- Code reviews
This week:
- Help with anti-censorship hiring process
- Update #25573
- Keep digging into #27066
- WTF-PAD proposal update
- Research website update
- Vanguards/onion service security blog post with asn?
More information about the tor-project
mailing list