[tor-project] Anti-censorship team meeting notes, 2024-07-25

Hey everyone!

Here are our meeting logs:

http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-07-25-16.00.html

And our meeting pad:

Anti-censorship

···

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

Next meeting: Thursday, August 1 16:00 UTC
Facilitator: shelikhoo
^^^(See Facilitator Queue at tail)

Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)

This week's Facilitator: meskio

== Goal of this meeting ==

Weekly check-in about the status of anti-censorship work at Tor.
Coordinate collaboration between people/teams on anti-censorship at the Tor Project and Tor community.

== 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 96 <-- meskio, shell, onyinyang, cohosh
      * Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibet · The Tor Project · GitLab
    * Sponsor 150 <-- meskio working on it
      * Issues · Anti-censorship · GitLab

== Announcements ==

  * Roger wrote up his Snowflake blocking experiment notes, [anti-censorship-team] snowflake blocking experiment -- more hackweek/experiment opportunities remain :slight_smile:

== Discussion ==

== Actions ==

== Interesting links ==

  * [2405.13310] Bytes to Schlep? Use a FEP: Hiding Protocol Metadata with Fully Encrypted Protocols "Bytes to Schlep? Use a FEP: Hiding Protocol Metadata with Fully Encrypted Protocols"
    * update to The Internet censorship bibliography "Security Notions for Fully Encrypted Protocols" from FOCI 2023
  * GitHub - tst-race/raceboat at documentation Raceboat source code
  * V2Ray has received a security audit from 7ASecurity · v2fly/v2ray-core · Discussion #3096 · GitHub
    * V2Ray has received a security audit from 7ASecurity
    * https://www.opentech.fund/security-safety-audits/v2ray-security-audit/

== Reading group ==
  * We will discuss "" on
    * 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.

cecylia (cohosh): 2024-06-27
  Last week:
      - snowflake-webext updates
      - reviewed mv3 prototype
      - helped onyinyang on rebasing and debugging wasm-bindgen
      - worked on squashing Conjure PT into lyrebird
          - Squash PTs into Lyrebrid (#40015) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / lyrebird · GitLab
          - Adapt Conjure Tor PT into a library that could be easily integrated into lyrebird (#42) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / conjure · GitLab
  This week:
      - take a look at snowflake web and webext translations and best practices
      - make changes to Lox encrypted bridge table
          - Simplify BridgeLine struct and make it variable length (!147) · Merge requests · The Tor Project / Anti-censorship / lox · GitLab
  Needs help with:

dcf: 2024-07-11
  Last week:
    - snowflake azure CDN bookkeeping Changes · Snowflake costs · Wiki · The Tor Project / Anti-censorship / Team · GitLab
    Next week:
    - review snowflake unreliable+unordered data channels rev2 Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
    - open issue to have snowflake-client log whenever KCPInErrors is nonzero Deploy snowflake-server for QueuePacketConn buffer reuse fix (#40260) (#40262) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
      - parent: Improve bug discovery process (#40267) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
    - open issue to disable /debug endpoint on snowflake broker
    - move snowflake-02 to new VM
Help with:
    - tell me when to restart the brokers for Upgrade snowflake broker machine from Debian 10 (#40349) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab

meskio: 2023-07-25
    Last week:
        - investigate what builtin bridges are offline and contact operators (team#141)
        - work on Sponsor 96 final report
        - ignore dots on emails on the email distributor (rdsys#208)
    Next week:
        - check if lyrebird reduces size removing old PTs (lyrebird#40016)

Shelikhoo: 2024-07-25
    Last Week:
            - Chrome Manifest V3 transition: Migrate to Manifest V3 (#29) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake WebExtension · GitLab
            - Merge request review
            - S96 Report Response to feedback
        - Merge request reviews
    Next Week/TODO:
        - Merge request reviews
        - Chrome Manifest V3 transition: Migrate to Manifest V3 (#29) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake WebExtension · GitLab

onyinyang: 2023-07-25
  Last week(s):
    - FOCI/PETS online
    - Working on tor-browser integration with updated lox-wasm binary:
      - switched back to building modules and using them with a downloaded Tor browser
        - tor-browser-build was mixing up inputs for one function which caused the module to error at load time, flipping them seems to have fixed the error
      - updating Lox module for key rotation logic
      - Identified that the lastPassed variable is not working as expected for Lox: lox resources bypassing grace period (#209) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab and is probably the reason behind this issue: Lox Ready for Open Testing Call · Milestones · The Tor Project / Anti-censorship / lox · GitLab
  Next week:
    - continue with key rotation integration work
    - fix lastPassed issue in rdsys (or lox if the rdsys fix is too complicated)
    - Work on outstanding milestone issues:
      in particular: Increase the acceptable time for bridgeline failure (#69) · Issues · The Tor Project / Anti-censorship / lox · GitLab
      - key rotation automation
      
    Later:
    - begin implementing some preliminary user feedback mechanism to identify bridge blocking based on Vecna's work
    - improve metrics collection/think about how to show Lox is working/valuable
    - sketch out Lox blog post/usage notes for forum
    
  (long term things were discussed at the meeting!): Riseup Pad
    - brainstorming grouping strategies for Lox buckets (of bridges) and gathering context on how types of bridges are distributed/use in practice
      Question: What makes a bridge usable for a given user, and how can we encode that to best ensure we're getting the most appropriate resources to people?
        1. Are there some obvious grouping strategies that we can already consider?
          e.g., by PT, by bandwidth (lower bandwidth bridges sacrificed to open-invitation buckets?), by locale (to be matched with a requesting user's geoip or something?)
        2. Does it make sense to group 3 bridges/bucket, so trusted users have access to 3 bridges (and untrusted users have access to 1)? More? Less?
    
theodorsm: 2023-07-11
    Last weeks:
      - Completed my master thesis (https://theodorsm.net/thesis)
      - Had some time off
    Next weeks:
      - Wait for pion upstream releases
      - Test Snowflake fork with covert-dtls
      - Condensing thesis into paper
    Help with:
      - Feedback on thesis
      
Facilitator Queue:
     shelikhoo onyinyang meskio
1. First available staff in the Facilitator Queue will be the facilitator for the meeting
2. After facilitating the meeting, the facilitator will be moved to the tail of the queue

--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.