Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-08-08-16.00.html
And our meeting pad:
Anti-censorship
--------------------------------
Next meeting: Thursday, August 16 16:00 UTC
Facilitator: onyinyang
^^^(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:https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards
* The anti-censorship team's wiki page:
*
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home
* Past meeting notes can be found at:
* https://lists.torproject.org/pipermail/tor-project/
* Tickets that need reviews: from projects, we are working on:
* All needs review tickets:
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&assignee_id=None
* Project 158 <-- meskio working on it
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Project%20158
== Announcements ==
*
== Discussion ==
* https://github.com/pion/dtls/releases/tag/v3.0.0
== Actions ==
== Interesting links ==
== Reading group ==
* We will discuss "Bridging Barriers: A Survey of Challenges and
Priorities in the Censorship Circumvention Landscape" on Aug 22, 2024
* PDF at
https://lists.torproject.org/pipermail/anti-censorship-team/2024-August/000346.html
* 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-08-08
Last week:
- reviewed snowflake mv3 changes
- checked on snowflake proxy counts
-
https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/142
- looked into logged pion library errors
This week:
- take a look at snowflake web and webext translations and best
practices
- make changes to Lox encrypted bridge table
-
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147
Needs help with:
dcf: 2024-08-01
Last week:
- snowflake azure CDN bookkeeping
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=900bf4113a94da9d6e0425e440462af74c5fd011
- attended FOCI and PETS, had conversations with people from
Raceboat, TorKameleon, FEPs
- commented on PT STATUS incompatibility with Arti
https://gitlab.torproject.org/tpo/core/torspec/-/issues/267#note_3054205
Next week:
- review snowflake unreliable+unordered data channels rev2
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
- open issue to have snowflake-client log whenever KCPInErrors
is nonzero
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40262#note_2886018
- parent:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40267
- 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
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349
meskio: 2023-08-08
Last week:
- distribute IPv6 bridges in rdsys (rdsys#215)
- add TLS_ERROR support to bridgestrap (bridgestrap#45)
- update lyrebird in Tor Browser to include IPv6 support in webtunnel
(tor-browser-build!1012)
- report a different implementation for snowflake client and server
(snowflake!348)
Next week:
- deploy email and https distributors in rdsys in parallel with
BridgeDB (rdsys#187 rdsys#214)
Shelikhoo: 2024-08-01
Last Week:
- Chrome Manifest V3 transition:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29#note_3035763
- Merge request review
- Merge request reviews
Next Week/TODO:
- Merge request reviews
- (AFK: DWebCamp)
- Usenix Security Conference
onyinyang: 2023-08-01
Last week(s):
- continue with key rotation integration work
- fix lastPassed issue in rdsys (or lox if
Next week:
- vacation
- continue with key rotation integration work
- add trusted invitation logic to tor browser integration:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974
- Work on outstanding milestone issues:
in particular:
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69
- 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!):
https://pad.riseup.net/p/tor-ac-community-azaleas-room-keep
- 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-08-08
Last weeks:
- Vacation
Next weeks:
- Update Snowflake to use latest pion upstream releases
(DTLS: v3 and WebRTC: v4)
- Test Snowflake fork with covert-dtls
- Condensing thesis into paper
Help with:
- Feedback on thesis
Facilitator Queue:
onyinyang meskio shelikhoo
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.
signature.asc
Description: signature
_______________________________________________ tor-project mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
