- tor-project - lists.torproject.org

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

25 Apr '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-25-17.01.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday April 25th 17:00 UTC Weekly meetings every Thursday 17:00 UTC on #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == THE Anti-censorship Roadmap (kanban board): https://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… <-- a subset of tasks from trac that the team is working on. (There is a bug in wekan, what we use for the board, that make it hard to load. You have to click in 'all boards' and then in the board to get it to load) Roadmap by topic: https://storm.torproject.org/shared/KXkqlNP8ouNks_ey5khZKUSbNj9ZoidXmEp80OD… Gettor Roadmap: https://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. ------------------------------ ---- 25th April 2019 ---- ------------------------------ == Announcements == * FTE is about to be retired: <https://bugs.torproject.org/29319> * We will have to discontinue its support in BridgeDB. * What else is affected? == Discussion == * Code that needs review: * gettor: * https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * obfuscation: * https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * The TapDance researchers are eager about the idea of making a * TapDance pluggable transport for Tor * The infrastructure is already there (deployed on routers at * Merit ISP and UColorado) * It's already been stress-tested with ~10,000 Psiphon users at * a time * The client is written in Go already and the dependencies * shouldn't cause problems * https://github.com/refraction-networking/tapdance * https://github.com/sergeyfrolov/gotapdance/ == 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-25): - Discussed GetTor roadmap with gaba and hiro. - Filed https://bugs.torproject.org/30247 to better understand GetTor usage. - Filed https://bugs.torproject.org/30264 to discuss how to proceed with default bridges. - We may want to add more default bridges. Some are saturated, other aren't. - Cohosh suggested to use potential new default bridges for experiments in: https://bugs.torproject.org/29279 - Started writing code for https://bugs.torproject.org/9316 to export BridgeDB metrics. https://gitweb.torproject.org/user/phw/bridgedb.git/log/?h=bug9316 - Mostly finished https://bugs.torproject.org/28655 - https://gitweb.torproject.org/user/phw/bridgedb.git/log/?h=bug28655 - Estimated how many bridges would be affected by this patch. - Sent BridgeDB logs to Karsten, so he can propose a metrics format. - Metrics team currently overloaded. This is on hold for a few weeks. - Tried to understand the NewNode protocol. - Helped with revising new anti-censorship proposal. Next week: - Will be on vacation all week. Cohosh will run the meeting on Thursday. Help with: - Feedback on https://lists.torproject.org/pipermail/tor-dev/2019-April/013786.html - Is the data collection method safe and sound? - I plan to approach the research safety board with this too. hiro: GetTor Status https://nc.riseup.net/s/na23xE4MJH2rsoD If review is ok, planning to deploy tomorrow. Gaba: Last week: * discussed gettor roadmap and include it in the anti-censorship * roadmap This week (04/25): * helping with new anti-censorship proposal for sponsor to work * on bridges (it will require a security audit for the code) ahf (might be missing the meeting as I'm at a BornHack meeting) Last week (2019/4/18): - Talked with cohosh about remaining tasks to finish for #29207/#29206. - Send feedback to Kat about report #2. - Mostly off due to Easter holiday here in DK. This week (2019/4/25): - Got Hiro setup with Gitlab too, she got the remaining LDAP sync to work. - Preparing for handover for cohosh of #29207/29206. - Less network team things this week it seems. kat5 (will miss the meeting Apr 25): Last week (April 15): - Reviews/notes - queries re: author list This week (April 22): - There is a GetTor roadmap! Yay! - Adding GetTor content from the rodamap dcf: 2019-04-25 Last week: - AMP cache prototyping - posted a patch for meek-client-torbrowser termination (#25613/#15125) - reported a bug about Tor Browser starting two copies of meek (#30249) - commented on disk space monitoring plans (#29863) - commented on BridgeDB statistics (#9316) - Metrics Timeline maintenance Next week: - merge uTLS for meek-client (#29077) - AMP cache prototyping - remove serene's accounts from snowflake commit/admin (#30138/#30142) Help with: - review on meek-client-torbrowser exit behavior (#25613/#15152, same branch) cecylia (cohosh): last updated 2019-04-25 Last week: - snowflake - got caught up by sukhe on windows snowflake build (#25483) - started looking into the firefox webrtc API - talked more about disk space monitoring (#29863) - started dogfooding - went to decoy routing meeting and talked with them about making a TapDance PT for Tor Next week: - snowflake - take a look at metrics team notes on #21315 - revise proxy geoip patch (#29734) - continue with windows build problem (#25483) - work on client connectivity issues (#30258) - continue snowflake dog food - review of #15125 and #25613 Help with: 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 week of 4/18 (actual): - reviewing #30091 (sponsor31 control-cmd refactor) week of 4/25 (planned): - more sponsor31 work - maybe get back into #29976 (hook up bootstrap to pubsub) and #27104 (intermediate application circuit bootstrap progress) arlolra: 2019-04-25 Next week: - snowflake webextension

1 0

Tor Browser team meeting notes, 23 April
by Georg Koppen 25 Apr '19

25 Apr '19

Hello! Due to Easter we had our weekly meeting on Tuesday this week (same time, same location, though). The IRC log can be found at http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-04-23-17.31.l… and our pad items are pasted below: Discussion: - tbb-8.5-must tickets and 8.5 release (GeKo: We plan to get the building for 8.5 started next week) GeKo: Last week: - mostly offline, trying to do some vacation This week: - backlog processing - getting back to reviews - back to work on Tor Browser 8.5 blockers starting with missing localization for mobile (#30069) - I am still missing self-feedback from some of you (not naming names) sysrqb: Last week: - Alpha release - TOPL review (#30199, #27609) - Reviewed Google Play analytics, opened tickets for reported crashes - Opened and began investigating #30239 This week: - Finish investigating and start writing patch for #30239 - Work on animation for #28329 antonela: Last week: - Tried to be offline. This week: - #25658, what is left here? Anything needed on my side? (GeKo: I think we are good here for 8.5; we should pick up the missing site-permissons in May, I think) - #28800, still in April? - https://trac.torproject.org/projects/tor/ticket/28800 (GeKo: no, that's more for May) - #27399, #29955 could we sync on it? (GeKo: yes, let's do that in the next days) - #30000, in progress - DRL review, O3 GeKo, could we sync about this objective to be in the same page? Deadline is Friday (GeKo: sure) acat: Last week(s): - 24622: Torcrazybutton can't decipher website s3.amazonaws.com - 30115: NoScript's XSS popup breaks circuit display in some cases - 30171: Always accepting third party cookies seems to break first party isolation - 26607: verify that subpixel accuracy of window scroll properties does not add fingerprinting risk - 26608: investigate <link rel="preload">) This week: - Follow up 26607 - More fingerprinting (if there is nothing with more priority) 26599: investigate CSS masks feature for fingerprinting potential 26602: investigate whether CSS clip-path adds a fingerprinting risk 26601: investigate whether SVGGeometryElement introduces a fingerprinting vector 26605: investigate window.requestIdleCallback() for possible timing leaks [Tom] Looking at bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=467035 and https://bugzilla.mozilla.org/show_bug.cgi?id=1461454 may be active fingerprinting vectors I'd suggest reviewing the status of (GeKo: I'll look into that and file at least tickets if needed) mcs and brade: Past two weeks: - #29768 (Introduce new features to users in Tor Browser). - #30104 (browser onboarding: 8.5 security level image includes English text). - Posted patch for #29045 (ask tor to leave dormant mode). - #30000 (Integrating client-side authorization to onion services v3). - set up and experimented with v2 and v3 onion services that have client authorization enabled. - Helped with triage of incoming tickets. - Code reviews. - Completed our self-evaluations for the Tor employee/team feedback process. - Took some time off for Easter. This week: - #30000 (Integrating client-side authorization to onion services v3) - Finalize travel plans for the Stockholm meeting. tjr - Sent mail about letterboxing - Next step: I'd like to get a Yay or Nay on the proposed solution. (It's very similar to the current rounding of 200x100) (GeKo: I look closer at it this week) Can people test in Nightly using the pref string, or should I bake the logic in there so people only have to toggle the pref on? - Then try to backport to 60 for TB Alpha testing? boklm: Past two weeks: - helped build 8.5a11, published it and followed comments on the blog - did some cleanup on dist.tpo (#30204) - some reviews - updated patch for #29981 (Add option to build without using containers) - made patch for #30089 (Use apksigner instead of jarsigner) This week: - Finish fixing #27137 and disable all currently failing tests - Make some patch for #26907 (Guard against failures during MAR file generation) - Travel plans for the Stockholm meeting pili: Last week: - vacation This week: - Submitted google season of Docs application - ideas reviews still welcome: https://trac.torproject.org/projects/tor/wiki/doc/GoogleSeasonOfDocs2019 - S27 roadmapping - Need to think about how to deal with orbot tickets (GeKo: I think we should call a meeting with n8fr8 and nail things down, finally) pospeselr: Last weeks: - #27503 investigation (widl is at least partially to blame here) - filed several bugs with wine devs with min repros demonstrating invalid tlb generation - submitted a patch for one of the issues - misc nextcloud admin'y things - reviewed the 'Decks' app This week: - working on widl patches sisbell: Last week: - #30162: Tor bootstrap process stuck. Investigated. Confirmed this is due to previous tor process running. Opened some issues in TOPL regarding fixes - #30272: Opened this issue - startup doesn’t handle loss of connection like airplane mode -#30166: Custom bridge - fixed issue - TOPL Pull request approved and merged into their master. This Week: - Fixes for #30162 - there are a few issues surrounding this to improved startup - #30168 : Cleanup tor-browser-build for TOPL fixes. Specifically fix Orbot issue #199 - Move resources from orbotservice to main app - Do self-review Georg

1 0

Tor Browser Release meeting: Today Wednesday 24th April @ 1800UTC
by Pili Guerra 24 Apr '19

24 Apr '19

Hi everyone, This is your reminder for our Tor Browser release meeting today at 1800UTC on #tor-meeting. This week we’ll be discussing the final details for the 8.5 stable release. Please join us! 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

For-profits using Tor
by Sarah Stevenson 23 Apr '19

23 Apr '19

Hello! I’m seeking some assistance in building a list of all for-profit companies that utilize Tor. Please take a look at this pad and add any you may be aware of and add your name if you have a contact at that company. https://pad.riseup.net/p/o87cPxlVMnQVog-Jz2Oh <https://pad.riseup.net/p/o87cPxlVMnQVog-Jz2Oh> Thanks in advance! 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 0

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