Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-05-30-16.00.html
And our meeting pad:
Anti-censorship
···
--------------------------------
Next meeting: Thursday, June 6 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 ==
*
== Discussion ==
* Add nginx rate limiting to address "TTP-03-001 WP1: Snowflake broker vulnerability"
* TTP-03-001 WP1: Snowflake broker vulnerability (#40329) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
* It will be applied once we move the broker Upgrade snowflake broker machine from Debian 10 (#40349) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
* shelikhoo will apply the changes into the nginx of the new broker, it will take effect as soon as we migrate to it
* Is the broker migration ready to apply yet? Upgrade snowflake broker machine from Debian 10 (#40349) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
* dcf can change the VM memory configuration, then someone needs to contact TPA to ask them to change a DNS record
* Example of asking for a DNS change: Set DNS for snowflake.torproject.net to snowflake-01 host (#40716) · Issues · The Tor Project / TPA / TPA team · GitLab
* Caveat: we will have to use the same Let's Encrypt account as the old broker, because of CAA records:
* CAA record prevents renewing certs for snowflake.torproject.net, 02.snowflake.torproject.net, and snowflake-broker.torproject.net (#41462) · Issues · The Tor Project / TPA / TPA team · GitLab
* Figure out why acme/autocert has not renewed bridge TLS certificates since October (#40319) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
* David Fifield / autocert-account-id · GitLab
== Actions ==
== Interesting links ==
*
== Reading group ==
* We will discuss "Communication Breakdown: Modularizing Application Tunneling for Signaling Around Censorship" on May 30
* PoPETs Proceedings — Communication Breakdown: Modularizing Application Tunneling for Signaling Around Censorship
* 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-05-30
Last week:
- tor meeting
- s152 final and monthly reports
- commented on mv3 migration issue
This week:
- take a look at snowflake web and webext translations and best practices
- get around to backlog of MR reviews
- 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
- follow up on reported SQS errors
- update wasm-bindgen fork to fix some bugs and hopefully upstream changes
Needs help with:
dcf: 2024-05-30
Last week:
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-05-30
Last week:
- back from tormeeting and catching up
- plan rdsys deployment to replace BridgeDB (tpa/team#41613)
- look at onbasca issues failing to test bridges (onbasca#171)
- map existing monit alerts into prometheus blackbox exporter (not pushed yet)
Next week:
- use safeprom in rdsys (rdsys#203)
- add prometheus metrics to replace bridgedb metrics in rdsys (rdsys#188)
Shelikhoo: 2024-05-30
Last Week:
- [Merge Request Waiting] Add Container Image Mirroring from Tor Gitlab to Docker Hub(Add Container Image Mirroring from Tor Gitlab to Docker Hub (!280) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- [Merge Request Waiting] Snowflake Performance Improvement rev2 (Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- Chrome Manifest V3 transition research
- Vantage point maintaince
- merge request processing
- Merge request reviews
Next Week/TODO:
- Merge request reviews
onyinyang: 2023-05-30
Last week(s):
- continued key rotation implementation
- Fixed bug in blockage_migration protocol
Next week:
- Work on outstanding milestone issues: Lox Ready for Open Testing Call · Milestones · The Tor Project / Anti-censorship / lox · GitLab
- prepare for end to end testing of the Lox system with browser integration
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-05-16
Last weeks:
- Pion dtls have merged my PR for hooking of client hellos, server hellos and certificate request (Add handshake hooking capabilities by theodorsm · Pull Request #631 · pion/dtls · GitHub).
- Quick test with my mimicking library (GitHub - theodorsm/covert-dtls: Fingerprint-resistance module for pion/dtls.) with snowflake: promising results
- Writing for my thesis
Next weeks:
- Add hook to pion/webrtc so it can be used in snowflake.
- Further test and validate mimicked client hello with snowflake.
- Add randomized fingerprint
- Writing my thesis
- Might explore some stateful attacks/fingerprints
Help with:
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.