June 2020 - 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

Tor UX meetings start happening again on July 7th at 14UTC in IRC
by Antonela Debiasi 30 Jun '20

30 Jun '20

Hi! We discussed the best way to resume the User Experience team meetings to cultivate our open space for discussions around ethical user research, user interface design, and user experience. Given our current capacity, we consider a monthly meeting a good way to keep the group updated. Meetings will happen every first Tuesdays of the month at 14UTC, starting next Tuesday 7th in irc.oftc.net #tor-meeting.More details on our wiki [0]. I hope to see you around to update each other about what we are up to and share the open calls for research and design. Peace and love, A [0] https://gitlab.torproject.org/tpo/ux/team/-/wikis/home -- Antonela Debiasi UX Team Lead @antonela E2330A6D1EB5A0C8 https://torproject.org

1 0

Tor browser meeting notes, 29 June 2020
by Gaba 29 Jun '20

29 Jun '20

Hi! Tor Browser meetings are happening every Monday at 1800UTC on #tor-meeting in irc.oftc.net We had a meeting on June 29th and here are the logs and notes. Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-29-18.01.log… Pad: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Contents of the pad for today: == Tor Browser meeting pad! == Next meeting is at Monday 6th July 1800 UTC on #tor-meeting on OFTC. July Schedule: * Monday 29 June 18:00 UTC * Monday 6 July 18:00 UTC Release meetings: https://pad.riseup.net/p/tor-browser-release-meeting-keep Tuesday July 7th 18:00 UTC (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Upcoming Releases and other important dates 2020.06.30: 9.5.1 and 10.0a2 - ESR68.10, ESR78.0 Latest Releases: 2020.05.22: 9.5a13 https://blog.torproject.org/new-release-tor-browser-95a13 2020.06.02: 9.5 Stable https://blog.torproject.org/new-release-tor-browser-95 2020.06.02: 10.0a1 https://blog.torproject.org/new-release-tor-browser-100a1 == Previous notes == (Search the tor-project mailing list archive for older notes.) June 15th - https://lists.torproject.org/pipermail/tor-project/2020-June/002878.html June 22nd - https://lists.torproject.org/pipermail/tor-project/2020-June/002891.html == What project we are working on? == SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements Milestone: https://gitlab.torproject.org/groups/tpo/-/milestones/11 Parent ticket: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33664 Timeline: https://nc.torproject.net/s/ow2r6cLgL7Cd9BA == Stuff to do every week == Kanban https://gitlab.torproject.org/groups/tpo/applications/-/boards Check reviews not taken! How reviews from last week worked? Any blocker? https://gitlab.torproject.org/groups/tpo/applications/-/issues?scope=all&ut… Next release: anybody need help with anything? ------------------------------- ---- 29 June 2020 ------------- ------------------------------- == Announcements [please date] == == Discussion [please date] == [June 29th] Please review http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/58-… . Bekeela will be sending it today. [June 29th] dev.tpo needs Application Team review > https://gitlab.torproject.org/tpo/web/trac/-/issues/24132 == Status Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. ahf: Week of 22/6 planned: - Trying to minimize myself in the Gitlab stuff for now. - Need to deal with review backlog. - Back to doing Fenix + Tor integration. - Get Tor network extension working on device with TGP sponsorship. Week of 22/6 actually: - Got help from Benjamin with certificates and all the Apple "security" stuff with running your own apps on your own devices... - Failed at completely detaching myself from Gitlab things: worked on a few minor issues and the label clean-up. - Tried to push for some sponsorship for CI for our Gitlab instance. - Read Mike's congestion pads/mails. - Got back to Fenix+Tor integration. Week of 29/6 planned: - Delete unused labels from Gitlab. - Try to solve Gitlab#41 with Hiro since it makes working with GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup. - Do merging/backporting of Tor things. boklm: Week of 2020-06-15 (actual): - Made patches to use rootless containers and was able to do builds of Tor Browser for windows-x86_64 and osx-x86_64 (tor-browser-build#23631 and rbm#40001). For some unknown reason the builds based on wheezy are not working. Week of 2020-06-22 (planned): - Add some documentation for rbm#40001 and set the patch as Needs Review - Improve patch for rbm#32272 to handle Ctrl+C Mike: Week of 06/22 (planned): - Wrap up congestion control proposal draft - gecko-dev proxy audit Week of 06/22 (actual): - Funding proposal work - Congestion control work for funding proposal notes - Gitlab label cleanup Week of 06/29 (planned): - Performance funding proposal pre-meeting + funder meeting - gecko-dev proxy audit mcs and brade: Week of June 22nd (actual): - Rebased & landed “update downloading” patch (upstreaming tor-browser#28885). - See https://bugzilla.mozilla.org/show_bug.cgi?id=1642404 - Investigated intermittent test failure for other part of tor-browser#28885. - See https://bugzilla.mozilla.org/show_bug.cgi?id=1647313 - So far we have not reproduced the failure. - tor-browser#33534: Finished reviewing Firefox 75-78beta release/dev notes. Week of June 29th (planned): - tor-browser#33534: Review closed bugs for Firefox 75-78. - More work on the intermittent test failure bug (Bugzilla 1647313). - tor-browser#33852 (Clean up about:logins (LockWise) to avoid mentioning sync, etc.) sysrqb: Week of 15 June (planned): Really, really finish #33939 Review testsuite patches and merge them so we have a working...testsuite Catch up on current 9.5/10.0a tickets Finally land vpx patch upstream Review https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 Continue tracking OTF/DRL situation Audit GitLab labels Release prep Week of 15 June (actual): Really, really finish #33939 (no) Review testsuite patches and merge them so we have a working...testsuite (handed off to GeKo) Catch up on current 9.5/10.0a tickets (no) Finally land vpx patch upstream (small progress) Review https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 (no) Continue tracking OTF/DRL situation (spent some time) Audit GitLab labels (complete) Release prep (complete) Week of 22 June (planned): #33939 Unblock any other Fenix work 9.5.1/10.0a2 releases cpu_features patch uplift GeKo: Week of June 22 (planned): Gitlab work Finish review of #33533 Finish application-services build Week of June 22 (actual): Gitlab work Finish Review of #33533 Work on application-services build Week of 29 June: Finish build of application services help with releases were fit Reviews (dev.tpo, O3.2 design for S30, #27105, #30832) Antonela: Week of 22 June (planned): - Review HTTPS-E Names https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010#n… - Work on S58 tickets TBA UI - Waiting for tbb-dev review in S30 https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 Week of 22 June (actual): - Nothing of that Week of 29 June: - Review HTTPS-E Names https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010#n… - Work on S58 tickets TBA UI - Waiting for tbb-dev review in S30 https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 acat: Week of 22nd June (planned): Possibly address GeKo's feedback on #33533 Add tests in tor-browser-bundle-testsuite: 40001: Add test for "Communicating security expectations TB patch" 40002: Add test for "Add v3 onion services client authentication prompt" TB patch 40003: Add test for "Implement Onion-Location" TB patch 40004: Add test for "Implement .onion alias urlbar rewrites" TB patch 40005: Add test for "Replace security slider with security level UI" TB patch Rebase #33533 to latest beta and test tor-browser-spec#40001 process Week of 22nd June (actual): - Add tests in tor-browser-bundle-testsuite (will push MR after meeting): - 40001: Add test for "Communicating security expectations TB patch" - 40003: Add test for "Implement Onion-Location" TB patch - 40004: Add test for "Implement .onion alias urlbar rewrites" TB patch - 40005: Add test for "Replace security slider with security level UI" TB patch Week of 29th June: - Finish tor-browser-bundle-testsuite@40002: Add test for "Add v3 onion services client authentication prompt" TB patch - Revise & Rebase #33533 to latest beta and test tor-browser-spec#40001 process - Revise tor-browser-spec@40001: Add rebasing process document - Maybe iterate on tor-browser@33791: Evaluate Firefox tests - I was thinking of finding the subset of FF tests that pass and put it in some list/script so that we can run/keep track of it.+1 (+1, yes, please) Jeremy Rand: Week of 15 and 22 June (actual): Ask for feedback on latest Namecoin patches to Tor Browser on Reddit. https://old.reddit.com/r/Namecoin/comments/hbf9fq/we_need_more_testers_for_… Got some decent feedback. At this point it looks like the primary request from testers is adding macOS and Windows support. Upstream Electrum released a couple of betas of Electrum 4.0.0. Started looking at rebasing Namecoin's patches to 4.0.0 (most are rebased continuously, but a few only get rebased for releases.) Dealing with various funding-related things e.g. NLnet proposal. Discussed having Namecoin issue a statement about the OTF situation. Tried to activate my GitLab account, failed. Week of 29 June (planned): Look more seriously at what's needed to port the Namecoin support to macOS/Windows. Keep working on rebasing Namecoin's patches to Electrum 4.0.0. Continue working on upstreaming Namecoin's Electrum patches. Continue talking to NLnet about funding things. Issue a formal statement from Namecoin about the OTF situation (hopefully it helps). Hopefully get my GitLab account sorted out. -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network meeting notes, 29th June 2020
by Gaba 29 Jun '20

29 Jun '20

Hi! Network meetings are happening every Monday at 1700UTC on #tor-meeting in irc.oftc.net We had a meeting on June 29th and here are the logs and notes. Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-29-16.59.log… Pad: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Contents of the pad for today: == Network meeting pad! == Next meeting is at Monday 29th June 1700 UTC on #tor-meeting on OFTC. June Schedule: * Monday 29 June 17:00 UTC Welcome to our meeting! We meet each month at: Mondays at 1700 UTC On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the tor-project mailing list archive for older notes.) 1 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002857.html 8 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002865.html 15 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002877.html 22 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002890.html == Stuff to do every week == Let's check and update our roadmap: What's done, and what's coming up? Any change? Board: https://gitlab.torproject.org/groups/tpo/core/-/boards S28 & S30 - Continue after October - Ahf S55 - Nickm & dgoulet Non sponsor stuff DoS defenses = Dgoulet + Asn Library Size reduction = Ahf + Dgoulet sbws = Ahf + Juga Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws: [NEEDS NEW GITLAB LINK] Merge requests in Core: https://gitlab.torproject.org/groups/tpo/core/-/merge_requests Let's check out 0.4.4 release status and open tickets! Tickets in 0.4.4.x with no owner. https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta… nickm: https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta… dgoulet: https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta… ahf: https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta… asn: https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta… == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Check other's people call for help in their entries. Volunteers need help. Please help them when you are around. Maybe we should have times of day when different people are responders, and expectations of who helps. ------------------------------- ---- 29 June 2020 ------------------------------- == Announcements [please date] == == Discussion [please date] == [June 29th] Please take a look! (antonela) in the next 1 week to dev.torproject.org work -> https://gitlab.torproject.org/tpo/web/trac/-/issues/24132#note_2681345 [June 29th] David, Nick: please review s55 board https://gitlab.torproject.org/groups/tpo/core/-/boards?scope=all&utf8=%E2%9… === Active Proposed Policies === * Pull Request Guidelines (stalled) === Design proposals under discussion === 315: require more fields in directory documents (still waiting [6/1]) 316: flashflow (asn and nickm are reviewing, should schedule discussion with pastly. [5/18]) 317: dns (under discussion on ML [5/18]) 318: limit protovers (waiting for more commment; needs discussion [6/1]) 319: wide everything (nick replied on ml; waiting for more discussion [6/1]) 320: tap out again - Do we have a consensus to replace this with a "deprecate v2 onion services" proposal? If so, who writes it? [6/1] protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18]) 321: happy families (need feedback [6/1]) 322: dirport linkspec (need feedback [6/1]) == Recommended links == == Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! Nick: Week of 22 June (planned): - Go through backlog - Work on misc 0.4.4.x issues - Fix S55 bugs - More gitlab stuff, probably. - catch up on email backlog? Week of 22 June (actual): - Fiddle with gitlab - Review and merge - Work on various 044 tickets assigned to me, including: - Move Codestructure.md into Doxygen - Remove OPTIONS_DUMP_DEFAULTS - Work on various S55 tickets, including: - 34445 (remove authority semantics for assumereachable) - Other assumereachable handling - Catch up on email backlog - Look through Mike's congestion control proposal Week of 29 June (planned): - More S55 work - 044 work - Investigate problems building/running with Openssl 3 alpha (tor#34139) - Maybe move OSS-fuzz off of openssl 3? - Write a proposal for packing multiple commands into a relay cell. - More thinking on congestion control - Work on stable releases ahf: Week of 22/6 planned: - Trying to minimize myself in the Gitlab stuff for now. - Need to deal with review backlog. - Back to doing Fenix + Tor integration. - Get Tor network extension working on device with TGP sponsorship. Week of 22/6 actually: - Got help from Benjamin with certificates and all the Apple "security" stuff with running your own apps on your own devices... - Failed at completely detaching myself from Gitlab things: worked on a few minor issues and the label clean-up. - Tried to push for some sponsorship for CI for our Gitlab instance. - Read Mike's congestion pads/mails. - Got back to Fenix+Tor integration. Week of 29/6 planned: - Delete unused labels from Gitlab. - Try to solve Gitlab#41 with Hiro since it makes working with GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup. - Do merging/backporting of Tor things. asn: Week of 22/06 (planned): - More work on PoW proposal. Fold in David's work on the scheduler and derive results from that. - Hopefully merge #32040. - More reviews & merges. Week of 22/06 (actual): - Another version of the PoW proposal is out: https://lists.torproject.org/pipermail/tor-dev/2020-June/014381.html - OBv3 now has a bunch of new features as the result of the gitcoin hackathon: - SIGHUP support - status socket support - OBv3 is also in Debian sid - Wrote guidelines for gitlab review process: - https://gitlab.torproject.org/tpo/core/tor/-/wikis/NetworkTeam/GitlabReviews - Did a bunch of reviews & merges Week of 29/06 (actual): - More PoW work - A look at v3 metrics. - More OBv3 hackathon. Someone is hacking on distinct descriptor support. - Need to adapt the gitlab process to using MRs as discussed on Thurdsay. - A bunch more reviews & merges. jnewsome: Week of June 15 (planned): - Work out logging from the shim with the new file IO design - Help flesh out support for syscalls and libraries needed to run Tor - Start looking into code-coverage tools (gcov) Week of June 15 (actual): - Fixed logging destination from the shadow/phantom shim - Patched libc from package sources to allow benchmarking for "preload" interposition mechanism without having to reimplement more of libc - A little bit of initial benchmarking of shadow/phantom. (So far much slower, but have some ideas for improvement) - Backported centos 7 fixes for shadow https://github.com/shadow/shadow/pull/851 Week of June 22 (planned): - More profiling of shadow/phantom and start work on optimizations Week of June 22 (actual): - Ported "interposable libc" patch to centos 7 (our benchmarking platform). This version of glibc took a bit more work. - Switched ptrace-based shadow/phantom to use PTRACE_SYSEMU, substantially improving performance. Week of June 29 (planned): - Fix https://github.com/shadow/shadow/issues/853 - Help with shadow/phantom benchmarking and optimization as needed - Work on shadow test code-coverage measurement strategy pastly: Week of 18 May (planned): - Finish bones of external FlashFlow repo (python?) to control tor clients that perform FF measurements - Finish bones of little-t tor changes s.t. measurement can be performed - Discuss FlashFlow with network team devs as they have questions c: Week of May 25 (planned): - close up work on #33609 - get started on other s55 tickets, potentially knock out 'easy' ones first and take it from there - update https://trac.torproject.org/projects/tor/wiki/doc/gsoc with my information Week of May 25 (actual): - #33609 ready for review - started hunting down and working on other Sponsor55-can and -must issues - talking in #tor-project about wiki Week of June 1 (actual): - opened and made #34381 ready for review - IPv4 part of #32888 Week of June 8 (planned): - #33598 - IPv6 part of #32888 <-- do you have a ticket for it? Week of June 8 (actual): - #32888 IPv6 PR: https://github.com/torproject/tor/pull/1932 - requested reproducibility info for https://bugs.torproject.org/33598 -- maybe I'll start thread on tor-dev@ since trac is read-only - wrote Outreachy blog post explaining Tor's IPv6 goals Week of June 15 (planned): - during meeting, poke someone about https://github.com/torproject/chutney/pull/66 - chutney work with nickm (#34445 - #34448) - force myself to remain regularly active on tor-dev@ so we can get things done more efficiently :) - in general just check behind myself and others to clean up open issues in need of commentary or review Week of June 15 (actual): - started work on more chutney documention - opened discussions on gitlab about chutney components Week of June 22 (planned): - continue chutney discussion/work - #32888 / work on Address config to support IPv6 dgoulet: Week of 22/06 (actual): - Finalized #33233 and it is now merged. - Patch on small tickets: #40008 and #33618 - Reviewed and merged a series of tickets. - Patch on #40006 and merged as well. - Reviewed congestion control proposal from mikeperry. - Worked with asn on our Gitlab review process - Discussion with asn on v3 metrics - s55 sync with nickm. Week of 29/06 (planned); - s55 work: Remaining tickets are in #33049 - Write HSv2 deprecation blog post and hopefully publish -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Anti-censorship meeting notes, 25 Jun 2020
by Philipp Winter 25 Jun '20

25 Jun '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-25-15.58.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday June 25th 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://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam <-- it will be moved into gitlab * 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… * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 <-- it will be moved into gitlab * 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 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 <-- it will be moved into gitlab * 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 == Announcements == * == Discussion == * Gitlab review workflow * https://about.gitlab.com/blog/2016/10/25/gitlab-workflow-an-overview/#code-… * Move snowflake issues to snowflake-webextension / snowflake-mobile where appropriate == Actions == * == Interesting links == * Ongoing Internet measurement village talks this month: https://ooni.org/post/2020-internet-measurement-village/#schedule * Psiphon Data Engine: https://psix.ca/ == Reading group == * We will discuss Geneva on June 25th * https://censorbib.nymity.ch/#Bock2019a * 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-06-25): * Fixed and deployed #29184. * Improved emma's Makefile and filed a few minor issues. * Mostly wrapped up #34260. * Debugging and improving #31422. * Started working on IMV'20 presentation. * Brainstormed Salmon UI considerations in #31873. * Built new exitmap module to find yet another case of Bitcoin rewriting. Next week: * Wrap up #34260. Help with: * #33647 * #34260 cecylia (cohosh): last updated 2020-06-25 Last week: - reviewed #29184 - revised nat discovery feature (#34129) - trial refactor of bridgedb to get ready for a GetTor integration (#3780) - sponsor 28 evaluation prep - snowflake proxy on mobile work, reviews This week: - away on vacation Needs help with: - another review of #34129 - review/feedback on #3780 juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-06-11 Last week: - Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-06-25 Last week: - tried to grant admin access to the snowflake broker CDN configuration (#30510) Next week: - reply on revisions to NAT behavior (#34129) Help with: Antonela: 2020-06-25 - (S30) planning activities for the user group in HK: - Run emma https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%2… - Discovery issues with Bridges flow - working on the script https://gitlab.torproject.org/tpo/ux/research/-/issues/4 agix:2020-06-11 Last week: -Started taking a look at #34318 -(Will be occupied due to university exams till 06-26) Next week: -Work on fixing #34318 Help with: - hanneloresx: 2020-06-25 Last week: - Read existing documentation for BridgeDB and GetTor. Get acclimated to GitLab. Next week: - Work on #33727 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-06-25 Last week: - MR: Fininshed working on #40001 (Snowflake) - Finished Part A of project and started Part B - MR: #1 (Snowflake Mobile) on Snowflake Mobile project Next week: - Working, planning on Part B of project. - Making MRs for #2 (Snowflake Mobile),#34277 (Snowflake) Help with: -

1 0

Meetrics meeting notes, June 25th 2020
by Gaba 25 Jun '20

25 Jun '20

Hi! Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net Next meeting on July 2nd we will talk about the roadmap for July. Here are the minutes for the meeting of June 25th: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-25-14.59.log… And here is the pad notes: Public pad URL is: https://pad.riseup.net/p/tor-metricsteam-2020.1-keep Weekly meetings, every Thursday at 15 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). Links: Old Metrics Team wiki page (including roadmap) : https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam << this will be moved to gitlab wiki >> OnionPerf board: https://gitlab.torproject.org/tpo/metrics/onionperf/-/boards OnionPerf milestone: https://gitlab.torproject.org/groups/tpo/metrics/-/milestones/1 Next meeting: Thursday, July 2nd, 15 UTC ----------------------------------------------------- Agenda Thursday, June 25th, 15 UTC ----------------------------------------------------- Board https://gitlab.torproject.org/tpo/metrics/onionperf/-/boards https://gitlab.torproject.org/tpo/metrics/website/-/issues/40001 https://gitlab.torproject.org/tpo/metrics/onionperf/-/issues/33974 Reviews Any blockers, anyone? Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-25-14.59.log… Next week: Roadmap for July -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

TPA wiki migrated to GitLab
by Antoine Beaupré 24 Jun '20

24 Jun '20

Hi, Just a short note to let you know that the sysadmin (AKA TPA) wiki, previously known as: https://help.torproject.org/tsa/ ... was migrated to GitLab: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/home Redirects to the new wiki are in place, so you don't absolutely have to update your bookmarks, but I figured it was worth announcing it to avoid any surprises. That project is also, incidentally, where you file support requests to us: https://gitlab.torproject.org/tpo/tpa/team/-/issues The migration was somewhat interesting, because I had to rewrite the ikiwiki-specific Markdown content into GitLab's Markdown. I also had to make up a migration procedures for git repositories, which we may want to reuse for other repositories. All the gory details are, of course, documented in this GitLab issue: https://gitlab.torproject.org/tpo/tpa/team/-/issues/34437 As usual, if you need our help, the "how to get help" support policy is where you find that info: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-2-support… Thank you for your attention, a. -- Antoine Beaupré torproject.org system administration

1 0

Have "anything goes" blog post?
by Philipp Winter 24 Jun '20

24 Jun '20

We have many comments on our blog that are unrelated to the respective blog post but still bring up reasonable topics. To make it easier for our users to be heard, why not have an "anything goes" blog post once a month? A user suggested this idea over here: <https://blog.torproject.org/comment/288185#comment-288185> The idea is for users to comment on any topic as long as it's not in violation of our blog comment policy (minus the "on topic" requirement): <https://trac.torproject.org/projects/tor/wiki/doc/community/blog-comment-po…> Hopefully, this will give our users an opportunity to talk about problems they have, ask us questions, and request features. How does that sound? I can draft the blog post and help moderate comments but would appreciate a few people helping with that. I propose June 26th -- the last Friday this month. I suggest giving it a shot as a one-off experiment and repeat if it goes well. Cheers, Philipp

10 15

The Gitlab ticket workflow of the network team
by George Kadianakis 23 Jun '20

23 Jun '20

Hello, me and David assigned reviews today and here is the procedure we came up with. Unfortunately, because we dont use merge requests in gitlab yet, we cannot use the natural procedure of gitlab when it comes to code reviews, so we had to hack something up with labels for now. == Marking something for review == When you write code and you want to mark it for review, please add the "Needs Review" label. == Assigning reviews == When me and David assign reviews, we use the "Reviewer" label and then assign the ticket to the right reviewer. == Finding your reviews == To find your reviews you use this query: ahf: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… nickm: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… asn: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… dgoulet: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… == Reviewing your reviews (happy path) == When you do your reviews, the happy path is that the patch was good and you merge it and you move forward. Because ahf can't commit yet, when ahf reviews code, he can add the label "Merge Ready" and then its our responsibility to merge it. Hopefully ahf will start committing next week and we won't need to do that. == Reviewing your reviews (sad path) == If the patch was not good, you need to put it in needs revision. This is crammy in our workflow (because of lack of MRs) but we suggest the following procedure: - You add the "Needs Revision" label. - You don't change any other label. It's now the responsibility of the code author to notice this label, and revision the code. It's also the responsibility of the reviewer to poke the code author if they haven't done this in a reasonable amount of time. == TODO == How to handle backports? Transition to MR workflow which will greatly improve the sad path above.

2 3

PrivChat w/ Tor - you're invited!
by Al Smith 23 Jun '20

23 Jun '20

Hi Tor people! Next Tuesday, we're hosting Tor's very first PrivChat (https://torproject.org/privchat) a live conversation and Q&A event series designed to bring together experts in the privacy, tech, and human rights space + host a platform for the community to ask questions and get answers + raise funds for Tor. You are invited!!! What: PrivChat with Tor | Online Privacy in 2020: Activism & COVID-19 When: Tuesday, June 23 @ 18:00 UTC / 2:00pm Eastern / 11:00am Pacific Where: https://youtu.be/gSyDvG4Z308 Panelists: -- Carmela Tronsco (EPFL) -- Daniel Kahn Gillmore (ACLU) -- Matt Mitchell (Ford Foundation) -- and facilitated by our very own Roger Dingledine Fundraising element: Event is free. We are encouraging attendees to consider becoming monthly donors if they feel inspired by the content of PrivChat, but watching is free and there is no registration. Hashtag: #PrivChatWithTor. Please help us spread the word! Even a retweet from @torproject to your people would be great. We'd love your support during our first PrivChat. <333 Al -- Al Smith (they/them) Fundraising • Communications The Tor Project

1 1