[tor-project] Anti-censorship team meeting notes, 2023-09-14
onyinyang
onyinyang at torproject.org
Thu Sep 14 16:25:14 UTC 2023
Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-09-14-15.58.html
And our meeting pad:
Anti-censorship
--------------------------------
Next meeting: Thursday, Sep 21 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: onyinyang
== 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 sponsors, 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
* Sponsor 96 <-- meskio, shell, onyinyang, cohosh
* https://gitlab.torproject.org/groups/tpo/-/milestones/24
* Sponsor 139 <-- hackerncoder, irl, joydeep, meskio, emmapeel
working on it
* https://pad.riseup.net/p/sponsor139-meeting-pad
== Announcements ==
== Discussion ==
== 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-09-14
Last week:
- posted shadow + PT guide on the forum
-
https://forum.torproject.org/t/experimenting-with-tor-pluggable-transports-in-shadow/9117
- followed up on a report that snowflake is being blocked in russia
-
https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40030#note_2941589
-
https://ntc.party/t/ooni-shows-blocking-on-snowflake-in-select-isps-in-russia-since-2023-02/5648
- opened issue with OONI for adding probe-engine version
filter to MAT
- https://github.com/ooni/probe/issues/2533
- filed an upstream issue with conjure on not relying on the
replace directive
- https://github.com/refraction-networking/conjure/issues/226
- updated gotapdance library version in Conjure PT to fix a
stall issue
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/merge_requests/15
- worked on deploying lox distributor
-
https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/167
This week:
- finish deploying lox distributor
- map out next steps for conjure work
- followup on conjure reliability issues
- visualize and write up some snowflake shadow simulation results
Needs help with:
dcf: 2023-09-13
Last week:
- snowflake CDN bookkeeping
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=4a6fa36c5bfc350fa01a5fe774b297f6fcddb51c
Next week:
- revise encapsulation.ReadData redesign to return an error in
the case of a short buffer
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/154
- 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
Help with:
meskio: 2023-09-07
Last week:
- vacation :)
- coordinate with TPA to get a VM for a rdsys staging server
- review lyrebird merge requests
Next week:
- deploy the rdsys staging server
Shelikhoo: 2023-09-07
Last Week:
- [Merge Request Awaiting] Add SOCKS5 forward proxy support to
snowflake (snowflake!64) (stalled)
- logcollector alert system
- Add Remote Network Address Mapping in HTTP Upgrade Transport
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/merge_requests/17)
- Merge request reviews
Next Week/TODO:
- Add Remote Network Address Mapping in HTTP Upgrade Transport
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/merge_requests/17)
(Continue)
- Release new version of snowflake
- Merge request reviews
onyinyang: 2023-09-14
Last week(s):
- Continued updating dependencies, including:
- aes-gcm:
https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/35
- base64:
https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/36
- found issues with zkp library and am working on
determining how to best handle those going forward, fixes are required
to keep other dalek-cryptography libraries up to date:
https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/51
- Started on adding metrics
This week:
- Update rdsys API at the /resources endpoint to meet the needs
of Lox
- Continue with adding metrics
(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?
--
---
onyinyang
GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x156A6435430C2036.asc
Type: application/pgp-keys
Size: 6206 bytes
Desc: OpenPGP public key
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20230914/f9d3f3a0/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20230914/f9d3f3a0/attachment.sig>
More information about the tor-project
mailing list