Hey everyone!

Here are our meeting logs:

http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-10-24-16.00.html 

And our meeting pad:

Anti-censorship
--------------------------------

Next meeting: Thursday, October 31 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 ==

        * Snowflake broker transition still pending.

        * Adding a snowflake transport to lyrebird
                * 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/merge_requests/63
                * Squash PTs into Lyrebird: 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/40015
                * TODOs: add proxy support and event logging
                * We decide is a good idea to integrate the snowflake client 
into lyrebird
                * we are not removing the snowflake client from the snowflake 
proyect for now, we'll keep both until it becomes a burden.
                * only the snowflake client will be integrated in lyrebird, not 
the server

        * pion/webrtc v4 release is out
                * it has support to integrate with covert-dtls
                * on the beta testing there were some issues, we'll need to 
check if it works with the release or it needs work

        * split broker into components
                * there is an old MR with a WIP version of this change
                * we are still interested on it
                * cohosh will check with arlo if he can continue that work or 
we'll close it for now


== Actions ==

== Interesting links ==

        * OS image with remote access (for providing vantages in censored 
regions), with built-in circumvention as an incentive to run it.
                * https://github.com/ValdikSS/hoogmoon-testing
                * https://ntc.party/t/5939
        * Tor 0.4.8.13 was released with STATUS TYPE=version support so PTs can 
report their version
                * 
https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.8/ReleaseNotes
        * https://github.com/refraction-networking/uquic
                * "Low-level access to the QUIC Initial Packet for mimicry 
purposes, hard fork of quic-go."

== 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-10-24
        Last week:
            - finished IPtProxy rewrite
                - https://github.com/tladesignz/IPtProxy/pull/61
            - added a snowflake transport into lyrebird
        
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/merge_requests/63
            - added OnClientConnected callback to the snowflake proxy
        
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40402
            - fixed a panic when SnowflakeConn is closed more than once
        
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40405
            - merged some dependency updates
            - lots of reviews
        This week:
            - continue work on adding a snowflake transport to lyrebird
            - finish snowflake dependency upgrades that were causing problems
            - 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:
            - abandoned snowflake MR
                - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/39

dcf: 2024-10-24
        Last week:
                - reviewed merge request to remove inner pollInterval in 
snowflake standalone proxy 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/414#note_3096735
                - reviewed merge request to pre-resolve snowflake relay URL 
hostnames to check if they are local 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/413#note_3096742
                - answered a question about domain fronting with Google and 
meek 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek/-/issues/40005#note_3096753
                - commented on merge request to guess an unrestricted NAT type 
on the first attempt if unknown 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/392#note_3096759
                = made additional comments on merge request to run Manifest 
Version 3 snowflake proxy while the browser is closed 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/merge_requests/83#note_3096761
                - commented on a double Close panic in the snowflake client 
library 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40405#note_3098748
        Next week:
                - comment on updates to unreliable snowflake transport 
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
Help with:
                - tell me when to restart the brokers for 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349

meskio: 2024-10-24
    Last week:
        - bring back QR coes for email bridges (rdsys#244)
        - add QR codes to Telegram distributor (rdsys#243)
        - debug gettor telegram issues (onionsproutsbot#63)
    Next week:
        - update snowflake proxy debian package

Shelikhoo: 2024-10-24
    Last Week:
         - [Next Action Pending] snowflake broker update/reinstall(cont.):
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349#note_3026336
         - [Awaiting Review] Unreliable+unordered WebRTC data channel transport 
for Snowflake rev2 (cont.)( 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
 ) improvements 
         - [Awaiting Input] Review CI: fix `latest` container image tag.  
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/408#note_3089605
         - Update vantage point image on cnnext, russia
         - Prepare State of the Onion script/slide
            - Merge request reviews
    Next Week/TODO:
        - Merge request reviews
         - Unreliable+unordered WebRTC data channel transport for Snowflake 
rev2 (cont.) ( 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
 ) improvements
         - Prepare State of the Onion script/slide
         - Work on finishing snowflake container release(and fix the comments)
         - Work on Parpare DeploymentTool for Publishing  
https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/logcollector-admin/-/issues/9

onyinyang: 2024-10-24
        Last week(s):
                - MR for troll-patrol integration for Lox bridge blockage 
detection
                        - 
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/263
        Next week:
                - fix up some troll-patrol functionality
                        - extra-info collecting/parsing should work correctly 
and exit gracefully
                        - maybe make blockage detection in extra info a bit 
more reasonable
                                - prevent evaluation before stats are published
                - implement and deploy test distributor
                - update lox protocols to return duplicate responses for an 
already seen request
                - Work on outstanding milestone issues: 
                        in particular: 
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69
                        - key rotation automation
                
                Later:
                pending decision on abandoning lox wasm in favour of some kind 
of FFI? 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
                        - add pref to handle timing for pubkey checks in Tor 
browser 
                        - add trusted invitation logic to tor browser 
integration:
                        
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974
                - 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!): 
                - 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: 2024-10-24
                Last weeks:
                        - Adjusting to post-student life
                        - Testing out beta releases of pion dtls and webrtc
                Next weeks:
                        - Update Snowflake to use latest pion upstream releases
                        - Test Snowflake fork with covert-dtls
                        - Condensing thesis into paper
                Help with:
                        - Feedback on thesis
                        
                        

Facilitator Queue:
                 onyinyang shelikhoo 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.

Attachment: signature.asc
Description: signature

_______________________________________________
tor-project mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project

Reply via email to