[tor-project] Anti-censorship team meeting notes, 2022-04-14

Hey everyone!

Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-14-15.59.html

And our meeting pad:

Anti-censorship work meeting pad

···

--------------------------------

Next meeting: Thursday April 21th 16:00 UTC

Weekly meetings, every Thursday at 16: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:
    * Roadmap: Development · Boards · Anti-censorship · GitLab
  * The anti-censorship team's wiki page:
    * Home · Wiki · The Tor Project / Anti-censorship / Team · GitLab
  * Past meeting notes can be found at:
    * The tor-project Archives
  * Tickets that need reviews: from sponsors we are working on:
    * All needs review tickets: Merge requests · Anti-censorship · GitLab
    * Sponsor 28
      * must-do tickets: Sponsor 28: Reliable Anonymous Communication Evading Censors and Repressors (RACECAR) · The Tor Project · GitLab
      * possible tickets: Issues · The Tor Project · GitLab
    * Sponsor 96
      * Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibet · The Tor Project · GitLab

== Announcements ==

  * Roger is working on a Defcon talk submission, around the Russia censorship thing. Soon it will be ready for internal feedback and then we'll submit it. (Write and submit a defcon 2022 talk: censorship, russia, snowflake, bridge distribution, etc (#73) · Issues · The Tor Project / Anti-censorship / Team · GitLab)

== Discussion ==

  * [Distributed Snowflake Server Support](Distributed Snowflake Server Support (#40129) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab) is ready for testing
    * A testing Broker will be setup
    * A secondary Bridge from dcf will be used for testing
    * Once testing is concluded, get help from other orgs to run other secondary snowflake bridges(like in Asia)
    * shelikhoo will create a ticket for an automated bridge setup system

== Actions ==

  *

== Interesting links ==

  * Reported shutdown in Turkmenistan 2022-04-11 - Turkmenistan - NTC
    * Seems to be over now https://twitter.com/CloudflareRadar/status/1513907409579876360 https://radar.cloudflare.com/tm

== Reading group ==

  * We will discuss "Blocking of HTTP/3 (QUIC) in Russia" on Apr/28th/2022
    * Blocking of HTTP/3 (QUIC) in Russia · Issue #108 · net4people/bbs · GitHub
    * Questions to ask and goals to have:
      * What aspects of the paper are questionable?
      * Are there immediate actions we can take based on this work?
      * Are there long-term actions we can take based on this work?
      * Is there future work that we want to call out, in hopes that others will pick it up?

== Updates ==

Name:
     This week:
         - What you worked on this week.
     Next week:
         - What you are planning to work on next week.
     Help with:
       - Something you need help with.

anadahz: 2022-01-27
  Last week:
    - Increase timeout check cycles for default-bridge-felix-1 and default-bridge-felix-2 as they have been generating too many alerts: Increase number of cycles for felix bridges (!1) · Merge requests · The Tor Project / Anti-censorship / monit-configuration · GitLab

cecylia (cohosh): last updated 2022-04-14
Last week:
     - moved tor-specific snowflake code out of client library (snowflake#40124)
         - merge request: snowflake!85
     - bump version of webrtc dependency (snowflake#40127)
         - merge request: snowflake!86
     - commented on snowflake web workflow (snowflake#40125)
     - opened issue to bump version of snowflake and webrtc in tor browser (tor-browser-build#40474)
     - work on conjure test environment setup
This week:
     - continued work on conjure PT
     - continue snowflake maintenance tasks
Needs help with:

dcf: 2022-04-14
  Last week:
    - monitored the transition of the snowflake bridge to its new server Move bridge to a permanent faster server (#40111) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
  Next week:
    - look at STATUS VERSION proposal Add STATUS VERSION message for PT protcol (!63) · Merge requests · The Tor Project / Core / Tor Specifications · GitLab
    - install second snowflake bridge site Set up a second snowflake bridge site (#40122) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
  Help with:

agix: 2021-02-10
  Last week:
    - Continued work on gettor-twitter
    Next week:
    - Hopefully finish the task
  Help with:
    -

arlolra: 2022-04-07
  Last week:
    - Merged the rest of snowflake !81
  Next week:
    - Get to snowflake-webext #10
  Evergreen:
    - Figure out where in pion/webrtc ALPN should be configured and used
    - Maybe add Chacha20Poly1305 to pion/dtls
    GitHub - pion/dtls: DTLS 1.2 Server/Client implementation for Go
    Make Snowflake's DTLS fingerprint more similar to popular WebRTC implementations (#40014) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
  Help with:
    -

maxb: 2021-09-23
  Last week:
    - Worked on uTLS for broker negotiation (#40054) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab re: utls for broker negotiation
    - Had conversation with someone about upstream utls http round tripper feat: sketch out utls http.RoundTripper by bassosimone · Pull Request #74 · refraction-networking/utls · GitHub
    - Too busy with work :confused:
  Next week:
    - _Really_ want to get a PR for utls round tripper

meskio: 2022-04-07
  Last week:
      - document circumvention settings API (bridgedb#40043)
      - accept bridge distributor request changes (rdsys#104)
      - investigate bridgestrap reporting odd timing (tor#40592)
      - review cross compile docker snowflake-proxy (docker-snowflake-proxy!6)
  Next week:
      AFK

Shelikhoo: 2022-04-14
    Last Week:
    - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64)
    - [Coding & Deployment] Proposal: Centralized Probe Result Collector (anti-censorship/team#54)
    - [Discussion] Centralized Probe Log Collection Ascension Request
    - [Discussion] Hosting Centralized Probe Log Collection Server on TPA managed VPS
    - [Discussion] Proposal: Support for Dynamic IP obfs4 bridges with unattended proxy information update(aka "Subscription")
    - [Discussion+Coding] Support Automatic Bridge Info update(shelikhoo/LogCollectorAncillary#1)
    - [Discussion+Coding] Remove Inactive Bridge from Test Result(shelikhoo/LogCollectorAncillary#2)
    - [Coding] Distributed Snowflake Bridges - Broker
    - [Coding] Distributed Snowflake Bridges Testing Environment - Dockerlized
    Next Week:
    - [Coding] Distributed Snowflake Bridges (continue)
    - [Deployment] Distributed Snowflake Bridges Testing Broker

Itchy Onion: 2022-04-14
     Last week:
         - pair programming with Cecylia on the general workflow for updating racecar plugin
         - resolving a compatible issue introduced in racecar 2.1.0

     This week:
         - continue working on racecar 2.1.0 (need to rebase snowflake)
         - set up LDAP

HackerNCoder: 2021-12-16
This week:
     Last/done:
         Setup web mirror on tor.encryptionin.space
     Next:
         Get (new VPs with) new IP and setup new web mirror on new domain

hanneloresx: 2021-3-4
  Last week:
    - Submitted MR for bridgestrap issue #14
  Next week:
    - Finish bridgestrap #14
    - Find new issue to work on
  Help with:
    -

ln5: 2022-03-24
   Last week:
       - Received hardware for a new home for snowflake.tpn; discussed OS configuration with dcf in private email
   Next week:
       - Install Debian 11 on new snowflake.tpn
       - Possibly rack new snowflake.tpn, if I can get access and find time to do the transportation
   Need help with:
       - Input on urgency appreciated, for my planning
       - Input on preferred CPU configuration, esp wrt HyperThreading -- lacking input before deployment in data centre, the machine will *not* have HT disabled and CPU bug mitigation will thus have to be carried out by the kernel

1 Like