Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-12-21-15.57.html
And our meeting pad:
Anti-censorship
···
--------------------------------
Next meeting: Thursday, January 11 16:00 UTC
Facilitator: shelikhoo
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 ==
* No meetings December 28, neither January 4
== Discussion ==
* Tor Browser users on Windows 7/8 have started having problems with PTs because Go 1.21 removed support
* tor-browser-build now uses Go 1.20 for everything except Snowflake: Bug 41053: Use Go 1.20 on Windows, except for Snowflake (22731a74) · Commits · The Tor Project / Applications / tor-browser-build · GitLab
* we'll try to fix the issue by providing our own random source and see how invasive si the change
* manifest v2 deprecation in browsers and snowflake webextension
* Migrate to Manifest V3 (#29) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake WebExtension · GitLab
* Resuming the transition to Manifest V3 | Blog | Chrome for Developers
* google chrome will stop supporting mv2 June 2024
* will the snowflake webextension stop working? do we want to do something? or just recommend firefox?
* cohosh will look into this next year and see how hacky needs to be the solution
* validation for bridgelines
* Add validation and improve the formatting of manually added bridge lines (#41913) · Issues · The Tor Project / Applications / Tor Browser · GitLab
* there is no fingerprint in the conjure bridgeline we shared, and we have some doubts if giving an error on bridgelines without fingerprint in TB or not
* we'll include a fingerprint in future conjure bridgelines
* and we'll not give an error for now on missing fingerprint bridgelines
== Actions ==
== Interesting links ==
== 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): 2023-12-21
Last week:
- debugged some issues with the lox distributor deployment
- Add proxypass rule for lox distributor on rdsys-frontend-01 (#41406) · Issues · The Tor Project / TPA / TPA team · GitLab
- lox tor browser integration work
- removed extra log message for snowflake connection closure
- Excessive logging in ordinary, non-verbose, log ("Proxy connection closed") (#40310) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- worked on finding alternative domain fronting providers
This week:
- conjure bridge maintenance
- review SQS rendezvous
Needs help with:
dcf: 2023-12-14
Last week:
- opened issue to upgrade snowflake bridges to 0.4.8.10 Upgrade tor on snowflake bridges to 0.4.8.10 (#40311) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- azure CDN bookkeeping Changes · Snowflake costs · Wiki · The Tor Project / Anti-censorship / Team · GitLab
Next week:
- upgrade snowflake bridges to 0.4.8.10 Upgrade tor on snowflake bridges to 0.4.8.10 (#40311) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- review draft MR for unreliable data channels Draft: Unreliable+unordered WebRTC data channel transport for Snowflake (!219) · 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
Before EOY 2023:
- move snowflake-02 to new VM
Help with:
meskio: 2023-12-21
Last week:
- grant writing
Next week:
Shelikhoo: 2023-12-21
Last Week:
- Work on snowflake performance improvement (WIP): Files · dev-udp-performance-rebased-exp · shelikhoo / Snowflake · GitLab
Draft: Unreliable+unordered WebRTC data channel transport for Snowflake (!219) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- Analysis of S150 HTTPS distributors design: Implement HTTPS distributor with comparable feature set to bridgedb implementation (#191) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
- Merge request reviews
Next Week/TODO:
onyinyang: 2023-12-21
Last week(s):
- Worked on Telegram bot: Add Lox invitation to Telegram bot (!223) · Merge requests · The Tor Project / Anti-censorship / rdsys · GitLab
- Added several additional Lox wasm stubs needed by applications team
This week:
- Finish up Telegram bot dev
- Continue to support Lox wasm stubs as needed
- attempt hyper upgrade again
- Holiday!
(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?
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.