- tor-project - lists.torproject.org

S30 Meeting on Tuesday 14th January 2020
by Gaba 14 Jan '20

14 Jan '20

Hi! We are meeting today for the S30 project [0]. The meeting with be at 1800 UTC in #tor-meeting, irc.oftc.net cheers, gaba [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 1

Tor Browser Release meeting this week: Wednesday 15th January @ 19UTC
by Pili Guerra 14 Jan '20

14 Jan '20

Hi everyone, This week we are starting up our Tor Browser release meetings once again. The meeting will take place this Wednesday 15th January @ 19UTC on #tor-meeting. We look forward to seeing you there. 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

minutes from the sysadmin meeting
by Antoine Beaupré 13 Jan '20

13 Jan '20

Hi everyone! Here are the minutes from the last sysadmin meeting. # Roll call: who's there and emergencies anarcat, hiro, gaba, qbi present, arma joined in later # What has everyone been up to ## anarcat * unblocked hardware donations ([#29397][]) * finished investigation of the onionoo performance, great team work with the metrics led to significant optimization * summarized the blog situation with hiro ([#32090][]) * ooni load investigation ([#32660][]) * disk space issues for metrics team ([#32644][]) * more puppet code sync with upstream, almost there * built test server for mail service, R&D postponed to january ([#30608][]) * postponed DMARC mailing list fixes to january ([#29770][]) * dealt with major downtime at moly, which mostly affected the translation server (majus), good contacts with cymru staff * dealt with kvm4 crash ([#32801][]) scheduled decom ([#32802][]) * deployed ARM VMs on Linaro openstack * gitlab meeting * untangled monitoring requirements for anti-censorship team ([#32679][]) * finalized iranicum decom ([#32281][]) * went on two week vacations * automated install solutions evaluation and analysis ([#31239][]) * got approval for using emergency ganeti budget * usual churn: sponsor Lektor debian package, puppet merge work, email aliases, PGP key refreshes, metrics.tpo server mystery crash ([#32692][]), DNSSEC rotation, documentation, OONI DNS, NC DNS, etc [#32692]: https://bugs.torproject.org/32692 [#32281]: https://bugs.torproject.org/32281 [#32679]: https://bugs.torproject.org/32679 [#32802]: https://bugs.torproject.org/32802 [#32801]: https://bugs.torproject.org/32801 [#29770]: https://bugs.torproject.org/29770 [#32644]: https://bugs.torproject.org/32644 [#32660]: https://bugs.torproject.org/32660 [#32090]: https://bugs.torproject.org/32090 [#29397]: https://bugs.torproject.org/29397 ## hiro * Tried to debug what's happening on gitlab (a.k.a. dip.torproject.org) * Usual maintenance and upgrades to services (dip, git, ...) * Run security updates * summarized the blog situation ([#32090][]) with anarcat. Fixed the blog template * [www updates][] * Issue with KVM4 not coming back after reboot ([#32801][]) * Following up for the anticensorhip team monitoring issues ([#31159][]) * Working on [nagios checks for bridgedb][] * Oncall during xmas [nagios checks for bridgedb]: https://dip.torproject.org/torproject/anti-censorship/roadmap/issues/6 [#31159]: https://bugs.torproject.org/31159 [www updates]: https://dip.torproject.org/torproject/web/www-monthly/blob/master/2019-12.md ## qbi * disabled some trac components * deleted a mailing list * created a new mailing list * tried to familiarize with puppet API queries # What we're up to next ## anarcat Probably too ambitious... New: * varnish -> nginx conversion? ([#32462][]) * review cipher suites? ([#32351][]) * publish our puppet source code ([#29387][]) * setup extra ganeti node to test changes to install procedures and especially setup-storage * kvm4 decom ([#32802][]) * install automation tests and refactoring ([#31239][]) * SLA discussion (see below, [#31243][]) [#31243]: https://bugs.torproject.org/31243 [#32462]: https://bugs.torproject.org/32462 [#32351]: https://bugs.torproject.org/32351 [#31239]: https://bugs.torproject.org/31239 [#29387]: https://bugs.torproject.org/29387 Continued/stalled: * followup on SVN shutdown, only corp missing ([#17202][]) * audit of the other installers for ping/ACL issue ([#31781][]) * email services R&D ([#30608][]) * send root@ emails to RT ([#31242][]) * continue prometheus module merges [#17202]: https://bugs.torproject.org/17202 [#31781]: https://bugs.torproject.org/31781 [#30608]: https://bugs.torproject.org/30608 [#31242]: https://bugs.torproject.org/31242 ## Hiro * Updates || migration for the CRM and planning future of donate.tp.o * Lektor + styleguide documentation for GR * Prepare for blog migration * Review build process for the websites * Status of monitoring needs for the anti-censorship team * Status of needrestart and automatic updates ([#31957][]) * Moving on with dip or find out why is having these issues with MRs [#31957]: https://bugs.torproject.org/31957 ## qbi * DMARC mailing list fixes ([#29770][]) # Server replacements The recent crashes of kvm4 ([#32801][]) and moly ([#32762][]) have been scary (e.g. mail, lists, jenkins, puppet and LDAP all went away, translation server went down for a good while). Maybe we should focus our energies on more urgent server replacements, that is specifically kvm4 ([#32802][]) and moly ([#29974][]) for now, but eventually all old KVM hosts should be decommissisoned. [#29974]: https://bugs.torproject.org/29974 [#32762]: https://bugs.torproject.org/32762 We have some budget to expand the Ganeti setup, let's push this ahead and assign tasks and timelines. Consider we need a new VM for GitLab and CRM machines, among other projects. Timeline: 1. end of week: setup fsn-node-03 (anarcat) 2. end of january: setup duplicate CRM nodes and test FS snapshots (hiro) 2. end of january: kvm1/textile migration to the cluster and shutdown 3. end of january: rabbits test new CRM setup and upgrade tests? 4. mid february: CRM upgraded and boxes removed from kvm3? 5. end of Q1 2020: kvm3 migration and shutdown, another gnt-fsn node? We want to streamline the KVM -> Ganeti migration process. We might need extra budget to manage the parallel hosting of gitlab and git.tpo and trac. It's a key blocker in the kvm3 migration, in terms of costs. # Oncall policy We need to answer the following questions: 1. How do users get help? (partly answered by <https://help.torproject.org/tsa/doc/how-to-get-help/>) 2. What is an emergency? 3. What is supported? (This is part of [#31243][].) >From there, we should establish how we provide support for those machines without having to be oncall all the time. We could equally establish whether we should setup rotation schedules for holidays, as a general principle. Things generally went well during the vacations for hiro and arma, but we would like to see how to better handle this during the next vacations. We need to think about how much support we want to offer and how. Anarcat will bring the conversation with vegas to see how we define the priorities, and we'll make sure to better balance the next vacation. # Other discussions N/A. # Next meeting Feb 3rd. # Metrics of the month * hosts in Puppet: 77, LDAP: 80, Prometheus exporters: 123 * number of apache servers monitored: 32, hits per second: 175 * number of nginx servers: 2, hits per second: 2, hit ratio: 0.87 * number of self-hosted nameservers: 5, mail servers: 10 * pending upgrades: 0, reboots: 0 * average load: 0.61, memory available: 351.90 GiB/958.80 GiB, running processes: 421 * bytes sent: 148.75 MB/s, received: 94.70 MB/s * planned buster upgrades completion date: 2020-05-22 (20 days later than last estimate, 49 days ago) Happy new year everyone! -- Antoine Beaupré torproject.org system administration

1 0

Community Team report - November & December 2019
by gus 13 Jan '20

13 Jan '20

Community Team November & December 2019 ======================================= Support and Documentation ------------------------- In December, Cleopatra (c1e0 on IRC) started as Outreachy intern in the project "Help Tor support our users" <https://trac.torproject.org/projects/tor/wiki/Outreachy#Project1:HelpTorPro…>. In the last month, Gus introduced C1e0 in the Frontdesk world, and we worked together to answer users requests. We've narrowed the queue for less than 90 new tickets. C1e0 will compile our users feedback in a monthly report, see <https://lists.torproject.org/pipermail/tor-project/2020-January/002645.html>. During the Outreachy contribution period, MacTavish started the Tor Browser for Android Manual, Cleopatra and Gus are reviewing it and in January we will have as a new section inside Tor Browser Manual <https://tb-manual.torproject.org>. Trainings --------- In November we met with training partners in Global South to organize and schedule digital security trainings. And Tails and Tor were presented (among other tools) to journalism students at IUT Lannion (Lannion, France), Sciences Po Rennes (Rennes, France) and Bordeaux Aquitaine Institute of Journalism (IJBA) (Bordeaux, France). In December Fundación Karisma (Colombia) and Zaina Foundation (Tanzania) organised digital security trainings about Tor in their local communities. They used our training materials and followed our User Research guideline to collect feedback to UX team. Outreach -------- November - (Copenhagen) Ahf talked about Tor & circumvention censorship at Driving IT <https://blog.torproject.org/events/driving-it-copenhagen> - (Firenze) Gus talked about Tor at If_do hacklab <https://blog.torproject.org/events/internet-e-anonimato-la-rete-tor-firenze> - (Brussels) Tor Meetup Brussels with ahf, gus, francisco, vasilis <https://blog.torproject.org/events/tor-meetup-brussels> - (Brussels) Ahf and Gus organised Tor sessions at Freedom not Fear <https://blog.torproject.org/events/freedom-not-fear-brussels> - (DC) Roger talked at "The Future of Speech Online" <https://blog.torproject.org/events/future-speech-online-dc> - (Seattle) Gaba presented "The State of the Onion" during "Seattle GNU/Linux Conference" <https://blog.torproject.org/events/seagl-seattle> - (Roma) Gus talked about Tor with Avana hacklab at Strike: <https://blog.torproject.org/events/tor-workshop-strike-spa-roma> - (Torino) Gus talked about Tor at UNITO - "Non è la silicon valley, ma si mangia meglio!" <https://blog.torproject.org/events/non-e-la-silicon-valley-ma-si-mangia-meg…> - (Barcelona) Pili talked at "V Jornades Internacionals de dones en el sector TIC" <https://blog.torproject.org/events/v-jornades-internacionals-de-dones-en-el…> - (Pune) Kushal speaked about Tor at "WoSec and InfoSecGirls Workshop" <https://blog.torproject.org/events/wosec-and-infosecgirls-workshop-pune> - Global South online meeting notes: <https://lists.torproject.org/pipermail/global-south/2019-December/000268.ht…> December - (São Paulo) Gus talked about Tor 101 and SecureDrop during Criptofesta <https://blog.torproject.org/events/criptofesta-sao-paulo-0> - (Campinas) Caio talked about Tor and relays in LHC hackerspace <https://blog.torproject.org/events/cebolizando-campinas> - (Brasilia) Gus talked at Criptobaile <https://blog.torproject.org/events/criptobaile-brasilia> - (Brooklyn) Isabela talked about "Taking Back the Internet with Tor" during Hackers Next Door <https://blog.torproject.org/events/hackers-next-door-brooklyn> - (Montevideo) Gaba gave a Tor/infosec workshop to journalists from <ladiaria.com.uy> - Relay operators met during the 36C3, read the assembly notes <https://lists.torproject.org/pipermail/tor-relays/2020-January/018022.html> - Blog post about Human Rights day <https://blog.torproject.org/digital-rights-are-human-rights> - Global South online meeting notes: <https://lists.torproject.org/pipermail/global-south/2019-December/000270.ht…> Next Events ----------- February - Meet us during FOSDEM 2020 <https://trac.torproject.org/projects/tor/wiki/org/meetings/2020Brussels> Meta ---- Community Team weekly meetings, every Monday at 16:00 UTC, in #tor-meeting at OFTC <irc.oftc.net> Meeting notes * Community Team Meeting Notes - 04 Nov 2019 * <https://lists.torproject.org/pipermail/tor-community-team/2019-November/000…> * Community Team Meeting Notes - 18 Nov 2019 * <https://lists.torproject.org/pipermail/tor-community-team/2019-November/000…> * Community Team Meeting Notes - 25 Nov 2019 * <https://lists.torproject.org/pipermail/tor-community-team/2019-November/000…> * Community Team Meeting Notes - 02 Dec 2019 * <https://lists.torproject.org/pipermail/tor-community-team/2019-December/000…> * Community Team Meeting Notes - 09 Dec 2019 * <https://lists.torproject.org/pipermail/tor-community-team/2019-December/000…> * Community Team Meeting Notes - 16 Dec 2019 * <https://lists.torproject.org/pipermail/tor-community-team/2019-December/000…>

1 0

www December 2019 report
by Hiro 13 Jan '20

13 Jan '20

What has happened in December in the Tor www world The blog template has finally been fixed! If you want to know more about the blog status check the following Trac ticket: https://trac.torproject.org/projects/tor/ticket/32090 The download page has been improved based on feedback received since the redesign. User research has been running over: https://lektor-staging.torproject.org/tpo/develop/download/ We debugged errors in the build process for the websites. This was affecting translations specifically more than other things. We uplifted the styleguide Our wiki content is now in one place: https://dip.torproject.org/torproject/web/wiki We improved on Localized links so that a visitor isn't taken out of their locale while browsing. We applied some fixes for left-to-right/right-to-left support of different langauges Meeting notes for Dicember can be found: https://dip.torproject.org/torproject/web/www-meeting-notes/blob/master/201… This summary and past and future ones can be accessed online: https://dip.torproject.org/torproject/web/www-monthly

1 0

OONI Monthly Report: December 2019
by Maria Xynou 10 Jan '20

10 Jan '20

Hello Tor world, In December 2019, the OONI team prioritized on the following: * Integrating the new OONI Probe test for Psiphon into the OONI Probe desktop app * Provisioning of Psiphon configuration into apps * API query optimization * Reducing technical debt and bug fixing ## Circumvention tool testing Throughout December 2019, we made important progress on the testing of circumvention tools. Specifically, we: * Added support for giving out Psiphon configuration files to clients in orchestra: https://github.com/ooni/orchestra/issues/78 * Added client support for performing authenticated orchestra requests: https://github.com/ooni/probe-engine/issues/109 * Added support for running circumvention tool tests inside of the OONI Probe CLI: https://github.com/ooni/probe-cli/issues/77 Through the above work, we laid the foundation for implementing future circumvention tool tests inside of OONI Probe. You can now download and run the new OONI Probe Psiphon test via one of the latest ooni/probe-cli release candidate builds: https://github.com/ooni/probe-cli/releases ## Measurement improvements We made a series of improvements to how OONI Probe measurements are performed. Specifically, we: * Released a new version of Measurement Kit which includes DASH using HTTPS: https://github.com/measurement-kit/measurement-kit/releases/tag/v0.10.8 * Validated that the OONI Probe Telegram test works well by using jafar (our censorship simulation tool) to trigger certain network conditions and ensure that the data output is OK: https://github.com/ooni/jafar/pull/15 & https://github.com/ooni/jafar/pull/17 * Added support to probe-engine to use the orchestra to fetch the configuration for Psiphon and to store locally the credentials for logging-in to orchestra: https://github.com/ooni/probe-engine/pull/185 ## OONI Probe 3.0 improvements We added support for the clean shutdown of probe-cli, providing a clean way of interrupting a running test on the OONI Probe desktop app: https://github.com/ooni/probe-cli/issues/76 We also added support for filtering out incomplete test results (https://github.com/ooni/probe-desktop/pull/92) and we upgraded the styled-components to 4.0.0 (https://github.com/ooni/design-system/issues/49) ## OONI Explorer performance As the new OONI Explorer fetches measurements from the OONI API, improving the performance of OONI Explorer (in order to serve query results faster and more reliably) required improving the performance of the OONI API (see: https://github.com/ooni/api/issues/135) We therefore did a lot of work on improving the OONI API. More specifically, we: * Added throttling to the OONI API in order to prevent abuse: https://github.com/ooni/api/pull/139 * Removed SQLAlchemy models (resulting in performance improvements): https://github.com/ooni/api/pull/153 * Refactored the list_measurements table (resulting in a huge performance boost): https://github.com/ooni/api/pull/150 We also did several other important improvements to the OONI API and data processing pipeline: * Added support for detecting issues with the ingestion of data: https://github.com/ooni/pipeline/issues/256 * Added support for anomalous and confirmed blocked measurement columns in the fast-path pipeline: https://github.com/ooni/api/pull/141 * Added support for filtering by domain name for results in the fast-path pipeline: https://github.com/ooni/api/pull/144 * Created two new tables for citizenlab/test-lists ingestion: https://github.com/ooni/pipeline/pull/274 * Added tables that allow us to query by category code: https://github.com/ooni/pipeline/issues/263 * Explored how to update one of our postgresql databases ## Infrastructure Throughout December 2019, we spent a lot of time improving our infrastructure and dealing with incidents. Details around these incidents and what we did to resolve them are available through the following tickets: https://github.com/ooni/sysadmin/issues/410 https://github.com/ooni/sysadmin/issues/406 The infrastucture monitoring and alerting system that we have in place enabled us to more easily identify these issues. ## Blog post to encourage LGBTQI site testing In collaboration with OutRight Action International, we jointly published a blog post to encourage OONI Probe testing of LGBTQI websites around the world. The blog post is published on the following sites: * OONI: https://ooni.org/post/2019-measure-blocking-lgbtqi-sites/ * OutRight Action International: https://outrightinternational.org/content/let%E2%80%99s-measure-blocking-lg… VPNCompare published a blog post discussing our LGBTQI testing research: https://www.vpncompare.co.uk/ooni-lgbtqi-censorship/ ## Press coverage An Intercept article was published to cover our joint research report with Coding Rights & Women on Waves (titled "On the blocking of abortion rights websites: Women on Waves & Women on Web"): https://theintercept.com/2019/12/12/net-claro-e-vivo-bloqueiam-site-aborto-… ## User-base In December 2019, OONI Probe was run 9,270,932 times from 5,564 different vantage points in 209 countries around the world. This information can also be found through our measurement stats on OONI Explorer (chart on monthly coverage worldwide): http://explorer.ooni.org/ ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

August Fundraising Report
by Sarah Stevenson 10 Jan '20

10 Jan '20

Hello Tor world. Here is the Fundraising team’s report for August. As always, let us know if you have any questions. ## Events We ran our first booth at DEF CON in August. It was an exhausting few days, but we exceeded our goal and raised over $43,000! We also made several connections with folks who want to help us with projects in the coming months. We have compiled lessons learned and are looking forward to attending again next year. ## Appeals The Bug Smash campaign[1] ran from August 1 to August 31. We raised a little over $86K across postal mail, social media, email appeal, and in-person gifts at DEF CON and CCCamp. We received a mixture of currencies, including a variety of cryptocurrencies. This a strong increase over August 2018 when we raised $13K. ## Grants We submitted a grant to RIPE NCC Community Project’s support program for 50,000 EUR to improve our IPv6 support. Thanks to teor, Nick, & Gaba for their help writing this proposal. We submitted a concept note to OTF for a large Tor Browser project which would move us away from the ESR cycle and onto Mozilla’s regular release cycle; it would also allow us to implement some of Firefox’s Enhanced Tracking Protection features. Thanks to the Browser team and Pili for making this happen! We found out that two of our grant requests were declined, one to NLnet for ESR migration and the other to the Deer Creek Foundation for Communications work. Upcoming grant requests: DRL SOIs for Community and Scalability, due 9/20 MOSS Scalability project, due 9/?? (rolling) NLnet, due 10/1 Herb Block Foundation, due 10/3 NSF Dark Decoys project, due ?? (rolling) ## Cryptocurrency We made a connection with a company called The Giving Block[2] that helps nonprofits accept cryptocurrency donations called. We are now listed on their website and will participate in their Giving Tuesday efforts this coming December. We are also discussing other ways to collaborate. ## Monthly Donors We continue to see growth in our monthly donor program, Defenders of Privacy. In August we received $5,386.75 from this group. As you can see in the chart below, our efforts to recognize and communicate with these donors has resulted in more stable income and less attrition. We should expect the group to continue to grow through the end of the year and then have a dip again in January when people tend to reassess their monthly commitments. [1] https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs <https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs> [2] https://www.thegivingblock.com/donate-bitcoin <https://www.thegivingblock.com/donate-bitcoin>

1 5

Notes from Vegas Meetings JANUARY 2 & JANUARY 9 2020
by Erin Wyatt 10 Jan '20

10 Jan '20

Happy new year, everyone!! :D —————————>8 JANUARY 9 2019 + NEW BUSINESS - Considering using up our primary emergency hardware budget (162EUR/mth) to expand the Ganeti cluster to shutdown old machines and move critical services to the redundant cluster. [anarcat] • Response: Yes, let's do it. - How many proposal are we submitting to Righstcon? [gus] • Response: So far, 2. - Mozilla folks said that we should figure out ASAP what meetings/conversation topics and times wewant to have (if any) while at the Mozilla conference in Berlin, as the schedule will start filling up soon. (Last time, we scheduled our meeting with at the end of the conference, so we had time to prepare for it in person. I think this worked well, but it had some downsides due to lack of quick followup opportunities). FYI I am emailing [to ask] them for a meeting; planning on sending before the end of the week. + GENERAL NOTES Georg: 0) Still on "vacation" Erin 1) New vacation/AFK calendar on NC - email to people soon. 2) HR/Personnel stuff 3) Roadmapping 2020 - will include next review cycle, hiring process, handbook (incl. IP stuff), diversity report, etc. Anarcat 1. worked on evaluating automated install solutions since we'd possibly have to setup multiple machines if the donation comes through 2. got a big scare before vacations and we're evaluating priorities to avoid this problem in the future. will likely prioritize work on service stabilization and reliability instead of new services along with surveying/researching expectations on service support and availability to avoid the situation that happened 3. considering using up our primary emergency hardware budget (162EUR/mth) to expand the Ganeti cluster to shutdown old machines and move critical services to the redundant cluster. 4. happy new year everyone! :) Steph: 1) Doing campaign retros with comms/fundraising 2) Organizing a panel with EFF and FPF on privacy laws and tools for RightsCon 3) Working with Outreachy intern annalee_ 4) Started 2020 Comms roadmap with Isa 5) Preparing for San Fran fundraising event in March isabela 1) Having 1:1s w/ Vegas Leads about 2020 -> if I don't have one schedule w/ u yet, Jon is working on it and will schedule one soon 2) Off site meetings: Matt :), Brennan Center, NYU, ED NYC Club dinner 3) Doing some Money Machine + Comms tasks 4) Getting the Board Book prepared for our next meeting Jan 21st 5) Working on onboarding doc for onion advisors and updating the membership program doc (also need to do some follow up w/ julius). sarah 1) Working on final numbers and reflections for EOY campaign. 2) Planning March 26th event in San Francisco. 3) Several upcoming meetings with potential new foundation funders. 4) Updating the fundraising roadmap for 2020. Philipp 1) Giving a talk today on our anti-censorship work at my old college (https://twitter.com/torproject/status/1208102010832277504) 2) More writing for TTP grant application Antonela 1) Roadmapping UX team work for 2020 2) Community partners ran user research during December in Colombia and Tanzania. Working with nah on reporting those and integrate that user feedback in our development cycle. 3) Back to S27 land, syncing with devs, reviewing tickets. Gus 1) Roadmapping Community Team - 2020 with Pili 2) 1:1 with Isa last week 3) Coordinating remote trainings with partners in Global South 4) Outreachy: reviewing Cleopatra frontdesk support, new documentation PRs and monthly user feedback 5) Working on Tor Project Village proposal in IFF 6) Answering 2019 emails 7) Working on remote training workflow - https://trac.torproject.org/projects/tor/ticket/32893 [anarcat, we need your opinion about the RT part of this proposal] 8) Submitted a digital security workshop to Journalism Festival in Italy, but we didn't heard anything from the organization. Karsten 1) Started a discussion on tor-dev@ how to handle MaxMind's change to how we can access and use their databases. We use them for tor (statistics and path selection) and Onionoo. Right now we cannot update the databases that we have, so this is a bit urgent. 2) Reviewed and revised a patch to how we sanitize web server access logs (#32747), which will hopefully reduce sanitization time from several hours to under an hour each day. Maybe it'll also resolve artifacts like the one found in #31901. 3) Preparing for roadmapping meeting next week by going through the enourmous ticket backlog in Metrics/* components. Alex: 1) Scheduling 1:1 with network team folks for the next couple of months. Trying to have more of them on a single day to make my structure a bit simpler. 2) Some work around q1 roadmap. 3) Follow up on emails, EOM tasks, etc. 4) Figure out FOSDEM logistics and general q1 travel stuff for different events. Nick: 1) Wrapping up 0.4.3.x work; soon to enter feature-freeze. (Jan 15) 2) Likely to do another 0.4.2.x soon, plus maybe an 0.4.1.x too, to sort out minor issues in previous release with seccomp2 sandbox and NT services. 3) Still working on role transitions; got to figure out what planning/arch actually _is_. Mike: 0. Technically still on vacation. Will attend to discuss Mozilla Berlin stuff (see new biz above). 1. Have a Research Director Roles draft doc; will send to Gaba+Isa next week then circulate more widely. Pili: 1. Catching up from vacations 2. Roadmap Gardening 3. Organising for FOSDEM Matt: 1. Tor Browser releases based on 68.4.0esr and 68.4.1esr this week 2. At Real World Crypto 3. Tor Browser roadmapping and such. —————————>8—————————>8—————————>8 JANUARY 2, 2020 + OLD BUSINESS - Are we doing any RightsCon submissions? • Discussion: Yes, we discussed this at a vegas meeting; we are going to reach out to contacts that are going to check if they have any plans, maybe we can be part of their plans or plan something together with them. We created a list just before xmas, now its time to pick it up again and email some of the folks on that list - Did we ever make a shared plan on the trademark defense work? • Discussion: No for now; Jon is still the main point person to report such things, me and him still need to update the trademark FAQ regarding logo on swags that are for personal use not for sale etc - isabela (i think having things this way for now its fine, I believe we have other priorities i.e. membership program to organize and push fwd - isabela) + NEW BUSINESS isabela: - 2020 message: privacy by design + GENERAL NOTES Roger: 1) Are we doing any RightsCon submissions? 2) Did we ever make a shared plan on the trademark defense work? 3) Can we authorize and train some more people to do website changes? E.g. our Shadow dev job spot has been open for weeks after Erin filed a ticket to have it come down (#32826) and we keep getting new applicants. [this has done already by Pili and Hiro if anyone else needs or wants a training they should reach out to Hiro] [we also have some docs! https://dip.torproject.org/torproject/web/tpo/wikis/home - A] 4) The SponsorV and Sponsor2 reports are in. isabela: 1. Catching up on emails from the holidays 2. Working on email to sponsors reviewing tor in the media 2019 3. working on document for onion advisors orientation meeting and updating a little bit the membership program proposal 4. 2020 message privacy by design - next email I plan to send to tor-project sarah: 1. We raised about $315K for the EOY campaign. We probably still have checks at the PO box that haven't been added in yet. This is over $100K more than we raised last year and we've now raised more from individuals in the first 6 months of this FY than we did in FY19 in its entirety. I'll have a more comprehensive report in the coming days. [awesome work! -ahf] steph: 1. Wrapped up the EOY fundraising campaign. Comms report coming. 2. Will start planning/coordination for campaign for companies to run relays 3. Switching out social media campaign branding 4. Catching up! Alex: 1. Relaxed, a lot. 2. Went to 36c3. Was mostly at the BornHack assembly, but the Tor assembly seem to run fine (asfaik). The Relay operators meetup went well IMO. I did not go to the "Tor Relay Org" meeting there as I was told there was only 12 seats in the room, but it is my impression that went OK too. I have seen a number somewhere that around 20-25% of the exit capacity in the network were together in that room. 3. This "week" is going to be return to normal life, catch up on email, do harvest, schedule 1:1 with network team folks, and return to Gitlab work tomorrow. Nick: 0. Back online from the winter holiday; catching up on things. Antonela: 1. sending ux team report for december and a 2019 recap 2. emails, emails and more emails 3. resuming what i left open in december Philipp: 1. Back from holidays and catching up. Matt: 1. Missing this meeting 2. Catching up on missed items from the past week 3. Prepping release for next week

1 0

Anti-censorship meeting notes 09 January 2019
by Cecylia Bocovich 09 Jan '20

09 Jan '20

Here is our meeting log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-01-09-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday January 9th 18:00 UTC Weekly meetings, every Thursday at 18:00 UTC, in #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 == * Our anti-censorship roadmap: https://dip.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/groups/torproject/anti-censorship/gettor-project… * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Projects from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 ------------------------- --- January 9th 2020 --- ------------------------- == Announcements == * == Discussion == * Anyone want to mentor a student developer during the summer? We have time to apply until early February. https://summerofcode.withgoogle.com/how-it-works/#timeline Ideas from last year: https://2019.www.torproject.org/getinvolved/volunteer.html.en#Coding == Actions == * == Interesting links == * == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. Hiro: (last updated before 2020-01-09) Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation phw: This week (2020-01-02): * Catching up on emails. * Tried to write patch for #31009. Next week: * Helping with grant writing. Help with: * Let me know if you have thoughts on a potential BridgeDB rewrite * https://bugs.torproject.org/32900 Gaba: () Last week (Dec 16th): * s30 tracking This week (planned): AFK until January 9th. I'm on signal if needed cecylia (cohosh): last updated 2019-01-09 Last week: - finish debugging windows issues with snowflake (#31971) - update pion library version for Tor Browser (#32870) - grant writing - thought about passing STUN information through broker (#25591) - worked on updating and debugging gettor (#32906) - got a start at fixing the gitlab gettor distributor (#32711) This week: - finish gitlab gettor fixes(#32711) - think about gsoc projects - iterate on gettor survival guide - debug more issues with gettor links database - update gettor for newest tor browser alpha - look at reports of shadow socks blocking - snowflake proxy UX (#31109) Needs help with: - review of #31971 (from tor browser team) arlolra: 2019-12-12 Last week: - merged #32499 Next week: - read up on turbo tunnel - pick a new task (#31902, #31201, #19026, ?) Help with: - dcf: 2020-01-09, will miss 2020-01-09 meeting Last week: - worked on turning off the non-IPv6 Snowflake broker (#32502) Next week: - delete the old broker (#32502) - turbo tunnel in Snowflake Help with: cjb: last updated 2019-01-09 Last week: - came up with a patch for #31011, testing seems difficult, will ask for help in the ticket. Next week: Help with:

1 0

Communications Report: November & December 2019
by Stephanie A. Whited 03 Jan '20

03 Jan '20

1 0