May 2024 - tor-project - lists.torproject.org

Are there countries where using Tor is illegal?
by Cristian Consonni 11 May '25

11 May '25

Hi, (Sorry if this question has already been asked in the past, feel free to point me to the relevant resources.) I know that the legal FAQs by the EFF state that: «we believe that running a Tor relay — including an exit relay that allows people to anonymously send and receive traffic — is legal under U.S. law.»[1] I also know there is a list of countries for which there is legislation that exclude communication service providers from liability. They are indicated in the Legal of the Tor Exit Guidelines page[2], they are USA, Germany, Netherlands, Austria, France, and Sweden. >From some articles in the press[3a][3b] it may be illegal - depending on how you interpret the wording[*] - to use Tor (and other technologies such as VPNs or proxies) in the UAE, with fines ranging in the millions of dirhams (hundreds of thousand of dollars). A couple of weeks ago it was discussed - on this list as well - that a law was introduced to the state parliament to ban Tor[4a][4b]. This follows a case of some months ago of a Russian Tor exit node operator being arrested for inciting mass riots and terrorism[4c][4d]. The idea of blocking VPNs or Tor seems to have already been considered in the past[4e]. This infographic about pluggable transports[5] suggests access to the Tor network is censored or limited in China, Uzbekistan, Iran, and Kazakhstan. Tor being censored orblocked may be different from it being illegal. What about other countries? Is there a place where I can find more about this topic? Cristian [1]: https://www.torproject.org/eff/tor-legal-faq.html.en [2]: https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines [3a]: http://www.emirates247.com/news/emirates/dh500-000-fine-if-you-use-fraud-ip… [3b]: http://news.softpedia.com/news/people-caught-using-vpns-tor-or-proxies-in-t… [*]: «Whoever uses a fraudulent computer network protocol address (IP address) by using a false address or a third-party address by any other means for the purpose of committing a crime or preventing its discovery» [4a]: https://lists.torproject.org/pipermail/tor-talk/2017-June/043293.html [4b]: https://trac.torproject.org/projects/tor/ticket/22055 [4c]: https://lists.torproject.org/pipermail/tor-talk/2017-April/043109.html [4d]: https://techcrunch.com/2017/04/24/dmitry-bogatov-tor-russia/ [4e]; https://torrentfreak.com/vpn-and-tor-ban-looming-on-the-horizon-for-russia-… [5]: https://www.torproject.org/images/PT/2016-07-how-to-use-PT.png

4 3

PSA: GitLab tokens expiring
by Antoine Beaupré 19 Sep '24

19 Sep '24

Hi, GitLab recently introduced a maximum lifetime for *all* access tokens. The change is discussed in a [blog post][1] from last October. Most importantly: > As of the 16.0 milestone (May 2023), we applied an expiration date of > May 14, 2024, to any personal, group, or project access token that > previously didn't have one. We first noticed this issue in [January][2] and have looked at mitigations, but ultimately, there's no good workaround short of "service accounts" which is some Open Core thing they are pushing onto us. There's some work upstream to make it easier to rotate tokens (which make the entire security measure moot in the first place, fun). So anyways. Your things might break now. And when you recreate the tokens, they will still have an upper time limit (one year, IIRC), so you will need to fix this again and again. I'm sorry. Further discussion in [2]. For now our approach is wait and see what gitlab.com is going to do, because this is breaking a *lot* of things in a lot of places, and I can't imagine they will just let the thing burn for that long. The actual recommended workaround from upstream now is to have a *pair* of tokens that renew each other but we have found that to be really impractical. So for now, we're just trying to document the tokens we have and how to refresh them, as an immediate mitigation. I encourage you to pay attention to the "your token has expired" notification as well. Good luck! [1]: https://about.gitlab.com/blog/2023/10/25/access-token-lifetime-limits/ [2]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41510 -- Antoine Beaupré torproject.org system administration

1 2

cohosh's monthly status report, December 2023
by Cecylia Bocovich 17 Jun '24

17 Jun '24

Hi! This is my status report for contract work done in December 2023. # Reputation-based bridge distribution - Continued Tor Browser integration work https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/116 - Debugged some issues with the lox distributor deployment https://gitlab.torproject.org/tpo/tpa/team/-/issues/41406 https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/40 https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/42 https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/43 # Snowflake - Fixed excessive logs of closed connections at the Snowflake proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Released version 2.8.1 of Snowflake - Provided further review of the SQS rendezvous method https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… # Domain Fronting Alternatives - Looked for cloud providers that offer domain fronting - Looked for good potential front domains for working cloud providers

2 6

Anti-censorship team meeting notes, 2024-05-30
by meskio 31 May '24

31 May '24

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: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?s… * Sponsor 96 <-- meskio, shell, onyinyang, cohosh * https://gitlab.torproject.org/groups/tpo/-/milestones/24 * Sponsor 150 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == * Add nginx rate limiting to address "TTP-03-001 WP1: Snowflake broker vulnerability" * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * It will be applied once we move the broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * 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? https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * 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: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40716 * Caveat: we will have to use the same Let's Encrypt account as the old broker, because of CAA records: * https://gitlab.torproject.org/tpo/tpa/team/-/issues/41462 * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * https://gitlab.torproject.org/dcf/autocert-account-id == Actions == == Interesting links == * == Reading group == * We will discuss "Communication Breakdown: Modularizing Application Tunneling for Signaling Around Censorship" on May 30 * https://petsymposium.org/popets/2024/popets-2024-0027.php * 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 - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 - 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 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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/snow… 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(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/… - [Merge Request Waiting] Snowflake Performance Improvement rev2 (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) - 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: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/milestones/1#tab-is… - 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!): 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-05-16 Last weeks: - Pion dtls have merged my PR for hooking of client hellos, server hellos and certificate request (https://github.com/pion/dtls/pull/631) - Quick test with my mimicking library (https://github.com/theodorsm/covert-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.

1 0

Tor Browser Weekly Meeting Rescheduled to 2024-05-28
by Richard Pospesel 27 May '24

27 May '24

Hey everyone, The 27th is an official TPI holiday, so we'll reschedule the weekly browser meeting to tomorrow (Tuesday, 28th of May) at 1500 UTC in #tor-meeting. Have a good holiday o/ best, -richard

1 0

Applications meeting 2024-05-20 cancelled
by Richard Pospesel 19 May '24

19 May '24

Our weekly meeting tomorrow (2024-05-20) is cancelled. We will continue as normal the following week. best, -richard

1 0

Anti-censorship team meeting notes, 2024-05-16
by onyinyang 16 May '24

16 May '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-05-16-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, May 30 16:00 UTC Facilitator: meskio ^^^(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: 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?s… * Sponsor 96 <-- meskio, shell, onyinyang, cohosh * https://gitlab.torproject.org/groups/tpo/-/milestones/24 * Sponsor 150 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * No meeting May 23, we are at the tormeeting == Discussion == - 0.4.7.x bridges removal (2024-05-16: 500 bridges running EOL): https://metrics.torproject.org/rs.html#search/type:bridge%20version:0.4.7%20 == Actions == == Interesting links == * https://t.me/s/tor_bridges https://t.me/s/vanilla_bridges * Telegram channels handing out bridges, found at https://ntc.party/t/7701/4 * https://github.com/jmwample/ptrs * By Jack Wampler, abstraction for building pluggable transports in Rust, obfs4 implementation, and "lyrebird" multi-transport binary. * https://github.com/theodorsm/covert-dtls * covertDTLS is a library inspired by uTLS for offering fingerprint-resistance features to pion/dtls. * https://opencollective.com/censorship-circumvention/projects/snowflake-dail… * https://www.youtube.com/watch?v=w3QVkw7Beqc * onyinyang gave a presentation on snowflake for TechSoup's Securing the Future panel discussion (along with FPF, Quiet and EFF) == Reading group == * We will discuss "Communication Breakdown: Modularizing Application Tunneling for Signaling Around Censorship" on May 30 * https://petsymposium.org/popets/2024/popets-2024-0027.php * 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-09 Last week: - Updated dependencies for various projects - Shadow simulations - https://github.com/cohosh/ptnettools - Lox-wasm integration test fixups - Opened an issue about Lox blockage migration This week: - upload new snowflake-webext version 0.8.2 to both Firefox and Chrome web stores - make changes to Lox encrypted bridge table - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 - follow up on reported SQS errors - update wasm-bindgen fork to fix some bugs and hopefully upstream changes - create a Lox test environment and instructions for the browser team - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42503 Needs help with: dcf: 2024-05-16 Last week: - snowflake azure cdn bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… - archived snowflake-webextension-0.8.2 https://archive.org/details/snowflake-webextension-0.8.2 Next week: - review snowflake unreliable+unordered data channels rev2 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to disable /debug endpoint on snowflake broker - move snowflake-02 to new VM Help with: meskio: 2023-05-16 Last week: - add journaling to rdsys persistency so data don't get lost if an unexpected restart (rdsys#201) - make errors explicit on distributor assignments in rdsys (rdsys#200) - deploy rdsys backend with persistency on bridge assignments - investigate problems with renovate (rdsys#202) Next week: - tormeeting Shelikhoo: 2024-05-16 Last Week: - [Merge Request Waiting] Add Container Image Mirroring from Tor Gitlab to Docker Hub(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/… - [Merge Request] Snowflake Performance Improvement rev2 (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) - Merge request reviews Next Week/TODO: - In person tor event! - Merge request reviews onyinyang: 2023-05-16 Last week(s): - Hyper upgrade and tokio upgrade - prepared and presented for techsoup panel https://www.youtube.com/watch?v=w3QVkw7Beqc - key rotation implementation This week: - key rotation implementation - begin implementing some preliminary user feedback mechanism to identify bridge blocking based on Vecna's work Next week: - FOMO and sadness :( - 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-05-16 Last weeks: - Pion dtls have merged my PR for hooking of client hellos, server hellos and certificate request (https://github.com/pion/dtls/pull/631) - Quick test with my mimicking library (https://github.com/theodorsm/covert-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: 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 -- --- onyinyang GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036

1 0

Interview week – UX meetings cancelled
by Duncan Russell 13 May '24

13 May '24

Hi everyone, Since it’s interview week for both the Product Designer and User Research Coordinator positions we’re hiring for, and our schedules are pretty full, we’ll be skipping the UX Team meeting today. Similarly, the UX Team may not be able to attend other meetings and 1:1s like normal, as we’re prioritizing time slots that work for our candidates. Thanks for your patience! Duncan

1 0

Anti-censorship team meeting notes, 2024-05-09
by Shelikhoo 09 May '24

09 May '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-05-09-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, May 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: shelikhoo == 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?s… * Sponsor 96 <-- meskio, shell, onyinyang, cohosh * https://gitlab.torproject.org/groups/tpo/-/milestones/24 * Sponsor 150 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * No meeting May 23, we are at the tormeeting == Discussion == * should we start assigning/distributing webtunnel bridges in the settings pool? * https://gitlab.torproject.org/tpo/web/community/-/issues/348#note_3026653 * we agree it makes sense to start collecting bridges in the settings pool * meskio will configure rdsys to so after deploying the persistency for bridges in rdsys * Reports that our CDN 77 front domains are blocked in Russia? * https://gitlab.torproject.org/tpo/applications/tor-browser/-/blob/tor-brows… * we'll keep an eye to see if there is some confirmation of the block and start looking for alternatives == Actions == == Interesting links == * https://petsymposium.org/popets/2024/popets-2024-0027.php * Communication Breakdown: Modularizing Application Tunneling for Signaling Around Censorship * "The Raceboat framework simplifies using signaling channels for low-bandwidth and/or latency-tolerant tasks like bridge distribution and authentication. ... We also have a suite of non-decomposed channels that have been wrapped to support the Raceboat channel APIs. These include wrappers around several higher-bandwidth direct channels (Obfs, Snowflake, and Balboa)..." * (NB the demonstration application is using Obfs and Snowflake as a rendezvous channel, not providing a rendezvous channel for them.) * https://github.com/tst-race/raceboat-pets2024 (currently empty) == Reading group == * We will discuss "Communication Breakdown: Modularizing Application Tunneling for Signaling Around Censorship" on May 30 * https://petsymposium.org/popets/2024/popets-2024-0027.php * 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-09 Last week: - Updated dependencies for various projects - Shadow simulations - https://github.com/cohosh/ptnettools - Lox-wasm integration test fixups - Opened an issue about Lox blockage migration This week: - upload new snowflake-webext version 0.8.2 to both Firefox and Chrome web stores - make changes to Lox encrypted bridge table - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 - follow up on reported SQS errors - update wasm-bindgen fork to fix some bugs and hopefully upstream changes - create a Lox test environment and instructions for the browser team - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42503 Needs help with: dcf: 2024-05-09 Last week: - allocated new VPS for snowflake broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - archived snowflake-webext 0.8.1 https://archive.org/details/snowflake-webextension-0.8.1 - posted questions about periodic(?) changes in the estimated number of users of the snowflake-01 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to disable /debug endpoint on snowflake broker - move snowflake-02 to new VM Help with: meskio: 2023-05-09 Last week: - test email distributor in rdsys (rdsys#186) - extract safelog and prometheus ronded metrics from snowflake into ptutil (snowflake#40354) - look into renovate errors in rdsys, but still not clue (rdsys!305) - update and merge the bridge distribution documentation in rdsys (rdsys!295) Next week: - improve privacy on rdsys metrics reusing snowflake techniques (rdsys#203) - produce the same metrics of BridgeDB in rdsys (rdsys#188) Shelikhoo: 2024-05-09 Last Week: - [Merge Request Waiting] Add Container Image Mirroring from Tor Gitlab to Docker Hub(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/… - [Merge Request Merged] Fix ipv6 connectivity with restricted address support(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transpo… - [Issue] Design a new Constructor Design for Snowflake (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) - [Dev] Snowflake Performance Improvement - Upgrade snowflake broker machine from Debian 10 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Merge request reviews - Merge request reviews Next Week/TODO: - Revise Snowflake Performance Improvement MR(cont.) - Merge request reviews onyinyang: 2023-05-02 Last week(s): - Responding to pre-existing MR reviews and other notifications/questions in gitlab This week: - attempt hyper upgrade and tokio upgrade Probably next week and beyond: - preparing for upcoming panel (maybe) - implement 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-04-25 Last weeks: - Extended Pion dtls library to support hooking of client hellos, server hellos and certificate request (PR: https://github.com/pion/dtls/pull/631) Fingerprint generation of firefox and chrome + mimicking using the client hello hook have been moved to its own repo: https://github.com/theodorsm/covertDTLS - Analyzed the snowflake captures done in "Snowflake Anonymous Network Traffic Identification" paper: no handshakes found, so not relevant for me - Verified the consistency of the fingerprint generation Next weeks: - Add hook to pion/webrtc so it can be used in snowflake. - Test and validate mimicked client hello with snowflake. - Add randomized fingerprint Help with: 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

1 0

cohosh's monthly status report, April 2024
by Cecylia Bocovich 06 May '24

06 May '24

1 0