May 2019 - tor-project - lists.torproject.org

Are there countries where using Tor is illegal?
by Cristian Consonni 11 May '25

11 May '25

Hi, (Sorry if this question has already been asked in the past, feel free to point me to the relevant resources.) I know that the legal FAQs by the EFF state that: «we believe that running a Tor relay — including an exit relay that allows people to anonymously send and receive traffic — is legal under U.S. law.»[1] I also know there is a list of countries for which there is legislation that exclude communication service providers from liability. They are indicated in the Legal of the Tor Exit Guidelines page[2], they are USA, Germany, Netherlands, Austria, France, and Sweden. >From some articles in the press[3a][3b] it may be illegal - depending on how you interpret the wording[*] - to use Tor (and other technologies such as VPNs or proxies) in the UAE, with fines ranging in the millions of dirhams (hundreds of thousand of dollars). A couple of weeks ago it was discussed - on this list as well - that a law was introduced to the state parliament to ban Tor[4a][4b]. This follows a case of some months ago of a Russian Tor exit node operator being arrested for inciting mass riots and terrorism[4c][4d]. The idea of blocking VPNs or Tor seems to have already been considered in the past[4e]. This infographic about pluggable transports[5] suggests access to the Tor network is censored or limited in China, Uzbekistan, Iran, and Kazakhstan. Tor being censored orblocked may be different from it being illegal. What about other countries? Is there a place where I can find more about this topic? Cristian [1]: https://www.torproject.org/eff/tor-legal-faq.html.en [2]: https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines [3a]: http://www.emirates247.com/news/emirates/dh500-000-fine-if-you-use-fraud-ip… [3b]: http://news.softpedia.com/news/people-caught-using-vpns-tor-or-proxies-in-t… [*]: «Whoever uses a fraudulent computer network protocol address (IP address) by using a false address or a third-party address by any other means for the purpose of committing a crime or preventing its discovery» [4a]: https://lists.torproject.org/pipermail/tor-talk/2017-June/043293.html [4b]: https://trac.torproject.org/projects/tor/ticket/22055 [4c]: https://lists.torproject.org/pipermail/tor-talk/2017-April/043109.html [4d]: https://techcrunch.com/2017/04/24/dmitry-bogatov-tor-russia/ [4e]; https://torrentfreak.com/vpn-and-tor-ban-looming-on-the-horizon-for-russia-… [5]: https://www.torproject.org/images/PT/2016-07-how-to-use-PT.png

4 3

Roadmap for hypothetical network health team
by Roger Dingledine 29 Aug '19

29 Aug '19

Here is an area list for a hypothetical future "network health" team. I say hypothetical because we have no near-term plans to form such a team -- but imo the task areas make sense together. Some of them are being handled by other teams right now, but some of them aren't getting as much attention as they need. (1) track community standards about what makes a good relay - publish up-to-date expectations for relay operators - set best practices for how to set relay families - detect and resolve bad relays - exitmap, sybil detection, hsdir traps (2) anomaly analysis / network health engineer [with network team] - establish baselines of expected network behavior - look for and resolve denial of service issues - track connectivity issues between relays - look for relays hitting resource limits (3) make sure usage/growth stats are collected and accurate - track network performance, relay diversity by various metrics - count users [with network team and metrics team] - monitor bridge growth and usage [with censorship team] (4) relay advocacy [with community team] - maintain docs for setting up and running relays and bridges - grow a cohesive community of relay operators so they have peers - keep relays on the right tor versions - relaunch a gamification / badge system for lauding good relay progress - strengthen relationships with non-profit orgs that run relays - help companies that want to offset their tor network load (5) maintain the components of the network - maintain directory authority relationships - keep bandwidth authorities working (including setting the right balance between speed and location diversity) - have enough tor browser default bridges, and keep them running smoothly [with censorship team] - update the fallbackdirs list

3 2

April Fundraising Report
by Sarah Stevenson 17 Jul '19

17 Jul '19

Hello - below is the Fundraising team’s April update. Let us know if you have any questions! ## Grants The biggest news in the world of grants is that our proposal to DRL for anti-censorship work was approved. Al also submitted a proposal to CS Fund/Warsh Mott Legacy, Rights, and Governance that was declined and a proposal to Wallace Global on which we are still awaiting a response. We are also waiting to hear a response back from the DIAL Open Source Center about funding for the ESR migration. In these monthly updates we will begin informing you about proposals we intend to submit in the next month in case anyone might have comments or concerns about the funders, or connections that might help our chances. As a reminder, our grant work flow can be found on the Fundraising Team Wiki[1]. We plan to submit proposals to Media Democracy Fund, who have been funding us for several years now, the Reva and David Logan Foundation, NLnet, and The Charles Léopold Mayer Foundation for the Progress of Humankind. We welcome any and all feedback sent to grants(a)torproject.org <mailto:grants@torproject.org>. We have been working to better communicate with our grant program officers and, to that end, we sent our first Sponsors Newsletter[2]. The intent is to demonstrate the full impact of our work to funders who may only be familiar with specific projects. We plan to send the next newsletter after the meeting in Stockholm. Additionally, Isa and Sarah met with Michael Brennan from the Ford Foundation and are planning a follow-up meeting in June with others from Ford. ## Small Foundations / Major Donors In an effort to get lapsed major donors and small foundations to donate again, we sent a solicitation letter via postal mail. We included a nice insert, created by Steph, featuring Tor stories that we plan to use for acknowledgements that need to be sent in the mail. We’ve seen a small response. We sent a version of the Sponsors Newsletter to current major donors to let them know how impactful their giving has been. ## Monthly Giving / Defenders of Privacy We launched a donation page dedicated to monthly giving[3]. This will allow us to promote the Defenders of Privacy program and try to convert one-time givers into monthly givers. We currently have 334 people in the group who generated $3,438 in income in April. We will send a three-part series of emails to one-time givers beginning in May and will offer a new sticker or patch (yet to be determined) in the second invite. I will keep you updated on the growth of this program. ## Website Since the new website was launched at the end of March, we have been tracking the number of unsolicited donations from the website. That number decreased about 30% with the new site design. Our theory was that the Donate button was less noticeable, so at the end of April, Antonela changed the design and added a yellow Donate button in the header and footer. Since that change was made, donations are now almost double what they were per day before the website redesign. ## Administrative We have been working with a company called Labyrinth on making sure we are registered to fundraise in each of the 50 US states. This is a requirement that can result in fines if you are not properly registered. The process is a bit arduous since each of the states has different requirements. Thankfully, the process is almost complete for this year. ~ Fundraising Team [1] https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view <https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view> [2] https://crm.torproject.org/civicrm/mailing/view?id=158 <https://crm.torproject.org/civicrm/mailing/view?id=158>[3] https://donate.torproject.org/monthly-giving <https://donate.torproject.org/monthly-giving>

1 2

S27: Onion Services project - Next meeting Tuesday 21st May @ 1500UTC
by Pili Guerra 04 Jun '19

04 Jun '19

Hi everyone, Just a reminder that we’ll be meeting this week to discuss progress on the Onion Services project. Please join us this Tuesday 21st May @ 1500UTC on #tor-meeting if you’d like to participate. 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 1

Anti-censorship meeting notes, 30 May 2019
by Philipp Winter 30 May '19

30 May '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-05-30-16.59.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday May 30th 17:00 UTC Weekly meetings every Thursday 17:00 UTC on #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 == THE Anti-censorship Roadmap (kanban board): https://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… <-- a subset of tasks from trac that the team is working on. (There is a bug in wekan, what we use for the board, that make it hard to load. You have to click in 'all boards' and then in the board to get it to load) Roadmap by topic: https://storm.torproject.org/shared/KXkqlNP8ouNks_ey5khZKUSbNj9ZoidXmEp80OD… Gettor Roadmap: https://dip.torproject.org/anti-censorship/gettor/boards <-- We are experimenting with gitlab for gettor and hiro is working on the board there. Each ticket is linked back to trac for now to keep historical context --> Roger's thoughts on anti-censorship's priorities: https://storm.torproject.org/shared/kU83M2pQehsnQZPzR_mwmYslAijqKgYNOEak57T… Komlo's thoughts on anti-censorship's plan: https://pad.riseup.net/p/CensorshipTeam-Planning-keep PTO Calendar: Ask gaba for the link and keep it up to date with when you are not going to be around. --------------------------- ---- 30th May 2019 ---- --------------------------- == Announcements == * As part of Sponsor 28 work, we will improve our PT spec * GetTor (hiro & gaba) are experimenting with boards in the Tor gitlab to manage it. == Discussion == * Discuss tickets that the anti-censorship team would like the network team to do (ahf) * How are we going to handle snowflake changes that require upgrades for clients/proxies that are not backwards-compatable? (cohosh) * Should we keep doing the obfs4 probe tests (it's been 2 months now) * Is the roadmap up to date with what you are working on? https://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… < == Actions == * Please add your highlights of May to our monthly report pad: https://pad.riseup.net/p/P7hQ98M9fI0ck2SwKJYd * It should give the community an idea of the important things we did, and insights we gained on the way == Updates == FORMAT! Name: Last week: - What you worked on last 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: This week (2019-05-16): - Revised gettor code with phw - Merge new code - Deploy gettor - See who has access to gettor repository in torgit - Sync torgit repository with dip - Port tickets from roadmap to dip Next week: - Add more tests to gettor - Work on twitter distribution channel Past week: - Rebase gettor PR with phw - Started testing framework phw: This week (2019-05-30): - Assessed httpsproxy (<https://bugs.torproject.org/29278#comment:6>) - Attended Sponsor 28 kickoff meeting with Roger and Cecylia - Added list of criteria we have for default bridges: - https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/DefaultBridges… - Wrote a patch for https://bugs.torproject.org/30512 with David's help - Reviewed https://bugs.torproject.org/5304 - Incorporated Matt's comments in my patch for https://bugs.torproject.org/28655 - General BridgeDB refactoring - Added missing changelog entries - Updated translations https://bugs.torproject.org/30157 - Some coordination with Kat regarding the Sponsor 19 report - Incorporated Cecylia's comments in my work for https://bugs.torproject.org/30472 - Started working on a docker image for obfs4 - Started working on a Stem script to test the TCP reachability of BridgeDB's obfs4 bridges - Discussing our roadmap with Gaba and Cecylia Next week: - As part of our Sponsor 28 work, we will revise our PT spec - Accumulate resources and figure our issues with the current spec - Then, think about fixing these issues - Wrap up https://bugs.torproject.org/30472 - Wrap up https://bugs.torproject.org/30512 Help with: - Check if default bridge criteria make sense to you: https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/DefaultBridges… Gaba: Last week: * talked with phw,cohosh and kat5 about roadmap This week (05/30): * look at s19 and what is that we are completing in May ahf (will be AFK due to Ascension Day here in DK) Last week: - Uploaded rebased patches for #29736, #29207, and #29260 at https://github.com/ahf/snowflake/tree/features/websocket_r5 - Been playing around with a method that I think will allow us to load shared libraries of PT's for Tor (on Linux only for now). - Hacking on #28930 - Got OK from dcf on #28849! Thanks! Next step is to talk to the PT adapter person. This week: - Hacking on #28930 - Prepare presentation for some conference next week in Switzerland. - Away Thursday/Friday for "Ascension Day". kat5: Last week (May 20): - Added more content from tickets - Added Tails content This week (May 27): - Marked finished sections complete - Final edits - Hand off for submission to DARPA - NEEDS HELP: - Sign-off from phw dcf: 2019-05-30 Last week: - reviewed go 1.12.5 upgrade (#30536) - reviewed Snowflake broker certificate cache (#30512) - reviewed removal of OnIceComplete (#30511) - responded to report of metrics anomaly in Iran (#30636) - AMP cache performance measurement Next week: - make graphs using the old unsanitized broker logs before the June 1 deletion deadline (#30693) - look at WebExtension changes in https://bugs.torproject.org/23888#comment:24 Help with: - #30513 would be nice (default Cc for Circumvention/Snowflake tickets) cecylia (cohosh): last updated 2019-05-30 Last (2) weeks: - snowflake - attended sponsor kickoff meeting - started implementing a (simple) sequencing/reliability layer for snowflake client traffic (#25429, #29206) - reviewed obfs4PortScan - reviewed #30511 - updated obfs4 probe test results (#29279) - updated snowflake probe test results (#30368) - merged guard against large reads (#26348) - read over s19 report Next week: - continue reliability layer for snowflake (#25429, #29206) - clean up and increase test coverage for snowflake (#29259) - continue hacking on windows build (#25483) - update default STUN configuration (#26348) - make necessary changes for broker stats (#21315) Help with: - feedback on #21315 (broker stats) - review of obfs4 results (#29279) catalyst: week of 5/16 (planned): - get #29976 ready for review - peer and team leader feedback - help ahf more with bootstrap stuff as needed weeks of 05/16 and 05/23 (actual): - peer and team leader feedback done - #29976 merge_ready week of 05/30 (planned): - open new tickets for improving bootstrap reporting - #30639 looks like it might be good to work on next? (raises some questions about how we tell Tor Launcher that bootstrapping has failed) arlolra: 2019-05-30 Last week: - snowflake webextension This week: - more snowflake webextension Help with: - take a peak at the popup in https://trac.torproject.org/projects/tor/ticket/23888#comment:24

1 0

Tor Browser team meeting notes 28 May 2019
by Georg Koppen 29 May '19

29 May '19

Hi everyone! Here come the meeting notes from our weekly Tor Browser meeting yesterday (this time held on a Tuesday due to Memorial Day in the U.S. on Monday). The IRC log can be found at: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-05-28-17.30.l… and the contents of our pad are: Discussion: - Tor Browser 8.5 fallout (GeKo: we track 8.5 bugs with the tbb-8.5-issues keyword in Trac; we got some bugs and nice discussions about our security settings redesign; we plan to address the most pressing issues in upcoming 8.5.1 and 9.0a2 releases) mcs and brade: Last week: - Worked on #30000 (Integrating client-side authorization to onion services v3). - Reviewed and commented on SOCKS5 error code Tor proposal (#30382). - Started to implement support for new SOCKS5 error codes in the browser. - Implemented a prototype of the client auth prompt (#30237). - Helped with bug triage, e.g., #30565 (Linux update problem). This week: - #30565 (Linux update problem). - #30000 (Integrating client-side authorization to onion services v3). - Continue design discussions and make more progress on the client auth prompt implementation (#30237). - Continue to give feedback on SOCK5 error code proposal (#30382). - Maybe: #29197 (remove use of overlays from Tor Launcher) - Maybe: #30429 (ESR 68 Rebase — updater patches). GeKo: Last week: -worked on patches for - bug 30469 (ro bundles; about to post my patches) - bug 30541 (WebGL privacy (mcs/brade: could you have a look at that one as well) (reply from mcs: yes)) - bug 29969 (bumping NoScript version) - bug 30492 (switching to OpenSSL 1.1.x) - bug 28119 (arm64 builds for Android (sysrqb: could you test the posted .apk?)) - bug 30585 (clang 8 for ESR 68) - bug 30490 (cbindgen for ESR 68) -reviews: #30549, #30635, #30480, #30451, #30565, #26844 -helped with releases and release fallout triaging -hackerone fun -feedback for s27 work: #30237, #30024 -finished first pass on acat's proposal (for #10760) -filed #30639 (IPv6 issues on IPv4 network); mcs/brade: could you comment on that ticket? reply from mcs: yes -started to look into GPOs interfering with Tor Browser proxy settings on Windows (#30575) This week: -more hackerone fun -hopefully finish #30490 -release prep for point releases and start building them (probably Thursday/Friday) -patch for mingw-w64/clang toolchain (#28716) -first round of review of acat's rebase efforts (#30429) -reply to acat's #10760 prop mail -afk on Thursday pospeselr: Last week: Current status of #27503: COM Proxy dll (the point of entry screen-readers use to talk ia2 to Firefox) is working except for certain classes of functions (types that take T**) So the remaining issue is in the 'TypeFormatString' (a binary blob which defines parameter marshaling behavior) generated by widl Good news: correct strings are generated when using a separate set of compiler flags (but the surrounding code won't work for us as it depends on SEH which mingw doesn't support) This week: Memorial-Day Monday Fix the final(?) widl issue affecting us Traveling to the wilderness (Kansas :p) Thursday through next Monday, back online next Tuesday (June 4) Will try and get these widl patches broken apart in a way that the wine devs will accept on Saturday acat: Last week: - Rebasing patches (#30429). - Investigated 30565 - saved logins and tabs lost after tor browser bundle upgrade (8.5) This week: - Review #30541. - Get tbb-tests to run and pass. - Port onboarding for ESR68? (28822) - A bit of backlog (e.g. finish 30304 - Browser locale can be obtained via DTD strings) pili: Last week: - S27 and Tor Browser Release meetings - Responding to Season of Docs inquiries - Spoke with OKThanks and Nathan from Guardian Project regarding branding of applications in the Tor ecosystem - Helped a Master's degree student with questions about Tor Browser future This week: - S27 monthly report - Responding to Season of Docs inquiries - Speaking with HTTPS Everywhere people about joint project sisbell: Last week: - #30607: Investigation in Tor not working on Android Q Beta. Works on x86 emulator. Investigated Embedded API (simple wrapper around command line). I’ll have device update to do testing in June. - #Worked on android-toolchain. Fixes around gradle starting. License fix for Android build tools. This Week: - # 30665 Firefox working with 68 ESR - try to get working in offline mode with android-toolchain, updated Rust 1.34.1 sysrqb: Last week: Opened some post-release bug Made more progress on fastlane setup (#26844) Began investigating reported bug where Tor Browser is sent a URL from another app (#30573) Read blog comments Opened ticket about leaking locale in HTTP header (#30607) Made more progress on F-Droid build This week: Continued investigation and worked on patch for #30573 Created patch for bridges on Android Work on F-Droid build Work on fastlane repo 68esr rebase boklm: Last week: - helped publish new releases - reviewed #25930 (Update gcc to 8.X) and #30491 (Move our macOS builds to Debian Stretch) - worked on #28672 (Android reproducible build of Snowflake): now able to build webrtc using our toolchain, but still using the clang bundled with webrtc - made patch for #30549 (Add script to remove expired sub-keys from a keyring file) to make it easier to do #30548 (Clean up keyring files) - updated patch for #30480 (Check that a signed tag object contains the expected tag name) This week: - try to finish #28672 (Android reproducible build of Snowflake) - some reviews (#30492 #28119) - look at remaining failing testsuite tests - out of office on Thursday and Friday (but should be able to get some internet to start a build in the morning) Georg

1 0

Network team meeting notes, 28 May 2019
by Nick Mathewson 29 May '19

29 May '19

Hi! You can find our meeting logs at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-05-28-23.00.html Below are the contents of our meeting pad: = Network team meeting pad! = This week's team meeting is at Tuesday 28 May at 2300 UTC (Monday is a US public holiday) on #tor-meeting on OFTC. May schedule: * Tuesday 28 May at 2300 UTC (Monday is a US public holiday) June schedule: * Monday 3 June at 1700 UTC (The 28 May meeting was at the patch party time) * Monday 10 June at 1700 UTC * Monday 17 June at 1700 UTC * Monday 24 June at 1700 UTC Welcome to our meeting! First meeting each month: Tuesday 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.) 29 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002310.html 6 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002316.html 13 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002325.html 20 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002335.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… * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… . * See discussion notes below. 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. ------------------------------- ---- 28 May 2019 ------------------------------- == Announcements == == Discussion == Rotation updates: (CI/coverity mikeperry->nickm; bug triage catalyst->dgoulet) No new coverity issues Stale jenkins freebsd issue tagged and put on CI page (whose link is at the top of this pad) Bug triage queries are clean (or were earlier today) Should Tor controllers be able to change DisableAllSwap at runtime? Tor hangs a lot when stem sets "DisableAllSwap 1" on Travis (#30235) If it should work, we need to fix DisableAllSwap. (I think this is moot; I talked with teor about it around 48 hours ago? -nickm) ahf (27/05): arma wonders if we already run valgrind as part of our release checklist? if no, should it be added somehow? see #30629 IMO we should do this in CI if it's really necessary. But we should also figure out why our existing sanitizers didn't notice 30629. -nm Our control refactor caused at least two regressions: #30580 #30646. How can we make sure there aren't any others? == Recommended links == On allyship in newsrooms but also in workplaces: https://source.opennews.org/articles/how-be-ally-newsroom/ On roles in tech teams https://www.youtube.com/watch?v=KClAPipnKqw On feedback and how to do it well (focused on art school, but it also works for code): https://captainawkwarddotcom.files.wordpress.com/2017/05/peepasgotomay1.pdf == 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): . retrospective . meeting with briar on funding for dormant mode . reading documents for new sponsor (28) This week (planned): . check sponsor V work until now . monthly report for sponsor 27 (onion services) Help with: teor: (online for 28 May, offline at the usual meeting time) Week of 21 May (planned): - Something fun, interesting, and engaging - Catch up on backlog - Sponsor 19 - 041-must - Fallback directory mirror list rebuild Week of 21 May (actual): - Urgent: - Started fallback directory mirror list rebuild process with Gus (#28793) - Worked on more travis stem timeout issues (#29437) - It looks like stem hangs on its own CI, not just Tor's CI - We should have a controller trace soon, to help us find out which side is hanging - Important: - Catch up on backlog - Retrospective and other meetings - HR stuff x3 - Other: - Moderation on tor-relays - Answer easy questions and do quick tickets - Started on #16564 (reject bridge descriptors on non-bridge authorities) - Rewrote the CI for stem, found some bugs (#28170) Nick: Week of 20 May (planned): - Review and merge as top priority - S19 work as second priority. - 041 work as needed - try to triage and assign 041 tasks - try to release 0.4.1.1-alpha - Work on privcount integration, time permitting Week of 20 May (actual): - Review and merge, lots of it - Lots of meetings - Released 0.4.1.1-alpha - Tried to figure out some older bugs - 041-must and 041-should issues - 26848 (make sure sendme cells reflect some random data) - Started investigating PT transition bugs (29875, 24367), not much progress Week of 28 May (planned): - More for on PT transition bugs (29875, 24367). Fix? - More for on 041-must/should items - Chutney CI work with teor, tbd - Try to figure out stem CI issue with teor, tbd - Followup on issues from retrospective dgoulet: (will be afk for meeting) Week of 05/20 (actual): - Reviews and merges (See timeline). - Finalized all #26288 children meaning finalizing #30428 madness and #30365 to integrate authenticated SENDMEs in tor-spec.txt. Review on #26846 done by nickm. - Worked on s27 #30382 and wrote proposal 304 for it. Week of 05/28 (planned): - Sponsor 27 tickets. #30382, #15516 if I can get to it (DoS related). - Posted on tor-dev@ prop304. Code is done as well, need review from asn to continue further. - s27 related is #29034 that I finally got time to do. It is in needs_review and it should allow us to close 3 tickets in the pipe. [what is the situation with #29607? --gaba] Mike: Week of 5/20 (planned): - Bugfixing - Peer feedback, doh! - Spend time getting back up to speed on CI/Coverity - Work on circpad documentation; start mailing researchers Week of 5/20 (actual): - Laptop issues - Mailed researchers re circpad Week of 5/28 (planned): - Laptop issues - Scalability meeting - Peer feedback - Register for PETS - Circpad relay-side warn log bug (https://trac.torproject.org/projects/tor/ticket/30649) - Maybe circpad documentation? catalyst: week of 05/20 (2019-W21) (planned): - reviews - bug triage rotation - #29976 week of 05/20 (2019-W21) (actual): - reviews - bug triage - #29976 pull request week of 05/27 (2019-W22) (planned): - reviews - revise #29976 - other bootstrap work? asn: Week of 05/13 (planned): - Continue coding #30381 so that we unblock the TB team. - Keep on working on the DoS stuff by the side. - Got lots of reviews for this week. Got a few more last midweek, so I got stuff to do here. Week of 05/13 (actual): - Pretty big delta from the "planned" week since we got overflowed by WTF-PAD tasks last week given the 041 freeze. Spent most of the week testing, revising and rebasing #28634, #28780 and #29085. Everything is merged now, so hooray us! - Finished all peer feedback. - Did a meeting with hackerone and paid out a bug hunter for old bugs. - Bug triage duty: The bug triage queries are empty again. - Was sick on Friday. Week of 05/20 (actual): - Will be medically away for most of the week. Will try to be back on Friday but still unclear. Will also try to attend the retrospective. ahf (offline maybe? or in the sofa at very least 8) Week of 20/5 (planned): Network team: - Follow up on revision requests of #5304 and #28930 - Finish #28930 - Finish my last bits on some Snowflake patches that I have kept postponing (will probably spend all of Thursday or Friday on that). Week of 20/5 (actually): Network team: - Progress on #28930. - #5304 and #28849 is still pending review, but no changes last week. - Got most of my #29736 patches cleaned up and uploaded to GH. - Messed around with a way of loading .so compiled PT's into Tor. Hope to have a prototype ready before next week. Misc: - Tried to write a bot using the Trac XML-RPC API with the help from Hiro, but we haven't managed to make it work yet. Week of 29/5 (planned): Network team: - Continue with S19 tasks. - Begin review process of #29736 patches with cohosh while I finish the last bits. Misc: - Need to prepare a presentation for an event in Switzerland next week that Steph asked if I was up for. Going to be away some of the 5th of June while traveling for this event and the presentation is the 6th. - End of month tasks. - Away on Friday due to the "Ascension Day" (all the Danish holidays will be over soon!). juga(offline): Week of 05/13 (planned) - Continue with #30311, #30406, #30373 as needed Week of 05/13 (actual) - Continued with #30406: Refactor header constants in sbws to use Stem's one Week of 05/20 (plan) - Add Tor version to the bandwidth file (#30196)

1 0

Notes from May 23 2019 Vegas team meeting
by Karsten Loesing 24 May '19

24 May '19

Notes for May 23 2019 meeting: Roger: 0) I'm offline this meeting (today/tomorrow), at the Race kickoff mtg with Philipp and Cecylia. 1) What is the state of frontdesk@rt? Is it getting answered? If it isn't, should we set up an autoresponder so people know not to rely on it? And is it still linked from anywhere? [I have access and respond to donation-related questions. We get several Helpdesk type questions there per day and some questions about bridges. It is unclear to me whether anyone is answering them. I thought wayward was at some point, but may not be anymore. - Sarah] 2) It would be keen to add trac keywords to the "frequently encountered tickets" on Wayward's tor-project lists. Can somebody grab this idea? [I have it in my todo list of things to look at but happy to leave it to somebody else or collaborate on it - gaba][I can take this on - pili] 3) Julius suggested that we should have a Tor talk (or more than one) at CCCamp, and that we should get Isabela there to do a "this is the future vision of Tor, also donations would be nice" pitch at the end of the talk. When is the submission deadline? What are our most promising talk proposals? Tor Browser and OONI maybe? Tickets opened yesterday, so now is the time to build this plan. Gaba: 1) Two team retrospectives the same day (network and metrics). Bravo! 2) Gettor (new code is deployed by hiro!) 3) Giving some help around google season of docs distribution (connected with writethedocs crowd) 4) Still moderating comments on moz research blogpost 5) Sessions for meeting in Stockholm. Are we going to have any talk on priorities? It would be good to have a place for ideas coming up from different teams where we can coordinate what finally go into 3 days schedule. 6) Followed up on tech reports published for metrics team contract with OTF. Bekeela to send last mail with social network engagement and download numbers. 7) Trying to get the best of the Trac data to follow projects. 8) Other small issues. Georg: 1) Tor Browser 8.5 went out. So far it looks not that bad. We plan to start building a bugfix release by end of next week addressing the most pressing issues 2) Nick: There are a bunch of non-moderated blog comments for older Tor releases on the blog. Could you or anyone of your team address that (not sure how the network-team process works) 3) Erin: Not everyone on my team got three peer feedbacks yet. Am I supposed to follow up on that and if so, how? (Do you mean they asked for feedback and didn't receive it, or they didn't ask three people? -ewyatt I only know I got one review for one of my folks yet, out of what supposed to be three GeKo) Hmm. Maybe I'll send a reminder email to everyone asking them to confirm with their reviewers that the feedback is done. That seems the easiest way to distribute the work of figuring out who still needs to write/receive. Sound ok? -ewyatt Works for me. GeKo Sarah: 1) We were granted $25,000 from DIAL Open Source Center for ESR migration. 2) Various efforts like the more prominent donate button on tpo.org, discount swag sales on social media, and discount sticker pack for first-time donors have increased individual gifts made through the website almost 40% over this time period last year. There has also been an additional uptick in donations since yesterday's release which included a donate link on about:tor page. 3) Have an interview tomorrow with a journalist from the Daily Dot who is working on a story about cryptocurrencies and philanthropy. 4) Planning for major donor (Champions of Privacy) page. 5) Beginning to plan YE campaign. Mike: 1) Mailed researchers re Mozilla RFP as well as Tor circuit padding implementation 2) Am behind on reviews; doing them this week Antonela: 1) TB85 release, made graphics, pushed for having the manual updated, reviewed es localization 2) working in OTF 02A3, O2A1 3) working in OONI explorer stable release 4) coordinating user research with nah and gus for africa's trip 5) closed Q1 reporting with caroline 6) met SimplySecure about how we can collaborate 7) trying to unify media.tpo and https://github.com/TheTorProject/tor-media. Any advice? [Maybe it's good to consolidate everything that is smaller than 10MB into the git repo, ex exclude the video and misc directories. ~ Arturo] Erin: 1) new OONI dev starting next week; bio/announcement soon 2) general HR stuff Sue: 1) met with OONI team regarding budget to actual numbers 2) general Accounting stuff isabela: 1) went to SIF last week and met w/ Sida (one of our contract meetings) 2) Getting phase 3 Sida plan finalized to be submitted by mid next week 3) working on different fundraising efforts that we are rolling out 4) syncing tomorrow (friday) w/ panos on dev meeting logistics - and then w/ jon on all things meeting related. Arturo: 1) Onboarding Federico who is a new OONI dev! 2) Documented an incident of internet censorship in Indonesia and found how to circumvent the block with stock Android: https://twitter.com/OpenObservatory/status/1131207330366992384 3) Working on OONI Probe mobile 2.1 release 4) Working on OONI Explorer stable release 5) Responded to many media inquiries following the wikipedia Chinese blocking post: https://ooni.torproject.org/post/2019-china-wikipedia-blocking/ 6) Moving forward with the plan of having the OONI Probe engine in golang: https://github.com/ooni/probe-engine & https://github.com/ooni/probe-cli/pull/42 Nick: 1) 0.4.1.1-alpha is out, 0.4.0.5 is stable. 2) Working to stabilize 0.4.1.x; will open 042 window early if that works out 3) Encouraging team to focus on 0.4.1.x and Sponsor 19 4) Is there anybody to whom I can pass on the responsibility of being execdir@torproject when it comes to Apple? They want me to use 2-factor authentication and mostly I don't want to mess with their site. 5) Network team retrospective happening later today 6) Have received nearly all feedback. 7) I'm working on a paper about Walking Onions with Chelsea and Ian Goldberg. Pili: 1) Moving community portal forward 2) S27 - held bi-weekly meeting - Synced with Paul Syverson on their work in this area 3) Spoke with OKThanks and Guardian Project about Tor Branding and Tor applications ecosystem 4) Started working on S9 logical results framework 5) Tor Browser release meeting this week 6) GSoD promotion Karsten: 1) Operational issue notifications work moving forward. 2) OnionPerf improvements and new graphs moving forward. Anarcat: 1) figuring out the team lead work 2) continued working on refactoring Puppet manifests for standardization and collaboration 3) established an inventory of hardware, expenses and upcoming depreciation costs 4) tried to steer team demands towards funding requests because we're running out of capacity 5) will coordinate with the team to organize a planning meeting in Stockholm

1 0

Tor Browser team meeting notes 20 May 2019
by Georg Koppen 21 May '19

21 May '19

Hi! We had our weekly Tor Browser team meeting yesterday. As usual our IRC log can be found on meetbot.debian.net: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-05-20-17.30.l… The meeting notes are pasted below: Discussion: - Meeting next week? (on next Monday is public holiday in the US) - Same time (17:30UTC) on Tuesday 28th May GeKo: Last week: - reviews (#29982, #30489, #30162, #30166, #30518, #30404, #30284) - release prep - feedback mails - work on toolchain update for esr68 (Go update (#30536), macOS building on Stretch (#30491), Windows toolchain update for Firefox (#28238)) - work on getting ro and mk bundles in alpha series (#30468, #30469) - work on adding donation link to about:tor page (#30497) - work on testing IPv6 support on alpha (#29641) - work on getting letterboxing support into alpha (#30372) - Stockholm Internet Forum - HackerOne admin work - looked into WebGL-related bug reports (#30531, #30537) This week: - help with the release (sysrqb: the 8.5 bundles are signed in my build dir; I'd need *.apks signed with the shiny new key for the website to GPG sign them) - Windows toolchain update (#28238) - monitor potential 8.5 issues - look over acat's proposal for #10760 - work on ro and mk bundles in alpha series (#30468, #30469) - reviews sysrqb: Last week: Discussed a little the Final Orfox update with n8fr8 (#29955) Debugged white screen Preference bug on older android versions (#29982) Patched TOPL with additional torrc options (#30518) Reviewed GeKo's patch for empty control file on Android 4.4 (#30284) Reviewed BridgeDB ticket Extended lifetime of Tor Browser stable apk signing certificate (#26536) Tested Tor Browser 8.5 stable Uplifted bugs 1480877 and 1478438 Created internal testing release for Tor Browser on Google Play This week Tor Browser 8.5 release Followup on bmo bugs F-Droid deployment (#27539) Fastlane deployment (#26844) Maybe begin creating final Orfox update (#29955) Add a link for the new stable version (#30540) sisbell: Last week: - #30284: Tor startup was broken on KitKat. Provided and tested fix - Reviewed last 6 months of Orbot commits. Only one affected tor-android-service and it was addressed by sysrqb in #30518 - missing command line options - Opened #30501 BridgesList is overload field (in tor-android-service) - Submitted PR for TOPL changes (Accepted on 14th) - Had laptop failure that required reinstall and backup - Submitted feedback This Week: - #30460, #30461 Use new Android Toolchain - Submit PR to TOPL with KitKat fix mcs and brade: Last week: - Worked on #30000 (Integrating client-side authorization to onion services v3). - Investigated adding new NS_ERROR codes for the SOCKS5 errors that tor will soon return (#14389). - Researched various ways of implementing the client auth prompt (#30237). - Reviewed and commented on the Torbutton integration proposal (#10760). - Code reviews. - Submitted peer and team lead feedback. - Took a couple of days off for family things. This week: - #30000 (Integrating client-side authorization to onion services v3). - Start to implement support for new SOCKS5 error codes in the browser. - Make more progress on the client auth prompt implementation. Please read and respond to https://trac.torproject.org/projects/tor/ticket/30237#comment:6 if you care about this kind of thing. - More thoroughly review the UX proposal in #30237. tjr - Have a patch for the letterboxing FindBar/DevTools, will land and request uplift to 68: https://bugzilla.mozilla.org/show_bug.cgi?id=1546832 - r+ on the binutils removal, will land and request uplift to 68: https://bugzilla.mozilla.org/show_bug.cgi?id=1471698 - Investigated RDD process failures in MinGW. Didn't get far. - I think I am going to disable the (stronger) security mitigations for MinGW, get the process working. - Then have bugs for investigating and fixing the mitigations - Read acat's proposal. No comments. acat: Last week: - Finished and sent draft proposal for Torbutton integration. - Some reviews. - Started rebasing patches for ESR68 (#30429). This week: - Keep rebasing patches (#30429). boklm: Last week: - made a patch for #30480 (rbm should check that a signed tag object contains the expected tag name) - helped with building new releases - worked on #28672 (Android reproducible build of Snowflake) - sent feedback emails This week: - help with publishing new releases - continue work on #28672 (Android reproducible build of Snowflake) - look at remaining failing testsuite tests - some reviews - look at #29697 (archive.tpo running out of space) pili: Last week: - not much Tor Browser related :) This week: - Talking with Okthanks about Tor brand usage for iOS apps - S27bi-weekly meeting antonela Last week: - #30024 - #30497 - `about:tor` Donate link This week: - waiting for review at #30237 - #30024 - first approach on suggesting Onions -> https://trac.torproject.org/projects/tor/ticket/30024#comment:4 - should review the UX impact on #28044 and #10760 - Tor Browser 8.5 stable: - make sure that https://tb-manual.torproject.org/ gets updated with security settings docs - provide gifs/images for the announcement pospeselr: Last week: finished (?) widl patches fixing the 5 bugs blocking valid tlb generation made a quick windows build, demonstrated ia2 interfaces are now being exposed cross process (so the tlb seem to be working) some of the interface methods are causing tabs to crash, NVDA causes tab to crash immediately on mouse-over - IA2 Table related methods for sure cause crash, but not sure why This week: figure out which methods are crashing and why - odds are this is an issue with some of widl's generated code - will do a quick comparison of the generated .h/.c files and see if anything obvious stands out - failing that, will create a test harness to walk the IA2 'DOM' to track down what specifically is triggering the crash Georg

1 0

Network team meeting notes, 20 May 2019
by Nick Mathewson 21 May '19

21 May '19

Hi! Yesterday's meeting logs are at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-05-20-17.00.html Here are the recent contents of our meeting pad: = Network team meeting pad! = This week's team meeting is at Monday 20 May at 1700 UTC on #tor-meeting on OFTC. May schedule: * Monday 20 May at 1700 UTC * Monday 27 May at 1700 UTC June schedule: * Tuesday 4 June at 2300 UTC * Monday 10 June at 1700 UTC Welcome to our meeting! First meeting each month: Tuesday 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.) 25 Mar: https://lists.torproject.org/pipermail/tor-project/2019-April/002280.html 2 Apr: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-02-23.00.html (we forgot to post the notes) 8 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002289.html 15 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002296.html 23 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002308.html 29 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002310.html 6 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002316.html 13 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002325.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… * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… . * See discussion notes below. 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. * First monthly Retrospective is on Thursday May 23rd, 20:00 UTC ------------------------------- ---- 20 May 2019 ------------------------------- == Announcements == - The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0. == Discussion == Rotation updates: For retrospective meeting on Thursday do people prefer (please vote with +1): 1. Mumble in riseup.net ? 2. Jitsi ? +1 +1 3. Something else (explain). How do we handle our freeze and freeze period? Nick has suggestions: Let's default to "if a feature isn't needs_review by Wednesday, it isn't going in", with sensible exceptions. If the initial review suggests that the branch is high-risk, we should maybe not merge it, depending on impact. Let's IMMEDIATELY look for MUST items in 041, and try to fix them. Nick will recreate Teor's "040-must" page for 041. We can open 042 early if people are all focusing on 041-must fixes. Please look for 041 problems to fix, or S19 things to do, instead of getting an early start on 042. By default we keep 042 closed for a month, but should look at it fresh each meeting. == Recommended links == "Select male faculty, they said, effectively ran the Institute and were showered with private donations, while women were forced to fire essential staff and were shut out from power." This article is an excellent analysis of the mechanics of power and discrimination: https://www.nytimes.com/2019/04/18/magazine/salk-institute-discrimination-s… On allyship in newsrooms but also in workplaces: https://source.opennews.org/articles/how-be-ally-newsroom/ In github but a bot for assigning reviews: https://github.com/lmarkus/ReviewBot == 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): . checked sponsor 2 work with mike . looked at sponsor 27 for the team . got a few queries that can show me the work from the last month once I upload data https://github.com/gabelula/trac-tor/blob/master/2019AprilCoreTor.ipynb (still I only get closed tickets in the last month and how many points all those tickets took but not necessarily all the work done last month) . sent a mail with retrospective date This week (planned): check sponsor V work until now Help with: teor: (online for 23 April, then on leave until 21 May) * AFK Nick: Week of 13 May (planned): - Reviews and merge as top priority - Work on 29024 [PT support in chutney] for obfs4 at least - Freeze 0.4.1.x - Start on (and finish?) an alpha release - Privcount, time permitting - More work on 30414, time permitting, if review happens Week of 13 May (actual): - lots of review and merge - 0.4.1.x freeze, except for items marked postfreeze-ok - chutney support for obfs4 done (29024) - WTF-Pad test determinism (28878) - More work on test determinism (30519) - Work on pending coverity issues in tests (30150) - started a changelog for 0.4.1.1-alpha - initial ticket triage for 0.4.1 - new release-status page for 0.4.1 Week of 20 May (planned): - Review and merge as top priority - S19 work as second priority. - 041 work as needed - try to triage and assign 041 tasks - try to release 0.4.1.1-alpha - Work on privcount integration, time permitting Help with: - Everyone, please look at the 041 status page ( https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… ) and see whether there is anything in the last secton (neither 041-must or 041-should) that you think should be 041-must or should. - Also, please check whether there is anything assigned for 041 to you that you cannot do in the next week or two. (We're aiming for a Stable in mid-August, which implies that a release-candidate in mid-July is necessary.) dgoulet: Week of 05/06 (actual): - Reviews and merges (See timeline). - Work on #26288 child tickets. - Resolve important issue found by armadev about prop289 code: #30428 - While working on the #15516 defenses, find out that #30440 is a big problem so we are falling back to a token bucket approach instead. - Found #30454 issue in the HS code and made a fix for it. - Opened #30466 which is related to #30440. - Did worked hard on implementing a unit test for #26288 but ultimately couldn't achieve it with our current code setup :S. Week of 05/13 (planned): - Rush anything needed for the freeze. In particular, some child tickets in #26288. - Work on the #15516 Plan B which is token bucket rate limit design. - Make progress in #30382 which changed to using SOCKS error. - REMINDER: Will be offline on Thu and Fri. Mike: Week of 5/13 (planned): - Get child tickets of https://trac.torproject.org/projects/tor/ticket/28634 merged Week of 5/13 (actual): - Got https://trac.torproject.org/projects/tor/ticket/28634 and children merged, Week of 5/20 (planned): - Bugfixing - Peer feedback, doh! - Spend time getting back up to speed on CI/Coverity - Work on circpad documentation; start mailing researchers catalyst: week of 05/13 (2019-W20) (planned): - reviews - #29976 - peer feedback (2) and team leader feedback week of 05/13 (2019-W20) (actual): - reviews - peer feedback (2) and team leader feedback done week of 05/20 (2019-W21) (planned): - reviews - bug triage rotation - #29976 asn: Week of 05/13 (planned): - Continue coding #30381 so that we unblock the TB team. - Keep on working on the DoS stuff by the side. - Got lots of reviews for this week. Got a few more last midweek, so I got stuff to do here. Week of 05/13 (actual): - Pretty big delta from the "planned" week since we got overflowed by WTF-PAD tasks last week given the 041 freeze. Spent most of the week testing, revising and rebasing #28634, #28780 and #29085. Everything is merged now, so hooray us! - Finished all peer feedback. - Did a meeting with hackerone and paid out a bug hunter for old bugs. - Bug triage duty: The bug triage queries are empty again. - Was sick on Friday. Week of 05/20 (actual): - Will be medically away for most of the week. Will try to be back on Friday but still unclear. Will also try to attend the retrospective. ahf Week of 13/5 (planned): Network team: - Finish #28849 when we (PT community and us) agrees on spec changes. - Begin #28930 code. - Rebase #29736 code on top of master and see what is missing. Misc: - Submit peer review to people's respective team leaders. Week of 13/5 (actually): Network team: - Submitted patch for #5304 (OutboundBindAddress support in PT's) - Began working on #28930 (proxy/pt phase reordering) with some help from catalyst. - Wrote patches and revised spec changes for #28849 (dormant support in PT's) Misc: - Submitted peer review of everyone -- took longer than I had thought for the last parts (I hope!) - Spend Friday in the holiday house due to "Great Prayer Day" in DK. Week of 20/5 (planned): Network team: - Follow up on revision requests of #5304 and #28930 - Finish #28930 - Finish my last bits on some Snowflake patches that I have kept postponing (will probably spend all of Thursday or Friday on that). juga(offline): Week of 05/13 (planned) - Continue with #30311, #30406, #30373 as needed Week of 05/13 (actual) - Continued with #30406: Refactor header constants in sbws to use Stem's one Week of 05/20 (plan) - Add Tor version to the bandwidth file (#30196)

1 0