- tor-project - lists.torproject.org

UX team meeting on January 12th
by Duncan Larsen-Russell 08 Jan '21

08 Jan '21

Hello & happy new year everyone! Our first User Experience team meeting of the year will be held on Tuesday 12th January at 1400 UTC in #tor-meeting.* During this meeting we'll discuss upcoming work for the UX team across key projects, in addition to hosting an open call for user research, during which we’ll outline ways in which community members can help contribute towards user research for Tor. If you'd like to get involved please feel free to add yourself 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 user experience, meanwhile building 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>

1 0

Anti-censorship meeting notes, 07 January 2021
by Cecylia Bocovich 07 Jan '21

07 Jan '21

Happy new year! Here are our meeting notes: http://meetbot.debian.net/tor-meeting/2021/tor-meeting.2021-01-07-15.58.html and our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday January 7th 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. == 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 30 https://gitlab.torproject.org/groups/tpo/-/milestones/4 https://gitlab.torproject.org/groups/tpo/-/milestones/7 https://gitlab.torproject.org/groups/tpo/-/milestones/5 https://gitlab.torproject.org/groups/tpo/-/milestones/6 Sponsor 28 must-do tickets: https://gitlab.torproject.org/groups/tpo/-/milestones/10 possible tickets: https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… Anti-censorship related tickets that we want other teams to fix: https://pad.riseup.net/p/tor-anti-censorship-tickets-keep <-- it will be moved into gitlab with TPO labels <-- do we still need this? The label is 'for anticensorship team' Public bug-reporting pad: https://pad.riseup.net/p/tor-anti-censorship-bugs-keep == Announcements == Cure53 is engaged by the Berkeley Counter-Power Lab to do a security audit of Turbo Tunnel in Snowflake. dcf has advised them to correspond on the anti-censorship-team list if possible. == Discussion == https://www.reddit.com/r/TOR/comments/kj7git/is_bamsoftwarecom_related_to_t… Malwarebytes apparently blocks snowflake.bamsoftware.com and snowflake-broker.bamsoftware.com. But this should not have happened since https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… (webext-0.0.6), which changed *.bamsoftware.com to *.freehaven.net? https://gitweb.torproject.org/pluggable-transports/snowflake.git/commit/?id… How did this user get a copy of the browser extension that still contacts these old domains? Pick a reading for the next reading group discussion == Actions == December 2020 monthly report: https://pad.riseup.net/p/mh4PvdOzncZlcxwHGROn == Interesting links == GitHub is now available in Iran: https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-… == Reading group == We will discuss "Early Detection of Censorship Events with Psiphon Network Data" on Jan 21, 2021. https://tics.site/proceedings/2019a/icn_2019_7_10_38005.pdf 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. phw: This week (2020-01-07): Filled out TPA survey. Figured out root cause of bridgestrap's dormant mode issue. https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/12 Improved queuing mechanism of rdsys's interaction with bridgestrap. Filed issue to incorporate emma into OONI. https://gitlab.torproject.org/tpo/anti-censorship/emma/-/issues/5 Filed monit issue to watch out for future obfs4proxy problems. https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/iss… Found and fixed race condition in bridgestrap's cache implementation. Next week: Progress on Salmon's privacy improvements. Brainstorm a way to do censorship measurement for Salmon. Help with: https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/merge_reque… cecylia (cohosh): last updated 2020-01-07 Last 2-3 weeks: - mostly afk - updated version of pion webrtc to 3.0.0 (snowflake#40027) This week: - cleaned up a simple script for comparing the performance of two versions of snowflake: https://gitlab.torproject.org/-/snippets/69 This week: - continued work on snowflake overhead performance, and stacking reliable protocols Needs help with: - review of snowflake!25 (closes snowflake#40027) arlolra: 2020-10-29 Last week: - Next week: - getting back up to speed - follow ups to #33365 - start on #31201 Help with: - dcf: 2021-01-07 Last week: - Azure bookkeeping Next week: - make a ticket to change {snowflake,snowflake-broker}.freehaven.net into CNAMES of the corresponding torproject.net domains, not bamsoftware.com - review pion v3 upgrade https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: Antonela: 2020-08-27 This week: agix:2021-01-07 Last week: -Research on httpt #4 Next week: -Finish rdsys #6 Help with: - hanneloresx: 2020-10-22 Last week: - Took break to focus on work Next week: - #32117: Look at CAPTCHA success rate for users from the US across different types of bridges Help with: - HashikD: 2020-11-19 This week: - Next week: - Help with: -

1 0

OONI Monthly Report: December 2020
by Maria Xynou 06 Jan '21

06 Jan '21

Hello, Happy New Year! Hope 2021 brings more good health and joy to all. Throughout December 2020, the OONI team worked on the following sprints: * Sprint 27 - Hexacorallia (December 1 - 6, 2020) * Sprint 28 - Corallimorpharia (December 7 - 19, 2020) * Sprint 29 - Dogfish shark (December 20 - 31, 2020) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. ## Year in Review: OONI in 2020 Every year we summarize what the OONI team did through our annual “Year in Review” posts. At the end of December 2020, we published “Year in Review: OONI in 2020”, which shares OONI highlights from 2020, as well as upcoming OONI projects for 2021. In this post, we also highlight accomplishments from the OONI community in 2020. This post is available here: https://ooni.org/post/ooni-in-2020/ ## OONI Probe Mobile ### Released OONI Probe Mobile 2.8.0 We released OONI Probe Mobile 2.8.0 for: * Android: https://github.com/ooni/probe-android/releases/tag/v2.8.0 * iOS: https://github.com/ooni/probe-ios/releases/tag/v2.8.0 On Android, OONI Probe tests are run as Android services, where a notification of test progress is displayed. On both Android and iOS, the latest release enables users to free up space by deleting old measurement files in the app settings, and the OONI Probe measurement engine has been updated to v0.21.0. ### Other OONI Probe Mobile improvements Throughout December 2020, we also worked on the following: * Ensured we removed unused probe-engine settings: https://github.com/ooni/probe/issues/1307 * Ensured that tapping on notifications doesn't open OONI Run or the app: https://github.com/ooni/probe/issues/1307 * Fixed the unit tests on iOS * Changed the modal options for requesting push notification permission: https://github.com/ooni/probe/issues/1306 * Added support for interrupting OONI Probe tests when the user’s connectivity changes: https://github.com/ooni/probe/issues/1296 * Carried out some research on potentially disabling battery optimization: https://github.com/ooni/probe/issues/1301 * Made some progress on implementing the check-in API: https://github.com/ooni/probe/issues/1299 ## OONI Probe Desktop Throughout December 2020, we worked on the following: * Integrated the “Choose websites” function into the OONI Probe CLI (so that it can be supported on OONI Probe Desktop): https://github.com/ooni/probe/issues/1283 * Implemented an MVP for automated OONI Probe testing on Windows: https://github.com/ooni/probe/issues/1053 * Explored whether it’s possible to shed privileges or run with reduced privileges on Windows during automated testing: https://github.com/ooni/probe/issues/1300 * Added support for max_runtime to OONI Probe desktop: https://github.com/ooni/probe/issues/1280 * Started implementing a new dashboard to align with the look and feel of OONI Probe Mobile: https://github.com/ooni/probe/issues/1274 ### Updating OONI Probe macOS homebrew package We made considerable progress on updating the OONI Probe macOS homebrew package with the OONI Probe Command Line Interface (CLI), as documented through this ticket: https://github.com/ooni/probe/issues/1289 ## OONI Probe Engine In early December 2020, we completed a series of routine OONI Probe engine releases (in support of the OONI Probe Mobile 2.8.0 release), as documented through this ticket: https://github.com/ooni/probe-engine/issues/1043 ## Building Debian package for OONI Probe We further improved upon the new Debian package for OONI Probe: https://github.com/ooni/probe-cli/pull/162 We now have an OONI Probe Debian package that can be installed and run in the background: https://github.com/ooni/backend/issues/452 ## Expanding OONI Probe measurement methodologies As part of our ongoing efforts to improve upon and expand our measurement methodologies, we: * Reviewed the new HTTP/3 experiment (contributed by a community members) for quality assurance, as documented through this ticket: https://github.com/ooni/probe-engine/issues/1057 (this is an ongoing task) * Carried out research and encrypted DNS experiments: https://github.com/ooni/probe-engine/issues/900 ## Wrote paper on measuring DoT/DoH blocking using OONI Probe During the last weeks of December 2020, OONI’s Simone wrote an academic paper on measuring DoT/DoH blocking through the use of OONI Probe experiments. This paper describes DNScheck (an active network experiment for the detection of DoT/DoH blocking), which we implemented into OONI Probe. We compiled a list of popular DoT/DoH services and ran DNSCheck measurements with the help of volunteer OONI Probe users. Our paper presents preliminary measurement findings from Kazakhstan (AS48716), Iran (AS197207), and China (AS45090). We have submitted this paper to the DNS Privacy Workshop 2021: https://www.ndss-symposium.org/ndss2021/cfp-dns-privacy-workshop/ ## OONI Explorer In December 2020, we worked on refactoring the OONI Explorer search page to run only on the client side: https://github.com/ooni/explorer/issues/413 We have built a measurement aggregation toolkit, a generic web-based tool that can help with creating useful visualizations with aggregated measurement data from the API. It is currently deployed in the experimental section of OONI Explorer: https://explorer.ooni.org/experimental/mat Throughout December 2020, we made a series of improvements to our measurement aggregation toolkit, as documented here: https://github.com/ooni/explorer/issues/528 Progress on future work to improve it is documented here: https://github.com/ooni/explorer/issues/536 ## OONI backend Throughout December 2020, we worked on the following backend activities: * Switched orchestrate traffic to test-list/urls to API: https://github.com/ooni/backend/issues/478 * Investigated MIA route flapping * Investigated AMS connectivity issues * Monitored the dashboard reactive test-list * Deployed persistent journald * Fixed the measurement_forwarder ## Published new OONI Partners page We published a new page on the OONI website which features all of our partners, highlights their work, links to their websites, and shares some of the research reports and projects that we have collaborated on. The new OONI Partners page is available here: https://ooni.org/partners ## Creating a new Donate page for the OONI website We steadily made progress on creating a new Donate page for the OONI website. This involved: * Relevant frontend development: https://github.com/ooni/ooni.org/pull/723 * Writing the copy for the new page: https://github.com/ooni/ooni.org/issues/713 We also: * Wrote copy for OONI’s new Open Collective account: https://github.com/ooni/ooni.org/issues/704 * Edited the copy on OONI’s GitHub Sponsors page: https://github.com/ooni/ooni.org/issues/722 ## Collaboration with Netalitica on test lists We continued to collaborate with Netalitica researchers, who did excellent work updating more Citizen Lab test lists. Throughout December 2020, we reviewed (and shared feedback on) Netalitica updates to the following test lists: * Zimbabwe: https://github.com/citizenlab/test-lists/pull/701 * Algeria: https://github.com/citizenlab/test-lists/pull/702 * Colombia: https://github.com/citizenlab/test-lists/pull/707 * Ethiopia: https://github.com/citizenlab/test-lists/pull/708 * Lebanon: https://github.com/citizenlab/test-lists/pull/709 We also updated the following test lists (in collaboration with community members): * Global & Nigerian: https://github.com/citizenlab/test-lists/pull/694 * Global: https://github.com/citizenlab/test-lists/pull/696 and https://github.com/citizenlab/test-lists/pull/700 * Cuban: https://github.com/citizenlab/test-lists/pull/698 * Nigerian: https://github.com/citizenlab/test-lists/pull/699 ## Community use of OONI data ### Amnesty Malaysia: Unsilenced Amnesty Malaysia launched a campaign, called Unsilenced, which aims to fight censorship and defend freedom of expression in Malaysia. This campaign is available here: https://unsilenced.amnesty.my/ Among the resources listed on the Unsilenced site are the OONI website and OONI measurements collected from Malaysia (linking to the Malaysian page on OONI Explorer). ## Community activities ### Internet Shutdown Measurement Training Group Presentations Between 12th October 2020 to 19th November 2020, we helped lead Internews’ 6-week Internet Shutdown Measurement Training for human rights defenders in Sub-Saharan Africa. Throughout this training program, participants were asked to work in groups to develop relevant research and advocacy projects, which we supported through mentorship. On 1st December 2020, the training participants presented their research and advocacy projects. Leading up to these presentations, we supported training participants by reviewing their presentations and sharing feedback. ### Workshop: Building capacity for internet shutdown advocacy On 15th December 2020, OONI’s Maria attended Internews’ workshop, “Building capacity for internet shutdown advocacy: Community needs assessment”, where she facilitated the discussion on community needs around censorship measurement data. Information about the workshop is available here: https://www.eventbrite.com/e/building-capacity-for-internet-shutdown-advoca… ## Userbase In December 2020, 3,834,624 OONI Probe measurements were collected from 4,443 networks in 191 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. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

reminder: trac.torproject.org retires in two days
by Antoine Beaupré 30 Dec '20

30 Dec '20

Hi, This is just a quick heads up to remind everyone that our dear old Trac instance, https://trac.torproject.org/ is retiring in two days, on December 9th, as announced 6 months ago[1]. [1]: https://lists.torproject.org/pipermail/tor-project/2020-June/002866.html Around that time, Trac was put in "read-only mode", in that no changes were allowed through the web interface whatsoever. We have heard approximately zero complaints about the change: while some people have concerns about GitLab and lots of things could be improved there, it seems no one is actually missing poor old Trac. As much of the Trac content as possible was migrated into GitLab. An integral copy of the [Trac wiki] and [Trac issues] will be kept as is in GitLab. Most of those issues were migrated to their own projects, and lots of the wiki content was spread out to different, team-specific wikis (which makes the content a bit hard to find, see [issue 66] for details on that). [Trac wiki]: https://gitlab.torproject.org/legacy/trac/-/wikis/home [Trac issues]: https://gitlab.torproject.org/legacy/trac/-/issues [issue 66]: https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/66 Trac was also thoroughly archived on the Wayback machine[2] for those cases where you really only know how to find something by looking at it "the Trac way". This should also salvage some pages that do not get rendered quite right in the GitLab migration, which happens. [2]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40003 The plan, right now, is to redirect the Wiki and issue URLs into GitLab's relevant legacy project, and everything else to the GitLab front page. (It is considered bad practice to hotwire old sites into the wayback machine: we prefer to refer to live data instead, even though that old data is still available.) The actual virtual machine where Trac is hosted will be destroyed 30 days after the redirections are in place, as an exceptional measure considering the service Trac has given us over the years. Absolutely do tell us if you feel there is some critical data that would be lost when that happens, something that was not correctly migrated to Gitlab *and* would not be available through the Wayback machine. Further progress updates on the life and tribulation of troodi, the machine that hosted trac.torproject.org all those years, will only be posted in this ticket: https://gitlab.torproject.org/tpo/tpa/team/-/issues/34373 ## Post-scriptum: history People might also be interested in the history of bug trackers at the Tor project: * lost in the mists of time: migration from Bugzilla to Flyspray (40 tickets) * 2010-04-23: [migration from Flyspray to Trac completed][] (last Flyspray ticket is [1393][], first Trac ticket is [2000][]) * 2016-11-29: [first request to setup a GitLab server][] * ~2017: oniongit.eu (warning: squatted domain) deployed to test GitLab with the network team, considered as gitlab.torproject.net but ultimately [abandoned][] * 2019-02-28: `gitlab-01` AKA dip.torproject.org test server setup ([issue 29400][]), following the [Brussels meeting][] * 2019-07-17: GitLab discussed again at the [Stockholm meeting][] * 2019-07-29: Formal proposal to deploy GitLab [sent to tor-project][], no objection * 2020-03-05: GitLab migrated from `gitlab-01` (AKA "dip") to `gitlab-02` using the Omnibus package * 2020-04-27: `gitlab-01` retired * 2020-06-13 19:00UTC: [Trac readonly][] * 2020-06-13 02:25UTC: Trac tickets migrated (32401 tickets, last ticket id is [34451][], first GitLab legacy project ticket id is 40000) * 2020-06-14 21:22UTC: Trac wiki migrated * 2020-06-15 18:30UTC: bugs.torproject.org redirects to gitlab * 2020-06-16 02:15UTC: GitLab launch announced to tor-internal * 2020-06-17 12:33UTC: Archivebot starts crawling all tickets of, and the entire Trac website * 2020-06-23: Archivebot completes the full Trac crawl, Trac is fully archived on the Internet Archive Coming up next: * 2020-09-09: Trac redirects to GitLab * 2021-01-09: Trac server, troodi, destroyed [migration from Flyspray to Trac completed]: https://lists.torproject.org/pipermail/tor-dev/2010-April/000183.html [1393]: https://bugs.torproject.org/1393 [2000]: https://bugs.torproject.org/2000 [first request to setup a GitLab server]: https://gitlab.torproject.org/tpo/tpa/services/-/issues/20821 [abandoned]: https://gitlab.torproject.org/tpo/tpa/services/-/issues/21840 [issue 29400]: https://gitlab.torproject.org/tpo/tpa/services/-/issues/29400 [Brussels meeting]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdmi… [Stockholm meeting]: https://gitlab.torproject.org/legacy/trac/-/wikis/org/meetings/2019Stockhol… [sent to tor-project]: https://lists.torproject.org/pipermail/tor-project/2019-July/002407.html [Trac readonly]: https://lists.torproject.org/pipermail/tor-project/2020-June/002872.html [34451]: https://bugs.torproject.org/34451 A. -- Antoine Beaupré torproject.org system administration

1 1

(FWD) Research assistant position on Tor and Lightweight Cryptography
by Roger Dingledine 29 Dec '20

29 Dec '20

Forwarding on behalf of Tariq. We helped them get some funding to do research work on the intersection of Tor and IoT, and here is one of those spots. (Ok, reading the page in more detail, maybe it's more like the union of Tor and IoT, not the intersection. :) I asked him for clarification around timing and citizenship, and he said "We are flexible in the dates. Also the person just needs the right to work in the UK, but does not need to be a UK citizen." --Roger ----- Forwarded message from Tariq Elahi <t.elahi(a)ed.ac.uk> ----- Date: Thu, 10 Dec 2020 16:50:06 +0000 From: Tariq Elahi <t.elahi(a)ed.ac.uk> To: Roger Dingledine <arma(a)torproject.org> Cc: Vesselin Velichkov <vvelichk(a)staffmail.ed.ac.uk> Subject: Research assistant position for Tor and LWC Hi Roger, I hope you are well. As you know we were successful in our bid for the REPHRAIN centre and are now in the process of hiring fine researchers and implementers to join our projects. I am writing about a joint project with my colleague at Edinburgh Vesselin Velichkov (a crypto analyst) and myself. I was wondering if you would mind spreading the word around your network for a 6 month Research Assistant/Post-doctoral researcher position. Maybe you already know of someone, so any leads out be greatly appreciated. In short, the project is about implementing and evaluating various light weight crypto algorithms on embedded platforms. The project seeks to investigate the viability and directions for embedding PETS like Tor and mixnets to networks of IoT-class devices. The start date is early January, but we have some slight flexibility there. Remote work is possible, but a UK bank account is necessary. More information can be found here: https://www.rephrain.ac.uk/preserve/ Thanks for you help in advance. Best wishes, Tariq -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ----- End forwarded message -----

1 0

Tails report for November 2020
by intrigeri 18 Dec '20

18 Dec '20

Hi, The Tails report for November 2020 is out: https://tails.boum.org/news/report_2020_11/ Cheers!

1 0

Sponsor 38 2020-12 update (Shadow simulator)
by Jim Newsome 18 Dec '20

18 Dec '20

Our latest update on the Shadow simulator is in Shadow's new Discussions forum <https://github.com/shadow/shadow/discussions/1060>. Thanks, and Happy Holidays! The Shadow team <https://github.com/shadow/shadow/blob/master/docs/nsf-sponsorship.md#people>

1 0

Anti-censorship meeting notes, 17 Dec 2020
by Philipp Winter 17 Dec '20

17 Dec '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-12-17-15.57.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday December 17th 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. == 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 30 * https://gitlab.torproject.org/groups/tpo/-/milestones/4 * https://gitlab.torproject.org/groups/tpo/-/milestones/7 * https://gitlab.torproject.org/groups/tpo/-/milestones/5 * https://gitlab.torproject.org/groups/tpo/-/milestones/6 * Sponsor 28 * must-do tickets: https://gitlab.torproject.org/groups/tpo/-/milestones/10 * possible tickets: https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep <-- it will be moved into gitlab with TPO labels <-- do we still need this? The label is 'for anticensorship team' * Public bug-reporting pad: * https://pad.riseup.net/p/tor-anti-censorship-bugs-keep == Announcements == * Tor is moving to ed25519 IDs as relay/bridge identifiers. * Current fingerprint format (SHA-1 over RSA key) may not be around anymore. == Discussion == * Post mortem of moat outage * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek… * How can we prevent this from happening again? * Is this the last meeting until 2021? == Actions == * == Interesting links == * == Reading group == * We will discuss "" on * * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-12-17): * Wrote obfs4proxy patch that fixes -unsafeLogging. * https://gitlab.com/yawning/obfs4/-/merge_requests/1 * Helped Benjamin from Guardian Project debug ongoing obfs4proxy HPKP issue. * Still dealing with tor's dormant mode issue in bridgestrap. * https://gitlab.torproject.org/tpo/core/tor/-/issues/40228 * Created a Prometheus dashboard for bridgestrap. It's beautiful. * https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/13 * Mostly read rBridge paper. * Closed our obfs4proxy HPKP issue because numbers have mostly recovered. * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek… * Made progress on rdsys's persistence layer. * https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/5 Next week: * Progress on Salmon's privacy improvements. * Brainstorm a way to do censorship measurement for Salmon. Help with: * cecylia (cohosh): last updated 2020-12-17 Last week: - met with protozoa people about a new PT - did some research on issues with stacking reliable protocols - ran some tests for an increased window size in snowflake#40026 - merged snowflake!24 - read release notes for pion/webrtc v3.0.0 This week: (AWAY DEC 21 - JAN 06) - try an update to pion/webrtc/v3 (snowflake#40027) - update webrtc and snowflake versions in tor browser - continue to monitor snowflake stats - Figure out why we still have unknown proxies Needs help with: juggy : last updated before 2020-12-17 This week: - Got very basic "suggested readings" list up and running here : https://jugheadjones10.github.io/anti-censorship-reading/ Next week: - Keep studying BridgeDB to write architectural overview Help with: - Open issues here (https://github.com/jugheadjones10/anti-censorship-reading ) for papers/resources/readings that you think might be useful for newcomers arlolra: 2020-10-29 Last week: - Next week: - getting back up to speed - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-12-17 Last week: - looked at cohosh's patch to increase the KCP window size https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: Help with: Antonela: 2020-08-27 This week: - Wrapping Babatunde's research on the use of circumvention tools during internet censorship in Africa. Wrapping Personas for s30 with it. For september: - We are planning interviews with users in China to run our bridges discovery issues script in real time. We discussed to include TBA + snowflake as a task for users to run over a week or two and report back. https://gitlab.torproject.org/tpo/ux/research/-/issues/4 - I still have bridges.tpo to lektor issue open - More work on UX/UI for TB 10.0/10.5 - Review Salmon related tickets (im late with it!) agix:2020-12-17 Last week: -More on research httpt #4 -Worked on rdsys #6 (took a deep dive into extra-info descriptors)¶ Next week: -Finish rdsys #6 -More work on httpt #4 Help with: - hanneloresx: 2020-10-22 Last week: - Took break to focus on work Next week: - #32117: Look at CAPTCHA success rate for users from the US across different types of bridges Help with: - thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with: HashikD: 2020-11-19 This week: - Next week: - Research on how to implement a STUN check on Android. Help with: -

1 0

ANN: Updated Tor Browser Signing Key
by Matthew Finkel 15 Dec '20

15 Dec '20

Hello everyone, The OpenPGP Tor Browser signing key is due to expire this Saturday (19 December). While we usually rotate the signing key, we extended the expiration date instead due to the difficulty of activating a new key at this time. The signing key now expires on 12 June 2021. We may extend the expiration date again when we get closer to that date if key rotation is not a viable option over the next 6 months. The updated key is available from keys.openpgp.org [0], and it will be available from The Tor Project's key server [1] within the next few days. [0] https://keys.openpgp.org/search?q=torbrowser%40torproject.org [1] https://support.torproject.org/tbb/how-to-verify-signature/

1 0

You're invited: PrivChat hosted by Snowden | Friday 12/11 @ 18:00 UTC
by Al Smith 11 Dec '20

11 Dec '20

Hello Tor, Next Friday, *Edward Snowden *will host Tor’s third PrivChat (https://torproject.org/privchat) a fundraising livestream event and conversation with human rights defenders + real-life Tor users *Alison Macrina* (Founder, Library Freedom Project), *Berhan Taye *(Africa Policy Manager and Global Internet Shutdowns Lead, Access Now) and *Ramy Raoof* (Security Labs Technologist, Amnesty International). *What: *PrivChat | Tor Advancing Human Rights *When: *Friday, December 11 @ 18:00 UTC / 13:00 Eastern / 10:00 Pacific *Where: *The Tor Project’s YouTube channel: https://www.youtube.com/watch?v=S2N3GoewgC8 * **// What’s PrivChat? //* PrivChat is a fundraising event series held to raise donations for the Tor Project. Through PrivChat, we bring you important information related to what is happening in tech, human rights, and internet freedom by convening experts for a chat with our community. * **// Tor Advancing Human Rights //* The Tor Project's main mission is to advance human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies. People use our technology, namely the Tor network and Tor Browser, in diverse ways. Tor is used by whistleblowers who need a safe way to bring to light information about wrongdoing -- information that is crucial for society to know -- without sharing their identity. Tor is used by activists around the world who are fighting against authoritarian governments and to defend human rights, not only for their safety and anonymity, but also to circumvent internet censorship so their voices can be heard. Tor allows millions of people to protect themselves online, no matter what privilege they have or don't have. For our third edition of PrivChat, we are bringing you some real-life Tor users who will share how Tor has been important for them and their work to defend human rights and freedoms around the world. Please spread the word! There’s an easy tweet pinned to the top of our Twitter page: https://twitter.com/torproject/status/1334209034392465409?s=20 Hope to see you there, Al -- Al Smith (they/them) Fundraising • Communications The Tor Project

1 1