August 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

Tor Browser Weekly Meeting re-scheduled to 2024-09-03
by Morgan 29 Aug '24

29 Aug '24

Hi Everyone, 2024-09-02 is a Tor holiday, so we will reschedule our weekly meeting to 2024-09-03 at 1500 UTC in #tor-meeting on OFTC IRC. Have a good long weekend! best, -morgan

1 0

Anti-censorship team meeting notes, 2024-08-29
by meskio 29 Aug '24

29 Aug '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-08-29-16.00.html And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, September 5 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?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == * what to do with moat bridges once we turn off BridgeDB? * The plan is to switch off BridgeDB on 2024-09-09. * Currently, moat bridges are reserved exclusively for moat. When rdsys stops distributing moat bridges, those bridges will get no new users. They will only have the users that already knew about them. (The "request bridge" button in Tor Browser uses moat, after the switch the button will get bridges from circumvention settings instead.) * meskio will configure rdsys so new bridges are not assigned to that distributor * meskio will monitor the usage of moat bridges to decide when to move them somewhere * During the transition period, the request bridge button will display a captcha (because Tor Browser is expecting one), but it will be a placeholder captcha: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/182 https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/617c6ced3900… == Actions == == Interesting links == == Reading group == * We will discuss "SpotProxy: Rediscovering the Cloud for Censorship Circumvention " on September 12 * https://www.cs-pk.com/sec24-spotproxy-final.pdf * https://censorbib.nymity.ch/#Kon2024b * 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-29 Last week: - went through massive todo backlog - dealt with breaking changes in KCP library - answered a bunch of Lox questions for integration work - cleared out review backlog 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-29 Last week: - reinitialized new snowflake broker VM https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - made minor revisions to snowflake broker installation guide https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… Next week: - archive snowflake webextension v0.9.0 (manifest V3) - 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-08-29 Last week: - don't distribute blocked-in bridges in moat and https (rdsys#204) - plan switch from BridgeDB to rdsys (rdsys#218) Next week: - add ipversion subscription to rdsys - be ready for the BridgeDB switch Shelikhoo: 2024-08-29 Last Week: - Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Release Manifest V3 - Merge request reviews Next Week/TODO: - Merge request reviews - snowflake broker update/reinstall: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… onyinyang: 2023-08-29 Last week(s): - continued with key rotation integration work - collected issues and TODOs for all Lox work that needs to be done before deployment Next week: - finish up key rotation integration work - add pref to handle timing for pubkey checks in Tor browser - update lox protocols to return duplicate responses for an already seen request - 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: 2024-08-22 Last weeks: - Expose hooks in pion/webrtc library Next weeks: - Update Snowflake to use latest pion upstream releases (DTLS: v3 and WebRTC: beta v4) - 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.

1 0

Anti-censorship team meeting notes, 2024-08-22
by Shelikhoo 22 Aug '24

22 Aug '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-08-22-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, August 29 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: 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 projects, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == - Snowflake debian package is outdated: - Is there a plan for updates? If AC-Team wants to increase the number of snowflake standalone proxies, we need to maintain deb packages. Should we start a call for maintainers? If so, what are the requirements? - MR: https://gitlab.torproject.org/tpo/web/community/-/merge_requests/386/diffs Please note that every new string added to the community portal is localized. If this is a temporary issue, I don't think it worth merging it. (gus) - we do plan to update it but it will take some months, there will be work as part of P146 * https://github.com/eyedeekay/blizzard/ "Blizzard: The I2P Snowflake donor Plugin" * should we ask them to use a diferent identifier than "standalone" to find them in the stats? * meskio will open an issue on their side to ask them to use a different name * https://github.com/eyedeekay/blizzard/issues/5 * meskio has archived https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * hasn't being updated in 3 years * no complains for now * PT binary size updates * https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42607 * Remove conjure from android as a last resort * Manifest V3 Deployment pending, will proceed on next week == 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://www.usenix.org/conference/usenixsecurity24/presentation/xue-bridging * 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-22 Last week: - worked with applications team on reducing PT binary size - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re… - lots of reviews and gitlab todo items - ttp grant writing for conjure work This week: - finish backlog of reviews and todo items - 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-22 Last week: - presented Snowflake research at USENIX Security 2024 https://www.usenix.org/conference/usenixsecurity24/presentation/bocovich https://www.bamsoftware.com/talks/snowflake-usenix2024/ - commented on exposing pollInterval in snowflake proxy API https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - linked past "anti-fraud" issue to recent GFWeb research https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… - commented on adjusting copy buffer size in snowflake proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - sent email to authors to try and resolve obfs4/lyrebird naming confusion https://lists.torproject.org/pipermail/anti-censorship-team/2024-August/000… 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: - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2023-08-22 Last week: - deploy email distributors in rdsys in parallel with BridgeDB (rdsys#187) - test our new deployments - test ipv6 and webtunnel fake descriptors in rdsys-test (rdsys!365) - restart onionsprouts bot and investigate why it was not working (onionsproutsbot#62) - archive snowflake-mobile repo (snowflake-mobile#23) - investigate why gettor is not updating github and gitlab (rdsys#189) Next week: - don't distribute blocked-in bridges in moat and https (rdsys#204) - gettor updater should send links to github/gitlab (rdsys#189) Shelikhoo: 2024-08-22 Last Week: - Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Merge request reviews Next Week/TODO: - Merge request reviews - Release Manifest V3 onyinyang: 2023-08-22 Last week(s): - continue with key rotation integration work Next week: - continue with key rotation integration work - collect issues and TODOs for all Lox work that needs to be done before deployment - 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: 2024-08-22 Last weeks: - Expose hooks in pion/webrtc library Next weeks: - Update Snowflake to use latest pion upstream releases (DTLS: v3 and WebRTC: beta v4) - Test Snowflake fork with covert-dtls - Condensing thesis into paper Help with: - Feedback on thesis Facilitator Queue: meskio onyinyang 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

Anti-censorship team meeting notes, 2024-08-15
by onyinyang 19 Aug '24

19 Aug '24

Hey everyone! Sorry for the delay in getting the meeting notes sent out from Thursday. Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-08-15-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, August 22 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: 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 projects, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == == Actions == == Interesting links == * It's important to choose good function names – you never know when one will be immortalized in print! * https://cs.uwaterloo.ca/~dbarrada/papers/kon_sec24.pdf#page=8 * "We also added a /add handler to the proxy's HTTP server to enable direct reception of SDP offers from clients, using the existing makePeerConnectionFromOffer function for client connection." * makePeerConnectionFromOffer has been there since 2017: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * https://github.com/unknown-cstdio/iceball "A fork of snowflake that works as standalone proxy hosted in spot vm" * https://github.com/xvzc/SpoofDPI * https://github.com/eyedeekay/blizzard/ "Blizzard: The I2P Snowflake donor Plugin" == 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/attachments/202… * 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-10 Last week: - opened minor issue for chaning error messages from %v to %w https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - reviewed snowflake unreliable+unordered data channels rev2 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - snowflake azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… 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: - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2023-08-15 Last week: - partially AFK - tag a new rdsys version 0.13 - find issues with rdsys and tag 0.13.1 (rdsys!357) - deploy https distributor (rdsys#214) - prepare and give a talk about S96 Next week: - deploy email distributors in rdsys in parallel with BridgeDB (rdsys#187) - test our new deployments Shelikhoo: 2024-08-01 Last Week: - Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Merge request review - Merge request reviews Next Week/TODO: - Merge request reviews - (AFK: DWebCamp) - Usenix Security Conference onyinyang: 2023-08-15 Last week(s): - vacation - continued with key rotation integration work Next week: - 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: 2024-08-15 Last weeks: Next weeks: - Update Snowflake to use latest pion upstream releases (DTLS: v3 and WebRTC: beta v4) - 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 -- --- onyinyang GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036

1 0

ebanam's user support report for July 2024
by ebanam 15 Aug '24

15 Aug '24

Hello everyone! This is the user support report for the month of July. We saw another uptick in tickets from Chinese speaking users which can be attributed to the amazing outreach work[0]! Most of my work last month consisted of helping users in regions where Tor is censored which usually involves helping with instructions on how to use bridges, snowflake and other censorship circumvention methods, accessing Tor mirror sites, using GetTor as an alternative way to fetch Tor Browser binaries and general troubleshooting. As an interesting fact, July also saw more tickets coming in from email than Telegram! :) # Frontdesk (email support channel) * 546(↓) RT tickets created * 602(↑) RT tickets resolved Tickets by numbers: 1. 343(↑) RT tickets: private bridge requests from Chinese speaking users. 2. 139(↑) RT tickets: circumventing censorship in Russian speaking countries. 3. 4(↑) RT tickets: Circumventing censorship with Tor in Farsi. 4. 4 RT tickets: Reports of websites blocking Tor. 5. 4 RT tickets: 'New Identity' feature is not working in latest versions of Tor Browser for Android.[1] 6. 3 RT tickets: Questions about the banner warning users about the upcoming EOL for Win ≤8.1 and macOS ≤10.14.[2] Highlighting some other topics we received questions and feedback: 7. 3 RT tickets: Help with troubleshooting Tor Browser install on Windows. 8. Instructions and help with verifying Tor Browser's PGP signature. # Telegram, WhatsApp and Signal Support channel * 498(↓) tickets resolved Breakdown: * 476(↓) tickets on Telegram * 20(-) tickets on WhatsApp * 2(↓) ticket on Signal Tickets by numbers: 1. 286(↓) tickets: circumventing censorship in Russian speaking countries. 2. 52(↑) tickets: circumventing censorship with Tor in Farsi. 3. 23(↓) tickets: private bridge requests from Chinese speaking users. 4. 20 tickets: helping users on iOS, using Onion Browser or Orbot, to use censorship circumvention methods. Highlighting some other topics we received questions about: 5. 6 tickets: instructions on how to get Tor Browser binaries from GetTor. 6. 2 tickets: Reports of fake Tor apps in iOS App Store. 7. Help with troubleshooting Tor Browser install on macOS. # Highlights from the Tor Forum 1. Element's WebApp not working with Tor Browser.[3] 2. Importing browser data into Tor Browser.[4] e. [0]: https://github.com/torproject/tor4zh [1]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42589 [2]: https://tb-manual.torproject.org/installation/#system-requirements [3]: https://forum.torproject.org/t/app-element-io-broken-after-update/13548 [4]: https://forum.torproject.org/t/not-able-to-import-browsing-data-passwords-a…

2 1

Anti-censorship team meeting notes, 2024-08-08
by meskio 08 Aug '24

08 Aug '24

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?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == 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/000… * 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-co… - 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/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-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/snow… - 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.

1 0

Rhatto's Monthly Status Report, July 2024
by rhatto 01 Aug '24

01 Aug '24

Hi all :) This is my monthly status report for July 2024 with the main relevant activities I have done or was involved during the period. ## 1. Development * Onionbalance: the v2 codebase was finally removed (thanks @federico!): https://gitlab.torproject.org/tpo/onion-services/onionbalance/-/merge_reque… ## 2. Support * Update your bookmarks! The Onion Service Ecosystem docs has a new canonical URL: https://onionservices.torproject.org Thanks gus and lavamind for support and advice for finding a new location for these docs. Details at https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/1 ## 3. Organization * Most of my time was used in improving workflows and on general planning. * Ongoing sponsored work with deployment, maintenance and monitoring of Onion Services. -- Silvio Rhatto pronouns he/him

1 0

Anti-censorship team meeting notes, 2024-08-01
by Shelikhoo 01 Aug '24

01 Aug '24

Hey everyone! Here are our meeting logs: mailto:tor-project@lists.torproject.org?subject=%5Btor-project%5D%20Anti-censorship%20team%20meeting%20notes%2C%202024-08-01 And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, August 8 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: 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 projects, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == * Rename Sponsor to Project * Sponsors are now named Project * currently we are working on Project 158 or P158... == 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 * 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-01 Last week: - attended FOCI and PETS This week: - review MV3 changes - 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-co… - 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/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-08-01 Last week: - check if lyrebird reduces size removing old PTs (it doesn't that much) (lyrebird#40016) - add dkim verification to rdsys email distributor (rdsys#211) - plan rdsys deployment replacing BridgeDB - finish the work on Sponsor 96 final report Next week: - distribute IPv6 bridges in rdsys (bridgedb#40071) Shelikhoo: 2024-08-01 Last Week: - Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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-07-11 Last weeks: - Completed my master thesis (https://theodorsm.net/thesis) - Had some time off Next weeks: - Wait for pion upstream releases - 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

1 0