tor-project April 2019

tor-project@lists.torproject.org

15 participants
30 discussions

Notes from April 18 2019 Vegas team meeting
by Karsten Loesing 20 Apr '19

20 Apr '19

Notes for Apr 18 2019 meeting: Nick: 1) afk on a short break; back on Tuesday. Roger: 1) new plan for tor-security schleuder list? [delayed until nickm and geko are around] 2) sysadmin team, what is the 'chain of command' from vegas team to them? or maybe rather, who should be representing them here? similar question for anti-censorship team. Suggested plan is that Gaba will talk to phw, and Isa will talk to Anarcat, to help them know how they can raise issues as needed. 3) sue: did the pets invoice get paid? (yes) 4) sarah: moritz was having a heck of a time finding https://donate.torproject.org/cryptocurrency from https://donate.torproject.org/. We might want to streamline that path. [Yes, thanks for pointing that out. We are working on a better path. - Sarah] Sarah: 1) Grants team is responding to questions from DRL about approved anti-censorship project. 2) Evaluations. 3) Working on plan for inviting past donors to become monthly donors. 4) Finishing up first Sponsors Newsletter and will create a version for major donors. 5) Strategizing grant proposals for the next few months. 6) Working with Giant Rabbit on several projects to improve the donate pages. 7) Working with PayPal about suspected blocking of exit relay IP addresses. Arturo: 1) Lots of progress and work on OONI Explorer: https://github.com/ooni/explorer/projects/3 2) Almost done with setting up a system to share OONI pipeline metadb with third parties: https://github.com/ooni/sysadmin/issues/272 3) The OONI monthly report is out, check it: https://lists.torproject.org/pipermail/tor-project/2019-April/002298.html 4) Next week Maria is going to be in Nigeria presenting OONI at the Digital Rights and Inclusion Forum (DRIF): https://drif.paradigmhq.org/ Gaba: 1) grants team - strategy planning and DRL questions. 2) feedbacks 3) ooni monthly meeting 4) capacity planning and time allocation 5) google season of docs follow up while pili is on leave 6) anti-censorship: talking with kat what to do for reports (if it makes sense 3rd report or expand the 2nd) 7) sponsor 27 (onion services) planning 8) follow up on tor scalability 9) working on nextcloud to test it Steph: 1) Coordinating NYC fundraiser 2) def con arrangements 3) Have agreed to be a spokesperson available for the Internet Health Report launching next week 4) Campaigning for Ola 5) Working on internal doc and website page around dark web myths 6) meeting with Brooklyn Public Library on Monday Karsten: 1) Discussed possible visualizations of worst-case performance (#29772). 2) Worked on getting bandwidth files into Tor Metrics (#21378). Sue: 1) General accounting processes Alison: 1) 100% focused on LFI, which starts next month isabela: 1) writing self-feedback 2) organizing a batch of invites for people (at least 8 cuz we got 8 nos) on waiting list to be invited to the dev meeting 3) following developments of Ola's case and supporting whenever Tor can support 4) working on grants for general ops, reviewing letter to sponsors, helping with planing the next batch of proposals opportunities Mike: 1) Triaging/wrapping up Sponsor2 things for 041 2) Working on tor-scalability experiment list + needed metrics for April 26th meeting Erin: 1) last phase of screening for OONI dev 2) self-feedback is due tomorrow (Friday, 19-April) 3) general HR stuff

1 0

Anti-censorship meeting notes, 18 April 2019
by Philipp Winter 18 Apr '19

18 Apr '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-18-20.01.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday April 18th 20:00 UTC Weekly meetings every Thursday 20: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. Roadmap by topic: https://storm.torproject.org/shared/KXkqlNP8ouNks_ey5khZKUSbNj9ZoidXmEp80OD… Gettor Roadmap: https://storm.torproject.org/shared/rhsSl_3Pb253HPqoCdFiAdmXQ57NUG_BLvBCxqF… 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. ------------------------------ ---- 18th April 2019 ---- ------------------------------ == Announcements == * We now have a team wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * We now have a mailing list: https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-team * We now have a sysmon deployment that monitors anti-censorship infrastructure * Thanks to gman999! * Monitors BridgeDB, snowflake machines, GetTor, default Tor Browser bridges. * cohosh and phw are getting alerts over email. * Anyting else that you want monitored? == Discussion == * What GetTor-related material should we include in Sponsor 19 & in anti-censorship team roadmap? * hiro wants to be the new mantainer of GetTor. * Do we have a backup maintainer? * For the roadmap, the update from hiro has a list ( https://nc.riseup.net/s/na23xE4MJH2rsoD ) of what could be included: * automation * monitoring * deploy new code * Report Writing * report 1: status of anti-censorship at Tor * report 2: plans for anti-censorship at Tor <-- final report * anything else? * Let's start the meeting sooner to make it easier for non-NA participants? * moving it to 1700 UTC * Retire default bridges that went offline? * Metrics team want us to be careful (while we still do not have a guide but soon we will) on data collection. Let's check with them once there is a review #21315 * dcf: purging unsanitized Snowflake logs - see https://bugs.torproject.org/30125#comment:7 * #30125 will sanitize the snowflake logs. I'd like us to commit to a deadline for doing something with the old pre-sanitization logs, or else deleting them. * What specific statistics or visualizations do you want from the old logs? We can make sure to retain the information to make those possible, before deleting the originals. * Lets review roadmap briefly. Is there anything that you are working on that is not in the in-progress column? https://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Code reviews assignment? == Actions == == 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. phw: This week (2019-04-18): - Created team wiki page and had mailing list created -> sign up! - Lots of work on #28655. Looks good! Need better unit tests. - Worked with gman999 on infrastructure monitoring. Also looking good! - Had a chat with dgoulet and sysrqb about BridgeDB specifics. - Chat with hellais about updated version of "vanilla tor" test. Next week: Help with: - Feedback on https://trac.torproject.org/projects/tor/ticket/9316#comment:16 - Let me know if you want any machines or services monitored! - hiro: Can you help us with #30152? Yes I can help with this. Anarcat has been setting up a different prometheus instance to monitor services. This could be part of that effort. --hiro hiro: GetTor Status https://nc.riseup.net/s/na23xE4MJH2rsoD Gaba: This week (04/15): * checking on gettor ahf (gonna be missing at the meeting, but will read backlog): Last week (2019/4/4): - Meeting with gaba, cohosh, & phw Monday - Went over roadmap items in new roadmap docs. - Lots of tiny network team tasks. - Continued work on #t/#29206. This week (2019/4/11): - Mostly network-team tasks so far. Was off Wednesday. - Gitlab/LDAP access have been established. - Continue to hack on #29736 (and transition it off to cohosh too) - Gaba and I talked at our 1:1 Friday that I'll return to network team tasks only in May. kat5: Last week (April 8): - Started GetTor content - Copy editing - Conditionalized URLs - Figured out what's left This week (April 15): - Reviews/notes - queries re: author list Help with: - What else we want to report on (continuing discussion w/ gaba and phw from email) dcf: 2019-04-18 Last week: - reviewed Snowflake broker robots.txt patch (#29565) - reviewed further Snowflake log sanitization (#30125) - reviewed Snowflake broker proxy geoip patch (#29734) - helped debug a Snowflake broker outage (#30205) - AMP cache prototyping - worked on improving meek-client-torbrowser termination (#25613) Next week: - have meek-client-torbrowser signal exit by closing child process stdin (#25613) - AMP cache prototyping - comment on #29863 Help with: cecylia (cohosh): last updated 2019-04-18 Last week: (was out a bit due to flooding and then course-related things) - snowflake - merged and deployed #30125 (log sanitization) - became familiar with the rbm tor browser build system - closed #29565 (robots.txt) - dealt with #30205 (problem with log rotation during #30125 deployment) - community stuff - had a call with CGIProxy Next week: - snowflake - take a look at metrics team notes on #21315 - revise proxy geoip patch (#29734) - take a look at windows reproducible build problem (#25483) - work on client connectivity issues (#25429) - snowflake dog food Help with: - are we at an ok place to deploy what we have set up for #29863? catalyst: week of 4/11 (planned): - more sponsor31 work; maybe also #29976 as prep work for more bootstrap reporting improvements week of 4/11 (actual): - handed off #29276 (Make a release of BridgeDB) to phw - more sponsor31 work (control-fmt review #30091; control-proto stuff #30007) - travel logistics week of 4/18 (planned): - mostly sponsor31 stuff

1 0

March Communications Report
by Stephanie A. Whited 18 Apr '19

18 Apr '19

Last month, we helped with copy and promoted the launch of our new website. We celebrated International Women's Day and campaigned for donations related to diversity. We worked with the fundraising team on our welcome letter for new subscribers and our new cryptocurrency page. Steph, Alison, Isa, Nick, and Nathan spoke at LibrePlanet and ran a booth. We were accepted to be a vendor at DEF CON. Steph, Roger, Jon, and Sarah will be attending and running the booth. Steph was interviewed by Mozilla for the Internet Health Report launching next week. We published blog comment policies for moderators and commenters. March in links and stats: Blog posts https://blog.torproject.org/making-diversity-default-open-source-world https://blog.torproject.org/meet-new-torprojectorg https://blog.torproject.org/international-womens-day Twitter https://twitter.com/torproject New followers: 3,768 Top tweets https://twitter.com/torproject/status/1109130202393780225 https://twitter.com/torproject/status/1101491241429204992 https://twitter.com/torproject/status/1110207226810114052 Mastodon https://mastodon.social/@torproject New followers: 200 Instagram https://instagram.com/torproject New followers: 286 LinkedIn https://www.linkedin.com/company/tor-project/ New followers: 84 Facebook https://www.facebookcorewwwi.onion/TorProject/ New followers: 607 Newsletter https://newsletter.torproject.org/archive/2019-03-29-meet-new-tor-project/ Notable press https://www.fastcompany.com/90321235/i-protected-my-privacy-by-ditching-chr… https://www.coindesk.com/tor-project-takes-cryptos-after-donors-request-new… https://www.fastcompany.com/90316917/the-paranoid-persons-guide-to-online-p… o/ -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Key ID: 39A876AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

OONI Monthly Report: March 2019
by Maria Xynou 18 Apr '19

18 Apr '19

Hello, The OONI team made steady progress in March 2019. ## OONI Explorer Over the last year, we have been working on revamping OONI Explorer entirely. This has involved re-writing all of the OONI Explorer codebase in react.js (using next.js), re-designing the platform entirely to improve its UX, creating a more powerful search tool (which required a series of improvements to the OONI data processing pipeline), and adding a number of new features (based on community requests). During March 2019, we: * Worked on the new country profile pages * Worked on the the landing page and highlights page * Created the initial design of the mobile version for all major pages We expect to launch the revamped OONI Explorer in May 2019. ## System for sharing OONI metadb with third parties We have been working on setting up a system for sharing OONI's metadata database with third parties. This will allow external people to setup their own instance of the OONI measurement database that powers OONI API and OONI Explorer. The progress of our work on this can be tracked via the following ticket: https://github.com/ooni/sysadmin/issues/272 ## ndt7 OONI's Simone has been working on an improved performance test called ndt7, which is meant to replace the NDT test currently available in the OONI Probe mobile app. This development activity started during his OTF fellowship at Measurement Lab and he has continued to work on it since. During March 2019, he worked on the Golang server and on the Golang and JavaScript clients. By the end of the month, the code quality and readiness was near a first alpha version. See https://github.com/m-lab/ndt-server and https://github.com/m-lab/ndt7-client-golang/pull/3. ## OONI pipeline We worked on improving the testing and documentation of the OONI pipeline: * https://github.com/ooni/pipeline/pull/145 * https://github.com/ooni/pipeline/pull/144 * https://github.com/ooni/pipeline/pull/147 * https://github.com/ooni/pipeline/pull/149 ## OONI Probe mobile apps We worked on adding support for uploading non-uploaded measurements in OONI Probe Android and iOS: * https://github.com/ooni/probe-ios/pull/258 * https://github.com/ooni/probe-android/pull/214 We finalized the implementation of unit tests for OONI Probe Android and iOS: * https://github.com/ooni/probe-ios/pull/246 * https://github.com/ooni/probe-android/pull/195 We released OONI Probe 2.0.6 iOS with an OONI Run fix: https://github.com/ooni/probe-ios/pull/261 ## Backend Engineer interviews We interviewed a number of backend engineers who applied for the OONI job opening (https://www.torproject.org/about/jobs/). We are now finalizing the interview rounds and hope to hire an engineer by mid-May 2019. ## Community activities ### Vietnam Cyber Dialogue (VCD) OONI's Maria & Arturo participated at the Vietnam Cyber Dialogue (VCD) in Valencia, Spain, on 31st March 2019. As part of their participation, they facilitated a session on censorship measurement. Information about the event is available here: https://internetfreedomfestival.org/vietnam-cyber-dialogue/ ### Localization Lab Summit OONI's Elio participated at the Localization Lab Summit in Valencia, Spain, on 31st March 2019. As part of his participation at the Summit, he met with translators and facilitated sessions about how UX and localization can play better together in order to have better internalization support. Information about the event is available here: https://www.localizationlab.org/blog/2019/2/22/join-the-localization-lab-su… ### Community meeting On 26th March 2019, we hosted an OONI community meeting on our Slack channel (https://slack.openobservatory.org/). As part of the meeting, we shared updates on OONI sessions facilitated at the Internet Freedom Festival (IFF) and information about the OONI job opening for a backend engineer position (https://www.torproject.org/about/jobs/). ## Userbase In March 2019, OONI Probe was run 700,880 times from 5,115 different vantage points in 211 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

March Fundraising Report
by Sarah Stevenson 17 Apr '19

17 Apr '19

Hello from the Fundraising Team! Below you will find our March report. ## Cryptocurrency As mentioned last month, we launched our new cryptocurrency page[1]. This took a lot of work to understand and set up wallets and a mechanism to exchange coins to USD. We also had to create a workflow for acknowledging and recording donations in our CRM. So far, we have raised close to $18,000 by connecting with cryptocurrency enthusiasts on Twitter and have a few prospects for major gifts in the coming months. We also received some blog mentions[2][3][4][5][6] that have helped drive donations. We have received many suggestions for revisions and additions that we will tackle soon. ## Welcome email We created a welcome email[7] that gets sent to people who have just joined our email list. The intention is to set the tone for our relationship with the person, teach them a bit about what we do, and talk about how we are a nonprofit that depends on contributions from individuals. The communication about being a nonprofit organization came from the research done by The Berkeley Group who found most people they surveyed were unaware of that status. This message has gone out to over 22,500 new subscribers so far and has been well-received. ## Grants Al and the grants team wrote and submitted proposals to the following funders for the following projects: Indela Fund for LFI, craigslist Charitable Foundation for general operating funds, and the British Embassy of San Jose for digital security trainings in Costa Rica. We also submitted a letter of intent to the Charles Koch Foundation and two SOIs to DRL - one for OONI and another for UX/Community work. We also had a meeting with our program officer from the Media Democracy Fund. ## Administrative We worked with Isa and Sue to create fundraising projections for the remainder of this fiscal year and the next. This will allow us to better track our progress and create project budgets. Sarah attended the Data Privacy Summit in DC, hosted by Access Now, which was primarily about policy, but we have a few new contacts for potential collaboration. - Fundraising Team [1] https://donate.torproject.org/cryptocurrency <https://donate.torproject.org/cryptocurrency> [2] https://www.coindesk.com/tor-project-takes-cryptos-after-donors-request-new… <https://www.coindesk.com/tor-project-takes-cryptos-after-donors-request-new…> [3] https://dashnews.org/tor-accepts-dash-donations-advancing-privacy-initiativ… <https://dashnews.org/tor-accepts-dash-donations-advancing-privacy-initiativ…> [4] https://lumenthropy.com/tor-project/ <https://lumenthropy.com/tor-project/> [5] https://cointelegraph.com/news/tor-digital-privacy-project-accepts-donation… <https://cointelegraph.com/news/tor-digital-privacy-project-accepts-donation…> [6] https://z.cash/blog/zcash-empowers-charitable-giving/ <https://z.cash/blog/zcash-empowers-charitable-giving/> [7] https://crm.torproject.org/civicrm/mailing/view?id=165 <https://crm.torproject.org/civicrm/mailing/view?id=165>

1 0

Network team meeting notes, 15 April
by Nick Mathewson 15 Apr '19

15 Apr '19

Hi! You can find our meeting log at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-15-16.59.html Here are our notes from the meeting: = Network team meeting pad! = This week's team meeting is at Monday 15 April at 1700 UTC on #tor-meeting on OFTC. 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. April schedule: * Tuesday 2 April at 2300 UTC * Monday 8 April at 1700 UTC * Monday 15 April at 1700 UTC * Tuesday 23 April at 2300 UTC (Monday 22 April is the Easter Monday public holiday, teor is on leave for the first meeting in May) * (teor goes on leave) * Monday 29 April at 1700 UTC May schedule: * Monday 6 May at 1700 UTC (teor will not be in this meeting) (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.) 18 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002263.html 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 == 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.0 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… <-- 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 needs-review tickets, by reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&reviewer… 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. ------------------------------- ---- 15th April 2019 ------------------------------- == Announcements == - The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0. We need to prioritize 0.4.0 fixes and reviews in April, because stable is due on 15 April. == Discussion == Change the meeting time of Tuesday 23 April to 2300 UTC so we can include Teor (they are going on leave after that). YES Change the meeting of Tuesday 7 May at 2300 UTC to Monday 6 May at 1700 UTC because that week Teor will be on leave (no reason to move meeting). YES (not much to discuss) What to sponsor for 2020? We could have some inital thoughts on priorities (not necessary if you don't have time right now, there will be other opportunities when the grant oportunities come up). This pad summarize discussion in several places for the network team: https://pad.riseup.net/p/Pp3o8e9U6jH5DauxjxK8 (not much to discuss) Google season of docs - we are aplying to improve technical documentation. We need mentor/s from the team. Their tasks will be: help select technical writers be available for consults that the technical writes may have about documentation More info at https://developers.google.com/season-of-docs/docs/admin-mentor-responsibili…. They will need to be register in the website (google acount) and Pili is coordinating (to submit by April 23rd). PLEASE send a msg to Pili (cc me) if you want to be a mentor. (not much to discuss) Roadmap update. Nick and Gaba are going to go through the roadmap and check if anything needs to be updated/changed/re-prioritized. It will be in an open session in case other people in the team want to be involved. Tuesday 23rd of April at 1700 UTC (if we are moving the weekly meeting to later) on jitsi. Send gaba a msg if you want to attend. Can people add themselves as owner of the ticket when they start working on it? for example, is somebody working on #29223 (nickm?) [done -nickm], #29210 (nickm?) ? [shared between nickm and catalyst -nickm] thanks teor says: I can't do bug triage on 29 April, because I'll be away. Rotation updates (from nickm): Bug triage Started with 4 no-component items, some 3 months old. Started with 55 no-milestone "core tor/tor" items, some 3-7 months old. Many but not all from Brussels. Some but not many marked 04x-proposed. Had over 100 new incoming emails with bugtracker events to look at. Tried to assign tags as appropriate; worried that I missed some. Worried that if I missed some, there's no way to see what the backlog is for assigning tags. I don't know how to assign milestones to SBWS tickets. Current Status: 0 no-component, 0 no-milestone. CI Mysterious i386/xenial failures -- not sure how to procede. (If it's still happening.) Resolved #29922, delegated #29645. Told weasel about a disk-exhaustion condition on jenkins; he resolved it. Current status: travis and appveyor are passing. Current Tor jenkins failures are tor-ci-linux-0.3.5-extra-arm (stretch, armhf) -- Java exception, seems like a Jenkins issue. tor-ci-freebsd-amd64-0.2.9/ -- longstanding failure, two unit tests failing. (test_bt and fgets_eagain) Coverity Started the week with 44 pending coverity issues. Opened 30146 to work on the most important-looking. Some children in needs_review. Will work on more once the current children of 30146 are solved. Current status: 42 pending coverity issues; 30146 should solve many, I hope. == Recommended links == "The way you address the problem is by shipping changes not more slowly, but more QUICKLY. Fewer, smaller changesets turn into debuggable, understandable deploys." (The whole thread is a good read.) https://twitter.com/mipsytipsy/status/1117902725620977664?s=21 == 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 (a little distracted but here): Last Week of 03/08 (actual): - capacity for s27 and timeline on the project - it will happen when dgoulet is back - move s27 tickets into roadmap - it will happen after discussion on timeline - grant strategy with grants team includes priorities for funding for network team - it will happen this week - opened tor-scalability mailing list https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-scaling - updated tor on trac wiki page - compiled https://storm.torproject.org/shared/G3CvVVTiJuA5CRTeuQSmm8zRaPTjagnVMhMosmp… This Week (planned): - grant strategy meeting - self-feedback - test new nextcould instance Help with: finding a mentor for technical writer google season of docs voting for priorities for 2020 in https://pad.riseup.net/p/Pp3o8e9U6jH5DauxjxK8 read torontrac wiki page. I added a few things like points and owner to that list. https://trac.torproject.org/projects/tor/wiki/org/process/TorOnTrac teor: (offline except for the first meeting each month) Week of 8 Apr (planned): Notes: - I won't be doing reviews or merges until Wednesday or Thursday, so I can get some roadmap coding done. +1 High-Priority: - Do mainline merges and backport merges Roadmap: - CI with Chutney/Tor: #29729 and children - Other roadmap reviews Other: - Assigned reviews Week of 8 Apr (actual): Notes: - I made it through Monday and Tuesday, then CI started failing regularly. High-Priority: - Do mainline merges and backport merges - Diagnose test-stem failures in CI #29437 and children Roadmap: - CI with Chutney/Tor: #29729 and children Other: Week of 15 Apr (planned): Notes: - I won't be doing reviews or merges until Wednesday or Thursday, so I can get some roadmap coding done. High-Priority: - Diagnose test-stem failures in CI #29437 and children - Post 0.4.0.4-rc backport merges - Any mainline merges - Self-Feedback and maybe Team Lead Feedback Roadmap: - CI with Chutney/Tor: #29729 and children - Other roadmap reviews Other: - Assigned reviews Help with: - I'm going on leave in 2 weeks time, so I'm going to focus on work that I can't give away to other people. - Once #30122 merges into Stem, can someone help diagnose #29437? [I'd love to try, if I can reproduce it -nm] Nick: Week of 8 April (planned): - PETS discussion - Finish control.c command-parsing refactoring - Finalize draft abbrevs list. - More review and merge - 040 release - Write a couple of users for publish/subscribe logic. - CI failure tickets: #29645 test.exe hangs on Appveyor CI #29922 util/time test failure on Jenkins - I would like to to take time off between 17 and 19 April. 22 April (monday) is a state holiday for me. Is that okay with everybody? +1000 Week of 8 April (actual): - PETS discussion - Finished refactoring control command-line parsing; see 30091. (I'm excited to do more here once it's merged and catalyst's 30007 is in.) - Finished draft list of abbreviations for S31. Where do we go from there? (See 29223.) - Review and merge, more. - Fixed 29922 to get CI happy again. - Reviewed hackerone tickets - released 0.4.0.4-rc - CI & Coverity rotation. See discussion above. - Bug triage. See discussion above. Week of 15 April (planned): - Short vacation: Today is a state holiday for me; I'll be taking off next Monday instead since that better aligns with other people's holidays. - Short vacation: I'm also taking off from Wednesday through Friday. I'll see personally addressed email and Signal; all lists will go into my "after-vacation" folder. - Review & merge, especially 26288 (authenticated sendme) and 29209 (cpath encapsulation) - Time permitting, either add a pubsub user, or work on an ADL thing. - I want to prioritize working on stuff that would block others. Please let me know where you are blocking on me. dgoulet (missing meeting): - AFK. Mike: Week of 4/8 (planned) - Scalability planning & discussion - Plan lots of travel - Vanguards release - Finalize plan for keeping circuits open (#28780) - #29034 patch - Catch up on code reviews Week of 4/8 (actual): - Started working on performance+scalability experiments wiki page - Tax stuff - Organized neccessary wtf-pad items for working padding machine into child tickets of #28634 - Fixes for some child tickets of #28634 (#30092, #28780) - Fix for #29034 (HS relability bug found during padding work) - Tagged a vanguards release (0.3.1) Week of 4/15 (planned): - Work on child tickets of #28634 - Help asn with/review #28634 machine definitions - Vanguards blog post (pending debian packages) - Book travel catalyst: week of 04/08 (2019-W15) (planned): - reviews - finish up control.c protocol splitting (#30007) - get bootpubsub ready to review (#29976) week of 04/08 (2019-W15) (actual): - reviews - travel logistics - preliminary review on control.c command parsing refactor - cleaning up #30007 (control.c protocol splitting) -- rebased on new control-cmd branch; fought with Coccinelle some more week of 04/15 (2019-W16) (planned): - reviews - travel logistics - get #30007 into a reviewable shape - coordinate with nickm on control.c stuff as needed asn: Week of 04/08 (planned): - Will focus on the #29209 s31 deliverable this week. I hope to have it done by the end of the week, so that I can focus on s27 for the rest of the month. Week of 04/08 (actual): - Pushed #29209 to needs_review. It's basically a limited version of the actual deliverable, where we hide a part of crypt_path_t. Left general thoughts about the task in the ticket. - Worked more on #28634 after Mike's review. Needs some more work before being back in needs_review. - Reviewed #28780 as part of Sponsor2. - Did more triaging and discussion on Sponsor27 - Fixed some bugs we got from hackerone. - Did reviews/merges. Week of 04/15 (planned): - Push #28634 back to needs_review. - Start doing initial Sponsor27 work, and brief up David. - Review/test more leftover WTF-PAD stuff. - Finish up travel arrangements for Stockholm/AllHands ahf: Week of 4/8 (planned) Anti-censorship team: - Continue with #29736. Network team: - Solve 040-must #29930 (figure out why the file is still open). Misc: - Figure out PETS logistics. - I will probably be away some of Wednesday. Week of 4/8 (actually) Network team: - Trying to figure out #29930, but cannot figure out yet why we get the permission denied here. The file does not seem open when I use a debugger. - Been trying to reproduce #29645 locally with the PowerShell scripts that AppVeyor is running. Anti-censorship team: - WebSocket integration in go-proxy code for #29736. Misc: - Was off Wednesday - Roger solved the PETS questions I had via email. Week of 4/15 (planned) Anti-censorship team: - Talk with cohosh about #29207/#29206 - Re-read Kat's report #2 and give some feedback. Network team: - Continue with #29930, #29645, and #30187 Misc: - Easter in Denmark coming up: will likely be less online Thursday and Friday this week.

1 0

Notes from April 11 2019 Vegas team meeting
by Karsten Loesing 12 Apr '19

12 Apr '19

Notes for Apr 11 2019 meeting: Roger: 0) I had a good meeting with phw last week, to get him going on the new anti-censorship team. 1) Need some Apple contacts? For making webkit adhere to Tor Browser guidelines, or for helping get rid of the fake Tor Browsers on the app store? [I think we do, at least if we have them we should give to guardian project and mike tigas -isabela] 2) I keep encountering threat intelligence CTOs who admit that their company's marketing team is misleading people about "the dark web" and how it relates to Tor. It seems to me that we should be able to align the incentives from the marketing teams better: all it takes would be one of them realizing that they can differentiate themselves by pointing out that "all the *other* ones are misleading you". Next possible steps include doing a joint blog post with one company that wants to, and/or doing a talk to an NYC-based threat intelligence company. 3) May 1 is the deadline for mainline Defcon talks. I am pondering submitting one -- a retrospective of some sort maybe. A brainstorming session seems smart. Gaba: 1) follow up on sponsor 13 reporting. 2) worked over a summary from ideas for funding for grants strategy meeting. 3) looked at capacity for network team for the year. 4) follow up on tor-scalability (will open mailing list today) 5) started weekly syncs with phw Georg: 1) Work on Tor Browser 8.5 2) Helping OTF with proposal review and recommendations 3) Dealing with HackerOne bug bounties and additional HackerOne help with out bug bounty program Nick: 1) team continues to be somewhat strained for resources, but great work is still getting done. 2) I'll be off from next wednesday through the following monday (17th through 22nd), though I could be available for meetings if really needed and we schedule in advance. Pili: 1) Sponsor 27 organisation 2) Google Season of Docs - started filling out application form - working on fleshing out projects - blog post - recruiting mentors 3) New Website Launch Retrospective 4) Working on funding ideas for teams Alison: 1) Refining LFI curriculum 2) Making the public announcement about the new cohort soon 3) Still redesigning the website 4) Writing a piece on facial recognition for ALA Choose Privacy Week 5) Gus is traveling; we will go to Mexico together in May Steph: 1) Helped with irl’s and juga’s blog posts 2) Responded to inquiry about CIPA 3) Will be presenting at a cryptocurrency gathering (post Ethereal Summit) doubling as a Tor fundraiser in NYC may 15. Gman will join me. 4) def con prep 5) Talking with a librarian at the Brooklyn Public Library about possibly running a workshop or talk isabela: 1) I have been sick this week so I am behind on some things. 2) Catch up to do list, emails and meetings. 3) Plan on start inviting people on 'waiting list' of dev meeting invite list. 4) Plan to meet w/ Alison to kick off the process to organize the schedule for the dev meeting. 5) Work on Sida phase3 plan and review proposal for general ops fund Sarah: 1) More admin to finish up state registrations. 2) Sending out new welcome email to new email list subscribers. We are now up to 45,424 people on the main email list. 3) Al submitted proposals for general operating funds from the CS Fund and funds for ESR migration from Open Source Center. 4) Researching Handshake details 5) Postal letter to lapsed major donors and small foundations went out last week. Sue: 1) General Accounting processes Erin: 1) General HR stuff Karsten: 1) Decide how to proceed with TorDNSEL replacement: a) our hope to upgrade the Haskell code from 7.6 to 8.0 did not work out; b) the rewrite is at least a few weeks away if we want it to work properly; c) the metrics team might take ownership of the oldstable VM from the admins, but running machines is not what we're good at; d) we could let it die and put up the replacement once we have it, even though that will make at lot of people sad; e) we get an extension for the shutdown as long as we make progress (Brexit style); f) do a quick-and-dirty thing (maybe exitmap + stem + some duct tape, possibly leaving out the DNS server at the beginning) that keeps working until we have the proper rewrite in place. Antonela: 1) Coordinating user research in Colombia with Nah and Gus 2) Reviewing Caroline's report for Q1 user research 3) Preparing outreach material in Spanish to print for Colombia 4) website tickets triage, working on /download 5) S27 meeting, starting with O2A1 6) Following up with IFF people 7) Working on TB8.5 release 8) Working on OONI Explorer ux issues with Arturo 9) Reviewing community.torproject.org 10) Reviewed research.torproject.org with irl Mike: 1) Trying to organize next tor-scalability meeting 2) network team development 3) @steph: vanguards should be in the next debian/stable and debian backports; I would like to do a blogpost and tweet when that happens. Not sure if it will happen this week or next yet. [great, lmk when you've got a draft -steph]

1 0

Anti-censorship meeting notes, 11 April 2019
by Philipp Winter 12 Apr '19

12 Apr '19

Here are our meetings logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-11-20.00.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday April 11th 20:00 UTC Weekly meetings every Thursday 20: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. Roadmap by topic: https://storm.torproject.org/shared/KXkqlNP8ouNks_ey5khZKUSbNj9ZoidXmEp80OD… Gettor Roadmap: https://storm.torproject.org/shared/rhsSl_3Pb253HPqoCdFiAdmXQ57NUG_BLvBCxqF… 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. ------------------------------ ---- 11th April 2019 ---- ------------------------------ == Announcements == * A reminder to change owner of ticket to yourself in trac if you are working on that ticket. == Discussion == * What GetTor-related material should we include in Sponsor 19 & in anti-censorship team roadmap? <-- move this discussion for next week. * hiro wants to be the new mantainer of GetTor. Do we have a backup maintainer? * Do we want a (public) anti-censorship team mailing list? We can use it for: * Coordinating team meetings * Making it easy for people to contact the team (e.g., in case of censorship events) * Hopefully, a public mailing list does not discourage anyone * Publishing our monthly team reports * Bringing up and discussing related anti-censorship efforts (e.g., v2ray tool) * Pointing out when something in our docs or processes is broken * How can/should this overlap with the traffic-obf Google mailing list? * How are we going to manage code reviews? So far asn helped. * reviews will be assigned in this weekly meeting. * On Monitoring infrastructure <-- let's bring this conversation to next week. * Let's add https://trac.torproject.org/projects/tor/ticket/30121 to our roadmap backlog? Anything else to add/edit to the roadmap? * Plan for project maintainership * We should strive for two maintainers per project * dcf: should we remove serene's snowflake.git commit access? Not used since March 2017. https://bugs.torproject.org/30044#comment:2 shows the users with commit access. Cf. #30138 regarding an admin account. == Actions == == 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. phw: This week (2019-04-11): - Got my own bridgedb and bridgedb-admin repos. Started reading code and re-assigning tickets to me. - Inquired about status of ICLab and if the project could help us scan our bridges. - Wrote a small script that helped us analyze the throughput of a download over time. - Figured out who runs our default bridges and contacted operators of broken bridges. + See https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/DefaultBridges + Filed #30121 to improve how we manage list of default bridges. + Some progress in #30006, which is about monitoring our default bridges. - Started working on a fix for #26154. Breaks many unit tests -- more thinking required. Next week: Help with: - #28655 review (If a bridge supports obfs4, don't give out its other flavors) - Need to talk to sysrqb and/or dgoulet to learn more about BridgeDB deployment. Gaba: This week (04/11): ahf (gonna be missing at the meeting, but will read backlog): Last week (2019/4/4): - Meeting with gaba, cohosh, & phw Monday - Went over roadmap items in new roadmap docs. - Lots of tiny network team tasks. - Continued work on #t/#29206. This week (2019/4/11): - Mostly network-team tasks so far. Was off Wednesday. - Gitlab/LDAP access have been established. - Continue to hack on #29736 (and transition it off to cohosh too) - Gaba and I talked at our 1:1 Friday that I'll return to network team tasks only in May. kat5: Last week (April 8): - Brought phw up to speed about reports - Figured out where various content came from - Thought about what to remove and what to keep - A little more Snowflake and BridgeDB content This week (April 11): - Started GetTor content - Copy editing - Conditionalized URLs - Figure out what's left Help with: (I will sort these questions out over email.) - Need ahf to review (at least certain sections of) the report. - I think I should include arma and dcf1 in the author list because I took text from tickets they wrote and I think I should include catalyst because they gave me text that I used, but I don't want to do that without consent. - ON HOLD -> need direction - private bridge guide for NGOs (hold off until we figure out a strategy for making set-up easy) not sure where this is nor what should heppen next dcf: 2019-04-11 Last week: - reviewed proxy-go deadlock patch in #25688 - participated in discussion about Snowflake monitoring in #29863 - merged goptlib LOG branch (#28940) - made accounts for phw on bridge and broker (#29985) - filed a ticket to remove serene from Snowflake bridge admin (#30138) Next week: - have meek-client-torbrowser signal exit by closing child process stdin (#25613) - review proxy geoip patch (#29734) - review on further log sanitization (#30125) and recommendations for deployment - prototyping with AMP cache Help with: cecylia (cohosh): last updated 2019-04-11 Last week: - investigated obfs4 blocking (#29279) - Looked at data from VPS in China and NA probe site - modified phw's tcpdump scripts and published results - snowflake - merged and deployed #21304 and #25688 - more discussion about #29863 - closed #21305 and started looking at #25429 instead - revised #29734 for geoip data on proxies - implemented #30125 - community stuff - discussed with phw my thoughts on the PT integration pipeline Next week: - investigate obfs4 blocking (#29279) - keep checking current tests - expand tests for bridge enumeration problem? - snowflake - make some progress on websocket protocol - take a look at windows reproducible build problem (#25483) - work on client connectivity issues (#25429) Help with: - review of #30125 - ahf: are you still working on snowflake? i'd like to move forward with #29736 (and #29207), since it's blocking work on #29260 and #21315 - phw: I think it would be cool to expand the study for #29279 (see https://trac.torproject.org/projects/tor/ticket/29279#comment:16 ). I'm happy to do the leg work with designing and running the study, though you're probably in the best position to handle (2) at the moment. It's probably worth our time at this point to design it carefully. Also, do we want to have actual people doing probes instead of just our VPS probe site? catalyst: week of 4/4 (planned): - focus on sponsor31 stuff (like control.c refactor) that might be blocking nickm; please let me know if i should reprioritize - work on #29276 (bridgedb release) if there's time week of 4/4 (actual): - mostly sponsor31 stuff like control.c refactor week of 4/11 (planned): - more sponsor31 work; maybe also #29976 as prep work for more bootstrap reporting improvements

1 0

march 2019 report for the sysadmin team
by Antoine Beaupré 11 Apr '19

11 Apr '19

Hello, Here are the minute from our last meeting, which we have just decided might double as a report for the larger project as well. I hope that's still useful! Agenda: * What has everyone been up to * What we're up to in April * Other discussions * Next meeting What has everyone been up to ============================ anarcat ------- 1. lots of onboarding work, mostly complete 2. learned a lot of stuff 3. prometheus research and deployment as munin replacement, mostly complete 4. started work on puppet code cleanup for public release lots more smaller things: 5. deployed caching on vineale to fix load issues 6. silenced lots of cron job and nagios warnings, uninstalled logwatch 7. puppet run monitoring, batch job configurations with cumin 8. moly drive replacement help 9. attended infracon 2019 meeting in barcelona (see report on ML) hiro ---- 1. website redesign and deploy 2. gettor refactoring and test 3. on vacation for about 1 week 4. IFF last week 5. many small maintenance things ln5 --- 1. nextcloud evaulation setup [wrapping up the setup] 2. gitlab vm [complete] 3. trying to move "put donated hw in use" forward [stalled] 4. onboarding [mostly done i think] weasel ------ 1. brulloi decommissionning [continued] 2. worked on getting encrypted VMs at hetzner 3. first buster install for Mandos, made a buster dist on db.tpo, cleaned up the makefile 4. ... which required rotating our CAs 5. security updates 6. everyday fixes What we're up to in April ========================= anarcat ------- 1. finishing the munin replacement with grafana, need to write some dashboards and deploy some exporters (trac #30028). not doing Nagios replacement in short term. 2. puppet code refactoring for public release (trac #29387) 3. hardware / cost inventory (trac #29816) hiro ---- 1. community.tpo launch 2. followup on tpo launch 3. replace gettor with the refactored version 4. usual small things: blog/git... ln5 --- 1. nextcloud evaluation on Riseup server 2. whatever people need help with? weasel ------ 1. buster upgrades 2. re-encrypt hetzner VMs 3. finish brulloi decommissionning, canceled for april 25th 4. mandos monitoring 5. move spreadsheets from Google to Nextcloud Other discussion topics ======================= Nextcloud status ---------------- We are using Riseup's Nextcloud as a test instance for replacing Google internally. Someone raised the question fo backups and availability: it was recognized that it's possible Riseup might be less reliable than Google, but that wasn't seen as a big limitation. The biggest concern is whether we can meaningfully backup the stuff that is hosted there, especially with regards to how we could migrate that data away in our own instance eventually. For now we'll treat this as being equivalent to Google in that we're tangled into the service and it will be hard to migrate away but the problem is limited in scope because we are testing the service only with some parts of the team for now. Weasel will migrate our Google spreadsheets to the Nextcloud for now and we'll think more about where to go next. Gitlab status ------------- Migration has been on and off, sometimes blocked on TPA giving access (sudo, LDAP) although most of those seem to be resolved. Expecting service team to issue tickets if new blockers come up. Not migrating TPA there yet, concerns about fancy reports missing from new site. Prometheus third-party monitoring --------------------------------- Two tickets about monitoring external resources with Prometheus (#29863 and #30006). Objections raised to monitoring third party stuff with the core instance so it was suggested to setup a separate instance for monitoring infrastructure outside of TPO. Concerns also expressed about extra noise on Trac about that instance, no good solution for Trac generated noise yet, there are hopes that GitLab might eventually solve that because it's easier to create Gitlab projects than Trac components. Next meeting ============ May 6, 2019, 1400UTC Meeting concluded within the planned hour. Notes for next meeting: 1. first item on agenda should be the roll call 2. think more about the possible discussion topics to bring up (prometheus one could have been planned in advance)

1 0

March 2019 report for the UX team
by Antonela Debiasi 11 Apr '19

11 Apr '19

Hello Tor, During March we launched the new torproject.org landing pages, using responsive web design to enhance the end-users experience. We included 7(seven) languages, and more locales are coming. As we shared back in Rome, this release is just one small part of the big website overhaul project. We released support.torproject.org back in February, and we will continue with community.torproject.org next month, and dev.torproject.org in the following quarter. https://www.torproject.org/ Tor Browser 8.5 is about to reach stable. We worked on both desktop and android alpha releases. Security Settings, Network Settings, Onboarding, and the new Icon are going live. https://trac.torproject.org/27484 https://trac.torproject.org/28329 https://trac.torproject.org/28622 https://trac.torproject.org/28628 https://trac.torproject.org/29768 Thanks, dunqan for working on the onboarding update for this release: https://trac.torproject.org/projects/tor/ticket/29768#comment:16 Thanks, wayward for working on the new Security Settings documentation for users: https://lektor-staging.torproject.org/tor-browser-manual/staging/security-s… Caroline is debriefing the user research we ran in India and Indonesia during Q1. We will share the key findings with the lists shortly. Elio has been working on finalizing OONI Explorer landing pages for the beta launch. You can sneak peek them here: https://www.figma.com/file/OElUj1XR5SmbXUpWVzl8iton/Explorer-Landing-Page?n… In order to have a better understanding of the project teams, pili ran a team vision exercise. You can see the outcomes and also the entire meeting log here. Thanks, pili. https://lists.torproject.org/pipermail/ux/2019-March/000444.html The Cyborgrrrls Encuentro Tecnofeminista happened in Mexico last month, and I gave a Tor 101 talk and we discussed how technology could allow us to shape our identities online. https://hysteria.mx/cyborgrrrls-encuentro-tecnofeminista-en-la-cdmx/ o/ A -- Antonela Debiasi UX Team Lead @antonela E2330A6D1EB5A0C8 https://torproject.org <https://keybase.io/antonela#show-public>

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project April 2019