- tor-project - lists.torproject.org

October Fundraising Report
by sstevenson＠torproject.org 18 Dec '18

18 Dec '18

The fundraising team was very busy in October! We attended the Mexico meeting and wrote a blog <https://blog.torproject.org/reflections-tor-meeting-newbie>about my experience. Launched YE campaign - Strength in Numbers <https://blog.torproject.org/strength-numbers-double-your-donation-mozillas-…>. With Mozilla’s match, we’ve raised $100,000 so far! Thanks to Antonela and the Tor Browser team, especially Arthur and Georg, for creating and implementing the series of banners that are seen in Tor Browser. Thanks to Steph for pushing the campaign out on social media and in Tor News. We are excited to see a good amount of traffic to the donate page coming from Mastodon. Thanks to hiro and emmapeel for translating and implementing changes to the banner on torproject.org and donate.torproject.org. Thanks to Jon for being the swag guru. Thanks to Karsten and Iain for monitoring the metrics. Attended DRL Implementers’ Meeting in DC - learned about how some other organizations function and talked about how we can all collaborate. Connected with fundraisers at a lot of nonprofits to crowdsource information on accepting different types of cryptocurrency. Al has been writing. A lot. A proposal for our anti-censorship work will be submitted today. Many thanks to everyone who has worked on this. A proposal for code modularization is also about to be submitted. Next week, we’ll send out a letter to family foundations. Have a great weekend! Sarah Sarah Stevenson Fundraising Director The Tor Project sstevenson(a)torproject.org Public Key: 93B3 AC08 4257 FA3D D4BB 8E95 CC08 5DBA C015 612A

1 1

November 2018 User Feedback Report
by Maggie 18 Dec '18

18 Dec '18

Hey, team! Welcome to the November User Feedback summary. November was /special/, in that users mentioned bugs and known issues much less than in other months. This is partially because there were no TB release blog posts in November, and most bug reports appear on the blog. As such, I'm skipping the user feedback sheet this month, since it's pretty bare compared to past months. All relevant user-reported bugs are included directly in this email. The most frequently mentioned bugs were the following: - Cannot select/copy/paste text on TBA (27256) - RESOLVED [1] - Tor Browser cannot be booted multiple times from a USB drive (28068) - OPEN [2] TL;DR: - I'm noticing that questions like "why can't I access this specific site on TB" are common across platforms (i.e. on RT, reddit, etc). - This month I've seen lots of questions about why Tor won't connect. This gives me the impression that bridges and pluggable transports are the biggest point of confusion for Tor users. Traumschule has compiled some more info to add to the pluggable transports section of the Tor Browser manual, which should help to address these questions. [3] ----------- Blog posts: ----------- Nothing of note - fewer releases this month than in past months, which means less user interaction on the blog posts, and fewer bug reports from users. ------- Reddit: ------- There wasn't much content in November that differed from past months. Still lots of people asking about using a VPN with Tor, wondering why they can't access a specific site, asking if a specific action will compromise their anonymity (adjusting settings, etc.), and wondering why bridges aren't working for them. The community is very good at answering these questions (though they still give varying answers regarding the question of VPNs). There have been a few questions about the Circle with Disney app, which people can use to monitor their family's internet use. --- RT: --- By far the most common question is 'why isn't Tor working?', with little supporting information. Maybe we can add something to the new support portal asking people to include a log and some context when they contact us on RT for help. --------------- Stack Exchange: --------------- most common tags: tor-browser-bundle: 12 this month configuration: 12 this month tor-install: 10 this month tails: 6 this month help: 5 this month vpn: 5 this month update: 5 this month That's all for November! As always, please feel free to get in touch with me any time for more information on user feedback. ---------- Footnotes: ---------- 1. https://trac.torproject.org/projects/tor/ticket/27256 2. https://trac.torproject.org/projects/tor/ticket/28068 3. https://github.com/torproject/manual/pull/7 -- Maggie pronouns: she/they | twitter: @meochaidha <https://www.twitter.com/meochaidha> pgp: 0626 9C68 D0CC 1A5B E41B 72F2 615E B878 975C 4CDC

1 0

Tor Browser meeting, 17 Dec 2018
by Georg Koppen 18 Dec '18

18 Dec '18

Hi! We had our last Tor Browser meeting for this year yesterday. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-12-17-19.00.log… Status updates from the pad are available below: Monday December 17, 2018 pospeselr: - super sick, may not make this meeting (GeKo: get better soon! I'll write something up then for our #3600 discussion, I guess, which you could digest later) Arthur: - Tim Huang has been looking at spoofing the macOS command key as "control" so that we could spoof useragent in JS. His preliminary observation is that it fixes google docs. Is that something that Tor thinks is a good idea to work on and would be interested in using? Or what would help in making this decision? (GeKo: yes, we are definitely interested as the current solution is just a workaround to somewhat balance usability/fingerprinting concerns) GeKo: Last week: -helped with releases getting out, nothing exploded it seems, which is reassuring but we got a lot of good bug reports (which I triaged and tried to help with): https://trac.torproject.org/projects/tor/ticket/28873 https://trac.torproject.org/projects/tor/ticket/28874 https://blog.torproject.org/comment/278874#comment-278874 (still need to verify that one) #28874 led me over the weekend to try to build a debug build which in turn uncovered issues with our debug builds (https://trac.torproject.org/projects/tor/ticket/28875) and I sat down writing patches for our broken ASan debug builds (#27597) - reviews/testing (#28720, #28640, #28850, #28764, #12885) - helped with Sponsor8 report - thought about our current donation banner logic and a potential release to show it longer to users - made progress on security slider redesign work (#25658) although not as much as I wanted - work on related bugs: -patch for #21805 (WebGL's click-to-play is not working) -investigating #28873 - started to work on mingw-w64-clang toolchain over the weekend (#28716) - TBA-a3 meeting This week: -make as much progress on #25658 as I can and optionally #28716 -I'll be afk from Thursday lunch time on and plan to show up on Jan 7, 2019 :) mcs and brade: Last week: - Reviewed work to be done for #25694 (Improve the user experience of updating Tor Browser). - Worked on #28885 (notify users that update is downloading). - Reviewed #12885 (disable Windows JumpLists). - Filed #28822 (re-implement desktop onboarding for ESR 68). - Commented in #28809 (Create build-specific installer for macOS). - Did a little testing of Tor Browser 8.0.4 on macOS. This week: - More work on #28885 (notify users that update is downloading). - We will be away from keyboard tomorrow (December 18). - We will mostly be away from keyboard between December 23 and January 1. sysrqb: Last week: Finished torbutton as a system-addon patch (#28640) Pushed a patch for review backporting Download crash on Android (#28705) TBA-a3 planning meeting Worked a little on new TBA Tor Launcher design (#28329) Began looking at Fastlane for localization (#26844) This week: More Fastlane work (#26844) Patch for adding permission for installing apps from TBA (#28814) Tor Launcher on Android design (pending mockups) (#28329) Start investigating F-Droid again (#27539) boklm: Last week: - attended reproducible builds summit, and sent an email about this to tbb-dev: https://lists.torproject.org/pipermail/tbb-dev/2018-December/000934.html - helped with publishing of the release - fixed #28850 (Error downloading dvlib-26.0.1.pom and dvlib-26.0.1.jar) - did email setup for sending testsuite results This week: - continue work on testsuite, and binutils issue tjr Working on analyzing the telemetry we have for content window sizes pili: Last week: - OTF Proposal for warnings and notifications and new identity work - Sponsor 8 Q4 report This week: - Looking ahead at next year and planning Tor Browser Sponsor work - Sponsor 8 Q4 report - AFK from Thursday 21st Dec - Friday 4th Jan inclusive sisbell: Last week: - #27609 - Evaluate Tor Onion Proxy - Evaluation Work - #28803 - Integrate building PT - Initial investigation - #28752 - Gradle downloads tor-android-binary (fixed) This Week: - #27609 - Evaluate Tor Onion Proxy - Break apart into definable tasks/issues - #28803 - Investigate Pluto 2 for building of transports antonela: Last Week: - #28329 TBA + Orbot - TBA-a3 meeting This Week: - #28329 TBA + Orbot - #23888 Snowflake web extension Georg

1 0

Notes from December 13 2018 Vegas team meeting
by Karsten Loesing 14 Dec '18

14 Dec '18

Notes for December 13 2018 meeting: Gaba: 1) network team: - s8 Q4 report on the make - MOSS modularization proposal was awarded this week. Starting Jan 1st (for 1 year). 2) metrics team: - s13 november's report was sent 3) ooni - monthly meeting on roadmap - process tweaking - hiring a new dev to replace one leaving 4) anti-censorship: - kat will start working on 2nd report - new developer hiring position: 2nd round for code challenge. we will make a decision soon. Antonela: 1) Reviewed blog related tickets, user testing docs and the new DRL proposal 2) Working with matt on #28329 TBA + Orbot 3) Working on snowflake extension UI 4) Working on Outreach material, Alison and I powdered magic last week 5) Writing a blogpost for the EOY campaign about the ux team 6) Writing November ux report 7) Hiro is working on tpo.org or tpo.org/about on staging 8) Elio delivered OONI Explorer Measurement pages this week 9) OONI and UX did a kick off for OONI Explorer Country pages Nick: 1) One more 0.3.5.x release likely before Christmas. Had to delay 0.3.5.x schedule again. 2) New "dormant" feature may affect applications in 0.4.0, especially if they rely on Tor to always bootstrap. Applications may affect the dormant feature, especially if they check for updates frequently. We should send some emails and schedule a meeting, I guess? Georg: 1) Tor Browser 8.0.4 and Tor Browser 8.5a6 went out and it looks like nothing exploded (yay!) 2) Preparation for our next big milestone for Tor Browser on Android Mike: 1) Sponsor2 work continues. Sarah: 1) Was in San Francisco last week for Berkeley Group presentation. 2) Spent time in Seattle office syncing with Al and writing notes on letters sent to donors who haven't shared their email address with us. 3) Seeing an uptick in donations from TB updates as well as social media contest for a Tor swag pack. 4) Drafted 2019 fundraising roadmap. 5) Reaching out to high net-worth individuals who may be interested in our work, but who have never donated. 6) Donate page was down early this morning and was fixed by Linus. It went down a few more times, but seems okay now. 7) Working with Steph on RightsCon roundtable proposal. 8) Sent Human Rights Day email to our email list. Steph: 1) EOY fundraising - social media, editing blogs: 2 more very close to finished. Did a push with graphics around human rights day 2) checking for people who may want to join Sarah and I in a RightsCon submission for a fundraising/marketing roundtable 3) Added some ideas for Sponsor19 Report 2 Arturo: 1) Circulated OONI monthly report, check it out: https://lists.torproject.org/pipermail/tor-project/2018-December/002122.html 2) Moving forward with OONI Explorer measurement page development 3) Finishing WDC -> MIA infrastructure migration and other devops fires 4) From January to beginning of March I am going to be in the UTC+13 timezone. 5) Bugfixing and improvements following the OONI Probe mobile app beta launch Sue: 1) Did cash forecast analysis and board book for board meeting. 2) Invoiced funders for October and November 3) If there are any milestones that I can invoice for please get them to me soon. 4) Working on finishing the audit by EOY 5) Working on Audit for 2014 and 2016 findings with DRL. Pili: 1) Sponsor 8 Q4 report - started gathering tickets and filling in indicators 2) Sponsor 9 Phase 1 report - looking at updating narrative report based on feedback from Sida 3) Sponsor 19 - started organising tickets for Browser, UX and Community teams 4) Started organising tasks for Community Portal 5) OTF Core Infrastructure Fund Proposal review 6) Reviewed outstanding blog tickets and started thinking about future plans for the blog isabela: 1) Mozilla All Hands was really great. 2) Following up with grants and sponsors reports 3) working on YE blog post and video for challenge 4) will be in DC for a day next week - will meet DRL - also will be working from Brazil from dec 20th till january 13 Karsten: 1) Published EOY campaign blog post "Strength in Numbers: Measuring Diversity in the Tor Network": https://blog.torproject.org/strength-numbers-measuring-diversity-tor-network Shari: 1) sending notes to potential major donors and other focus on end-of-year fundraising 2) lunch with Mitchell Baker from Mozilla on Tuesday 3) general editing and personnel stuff 4) wrapping things up in the office next week Erin: 1) my first vegas meeting! sitting across from Isa in NYC, getting into the flow. 2) what kinds of updates do you want? (so I can prepare for next meeting) 3) personnel stuff, wrapping up some offboarding 4) conversations w/ Isa re: our recruiting processes in progress

1 0

OONI Monthly Report: November 2018
by Maria Xynou 13 Dec '18

13 Dec '18

Hello Tor world, In November 2018, the OONI team released the public beta of the revamped OONI Probe mobile apps and, in collaboration with the Localization Lab, we started coordinating the translation of the apps in preparation for their stable release. We also dealt with infrastructure-related issues, worked on pipeline ingestion fixes, added end-to-end integration tests to the OONI Probe orchestration system, and presented OONI at a number of events. ## Public beta release of OONI Probe mobile apps We released the public beta of the OONI Probe mobile apps. On Android: * Sign up to the beta: https://play.google.com/apps/testing/org.openobservatory.ooniprobe * Update your OONI Probe mobile app (to get the public beta) from Google Play On iOS: * Tap on this link from your device and follow the instructions: https://testflight.apple.com/join/rh3Ig7fE ## Translation of revamped OONI Probe mobile apps The revamped OONI Probe mobile apps not only include new design, UI and features, but they also include new (and hopefully improved!) copy. During November we: * Translated all of the new OONI Probe mobile app copy to Greek * Published guidelines for translators: https://github.com/ooni/translations/blob/master/Guidelines.md The Localization Lab provided us support with regards to the coordination of the rest of the translations (https://www.transifex.com/otf/ooniprobe/) ## Infrastructure During November, we worked on improving our infrastructure and dealing with infrastructure-related issues. Specifically: 1. The eclipsis platform migrated their servers from Washington DC to Miami and we dealt with the issues related to that migration: https://github.com/ooni/sysadmin/pull/247, https://github.com/ooni/sysadmin/issues/241 2. Dissecting the XEN bug with Greenhost: https://github.com/ooni/sysadmin/issues/240 (that was triggered by simhash ingestion) 3. Open recursive resolver at ooni-zoo.infra.ooni.io used for amplification attack: https://github.com/ooni/sysadmin/issues/248 4. Dealing with services going down: https://github.com/ooni/sysadmin/issues/244, https://github.com/ooni/sysadmin/issues/245, https://github.com/ooni/sysadmin/issues/157#issuecomment-435663643 ## Pipeline ingestion fixes We worked on pipeline ingestion fixes (that are a dependency for further work on the pipeline code): https://github.com/ooni/pipeline/pull/126, https://github.com/ooni/pipeline/issues/48 ## Better testing for OONI Orchestra We added end-to-end integration tests to ooni/orchestra (https://github.com/ooni/orchestra/pull/44) the OONI Probe orchestration system. We also added support for running a full orchestration system as a docker-compose based harness. ## Worked towards the integration of Psiphon into Measurement Kit During November 2018, we started working towards integrating Psiphon into Measurement Kit (our network measurement library that powers the OONI Probe mobile apps), in order to enable OONI Probe users to test the accessibility of Psiphon. To this end, we discussed with Psiphon developers how to best move the project forward and we drafted an overall strategy (https://github.com/measurement-kit/measurement-kit/issues/1425) As part of this research activity, we improved the code of the Psiphon C library to make it more easily accessible to C/C++ clients (https://github.com/measurement-kit/libpsiphon/pull/2) This is work in progress, and we'll continue to work towards integrating Psiphon into Measurement Kit over the next months. ## Community use of OONI data ### Report on the blocking of Ukrainian websites in Crimea Digital Security Lab Ukraine published a new research report based on OONI data. Their report, examining the blocking of Ukrainian websites in Crimea, is available here: https://medium.com/@cyberlabukraine/ukrainian-websites-in-crimea-banned-by-… ## Community activities ### Community meeting We held a community meeting on Slack (https://slack.openobservatory.org/) on Wednesday, 27th November 2018. As part of the meeting, we discussed: 1. Post-court verdict scenario of cellular services suspension in Pakistan 2. Censorship measurement research during (and leading up to) the DRC's upcoming December elections 3. OONI updates: Public beta (mobile apps) & translations ### OONI workshops in Taiwan After the OTF Summit, OONI's Maria facilitated: * OONI workshop at the Mozilla Community Space Taipei (https://ocftw.kktix.cc/events/ooni-workshop) (1st November 2018) * OONI seminar at the Science & Technology Law Institute of Taipei (2nd November 2018) ### Internet Governance Forum (IGF) OONI's Simone traveled to Paris to attend the Internet Governance Forum (IGF), where he participated on a panel, explaining OONI and network performance tests. Information about the panel is available here: https://www.intgovforum.org/multilingual/content/igf-2018-dc-net-neutrality… ### OONI session at CryptoParty in Albania OONI's Elio facilitated an OONI workshop at the CryptoParty in Tirana, Albania (17th November 2018), where he taught local activist groups how to use OONI Probe and previewed the new OONI Probe 2.0 Beta. Photos of the event, including the OONI session, are available here: https://commons.m.wikimedia.org/wiki/Category:CryptoParty_Tirana_2018 ### Southeast Asia OONI Probe workshop Our Malaysian partners, Sinar Project, have been leading efforts to engage local Southeast Asian communities with OONI Probe censorship measurement research, particularly leading up to and during political events, such as elections. Sinar Project recently organized and facilitated an OONI Southeast Asia Regional Workshop for their local partners in Cambodia, Indonesia, Philippines, Thailand and Vietnam. The aim of their workshop was to teach their partners how to run OONI Probe, how to contribute to test lists, and how to participate in censorship measurement research more generally. In November, Sinar Project published a report, documenting the workshop and sharing their findings, resources and recommendations. Their report is available here: https://sinarproject.org/digital-rights/updates/open-observatory-of-network… ### OONI session at Barcamp Bangkhen in Thailand Our Thai partners, Thai Netizen Network, facilitated an OONI session at the Barcamp Bangkhen conference in Thailand on 25th November 2018. Information about the conference is available here: https://2018.barcampbangkhen.org/sessions Thai Netizen Network also shared their slides from their OONI session: https://docs.google.com/presentation/d/1-N6R_KqGipsBrDdUIskXMf1qr_BmEfIkPZO… ## Userbase In November 2018, OONI Probe was run 363,805 times from 4,733 different vantage points in 213 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

Tor Browser Release meeting: Wednesday 12th December @ 1900UTC
by Pili Guerra 11 Dec '18

11 Dec '18

Hi all, Just a reminder of the Tor Browser Release meeting this week. This will be the last meeting of the year! Our next release is planned for the end of January so please pop in if you have any requests you would like us to consider. The earlier we know, the better :) Otherwise we will be back on January 9th at the usual time. Happy holidays! 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

Network team meeting, 10 Dec 2018
by Nick Mathewson 11 Dec '18

11 Dec '18

Hi! The meeting log is at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-12-10-17.59.html Below are the contents of our pad from the meeting. = Network team meeting pad! = This week's team meeting is at Monday at 1800 UTC on #tor-meeting on OFTC. Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1800 UTC 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.) 12 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002054.html 19 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002074.html 26 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002084.html 3 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002117.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… Core Tor/sbws is now part of the bug triage, CI, and reviewer assignment roles * Let's try a different way of looking at proposed tickets: https://pad.riseup.net/p/network-team-triage-2018 0.3.5 (bugs only): https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… 0.4.0: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == 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 actual point when you finish a task (as well as "fix" the estimate when starting the issue). * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbd… * Check other's people call for help in their entries. << Remember that priority is Sponsor 8 - roadmap is sort out by priority >> Activity O2.5 is the one we are missing and need to be done by the end of December 2018. ------------------------------- ---- 10 December 2018 ------------------------------- == Announcements == This week's meeting is on Monday at 1800 UTC. Please don't bulk-delete all the old entries from this pad any more. Instead, delete the "planned" and "actual" for the previous week, but leave the "planned" for this week in place. Please check the dates before deleting. Gaba> Sponsor 8 Q4 REPORT : start adding tickets that you worked on in the last 3 months PLEASE pretty please https://storm.torproject.org/shared/E8jZ6LwgMxa9zeyOgEye3eq6ytTaFZjCCetMYm8… Teor is bringing a proposal for proposed ticket. Please make comments in the pad and we can discuss it in the first meeting in January when Teor will be present https://pad.riseup.net/p/network-team-triage-2018 Reviewer role proposal is still open for comments. gaba> I will work on it when I have a little more time to discuss it with the team in January (we need to separte process from responsabilities). https://pad.riseup.net/p/q0s3rQxVzSeZ == Discussion == * Discuss Snowflake who else go to work on it discuss the issues we have in the roadmap what came out of snowflake meeting that ahf leaded There is a Snowflake roadmap now that involves several teams at Tor: https://storm.torproject.org/shared/OdNtwrtRrqklh76l4PfcngBbQFDbjv_jRroj0We… - priorities: - spec [nick starts this in December] - tests - not reproducible on windows - #25601 is a pretty bad issue for deployment right now? - #21314 -- at least currently, when my tor goes quiet/dormant, my snowflake keeps on sending traffic * We won't have meetings in the weeks of 24 and 31 December 2018 Can we do a team meeting at 2300 UTC on Tuesday 8 January 2019? (teor can send out a reminder email in the last work week in December) [Yes, let's consider it scheduled for then.] * Who needs help with reviews? There are 4 review tickets that haven't been modified in the last 2 weeks, the oldest is 5 weeks old. Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Sponsor 8 is wrapping up in December. Right now working on this: catalyst, ahf, dgoulet, teor, nick. Any of you need help with it? O2.5 (bootstrap reporting) is most important REMINDER that it may be good to have this wrap up by December 20th the most. PLAN WORK/TICKETS: https://pad.riseup.net/p/qPH3xF4JaHOB * Please see tickets with tag "035-rc-blocker?" -- are any of them really rc blockers? Are there any other true rc blockers? https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… * Release schedule: any changes? * Look at Teor's proposed-ticket plans in https://pad.riseup.net/p/network-team-triage-2018 - everybody agreeing on starting this in January 2019 - adding open questions to a section at the bottom. == Recommended links == Category Theory for Programmers https://github.com/hmemcpy/milewski-ctfp-pdf Long, but even the first few chapters are useful for thinking about functions with(out) side-effects. == 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! Nick: Week of 12/3 (planned): - Attend Mozlando - Help as needed with proposal - Review and merge in my spare time - Possibly, return to dormant-persistency code (#28624) Week of 12/3 (actual): - Attended Mozlando, talked with various Mozilla folks. - Reviewed and merged a bunch of code - Implemented #28755 (generic K=V parsing) to help out ahf and dgoulet and teor with #28179. What can I implement for you? :) - Implemented dormant-persistency branch. (#28624) Week of 12/10 (planned): - Try to fix as many 035 and 040 bugs as possible - Fuzz #28755 et al via (#28808) - Reschedule 0.3.5 (and 0.4.0?) release plans. When can we call it RC? Notes: Want help with: - Please help identify 035-rc-blocker issues, if any. Mike: Week of 12/03 (hopefully): - Finish Nick's PR fixups on the wtf-pad branch - Work on more tests/high prio items Week of 12/03 (actual): - Did type clarification fixes on wtf-pad; chased down clang-specific test bug - Resolved conflicts between asn and my wtf-branches; Handed off wtf-pad code branch to asn Week of 12/10 (planned): - Custom 0.2.9 backport of #27049 fix? - wtf-pad unittests Want help with: Week of 12/03 (planned): Sponsor 8: - Finish off implementation of #27100 based on the orconn-track branch from Catalyst. - Upstream disable network patch to Orbot (#25497). - Simpleperf tests for #28409. Sponsor 19: - Write summary of meeting and create tickets. - Figure out where the issue is in my setup with termination of WS connections. Week of 12/03 (actually): Sponsor 8: - Talked with Nick, David, and David F (dcf) about #28180 and to both do STATUS and LOG. - Walked over Nick's review comments on #28179, solved the easy ones. - Looked at Nick's K/V parser for use in #28180 branch. - Walked over Meek Client + Snowflake Client code to see where STATUS notifications would make sense. Sponsor 19: - Talked with Gaba a bit about prioritize. - Been trying to debug the issue in #28726 together with dcf for my parallel Snowflake setup. Misc: - Sysadmin interviews. Week of 12/10 (planned): Sponsor 8: - Get some help with solving the dependency issue between src/lib/* code in patch for #28179. - Update specs for STATUS with example K/V pairs from currently deployed PT's. - Get #28179 reviewed again. Sponsor 19: - Continue to debug #28726 JS/Go proxy code. Misc: - Sysadmin interviews. asn: Week of 12/04 (planned): - Continue helping with WTF-PAD work. Hoping to push the branch out to Nick for review at the end of the week or the start of the next. Coordinate with Mike on how to achieve this. - Continue helping with anti-censorship hiring. - Do weekly reviews. Week of 12/04 (actual): - Lots and lots of work on #28142. - Worked on pushing the current #28142 WIP branch to Mike, so that we can swap positions. He starts writing unittests and I start doing fixups. - I started writing fixups for Nick's review on GH. - I noticed that #28142 branch started failing tests/compilation on appveyor, so I had to do various fixes there. It's still not green unfortunatey, since it's failing on 32-bit appveyor but not on 64-bit (see below). - Mike pointed out that there are about 15 of Nick's comments on GH that have been hidden as (outdated) with the exact same UX as the (resolved) ones. So now I'm writing fixups for another 15 of review comments. - Was assigned to come up with the coding task for the anti-censorship applicants. It was pushed to the applicants late last week. - Did reviews. Week of 12/10 (planned): - Continue doing fixups on #28142: - Currently 32-bit appveyor is failing on the stochastic prob distr tests. I'm not sure what's going on there and why it's failing only on 32-bits. I have informed Riastradh on this and see what he tells me. Other than that, maybe the tests are busted on 32-bits and we have to disable them. - I have more fixups to do based on past Nick's review on #28142. - Still need to check Mike' response on #28634. Help with: - Not right now. I think I'm sufficiently synched up with Mike for now. dgoulet: Week of 12/03 (planned): - Again, any s8 priority tasks that arise. For now, I have none lined up so hit me with those if you need me for s8. - I have one ticket that needs to be addressed part of s8 for 0.4.0 (maybe for 0.3.5 if I can get it in before rc!): #25899. - Considering my "on call" status for s8, I'll jump into prop289, my next task on the roadmap (non-s8). Week of 12/03 (actual): - HSv3 ticket: #28669, #28275. - Rework with ahf the #25502 s8 spec patches (#28180). - Discussion with ahf on the STATUS notification message for PTs. - The bad-relays land was in need of a bit more attention then usual this morning. Week of 12/10 (planned): - Finalize/review the STATUS notification work. Will require spec changes as well as code review. - Setup a Snowflake environment to start play with it more seriously. ~ gaba: Week of 12/3 (actual): - helping with onion services proposal - snowflake roadmap Week of 12/10 (planned): - S8 Q4 report - S8 follow up with work that needs to be done. https://pad.riseup.net/p/qPH3xF4JaHOB - 1:1s - anti-censorship position follow up help with: - communicating anything about sponsor8-bootstrap help/needs and progress catalyst: week of 12/03 (2018-W49) (planned): - time off 12/05-12/07 - travel request for Brussels - make more progress on orconn-tracker (#27167) - reviews week of 12/03 (2018-W49) (actual): - time off 12/05-12/07 - noticed some fallback directories seemed slow; teor seems to be taking care of it now - reviewed #28591 (accept future consensus for bootstrap) - responded to feedback from mcs on #27102 (decouple bootstrap progress numbers from BOOTSTRAP_STATUS enum values) - opened #28731 as a quick small change to improve troubleshooting bootstrap issues - as part of #27167, attempted to refactor some control event stuff in control.c; wound up in a big tangle with getinfo/setevents stuff. deferring for now - as part of #27167, attempted to refactor some control protocol stuff in control.c; this was somewhat more successful week of 12/10 (2018-W50) (planned): - CI + Coverity rotation <- nick is dong this one this week - reviews - travel request for Brussels - update detailed sponsor8 progress - more progress on orconn-tracker (#27167), specifically adding and combining circuit tracking with the work so far - get feedback on #28731 help with: - feedback on #28731 (log bootstrap tag to make troubleshooting easier) -- are users likely to report the tags if we show them? right now we do a lot of troubleshooting from the percentages, which might not work in the future if we need to renumber things. [generally, users will either copy-and-paste whatever they get in the logs, or report from memory if they can't copy-and-paste. The latter reports are generally not useful. -nm] - there's a lot of bootstrap troubleshooting knowledge in my head that we will still need after the sponsor8 work because older releases will still be out there. maybe we should create a troubleshooting guide? [I lean towards "yes if not too timeconsuming, but only after s8 is done". -nm] [yes please WHEN we wrap up s8 musts] teor (offline): Week of 3 Dec (planned): High-Priority: - I am on bug triage this week - Get my macOS install working again - Continue to work on s8 bootstrap tickets - integration testing for clock skew? - chutney CI - earlier s8 bugfixes Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews Revised Plan: - Do revisions on s8 bootstrap tickets - Need to update the fallback directory mirrors, they are causing bootstrap issues - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - Also on networks that drop packets - Update the reviewer, bug triage, and CI roles (and links) to include sbws - Send pad and meeting notes to tor-project Week of 3 Dec (actual): High-Priority: - Bug triage (x4) - I have a working macOS install, with backups that should actually work this time - Continued to work on s8 bootstrap tickets: - Rebuilt the fallback list, because it was causing slow bootstraps (#24786 and children, #28702, #28703) - Fuzzy match the fallback whitelist (#24838) - Updated the fallback script to match tor's reasonably live consensus checks (#28571) Medium-Priority: - 1.5 days of of sbws reviews, no more sbws this week - Code reviews - Metrics job applications - Other small tickets - Updated the reviewer, bug triage, and CI roles (and links) to include sbws Week of 10 Dec (planned): High-Priority: - Need to update the fallback directory mirrors, they are causing bootstrap issues - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - And also on networks that drop packets - Continue to work on s8 bootstrap tickets - integration testing for clock skew? - chutney CI - earlier s8 bugfixes Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews Week of 10 Dec (actual): High-Priority: - Sent network team meeting time email to tor-dev, because we're back to our regular schedule - Sent pad and meeting notes to tor-project - Need to update the fallback directory mirrors, they are causing bootstrap issues - Did the fallback list merge (thanks Phoul!) Medium-Priority: - 0.3 days of sbws reviews - Metrics job applications - Other code reviews Next week: - Send reminder emails for team meetings at: 2300 UTC on Tuesday 8 January 2019, 1800 UTC on Mondays 14 and 21 January, miss 28 January and 4 February due to hackfest/FOSDEM our first February meeting 2300 UTC on Tuesday 11 February Help with: - juga (offline): - Week 12/3 (planned) - continue with the work to monitor relays that are not measured: start using and external tool and/or add keyvalues that doesn't big modifications to the code - Update install and deploy documentation based on Torflow's documentation - Week 12/3 (actual) - Update install and deploy configuration based on Torflow's documentation (#28647) - Stop merging multiple torrc options with the same name (#28738) - Parse correctly torrc options that don't have an argument (#28715) - Make info level logs more clear and consistent (#28736) - Explain in the documentation that stdout will go to syslog when running with systemd (#28761) - Document configuration verify option and disable urllib3 warnings (#28788) - Week 12/10 (plan) - disable connection padding in sbws' Tor (#28692) - Try enabling predicted circuits (#28701) - Explain reasons why sbws might stall and find out more (#28663) - send scanner metadata as part of every HTTP request (#28741) - Help with: - teor: i left a comment in PR in #28602 - teor/nickm?: question in #21377

1 0

November 2018 report and December 2018 plans for the metrics team
by Karsten Loesing 11 Dec '18

11 Dec '18

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in November 2018 as well as a few expected highlights for the current month, December 2018. On behalf of the Tor metrics team, Karsten November 2018: Evaluated a number of frameworks that could help to reduce code maintenance costs. A number of features have been added to stem to support this work. The results of the evaluation are to be published in an upcoming tech report. Split up metrics-web's legacy module into more maintainable parts [1]. [1] https://bugs.torproject.org/28116 Released Onionoo 7.0-1.19.1 [2] that updates to MaxMind's GeoLite2 format for the ASN database [3]. [2] https://dist.torproject.org/onionoo/7.0-1.19.1/ [3] https://bugs.torproject.org/28254 Prepared new graphs on relays by country for a possible metrics-team blog post for Tor's end of year campaign. Reviewed first bunch of applications for the third full-time member of the metrics team [4]. [4] https://www.torproject.org/about/jobs-metrics-data-architect.html December 2018: Continue to evaluate frameworks for use in a CollecTor replacement and implement a prototype replacement [5]. [5] https://github.com/irl/bushel Deploy changes to the Total consensus weights across bandwidth authorities graph [6] with another line for the consensus [7] and with all lines showing only relays with the Running flag in their respective consensus or vote [8]. [6] https://metrics.torproject.org/totalcw.html [7] https://bugs.torproject.org/28352 [8] https://bugs.torproject.org/28137 Combine two bandwidth graphs by relay flag and switch to a better visualization using stacked area charts [9]. [9] https://bugs.torproject.org/28353 Tweak OnionPerf graphs by showing all measurements at once and therefore removing the combined all-sources lines [10]. [10] https://bugs.torproject.org/28603 Write blog post for Tor's end of year campaign.

1 0

Tor Browser meeting December 10, 2018
by Georg Koppen 10 Dec '18

10 Dec '18

Hi everyone! Our weekly Tor Browser meeting ended 1 hour ago. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-12-10-19.00.log… and the items on our meeting pad are pasted below, for your convenience: Monday December 10, 2018 Discussion: - Summary of All Hands Meetings? [GeKo: overall it seems the meeting went well, there'll be a summary sent to the tbb-dev list I hear] boklm: (afk during meeting) Last week: - helped build the new releases - some reviews - fixed #28775 (Add mercurial in tbb-build ansible role) - added patch for #26843 (Get l10n-changesets.json from tor-browser.git) - looked at #28685 (Tor Browser for Android needs a more dynamic Build ID) This week: - will be at reproducible builds meeting from tuesday to thursday: probably not much time tomorrow to help with release publishing. - on friday/monday: continue work on testsuite, and binutils issue mcs and brade: Last week: - Thought about bootstrap status reporting and commented in some tor tickets: - #27102 (decouple bootstrap progress numbers from BOOTSTRAP_STATUS enum values). - #28281 (outline of high-level bootstrap tracker abstractions). - Completed several code reviews: - #25794 (Disable PointerEvents). - #27290 (WebGL is broken in Tor Browser 8). - #27919 (Backport SSL status API). - #28075 (Torbutton WARN: no SOCKS credentials found). - #28608 (Disable HTTP response throttling by default). - #28695 (Set BRNameMatchingPolicy to "Enforce"). This week: - #25694 (Improve the user experience of updating Tor Browser). pospeselr: Last week(s): - updated #25702 patches with feedback (tor-browsesr re-branding) - patch for #28546 (windows installer rebranding) - patch for #12885 (remove broken 'jumplists' in tor-browser for windows) - closed #26280 (blurry app icon in Gnome) - Mozilla All-Hands, met up with Arthur re: tor browser uplift This week: - patch for #28809 (update tor-browser-build to allow side-by-side installation of release, alpha and nightly) - get back on that #3600 work, ping Steven E about that storage-api/TPI meeting and see what ideas we can integrate/steal - patch for #28561 (moving About Tor dialog from tor-button to tor-browser branding) - investigate #28810 (separate default tor ports for release, alpha, and nightly builds) sysrqb; Last week: Mozilla All-Hands Ran/attended meetings about: Sandboxing First-Party Isolation Canvas fingerprinting and fonts Mobile roadmap Other Tor+Mozilla things This week: Clean up torbutton-as-a-systemaddon patch - #28640 Try backporting patches for Android file/content URI crash - #28705 Start working on new TBA+Orbot UI - #28329 Meeting about next TBA alpha release tjr: - Sat at home last week and missed everyone - The NSS Version bump landed in esr60; so I will be (trying to) land build jobs and patches there: - mingw-gcc x64 build confirmed to run - mingw-clang build - x86 and x64 builds confirmed to run - missing resources backported and confirmed fixed - --enable-accessibility build works and runs on Windows 10 - did not test an accessibility tool though https://treeherder.mozilla.org/#/jobs?repo=try&revision=9192ea6f6abeb775f9a… is the full patchset for x86/x64 mingw-gcc, mingw-clang+resourcefix+accessibility on esr60 - Working on security bugs backports: - Randomize small allocations in jemalloc: https://bugzilla.mozilla.org/show_bug.cgi?id=1376408 - Backported patch - jemalloc changes a lot since it was originally written - unit tests pass, running Talos to get an approximation on performance - Need to fix a small Windows issue; and manually re-read patch to confirm it looks sane. - Arraybuffer Metadata in its own Arena: https://bugzilla.mozilla.org/show_bug.cgi?id=1474659 - Patches apply fine, unt tests are fine. Need to Talos run for perf, and double check with reviewer the patch is okay - I think enabling CFG via mingw-clang would be 'easy' and be something nice. Haven't tested it yet though. https://trac.torproject.org/projects/tor/ticket/28811#ticket - I am wondering what is up with #3600; in particular I was hoping to understand the proposals a bit better... GeKo: Last week: -a lot of reviews to get stuff into our releases (e.g. #26843, #28697, #28725, #28573, #28696, #28540, #27762, #28466) -built releases and started signing (stable is ready and is getting rsync'ed to dist) -did the begin-of-the-month admin work -wrote some smaller patches (#28750, #28747, #28695, #27290, #25794, #28608) -worked on Rust enabled in macOS Tor over the weekend (#25779) -found the missing binutils patch for enabling MOZILLA_OFFICIAL on 32bit-Windows builds on the weekend, currently testing result (see: #28618) -did some triage for TBA-a3 -worked on the security control redesign (#25658) -work on related bugs (#27290, #21805) This week: -help getting releases out -review of proposals for #3600 -more work on #25658 and related bugs -reviews -Tor Browser design doc update (#25021) sisbell: Last week: - #28697 - Reusable signing key and fixed timestamps to make apk reproducible (merged) - #28696 - Use hard-coded grade repo path to make apk reproducible (merged) - #28764 - OpenSSL Build for Android (in review) This Week: - #27609 - Evaluate Tor Onion Proxy - #28765 - LibEvent for Android - #28766 - Tor Build for Android pili: Last week: - Sponsor 8 Q4 report prep - Roadmap review - Research into Project Management tools This week: - More of the same - Tor Browser Release meeting antonela: Last Week: - Mozilla All-Hands This Week: - #28329 TBA + Orbot Georg

1 0

Network team meeting notes, 3 December 2018
by teor 10 Dec '18

10 Dec '18

Hi, Here's the network team meeting log and pad for last week. The meeting log is at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-12-04-23.04.html = Network team meeting pad! = Last week's team meeting was on Tuesday at 2300 UTC on #tor-meeting on OFTC. This week's team meeting is at Monday at 1800 UTC. Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1800 UTC 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.) 6 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002047.html 12 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002054.html 19 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002074.html 26 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002084.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Let's look at proposed tickets! 0.3.5 (bugs only): https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… 0.4.0: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == 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 actual point when you finish a task (as well as "fix" the estimate when starting the issue). * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbd… * Check other's people call for help in their entries. << Remember that priority is Sponsor 8 - roadmap is sort out by priority >> Activity O2.5 is the one we are missing and need to be done by the end of December 2018. ------------------------------- ---- 04 December 2018 ------------------------------- == Announcements == This week's meeting is the first meeting in December, it's on Tuesday at 2300 UTC. Next week we'll go back to Monday at 1800 UTC. Please don't bulk-delete all the old entries from this pad any more. Instead, delete the "planned" and "actual" for the previous week, but leave the "planned" for this week in place. Please check the dates before deleting. == Discussion == Next network team meeting: * we will discuss Snowflake (who else go to work on it and discuss the issues we have in the roadmap - what came out of snowflake meeting that ahf leaded) * Let's change how we add proposed tickets to releases https://pad.riseup.net/p/network-team-triage-2018 * We won't have meetings in the weeks of 24 and 31 December 2018 Can we do a team meeting at 2300 UTC on Tuesday 8 January 2019? (teor can send out a reminder email in the last work week in December) * Who needs help with reviews? Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Can we add Core Tor/sbws to the bug triage, CI, and reviewer assignment (done!) roles? * Is our process for "proposed" working? <-- we still didn't go through it yet teor says: things seem to get stuck in proposed. * Sponsor 8 is wrapping up in December. Right now working on this: catalyst, ahf, dgoulet, teor, nick. Any of you need help with it? • O2.5 (bootstrap reporting) is most important • REMINDER that it may be good to have this wrap up by December 20th the most. * Please see tickets with tag "035-rc-blocker?" -- are any of them really rc blockers? Are there any other true rc blockers? https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… * Let's suspend discussion on role "reviewer" until January. ok? https://pad.riseup.net/p/q0s3rQxVzSeZ * Release schedule: any changes? == Recommended links == Blameless Post-Mortems and a Just Culture https://codeascraft.com/2012/05/22/blameless-postmortems/ Software Defined Delivery Manifesto https://sdd-manifesto.org/ == 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! Nick: Week of 11/26 (planned): - book travel for brussels - meeting wrt privcount, tuesday, I think - review & merge aggressively - help everybody with deliverables - Release 0.3.5.6-? so that it can make the mid-december TB release? - Triage rotation - Identify 035-rc-blocker issues? Week of 11/26 (actual): - Review and merge - Worked on dormant persistency code (#28624), but got off to a false start - Worked on debugging and analyzing OpenSSL 1.1.1a bug (#28616). - Sick Thurs - Circulate the whitepaper about datagram-based designs. Week of 12/3 (planned): - Attend Mozlando - Help as needed with proposal - Review and merge in my spare time - Possibly, return to dormant-persistency code (#28624) Notes: - I'm not here; I'm at the Mozilla meeting. Want help with: - Please help identify 035-rc-blocker issues, if any. Mike: Week of 11/26 (planned): - Return from vacation; pick up wtf-pad Week of 11/26 (actual): - Caught up on mail and stuff. Sort of. - Did a final pass on the datagram paper; looks ok. - Looked over asn and Riastradh's code and squashed and rebased it - Started work on more wtf-pad fixups. Week of 12/03 (hopefully): - Finish Nick's PR fixups on the wtf-pad branch - Work on more tests/high prio items Want help with: - Feeling a little worried that maybe squashing was not the best plan? - But there are sooooo many fixup commits tho that I'm worried about conflicts accumulating and the branch being harder for Nick to re-review. Plus asn has been making and squashing branches.. - Nick: Is reviewing a squashed branch OK? I can still give you links to the various fixups for each of your github review commits. ahf: Week of 11/26 (planned) Sponsor 8: - Work with David with review on #28179, once he is happy I'd very much like Nick to also have a look at especially the Windows code. - Continue with s8-bootstrap and #27100 - Run simpleperf tests for #28409 and compare results. Sponsor 19: - Figure out next steps for candidates. - Meeting tomorrow at patch party time! Please have a look at https://trac.torproject.org/projects/tor/wiki/doc/Snowflake before our meeting :-) Misc: - CI and coverity duty. Week of 11/26 (actually) Sponsor 8: - Got a merge ready from David Goulet on #28179, moved to Nick's table. - Testet #26360 with #28179 changes and it seems to solve that issue as well. - Talked with Catalyst about the bootstrap situation for #27100 (see their excellent overview in #28281!) Sponsor 19: - Got a Bridge, Broker, Website (the JS part of Snowflake) and the client to run on my own infrastructure and laptop. - Working with dcf trying to figure out a bug in Snowflake where the connections gets terminated after a short while. - Snowflake network team kick off meeting. Misc: - CI: Fixed OpenSSL test failure for AppVeyor in ticket #28574. - Sysadmin interview. Week of 12/03 (hopefully): Sponsor 8: - Finish off implementation of #27100 based on the orconn-track branch from Catalyst. - Upstream disable network patch to Orbot (#25497). - Simpleperf tests for #28409. Sponsor 19: - Write summary of meeting and create tickets. - Figure out where the issue is in my setup with termination of WS connections. asn: Week of 11/26 (planned): - Continue going through the WTF-PAD TODO list. - Open tickets for future work on Riastradh's probability distribution code that don't need to happen right now. Week of 11/26 (actual): - Continue crunching through WTF-PAD (#28142): - Finalized probability distribution code and tests and squashed it all up in https://github.com/torproject/tor/pull/547 - Continued writing unittests for the rest of the code: https://github.com/torproject/tor/pull/547 Wrote unittests for histograms and token removal functions, fixed some bugs and did improvements along the way. - Summarized current work so that Mike can join in. Also organized the remaining tasks in some new master tickets: #28631 and its children #28632 and #28637 - Revised various parts of the onion service proposal. - Continue helping with anti-censorship interviews and other hiring stuff. - Helped a researcher who is doing a project with HSDirs and PIR. - Help with #28275. - Did weekly reviews (#28012, #28266). Week of 12/03 (planned): - Continue helping with WTF-PAD work. Hoping to push the branch out to Nick for review at the end of the week or the start of the next. Coordinate with Mike on how to achieve this. - Continue helping with anti-censorship hiring. - CI/coverity duty. - Do weekly reviews. Help with: - Mike, how should we split remaining WTF-PAD work? I've been writing tests for way too long and I would like a break. Do you want me to handle the remaining GH comments in PR#461, and you take care of the tests for this week? Any other suggestions? - Yes I am overwhelmed with fixups and have been struggling to get the motivation to do a huge pile more. Plus branches are getting unweildy with all of them. Maybe switching to testing will be a better plan. I have one more typedef-clarification fixup I've been working on that is pretty big, but helpful I hope. Let me get that in and then we can sync branches and switch. - Mike dgoulet: Week of 11/26 (planned): - Finalizing #28179 with ahf for upstream merge. I expects the branch to be ready for nickm's considerations today or tomorrow at worst. - Work on the remaining part of #25502, a s8 master ticket. Finalizing specs within #28180 to match implementation. - Whatever comes my way for s8 at that point. Week of 11/26 (actual): - Finished review and testing on #28179. It is in merge_ready now. - Updated the spec for #28179, they are in #28180. - Reviewed other s8 tickets: #28335, #28429. - Fixed various HSv3 bugs including an _old_ issue in the test: #28660. The #28669 took me a bit of time to figure out. - Helped a bit asn with the OTF onion proposal. - I've gone over the 035 tickets, flagged the one I think *must* be in and did patches for some. At this moment, they are all merged or in merge_ready. Week of 12/03 (planned): - Again, any s8 priority tasks that arise. For now, I have none lined up so hit me with those if you need me for s8. - I have one ticket that needs to be addressed part of s8 for 0.4.0 (maybe for 0.3.5 if I can get it in before rc!): #25899. - Considering my "on call" status for s8, I'll jump into prop289, my next task on the roadmap (non-s8). gaba (will have to leave mid-meeting): Week of 11/25 (actual): - anti-censorship interview - gettor meeting to check on work and move it forward between teams - snowflake meeting and start planning Week of 12/3 (planned): - helping with onion services proposal - ooni work - snowflake follow up help with: - communicating anything about sponsor8-bootstrap help/needs and progress catalyst: week of 11/26 (2018-W48) (planned): - proof of concept for orconn-tracker (#27167) - travel request for Brussels - reviews (priority on the sponsor8 ones) week of 11/26 (2018-W48) (actual): - pull request for #27402 - worked on a hash table for orconn-tracker - chatted with arma and others about why there seem to be two kinds of state change events in connection_or.c - reviewed #24661, #28554 (clock skew guard selection stuff) - wrote summary of proposed new list of bootstrap phases at #28281 - chatted more with ahf about #27100 - started enumerating places in connection_or.c where we call one kind of state change function but not another week of 12/03 (2018-W49) (planned): - time off 12/05-12/07 - travel request for Brussels - make more progress on orconn-tracker (#27167) - reviews help with: haxxpop: help with: teor (online, this week only!): Week of 26 Nov (planned): High-Priority: - Send tor-dev email about next week's meeting time (on Thursday, to avoid confusion) - Continue to work on s8 bootstrap tickets - accept clock skew for 24 hours in the future, as well as in the past - integration testing for clock skew? Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews Week of 26 Nov (actual): High-Priority: - Sent tor-dev meeting time email - Funding proposal review - Continued to work on s8 bootstrap tickets - accept clock skew for 24 hours in the future, as well as in the past - Unexpected macOS upgrade failure, and backup failure - I was off work for a day for some medical appointments Medium-Priority: - a day and a half of sbws reviews and tickets - Metrics job applications - Code reviews Notes: - Deferred the PrivCount blog post, because sbws is taking my extra time Week of 3 Dec (planned): High-Priority: - I am on bug triage this week - Get my macOS install working again - Continue to work on s8 bootstrap tickets - integration testing for clock skew? - chutney CI - earlier s8 bugfixes Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews Revised Plan: - Do revisions on s8 bootstrap tickets - Need to update the fallback directory mirrors, they are causing bootstrap issues - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - Also on networks that drop packets - Update the reviewer, bug triage, and CI roles (and links) to include sbws - Send pad and meeting notes to tor-project Week of 3 Dec (actual): High-Priority: - Bug triage - I have a working macOS install, with backups that should actually work - Continued to work on s8 bootstrap tickets: - Rebuilt the fallback list, because it was causing slow bootstraps (#24786 and children, #28702, #28703) - Fuzzy match the fallback whitelist (#24838) - Updated the fallback script to match tor's reasonably live consensus checks (#28571) Medium-Priority: - 1.5 days of of sbws reviews, no more sbws this week - Code reviews - Metrics job applications - Other small tickets Notes: - Looking forward to writing big chunks of Rust in 2019 Help with: - juga (offline): - Week 11/26 (plan) - continue with the work to monitor relays that are not measured - continue with the work to include the consensus measured bandwidth when calculating the minimum of the descriptors' bandwith - maybe some sbws refactoring - Week 11/26 (actual) - worked on monitor relays that are not measured - worked on include the consensus bandwidth when calculating the minimum of the descriptors' bandwith - removed broken links in documentation - changed http links to https in the documentation - include configuration file example in deploy documentation - worked on making CI to check for broken links in the documentation - create ticket for refactoring and started to collect ideas - Week 12/3 (plan) - continue with the work to monitor relays that are not measured: start using and external tool and/or add keyvalues that doesn't big modifications to the code - Update install and deploy documentation based on Torflow's documentation - disable connection padding in sbws' Tor - Help with: - need_review tickets: https://trac.torproject.org/projects/tor/report/72 (currently none of them change code functionality) T -- teor ----------------------------------------------------------------------

1 0