- tor-project - lists.torproject.org

(fyi) Outreachy contribution period (December 2021 - March 2022)
by gus 12 Oct '21

12 Oct '21

Hi, The Community team submitted a new Outreachy[1] project:"Mapping values and motivations of the Tor network's relay operators". You can read the complete project here[2]. The contribution period started this week and you will see some applicants on IRC during this month. You can help redirecting them to #tor-www channel and/or teaching them how to configure Element/matrix client, so they can follow up our discussions. cheers, Gus [1] Outreachy: https://www.outreachy.org/ [2] https://gitlab.torproject.org/tpo/community/team/-/issues/46 -- The Tor Project Community Team Lead

1 0

OONI Monthly Report: July 2021
by Maria Xynou 12 Oct '21

12 Oct '21

Hello, Hope you're all doing well. These days we're primarily supported by the DRL, which is why we do quarterly reporting. That said, we'd like to share monthly updates from the OONI team with the community, hence our July 2021 report shared below. I'll also follow-up to share our August and September 2021 reports. *# OONI Monthly Report: July 2021* Throughout July 2021, the OONI team worked on the following sprints: * Sprint 43 - Confused Kraken (5th - 18th July 2021) * Sprint 44 - Dancing Sirens (19th - 31st July 2021) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Published research report on media censorship in Azerbaijan* In collaboration with Azerbaijan Internet Watch, we co-published a new research report titled: "Media censorship in Azerbaijan through the lens of network measurement". Our report is available through the following sites: * OONI: https://ooni.org/post/2021-azerbaijan/ * Azerbaijan Internet Watch: https://www.az-netwatch.org/news/media-censorship-in-azerbaijan-through-the… As part of our analysis of OONI measurements collected from Azerbaijan between January 2020 to May 2021, we found: ** Blocking of independent news media and circumvention tool websites. *Throughout the testing period, several independent news media and circumvention tool sites presented HTTP failures caused by connection timeouts. This suggests the potential use of Deep Packet Inspection (DPI) by ISPs in Azerbaijan. ** Attempts to block Tor and Psiphon.* ISPs in Azerbaijan attempted to block Tor and Psiphon amid the 2020 Nagorno-Karabakh war. However, both attempts appear to have been quite ineffective, as these tools have built-in circumvention fallback options. Tor Metrics also show a spike in usage during this period. ** Temporary blocking of social media amid 2020 Nagorno-Karabakh war.* Between September 2020 to November 2020, several social media websites presented the same HTTP failures (as news media and circumvention tool sites), while the testing of WhatsApp and Telegram presented signs of TLS level interference. ** Variance of censorship across networks.* ISPs in Azerbaijan appear to be adopting similar censorship techniques. However, censorship varies from network to network, as different ISPs block different websites and apps at different moments in time. *## Hosted a 3-day online OONI Partner Training* Between 5th-7th July 2021, we organized and hosted a 3-day online OONI Partner Training for our partners from 9 countries in Asia and the Middle East (https://ooni.org/partners) The event also included participants from international organizations, Reporters Without Borders and Human Rights Watch. Overall, 45 participants from 23 digital rights organizations attended this 3-day OONI Partner Training. To ensure a safe, friendly, and pleasant experience for all during the training, we asked all participants to adhere to OONI’s Code of Conduct ( https://github.com/ooni/ooni.org/blob/master/CODE_OF_CONDUCT.md) and to follow the Chatham House Rule on Privacy ( https://www.chathamhouse.org/about-us/chatham-house-rule) The goal of the OONI Partner Training was to share knowledge and skills on OONI’s censorship measurement tools, dataset, and methodologies to enable their use as part of research and advocacy efforts. We also aimed to collect feedback on how to improve OONI tools to better serve community needs. The event was facilitated entirely online (over Zoom), and entailed two 1.5 hour sessions per day (over 3 days). We facilitated the following 6 sessions as part of the 3-day OONI Partner Training: 1) Information Controls Around the World 2) Introduction to Internet Censorship 3) Using the OONI Probe Apps 4) Using OONI Run to coordinate censorship testing 5) Using OONI Explorer to find censorship measurement data 6) Interpreting OONI data We published a blog post which shares further information about the training sessions and overall event: https://ooni.org/post/ooni-partner-training-2021/ At the end of the 3-day training, we shared a post-training survey ( https://forms.gle/n62ktvcfD1u7DgPMA) with all participants to collect their feedback on how to improve future OONI training events. To support ongoing learning, we shared a Resources document ( https://ooni.org/documents/2021-ooni-partner-training-resources/ooni-resour…) with participants that includes OONI-related resources, as well as other resources (on censorship circumvention, digital security, monitoring internet connectivity shutdowns, and other censorship measurement platforms) that participants expressed interest in. We also shared OONI training slides ( https://docs.google.com/presentation/d/1mpoB_ObjMH0EWQhyZRpKWnwl5PUHf-Sa5PK…) that they can use (and customize) to facilitate OONI workshops for their communities. In July 2021, we issued OONI certificates for participants who attended our 2 OONI Partner Training events ( https://ooni.org/post/ooni-partner-training-2021/) *## Blocking of social media in Cuba amid protests* On 12th July 2021, Cuba started blocking access to online social media services amid anti-government protests. On the same day, we reported on the blocking of the WhatsApp, Telegram and Signal apps based on real-time data collected from Cuba: https://twitter.com/OpenObservatory/status/1414622433156476930 OONI data on the blocking of WhatsApp, Telegram, and Signal in Cuba is available through the following links: * Signal: https://explorer.ooni.org/search?until=2021-07-13&since=2021-06-12&probe_cc… * Telegram: https://explorer.ooni.org/search?until=2021-07-13&since=2021-06-12&probe_cc… * WhatsApp: https://explorer.ooni.org/search?until=2021-07-13&since=2021-06-12&probe_cc… The blocking of the Signal Private Messenger App in Cuba was detected based on OONI’s new Signal test (https://ooni.org/nettest/signal) which was shipped in April 2021. Our new Signal test also contributes ongoing measurements on the blocking of the Signal app in Iran ( https://explorer.ooni.org/search?until=2021-07-30&since=2021-06-30&probe_cc…) and China ( https://explorer.ooni.org/search?until=2021-07-30&since=2021-06-30&probe_cc…) among other countries. We recently added support to our backend for the adjustment of URL priorities (as part of URL prioritization work). This allows us to specify in which countries certain URLs should have higher priority for testing and empowers us to dynamically adjust these in response to censorship events. Following the social media blockade in Cuba, we bumped up the priority of the GRP (Social Media) category code (from the Citizen Lab test lists: https://github.com/citizenlab/test-lists/blob/master/lists/00-LEGEND-new_ca…) on 14th July 2021 for Cuba. This enabled us to detect (and collect measurements on) the temporary blocking of facebook.com in Cuba ( https://explorer.ooni.org/search?until=2021-07-30&since=2021-06-30&probe_cc…) It also enabled us to detect (and collect measurements on) the blocking of tiktok.com in Cuba ( https://explorer.ooni.org/search?until=2021-07-30&since=2021-06-30&probe_cc…) Following the prioritization of URLs from this category, we were able to collect a total of 960 measurements for the GRP category code from Cuba. OONI’s response to the recent social media censorship events in Cuba has received the following press coverage: https://www.nbcnews.com/tech/tech-news/cubans-protest-government-cracks-int… https://www.wsj.com/articles/internet-powered-mass-protests-in-cuba-then-th… https://cpj.org/2021/07/journalists-detained-and-harassed-internet-disrupte… Cuban organization, YucaByte, published a report documenting the censorship events in Cuba amid the protests (citing OONI data): https://www.yucabyte.org/2021/07/12/11j-internet-cuba/ *## OONI Probe Mobile* We released OONI Probe Android 3.2.0 ( https://github.com/ooni/probe-android/releases/tag/v3.2.0) and OONI Probe iOS 3.2.0 (https://github.com/ooni/probe-ios/releases/tag/v3.2.0) This release includes: * A reminder encouraging users to enable automated testing * A badge to indicate that a proxy is being used * Support for minimizing a running test * Support for validating URLs shared via OONI Run ( https://github.com/ooni/probe-android/pull/443) * Font size fix on iPhone SE ( https://github.com/ooni/probe-ios/commit/8f3fcf90b286e7e9ffee18c4b8ea223f2f… ) These features were added to encourage users to enable automated testing and contribute measurements regularly. In response to community requests, we also added a badge to indicate that a proxy is being used, and we added support for minimizing a running test (enabling users to make use of other features of the OONI Probe app while a test is running). *## OONI Probe Desktop* We released OONI Probe Desktop 3.5.2: https://github.com/ooni/probe-desktop/releases/tag/v3.5.2 This release fixed a critical bug in autoupdate which prevented downloading and installing updates. In July 2021, we provided mentorship to Google Summer of Code (GSoC) student Shivam Shekhar, who worked on implementing end-to-end tests for OONI Probe Desktop. In particular, he implemented tests for the code responsible for running the OONI Probe command line tool ( https://github.com/ooni/probe-desktop/pull/231) Moreover, tests were implemented for several UI components as part of the following pull request: https://github.com/ooni/probe-desktop/pull/229 *## Progress on browser-based OONI Probe* We made some progress on the browser based implementation of OONI Probe. Specifically, we integrated React into the project so that we can reuse the existing components we developed for web based projects (see: https://github.com/ooni/probe-web/commit/a9da79b9384f7f496bb3278a4a00cacc39…) We also did some research into how to tweak the fetch API calls so that we minimise the amount of sensitive data transmitted to the measured web hosts (see: https://github.com/ooni/probe-web/commit/5bf0ba41a9e2464da070ba21f4463ddce2… ). *## Expanding OONI censorship measurement methodologies* We looked into alternative TLS stacks that we could use for performing measurements, but potentially also for communicating with our backend services. This was prompted by the fact that we have noticed that some countries (such as Iran) will implement blocking of all TLS connections that present a specific fingerprint. In particular, we looked into https://github.com/refraction-networking/utls and researched how we could go about integrating it into the OONI codebase, as well as what work would be necessary to update it to the latest version of the golang TLS library. This work is documented through the following ticket: https://github.com/ooni/probe/issues/1702 In July 2021, we provided mentorship to Google Summer of Code (GSoC) student Kathrin Elmenhorst, with whom we collaborated on making several improvements to how errors are handled inside of our measurement engine. Specifically, we ensured that it’s possible to accurately map more classes of errors to OONI error strings, as documented through the following ticket: https://github.com/ooni/probe/issues/1505 We also made some progress on comparing the new golang-written Web Connectivity test helper to the old python-based one. The goal of this comparison is to determine how well-suited the new test helper is at replacing the legacy one and if, in doing the switch from one to the other, we are introducing any inaccuracies in the resulting measurements. *## Created mockups for new OONI Probe Snowflake test results* We implemented mockups for displaying the test results of our new Snowflake pluggable transport test inside of OONI Probe. This has been tracked as part of the following issue: https://github.com/ooni/ooni.org/issues/759 *## Research on whether to ship PTs as a separate binary* We carried out research to explore whether to ship pluggable transports as separate binaries or link them with the ooniprobe binary. Based on this research, we wrote an internal document which explains our design choices, PT spec considerations, and conclusions. In the end, we chose to integrate our new Snowflake experiment into ooniprobe as a Go library leveraging version 2 of the pluggable-transports specification: https://github.com/ooni/ooni.org/issues/765 *## OONI backend* In July 2021, we worked on the following OONI backend activities: * Fixed certbot nginx configuration bug (server/port overlap) * Made improvements to the API rate limiting system and developed new integration tests to ensure it’s working as expected: https://github.com/ooni/api/pull/256 * Added support for the global prioritized testing of popular social media URLs: https://github.com/ooni/backend/issues/507 * Added support for the prioritized testing of the GRP Citizen Lab category code in Cuba * Worked on the test helper rotation tool which automatically deploys on cloud infrastructure machines for running backend infrastructure. These are rotated automatically on a periodic basis: https://github.com/ooni/backend/issues/496 * As part of the development of the rotating test helpers, we also did a major rework to how TLS certificates are generated. Specifically we integrated it with DNS and certbot and deployed it to production. * Test with probes on test API. * API: Deployed test.ooni domains in CORS: https://github.com/ooni/api/pull/259 * API: Switched URL submission to account_id: https://github.com/ooni/api/pull/260 * Reprocessed legacy measurements and created JSONL files * Monitored measurement coverage by unattended runs * Updated internal ASN coverage charts * Developed charts that make predictions on the expected measurement volume based on the submission API. We have these charts implemented in our internal backend dashboards and have configured alerts to notify us if the expected measurement volume falls below a certain threshold. * Implemented support for running end-to-end integration tests of the API and fastpath on our continuous integration platform. Through this setup we can ensure that a large part of the backend infrastructure is working as expected and that the API and fastpath are run on real OONI measurement data: https://github.com/ooni/api/pull/258. * Refactored scripts to run tests on different environments *## Building a web platform for test list updates* We deployed the private beta of our new web platform for test list updates to production (https://test-lists.ooni.org/login) We worked on fixing issues reported as part of internal team testing of the platform ( https://github.com/ooni/test-lists-ui/pull/2) We also shared the private beta with a few community members to collect their feedback, based on which we worked on further improvements, which are documented as issues here: https://github.com/ooni/test-lists-ui/issues Once the private beta is further polished, we will share it more extensively to collect further community feedback before launching the platform. *## Collaboration with Netalitica* Netalitica researchers continued to do excellent work in reviewing and updating more Citizen Lab test lists. In July 2021, we reviewed their updates to the test lists for India and Burundi and shared feedback for improvements. *## Test list updates* In July 2021, we contributed updates to the following Citizen Lab test lists: * Russia: https://github.com/citizenlab/test-lists/pull/805 * Ethiopia: https://github.com/citizenlab/test-lists/pull/804 * Armenia: https://github.com/citizenlab/test-lists/pull/803 *## New partnership with Internet Society (ISOC)* In July 2021, we established a new partnership with Internet Society (ISOC). As part of this partnership, OONI is now a data partner ( https://pulse.internetsociety.org/partners) for ISOC’s Pulse project on Internet shutdowns: https://pulse.internetsociety.org/shutdowns As a data partner, we will provide ISOC with relevant OONI data in support of their Pulse project which maps internet shutdowns around the world. *## Community activities### Zaina Foundation Internet Shutdown Training* On 12th and 13th July 2021, Zaina Foundation organized and facilitated an Internet Shutdown Training for human rights defenders in Tanzania. One of the core objectives of this training was to train coalition members on OONI censorship measurement methodologies and to explore OONI data. As part of this training, Zaina Foundation facilitated the following 2 OONI workshops: 1) Introduction to OONI Probe and OONI Explorer 2) OONI practical session Following the training, Zaina Foundation shared community feedback with us and coordinated with local communities on translating OONI Probe to Swahili. *### OONI presentation at the Nexa Center for Internet and Society* On 28th July 2021, OONI’s Arturo presented OONI at the Nexa Center for Internet and Society of the Polytechnic University of Turin. As part of his presentation, Arturo provided OONI updates on the state of internet censorship worldwide in 2020. Information about the event is available here: https://nexa.polito.it/lunch-90 The presentation can be viewed through the following link: https://www.youtube.com/watch?v=fO53FLTu4a8 *### Access Now webinar on internet shutdowns* On 30th July 2021, OONI’s Maria presented OONI as part of Access Now’s webinar titled: “#KeepItOn during an internet shutdown: How to measure, document, and circumvent network interference”. In particular, she discussed how OONI’s tools and data can be used for measuring partial internet shutdowns (involving the blocking of websites and apps). This webinar was live-streamed on YouTube: https://youtu.be/aFIBrRXKm2E *### OONI documentation in Farsi* Iranian community members created detailed and comprehensive documentation which explains OONI tools and methodologies in Farsi. This documentation is available here: https://wikicensorship.github.io/fa/docs/measure-internet-censorship/OONI/ The Farsi documentation covers the following areas: * Investigate Internet censorship through the OONI probe * How Websites Test Works * Directly enter custom addresses in the application * Create a custom test list * Analysis of results * Simple analysis of results * Advanced results analysis * Diagnosis of sanctions * Internal breaker setting only for backend connection * Data mining in OONI results data *### OONI Probe video tutorial in Spanish* Our Bolivian partners, Fundación Internet Bolivia ( https://ooni.org/partners/fundacion-internet-bolivia.org/) created a video tutorial in Spanish where they present OONI and explain OONI Probe, providing a live demo of using the tool. This is available here: https://peertube.tv/videos/watch/e6991978-a3d7-4718-b688-482a9a4de525 *### OONI Community Meeting* On 27th July 2021, we hosted the monthly OONI Community Meeting on our Slack channel (https://slack.ooni.org/) during which we discussed the following topics: 1) New web platform for updating the Citizen Lab test lists: Request for community feedback 2) Adding Signal under instant messaging tests for Debian/Ubuntu OONI Probe users 3) Backend proxy for OONI Probe Desktop and OONI Probe CLI *## Userbase* In July 2021, 13,522,345 OONI Probe measurements were collected from 4,969 AS networks in 195 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on “monthly coverage worldwide”): https://explorer.ooni.org/ ~ OONI team.

1 0

Survey: Understanding your use of Tor and VPNs
by Nah 12 Oct '21

12 Oct '21

Hello, We launched a survey to learn more about how and why our users use VPNs. If you're a Tor Browser user and use VPNs in any device, you can help us by answering this survey: https://survey.torproject.org/index.php/664393 (onion service available) The survey is anonymous, it has 22 questions, and shouldn't take more than 10 minutes to complete, but please take your time and answer at your own pace. Thank you very much. -- Nah UX Researcher The Tor Project

1 0

Anti-censorship meeting notes, 2021 September 30
by Cecylia Bocovich 07 Oct '21

07 Oct '21

Hi everyone! Here are our meeting notes from last week. First the meeting logs: http://meetbot.debian.net/tor-meeting/2021/tor-meeting.2021-09-30-16.00.html and the meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday September 30th 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Announcements == == Discussion == Using the STATUS message to send PT versions to the tor process: https://gitlab.torproject.org/tpo/core/tor/-/issues/11101 development of STATUS: https://gitlab.torproject.org/tpo/core/tor/-/issues/28181#note_2487283 https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt?id=1ecf3f6658681… motivation is to put version information in the bridge extrainfo descriptor, so we know when bridge operators haven't updated assuming network team wants this, what do we do on the PT side? we could add a new PT message for the version number, or reuse the existing STATUS message STATUS is not implemented in goptlib, though if there's a documented use case and a designated key string, dcf is not averse to adding support for it consider: tor may want to require that the version message be sent during the initial negotiation; i.e., before CMETHODS DONE / SMETHODS DONE. in that case it has to be documented that the STATUS / other message will be ignored if sent later also it should be documented what happens if the version self-reporting message is sent more than once perhaps good to consult with the wider PT ecosystem ptadapter https://github.com/twisteroidambassador/ptadapter has PT 2.x already considered version reporting? adopting zoossh https://github.com/NullHypothesis/zoossh/pull/12#issuecomment-930954831 zoossh is now being used in rdsys to parse networkstatus, bridge-descriptors, etc. we need modifications to the package phw (author of zoossh) is not developing it anymore but is willing to merge our patches or let us fork it the plan for now is to send patches upstream == Actions == == Interesting links == https://lists.zx2c4.com/pipermail/wireguard/2021-September/007142.html WireGuard with obfuscation support == Reading group == We will discuss "Exploring Simple Detection Techniques for DNS-over-HTTPS Tunnels" on 2021-10-07 https://dl.acm.org/doi/10.1145/3473604.3474563 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): last updated 2021-09-30 Last week(s): - finished some s28 work - anti-censorship/team#24 - anti-censorship/team#34 - anti-censorhsip/team#26 - added new bridges to the reachability tests we are running - revised client-side API changes (snowflake!56) - reviewed geoip standalone library (geoip!1) - reviewed snowflake proxy library (snowflake!52) This week: - continue snowflake v2 improvements - implement changes to server API - reviews - catch up on censorship-analysis measurements and work - do some snowflake simulations in shadow :) Needs help with: arlolra: 2021-08-12 Last week: - Migrate to v3 of the webextension manifest Next week: - Maybe get back to snowflake-webext #10 - Write up the pitch for our use case for supporting creating PeerConnections in background service workers https://github.com/w3c/webrtc-extensions/issues/77 Help with: - dcf: 2021-09-30 Last week: Next week: Help with: agix:2021-07-15 Last week: -Off due to final exams Next week: -Work on bridgebox for rdsys -More research on httpt #4 Help with: - hanneloresx: 2021-3-4 Last week: - Submitted MR for bridgestrap issue #14 Next week: - Finish bridgestrap #14 - Find new issue to work on Help with: - maxb: 2021-09-23 Last week: - Worked on https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… re: utls for broker negotiation - Had conversation with someone about upstream utls http round tripper https://github.com/refraction-networking/utls/pull/74 - Too busy with work :/ Next week: - _Really_ want to get a PR for utls round tripper meskio: 2021-09-30 Last week: - deploy censorship snapshot as part of rdsys (rdsys#61) - refactor snowflakes geoip code into a library (team#32) - explore zoossh as file parser (rdsys#69) Next week: - parse bridge-descriptors file and fix networkstatus parser (rdsys#69) - make bridgedb a rdsys distributor (bridgedb#40031) Help with: -

1 0

Joydeep's Monthly Status Report
by Joydeep Sen Gupta 06 Oct '21

06 Oct '21

Hello everyone! This is my monthly status report for September-October, 2021 (starting from September 15). The priorities for this month have been to continue our user support work on the official channels, namely frontdesk RT and #tor on OFTC IRC. Frontdesk stats: Timeline : 15 Sept 2021 (00:00 UTC) - 06 Oct 2021 (00:00 UTC) Total tickets created: 90 Total tickets resolved: 77 Note: We receive a lot of spam (more on that down below!) and the total number of tickets created might include some of the spammy tickets as well since we have to manually label them as 'spam'. Breakdown of number of RT tickets received with respect to operating system: Windows (10,8,7, all the way upto XP) - 10 macOS - 3 GNU/Linux - 3 Android- 7 (Note: This includes tickets where the user mentioned the operating system or it was evident from the issue they were running into and/or enclosed screenshots.) Frequent tickets (at least 2 RT tickets): 1. 18 RT Tickets - Private Bridge requests. We recently added the entry 'How to circumvent the Great Firewall and connect to Tor from China?' to the Support Portal [1] but I noticed [2] that a lot of those requests were going into spam as the subject line of the email generally consisted of non-ascii characters. We have now updated the article to suggest users to include 'private bridge' in the subject line (and it seems to be working well!). 2. 8 RT Tickets - Websites blocking Tor. We have received such complaints from users trying to access Youtube and websites using Cloudflare. 3. 4 RT Tickets - Failure to launch Tor Browser. This query is covered by the "Seven-point basic troubleshooting" article (template) on the RT. 4. 3 RT Tickets - macOS download links for Tor Browser resulting in a 404 error.[3] 5. 2 RT Tickets - Can't upload files with Tor browser on Android.[4] 6. 2 RT Tickets - Queries regarding v2 onion services deprecation. # Spam on frontdesk I aggregated some rough stats on how much spam we are getting every month and it's quite a lot. In the past few months, we have received nearly 1200 to 1300 spam tickets per month. Gus has been blocking some of the recurring spammers on the frontdesk although the stats, thus far, don't look very promising. I have requested TPA to help us improve the spam filter on frontdesk [5]. Apart from RT, I have been active on #tor IRC and other social media forums to answer support queries. If you have any suggestions, questions or want to discuss anything in detail please feel free to contact me. Thanks, -- Joydeep [1]: https://support.torproject.org/censorship/connecting-from-china/ [2]: https://gitlab.torproject.org/tpo/web/support/-/issues/261 [3]: https://gitlab.torproject.org/tpo/web/tpo/-/issues/234#note_2752838 [4]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40283 [5]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40425

1 0

UX team meeting next Tuesday, October 12th
by Duncan Larsen-Russell 04 Oct '21

04 Oct '21

Hi everyone! The User Experience team meeting has been postponed this week, and will be happening on Tuesday October 12th at 1400 UTC in #tor-meeting instead.* During this meeting we'll share an update on the UX team’s ongoing work across key projects, Including a review of UX issues pertaining to the torproject.org <http://torproject.org/> website, and a brief discussion about September’s upcoming User Feedback Report. If you'd like to get involved please feel free to add your items to the pad: https://pad.riseup.net/p/1D8sK8Zy74b_0qclC97I-ux-team-monthly-2020-keep <https://pad.riseup.net/p/1D8sK8Zy74b_0qclC97I-ux-team-monthly-2020-keep> Remember, User Experience team meetings are an open space for discussion around ethical user research, user interface design and the user experience of privacy-enhancing products. See you soon! Duncan [*] https://gitlab.torproject.org/tpo/ux/team/-/wikis/home <https://gitlab.torproject.org/tpo/ux/team/-/wikis/home> *** Duncan Larsen-Russell Product Manager & UX Team Lead duncan(a)torproject.org <mailto:duncan@torproject.org>

1 0

BBC Tor sites are now available on V3 Onion URL
by Abdallah al-Salmi - BBC 29 Sep '21

29 Sep '21

We are delighted to announce that BBC websites (News, Persian, Chinese and many more) are now available on a V3 Onion URL: https://www.bbcnewsd73hkzno2ini43t4gblxvycyac5aw4gnv7t2rccijh7745uqd.onion/ To get straight to the desired service, just add its name at the end e.g. for BBC Persian ==> /Persian; for BBC Chinese --> /chinese; for BBC Food --> /food ..etc This is also to thank Alec Muffett for his work on EOTK and his great help in migrating our V2 service. Abdallah al-Salmi | Strategy Analyst | @abdallaBBC | WSG Distribution | BBC | 1st Floor | Wogan House | London | W1A 1AA | Mobile: 078 94 80 5423 | PGP key ID: 0X3D1436B7

1 0

Event Invite: PrivChat #5 | Sept. 27 @ 17:00 UTC
by Al Smith 27 Sep '21

27 Sep '21

Hello Tor world, I wanted to send you an invite to a Tor event happening next week: *our latest edition of PrivChat <https://torproject.org/privchat>. *PrivChat is a live event series featuring experts discussing the latest in privacy and human rights news. * *What: *PrivChat: Protection Against Pegasus <https://torproject.org/privchat> * *When: *Monday, Sept. 27 @ 17:00 UTC * *Where:* https://www.youtube.com/watch?v=4ovmcZtaacY <https://www.youtube.com/watch?v=4ovmcZtaacY> * *More information:* https://torproject.org/privchat <https://torproject.org/privchat> Here's a calendar invite so you can easily save the date, which contains the full event details and description: https://www.torproject.org/static/images/privchat/privchat-5.ics Al Al Smith | smith(a)torproject.org Fundraising Director The Tor Project ------------------------------------------------------------------------ *PrivChat #5 | Protection Against Pegasus* Every year, governments, law enforcement agencies, militaries, and corporations invest billions of dollars into building and buying malicious spyware--software designed to silently infiltrate a user's device and allow attackers to view the contents without detection. This year, the Pegasus Project revealed that users of this kind of spyware, known as Pegasus and built by the NSO group, had targeted the phones that belong to thousands of people in more than 50 countries, including business executives, politicians, journalists, and human rights activists. In this edition of PrivChat, join *Likhita* and *Etienne Maynier* of Amnesty International and *John Scott Railton* of Citizen Lab to discuss: * What individuals, journalists, activists, and human rights defenders can do to protect themselves against sophisticated spyware? * What kind of organizations can we support to help stop this abuse? * Who is working on safer, more private software that we can trust? *Roger Dingledine*, Co-Founder of the Tor Project, will join us as our host and moderator. ------------------------------------------------------------------------

1 1

Anti-censorship meeting notes, 2021 September 23
by Cecylia Bocovich 23 Sep '21

23 Sep '21

Hi everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2021/tor-meeting.2021-09-23-15.59.html and our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday September 23th 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Announcements == Job opening on the anti-censorship team: https://www.torproject.org/about/jobs/software-developer-anticensorship-2/ \o/ == Discussion == https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… the go.mod warning turned out to be caused by a too-old git, and was nothing to fix in goptlib reading group: "BlindTLS: Circumventing TLS-based HTTPS censorship" https://dl.acm.org/doi/10.1145/3473604.3474564 summary https://github.com/net4people/bbs/issues/86 == Actions == == Interesting links == https://censoredplanet.org/webinar2021 https://www.macrumors.com/2021/09/17/icloud-private-relay-disabled-russia/ == Reading group == We will discuss "Exploring Simple Detection Techniques for DNS-over-HTTPS Tunnels" on 2021-10-07 https://dl.acm.org/doi/10.1145/3473604.3474563 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): last updated 2021-09-23 Last week(s): - fixed gitlab CI - afk till tuesday - a bunch of s28 things - anti-censorship/team#25 - anti-censorship/team#24 - hiring tasks This week: - continue snowflake v2 improvements - fixups for snowflake!56 - implement changes to server API - review rdsys!15 - catch up on censorship-analysis measurements and work - do some snowflake simulations in shadow :) Needs help with: arlolra: 2021-08-12 Last week: - Migrate to v3 of the webextension manifest Next week: - Maybe get back to snowflake-webext #10 - Write up the pitch for our use case for supporting creating PeerConnections in background service workers https://github.com/w3c/webrtc-extensions/issues/77 Help with: - dcf: 2021-09-23 Last week: - identified cause of go.mod issue (nothing to do with snowflake or goptlib, as it turns out) https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: Help with: agix:2021-07-15 Last week: -Off due to final exams Next week: -Work on bridgebox for rdsys -More research on httpt #4 Help with: - hanneloresx: 2021-3-4 Last week: - Submitted MR for bridgestrap issue #14 Next week: - Finish bridgestrap #14 - Find new issue to work on Help with: - maxb: 2021-09-23 Last week: - Worked on https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… re: utls for broker negotiation - Had conversation with someone about upstream utls http round tripper https://github.com/refraction-networking/utls/pull/74 - Too busy with work :/ Next week: - _Really_ want to get a PR for utls round tripper meskio: 2021-09-23 Last week: - implement censorship snapsot available on moat (bridgedb#40025) - Honour the operators choice of distribution method for bridges (rdsys#39) - parse bridge-descriptors file and fix networkstatus parser (rdsys#69) - Hiring process Next week: - deploy censorship snapshot as part of rdsys (rdsys#61) - refactor snowflakes geoip code into a library (team#32) - parse bridge-descriptors file and fix networkstatus parser (rdsys#69) Help with: -

1 0

Metrics-web 1.4.1 released
by Silvia/Hiro 21 Sep '21

21 Sep '21

Hi, I have released metrics-web 1.4.0 and made a bug fix release for 1.4.1. Metrics-web aggregates publicly available data about the Tor network and visualizes that data on a website. This release was a long time in the making and has a lot of contribution from different people, which I hope will continue for the following releases. People that contribute to this release are: Ana Custura Gaba Georg Koppen Hiro Iain Learmoth Karsten Loesing # Changes in version 1.4.1 - 2020-09-21 * Medium changes - Fix how v3 statistics are extrapolated. See: https://gitlab.torproject.org/tpo/network-health/metrics/statistics/-/issue… * Minor changes - Fix a few copy paste issues in relay search overloaded banner # Changes in version 1.4.0 - 2020-09-20 * Medium changes - Improve runtime performance of the hidserv module by storing extrapolated statistics even if computed network fractions are zero, to avoid re-processing these statistics over and over. - Extract directory authority bytes per day in the bwhist module. - Rewrite insert_bwhist in SQL to improve performance of the bwhist module. - Estimate relay users by country based on responses to directory requests to reduce the overall effect of binning and to make relay and bridge user estimates more comparable. - Estimate bridge users by country based on requests by country, if available, to get more accurate numbers than those obtained from unique IP address counts. - Update to metrics-lib 2.19.0 and ExoneraTor 4.4.0. - Switch from processing Torperf .tpf to OnionPerf analysis .json files. - Add Onion Service v3 statistics. - Add overloaded relay information by displaying an amber dot next to the relay nickname in relay search. - Update throughput calculation for Onionperf transfers. * Minor changes - Make Jetty host configurable. - Configure a base URL in order to turn ExoneraTor's permanent links into https:// links. - Set default locale `US` at the beginning of the execution. - Set default time zone `UTC` at the beginning of the execution. - Simplify logging configuration. You can find the release at: https://dist.torproject.org/metrics-web/1.4.0/ https://dist.torproject.org/metrics-web/1.4.1/ You can find the sources at: https://gitlab.torproject.org/tpo/network-health/metrics/website/-/tree/met… https://gitlab.torproject.org/tpo/network-health/metrics/website/-/tree/met… Thanks, hiro _______________________________________________ tor-project mailing list tor-project(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project

1 0