August 2019 - 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

update on ticket system discussion
by Gaba 17 Sep '19

17 Sep '19

Hi! There has been some discussion in the 'corridors' of Tor and in the last meeting face to face during the session on 'internal tooling' and specifically about tickets system. I'm sending this mail to try to summarize what the discussion has been until now, make it transparent and try to get an agreement on how to move forward. Problem: - Trac software is not being mantained (from our perspective of users of Trac this is a bomb getting ready to explode) [0] Solution - Move out into a better (possible feature parity with what we use now AND integration between project management tool and tickets) and mantained ticketing system. Discussion until now - A few years ago there was a survey [1] on which features people would like to see in a new ticketing system. - There is a ticket [2] that has a discussion on features needed and a document [3] that brainstorm features between trac and gitlab. - The last meeting in Stockholm there has been several discussions on what is needed. [4] - In 2017 Hiro and the network team experimented with the oniongit.eu Gitlab instance. - In 2019, a test instance was setup, called "dip.torproject.org"[5], that a few projects are using right now to test its use. We are mostly considering Gitlab (until now) because: 1. We can host it ourselves and not have other company control the data. 2. It is open source [6]. 3. It is mantained [7]. 4. It supports the project management tool that we are interested in. Before moving forward we need: 1. Consensus or a clear compromise on what to move into. 2. A plan on how the migration to a new ticketing system will happen. I started drafting it here (thinking that Gitlab would be the new one) [8]. This plan is still a work in progress and we will continue doing it when we all agree on which system to move into. cheers, gaba [0] https://trac.edgewall.org/roadmap [1] https://docs.google.com/spreadsheets/d/1V4Faq2y9vv8XTp-OADl4YRMTiRB0G9DHvj2… [2] https://trac.torproject.org/projects/tor/ticket/30857 [3] https://nc.riseup.net/s/TYX37BDT4eQfTiW [4] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… [5] https://dip.torproject.org [6] https://gitlab.com/gitlab-org [7] https://gitlab.com/groups/gitlab-org/-/roadmap?layout=MONTHS [8] https://nc.riseup.net/s/SnQy3yMJewRBwA7 -- Project Manager: Network, Anti-Censorship and Metrics teams and OONI support gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

5 11

Anti-censorship meeting notes, 29 Aug 2019
by Philipp Winter 29 Aug '19

29 Aug '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-08-29-16.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday August 29nd 17:00 UTC Weekly meetings, every Thursday at 17: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: https://dip.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/torproject/anti-censorship/gettor/boards * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 29th August 2019 ---- --------------------------- == Announcements == * Our obfs4 bridge campaign is now live! * https://blog.torproject.org/run-tor-bridges-defend-open-internet == Discussion == * == Actions == * Let me know what we should include in our monthly report: https://pad.riseup.net/p/ThKAw7J-lXGU3AY3uBwp == Interesting links == * == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. hiro: (2019-08-29)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) - Add script to update download endpoints from gettor VM: https://dip.torproject.org/torproject/anti-censorship/gettor/blob/master/sc… - Configure github and gitlab so that getulum can push - Add script to export stats in CSV: https://dip.torproject.org/torproject/anti-censorship/gettor/blob/master/sc… - Delete old gettor instances on gettor VM - gettor should use ansible for deployment and updates: started coding recipes Next week - use archive.org as new distribution endpoint: upload files to archive.org - review specs: are specs up-to-date? should we change something in the specs? - review request channels: We are currently only using email. Is it worth to have a chat bot on twitter to distribute links? should we consider other chat platforms instead? - statistics for help emails are not summing up correctly - prepare repo and web for locales hiro: (2019-08-22)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) This week: gettor-web: updates to documentation and website (current website is outdated) gettor: fix pipeline. Talk to browser team about the recommended version file format (so that our scripts do not break) check documentation how to make deployment easier. can it be done via jenkins? ci? Next week: gettor: use archive.org as new distribution endpoint: upload files to archive.org review specs: are specs up-to-date? should we change something in the specs? review request channels: We are currently only using email. Is it worth to have a chat bot on twitter to distribute links? should we consider other chat platforms instead? Past week: on vaca! phw: This week (2019-08-29): * Helped with launching Tor bridge campaign * Tested new obfs4 bridges and worked with some operators who ran into issues * Interacted with university folks who may be able to run new default bridges for us * RACECAR meeting to discuss progress on obfs4 improvements * Made some progress on obfs4 improvements (#30716) * Read up on website fingerprinting literature to understand status of ML-based attacks * Made me realise that obfs4's flow obfuscation was misguided * Experimenting with improving the way obfs4 shapes its flows * Re-built and re-deployed snowflake broker (#31454) * Re-built and re-deployed meek-server on BridgeDB (#31455) * Filed ticket to get rid of BridgeDB's silly chatspeak (#31528) * Started working on code to extract stable and unallocated bridges from BridgeDB for manual distribution * Worked with our new default bridge operator (#31164) Next week: * More work on obfs4 improvements Help with: * Gaba: (updated August 22nd) Last week (): * added september issues to the gitlab kanban board https://dip.torproject.org/torproject/anti-censorship/roadmap/-/boards This week (planned): * ahf - on leave Last week: - Worked on #28930 This week: - Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info. - Continued to work on a tool to convert Trac tickets into Gitlab tickets. cecylia (cohosh): last updated 2019-08-29 Last week: - deployed /metrics handler (#31376) and updated snowflake metrics spec (#31493) in preparation for CollecTor integration - implemented and updated snowflake webextensions with fix for session termination (#31385) - implemented and deployed a fix for the proxy ID reuse vuln (#31460) - moved snowflake metrics spec to snowflake repo (#31407) - fiddled with snowflake metrics spec to get it working for collecTor (#31493) - finally got around to updating snowbox - made progress on sequencing layer (#29206) - started reading up on NSF SaTC TTP This week: - make a patch for the proxy---broker communication (#29207) - stay updated on pion rbm build (#28942) - snowflake dogfood - continue work on sequencing layer (#29206) - revisit snowflake reachability scripts, check status of tests, and enhance (#30368) Help with: - review of progress on sequencing layer (#29206) - review of putting snowflake spec in git repo (#31407) - quick review of proposed protocol changes for proxy---broker (#29207) <-- not urgent, i can move forward with what i have catalyst: week of 08/22 (planned): - reorienting after leave - mostly sponsor31 stuff week of 08/22 (actual): - mostly sponsor31 stuff week of 08/29 (planned): - mostly sponsor31 stuff (control protocol refactoring that will hopefully lead to better bootstrap reporting) arlolra: 2019-08-29 Last week: - merged #30310 - helped with some review Next week: - add a build step / documentation for code reuse in cupcake - make an attempt at #31391 Help with: - dcf: 2019-08-29 Last week: - merged the meek-http-helper port to WebExtension (#29347) - read and summarized the Point Break paper from Usenix 19 https://lists.torproject.org/pipermail/anti-censorship-team/2019-August/000… - tried to reproduce a Snowflake packaging problem on Debian 9 (#31380) - reviewed serna's patch for broker-controlled Snowflake poll interval (#25598) - Helped deploy snowflake proxy webext-0.0.10 (#31385, #31200, https://archive.org/details/snowflake-webextension-0.0.10 ) - Redeployed my meek-server instances to mitigate a Go HTTP/2 DoS (#31455) - reviewed a patch to remove proxy IDs from broker /debug (#31460) - worked on an rbm build of Snowflake with pion-webrtc (#28942) - applied a documentation fix for file ownership in snowflake.tpo deploy (#31496) - filed a ticket to link Cupcake from snowflake.tpo (#31497) - Turbo Tunnel prototyping. Next week: - review Snowflake sequencing layer (#29206) - add snowflake to the Windows build with pion-webrtc (#28942) - Turbo Tunnel prototyping Help with: - redeploy meek-azure bridge for Go net/http DoS vulnerability (#31455) - needs attention from inf0 at Team Cymru (dcf has sent email) - someone to try to reproduce my checksums from https://bugs.torproject.org/28942#comment:43

1 0

Roadmap for hypothetical network health team
by Roger Dingledine 29 Aug '19

29 Aug '19

Here is an area list for a hypothetical future "network health" team. I say hypothetical because we have no near-term plans to form such a team -- but imo the task areas make sense together. Some of them are being handled by other teams right now, but some of them aren't getting as much attention as they need. (1) track community standards about what makes a good relay - publish up-to-date expectations for relay operators - set best practices for how to set relay families - detect and resolve bad relays - exitmap, sybil detection, hsdir traps (2) anomaly analysis / network health engineer [with network team] - establish baselines of expected network behavior - look for and resolve denial of service issues - track connectivity issues between relays - look for relays hitting resource limits (3) make sure usage/growth stats are collected and accurate - track network performance, relay diversity by various metrics - count users [with network team and metrics team] - monitor bridge growth and usage [with censorship team] (4) relay advocacy [with community team] - maintain docs for setting up and running relays and bridges - grow a cohesive community of relay operators so they have peers - keep relays on the right tor versions - relaunch a gamification / badge system for lauding good relay progress - strengthen relationships with non-profit orgs that run relays - help companies that want to offset their tor network load (5) maintain the components of the network - maintain directory authority relationships - keep bandwidth authorities working (including setting the right balance between speed and location diversity) - have enough tor browser default bridges, and keep them running smoothly [with censorship team] - update the fallbackdirs list

3 2

Campaign: Run a Tor Bridge
by Stephanie A. Whited 28 Aug '19

28 Aug '19

** *Hello Tor, * * You all know the importance of Tor bridges for circumventing censorship, and today we’re calling on our community to help censored users by running them. Bridges are relatively easy, low-risk, and low bandwidth to operate, but they have a big impact on people where the internet is under oppressive control. We now have new documentation for how to set them up. We have guides for several Linux distributions, FreeBSD, OpenBSD, and docker [1]. If you set up a bridge before September 30, you could be one of 10 bridge operators to be randomly selected for a Tor t-shirt. More details can be found in phw’s post [2]. If you cannot set up a bridge now, you can still help. You can share your support of running or using Tor bridges on social media with the hashtag #RunTorBridges [3] and a link to the post. Please also share the post with any friends or communities you think would be able to help. If there’s someone you think would be helpful for us to reach out to, please let me know. Thanks for your support. Best, Steph [1] https://community.torproject.org/relay/setup/bridge/ [2] https://blog.torproject.org/run-tor-bridges-defend-open-internet [3] https://twitter.com/hashtag/RunTorBridges?src=hashtag_click * -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Fingerprint: E976 9771 7D46 2E63 9697 9F6D 6D6B 72C3 39A8 76AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

nextcloud: next steps
by Gaba 27 Aug '19

27 Aug '19

Hi! We have been evaluating Nextcoud [0] this year as a replacement for storm [1] and some of us have been using it and giving feedback [2][3] . The next step is to meet with all people interested in this transition (or not) to - discuss cons/pros of nextcloud for Tor and try to make a decision on moving forward. The meeting day will be: Tuesday August 27th, 1800 UTC at #tor-meeting in irc.oftc.net If you can't come to the meeting but you still want to say something please reply to this mail in tor-project@ or send me or Linus a private message. Thanks! gaba [0] https://trac.torproject.org/projects/tor/wiki/org/operations/services/nextc… [1] https://storm.torproject.org [2] https://trac.torproject.org/projects/tor/ticket/30869 [3] https://trac.torproject.org/projects/tor/ticket/29415 -- Project Manager: Network, Anti-Censorship and Metrics teams and OONI support gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

2 2

Join Our DocsHackathon Next Week - Sept 2nd - 6th 2019
by gus 27 Aug '19

27 Aug '19

Hi, Documentation is extremely valuable to the health of open source software projects, but it is often overlooked. Due to the amount of interest we received during our search for a Google Season of Docs candidate, we're kicking off a week-long documentation hackathon Monday 2nd September 00:00UTC to Friday 6th September 23:59UTC. This is your opportunity to help us keep our documentation up to date and relevant for millions of Tor users around the world. We’ll also be rewarding the top 3 contributors with prizes at the end of the week. We are looking for copywriters, front-end devs, testers, and content reviewers to help us improve our documentation and its relevancy. Don't feel like any of these apply to you but still want to help out? Chat with us on IRC (#tor-www - irc.oftc.net) or the community team mailing list to join us and get involved - <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team>. ## How to participate in the DocsHackathon 1. Register: https://survey.torproject.org/index.php/726752?lang=en 2. Take a look at all of the tickets marked with the "DocsHackathon" keyword on Gitlab - <https://dip.torproject.org/groups/web/-/issues?scope=all&utf8=%E2%9C%93&sta…> 3. If you have a documentation issue that is not currently reflected in Trac, Gitlab or GitHub, create it, tag it and let one of us know on IRC channel #tor-www so we can assign some points to it. 4. Choose a ticket and start working on it! You can submit Pull Requets on GitHub or register on our Gitlab instance to submit merge requests there. 5. A contribution will be counted when your PR or merge request is merged to the master branch of the relevant repository. 6. The awards and prizes to contributors will be announced after all the merges were done. For more details on how you can contribute, check out our DocsHackathon wiki <https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH…>. We are a small nonprofit with a big mission, and we sincerely appreciate your help getting our documentation up to speed. We're looking forward to working with you next week!

1 0

Tor Browser team meeting notes, 26 August 2019
by Georg Koppen 27 Aug '19

27 Aug '19

Hello! We had our weekly browser meeting yesterday held in #tor-meeting2. Here comes, as usual, the IRC log http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-08-26-17.31.l… and our items from the pad: Discussion: sysrqb: what is the expectation of our mozconfigs in tor-browser.git? (GeKo: #23656. They should be the canonical ones I think so that both local and rbm builds are in sync) mcs and brade (will miss the meeting today): Last week: - #30429 (ESR 68 Rebase). - revised the updater patches in response to acat’s feedback (thanks!) - #29430 (Use uTLS for meek TLS camouflage in Tor Browser). - posted patches for review (but it seems that they need more work). - created ticket and patch for #31487 (Modify moat client code so it is compatible with ESR68). - created ticket and patch for #31488 (moat: support a comma-separated list of transports in Tor config). - created #31491 (clean up the old meek http helper browser profiles). - created core Tor ticket #31495 (cannot configure bridges). - Responded to Antonela's comments in #30237 (Onion Services client auth prompt). - Did a little testing for #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - Did some quick testing of the new macOS ESR68 Tor Browser nightly build. - Helped with triage of incoming tickets. This week/upcoming: - #29430 (Use uTLS for meek TLS camouflage in Tor Browser). - investigate circuit display breakage when meek is used. - #30429 (ESR 68 Rebase) — rebase updater patches. - test the ESR68-based updater on Windows. - We have several family commitments this week and had planned to only be working on Tuesday and Wednesday (27-Aug and 28-Aug). - Now Tuesday 27-Aug will be a partial day because we will attend the funeral of a friend. - We will be away from keyboard on September 5th and 6th (and Monday September 2 is a U.S. holiday). Pili: Last week: - OTF Browser proposal - S27 meeting This week: - Task re-org meeting tomorrow (Tuesday 27th @ 15UTC) - Tor Browser Release meeting on Wednesday 28th @ 18UTC - September Roadmapping and capacity planning - imported tickets for August in gitlab to help me with roadmapping for September - we need to look at what's going to be carried over to September and discuss time estimates - Team capacity for the month is currently 79 person days taking into account holidays and vacation (mcs, brade and sysrqb) - Please let me know if there's any other planned vacation/afk time I should know about - Please fill out the areas of expertise on the spreadsheet: https://nc.riseup.net/s/pLxWcGQD3THrXEd - S27 August report - OTF Browser proposal GeKo: Last week: - presentation at CCCamp (went well even though the acoustics were awful) - finished macOS toolchain (#30323) - thought more about notarization issue (#30126) - worked on windows toolchains (#28716 and #28328); final tests; patches for the former are up for review and I'll post patches for the latter later (barring unforeseen issues) - helped with the OTF proposal - again dealing with backlog This week: - release prep and building - final reviews for #30429 and #10761 - finish outstanding Windows toolchain issues - backlog tjr: - Began the WASM-support-for-extensions work: https://bugzilla.mozilla.org/show_bug.cgi?id=1576254 - Did a bunch of little mingw build patches last night - nothing urgent for Tor to worry about, they'll get to ESR68 when they get there - Still ( :( ) waiting in alloc/dealloc patch review https://bugzilla.mozilla.org/show_bug.cgi?id=1547519 - This is the only outstanding esr68 problem. esr68 needs --disable-malloc which is not in-tree. acat: Last week: - Ported #30683 and #31298 to esr68. - Updated rebased esr68 branch (#30429). - Added mcs/brade updater patches. - Added newer missing desktop patches from tor-browser-60.8.0.esr-9.0-1. - Backported patches (#2760 and #28711). - Patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1573276 (DTD locale leak patch regression) - Investigated changing noscript from security settings not working in nightlies (#31396). Next week: - Fix #31396. - Possibly address review comments on latest #30429 changes. - Review latest #31010 changes. - Try to upstream some patch in the backlog. - Keep testing nightly, file/fix tickets. sysrqb: Last week: Mostly 68esr rebase and testing Wrote draft Orfox R.I.P. blog post This week: Continue testing 68esr builds Help with build system, as needed Get nightly android builds? Publish Orfox blog post OTF proposal Next week: AFK mostly after release (until 12 Sep) boklm: Last week: - Backlog from previous weeks - Worked on #31449 (Signing tools for 32bit Linux are 64bit now) - Reviewed #30323 (macOS toolchain updates for esr68) and #31465 (tor-browser-build changes for macOS notarization) - Started looking at #31517 (Simplify macOS related bits in Firefox project) This week: - Verify that our esr68 mar-tools can be used for signing - Review #28716 (Create a mingw-w64-clang project) and other toolchain tickets - Investigate #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) - Review #30334 (build_go_lib for executables) and #31264 (tar.gz output files contain non-reproducible timestamps) - Help with new releases build Antonela: - #31286 - Tor network settings - are we OK using a plain-color version of the Tor Browser icon for the Tor network settings? mockup -> https://trac.torproject.org/projects/tor/raw-attachment/ticket/31286/C-abou… (GeKo: looks good to me, +1) pospeselr: Last Week: - network settings work (#31286) - completed the about:preferences xul and layout - started prototyping the 'request bridge' dialog - misc widl followup (#31458) This Week: - finish request bridge dialog xul, move on to wiring in logic from tor-launcher (#31286) - get a windows build with latest mingw and verify screen readers work as expected (#31458) I tried building release/nightly windows i686/x86_64 a couple times over the weekend and ran into some issues (first cbindgen not building which seems to be resolved, and now the firefox project pointing to a tag that supposedly doesn't exist ( tor-browser-68.0esr-9.0-1-build2 ), haven't investigate further, but is there a known working windows sku in tor-browser-build right now?) (GeKo: let me give you some bundles after the meeting; I have patches to enabled Windows nightly builds again) sisbell: - #30665: Get Firefox 68 ESR working for Android. Additional fixes to mozconfigs. Now working for arm7, arm8, x86. Ready for integrating patches. This week: - #30665: Work with sysrqb on getting patches applied. There is a build break if we disable webrtc, so will investigate this - Add x86_64 android support Georg

1 0

Network team meeting notes, 26 August 2019
by Nick Mathewson 26 Aug '19

26 Aug '19

Hi! You can find the transcript of our latest meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-08-26-17.00.html Below are the contents of our meeting pad when the meeting was done: = Network team meeting pad! = This week's team meeting is at Monday 19 August 1700 UTC on #tor-meeting on OFTC. We have changed the day from Tuesday to Wednesday. August schedule: * Monday 12 August 1700 UTC * Monday 19 August 1700 UTC * Monday 26 August 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes 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.) In-person meetings: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… 22 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002401.html 29 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002408.html 7 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002418.html 12 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002431.html 19 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002435.html == Stuff to do every week = * Let's check the 0.4.1 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://dip.torproject.org/torproject/core/tor/boards * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… == 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. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. * When you are overloaded, it is ok to say "no" to things. * And it is ok to reschedule things. ------------------------------- ---- 26 August 2019 ------------------------------- == Announcements == AFK ahf will be AFK all of August for BornHack and CCC Camp, but will be on IRC every now and then On September there is a technical writer from Google Season of Docs starting to work with us on rewriting the Tor manual page. She will be participating in the network team meetings. Her project: https://developers.google.com/season-of-docs/docs/participants/project-tor We are moving the kanban board from storm into https://dip.torproject.org/torproject/core/tor/boards . This will help lead a plan for migration into dip.torproject.org. The release date for 0.4.1.x-stable is postponed to 20 August, so that it will come out _after_ Nick is back from vacation. Please get all 041 blockers fixed and merged if possible? People working on sponsor 31 will meet on Thursday August 29th at 2300 UTC. We will talk in #tor-meeting and the agenda will be here:https://pad.riseup.net/p/IRjuGtQkWNKZLc7qskDb == Discussion == * [gaba] There are some tickets left from August in the Roadmap. Do we icebox them? https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… teor says: it's still August for 8 more days? * [gaba] do we schedule next network team retrospective? It may be a good idea to skip until end of September as many people were on leave in August. <-- It will be on late September --> == Recommended links == Ricochet Refresh with Tor 0.3.5.8: https://ricochetrefresh.net/ macOS 10.5 has a read-only system volume and a redesigned path structure. Standard Unix tools shouldn't be affected, but some builds or apps might be: https://eclecticlight.co/2019/08/21/its-time-to-test-your-scripts-against-c… the onion talk at ccc camp https://media.ccc.de/v/Camp2019-10340-updates_from_the_onion == 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! gaba: (updated on august 23rd) Last week (actual): . roadmap in gitlab: uploaded september issues . s31: scheduling check-in for this week . ipv6 funding proposal This week (planned): . s31 . scalability funding proposal Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 19 August (planned): Urgent: - config.c refactor code review (#30914), because we want to get it done by the end of August Roadmap: - finish add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - split off bugs I found while writing the control trace code - finish small 0.4.1 tasks - finish remaining code reviews, except for neel's big PR that I will split up Other: Week of 19 August (actual): Urgent: - CI monitoring - IPv6 funding proposal - release notes fixes for 0.4.1.5 Roadmap: - finished some code reviews - reviewed big config refactor PRs: - #30914 - merged - #30935 - ready for merge - #31240 - in the middle of the review - responded to reviews on my code - practracker bug fixes for #30979 and #31462 - backport deciding, tagging, and making backport branches from master PRs - bug fixes for monotime coarse conversion overflows (bug only in master) #31482 - diagnosing another bug in the token bucket refactor #31483 - implemented #23818 and #23507 and the associated spec change Other: - worked on #21003 so I could see the IPv6 addresses in logs to review #31088 <<-- gaba: this is not in the roadmap. what was the priority about it? Thanks! I was talking about #21003 and not the review -->> - I was assigned #31008 to review. I needed to see the IPv6 addresses in logs as part of the review. So I did #21003. - For more details see https://trac.torproject.org/projects/tor/ticket/21003#comment:17 - We can also make it Sponsor27-can, because it is useful for debugging #23818 and #23507 - helping with rustc version CI changes - helping relay operators with various issues Week of 26 August (planned): Urgent: - CI monitoring - config.c refactor code review, because we want to get it done by the end of August Roadmap: - finish add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - split off bugs I found while writing the control trace code - finish small 0.4.1 tasks - finish remaining code reviews, except for neel's big PR that I will split up - do the backports that are due after the 0.4.1.5 release, switch hidden tags - backport deciding Other: - team policies: commit bit and roles? Week of 26 August (actual): Urgent: Roadmap: - reviewed big config refactor PRs: - #30935 - ready for merge - #31240 - in the middle of the review Other: - helping relay operators with various issues Nick: Week of 19 August (planned): - Release 0.4.1.5 (stable) - More 29211 (configuration refactor) work. Hoping to reach the point where 1 module is module-wise configured - Review and merge - Revise old branches after they're reviewed. - Finish and submit walking onions paper. Week of 19 August (actual): - Stopped new work on 29211 pending catch-up from reviews - Released 0.4.1.5 stable - Review and merge - Worked on Walking Onions paper - Pending Coverity issues (pending) Week of 26 August (planned): - Revisions for 31240 (make confparse handle compound formats and objects) - Review and merge - Finish 31241 (refactor conf validation), make it needs_review - If we catch up with merge and revision on 29211: move on to 30866. - Practracker tests (31477) - Start early on September roadmap items, time permitting. Mike: Week of 8/19 (planned): - Medical leave Week of 8/19 (actual): - Medical leave Week of 8/26 (planned): - Catch up on mail/tickets - Work on circpad dev doc Need help with/at risk of dropping this month: - Circpad doc writing? (asn?) - Firefox ESR network code review - Deep-thought-required research project followup (masque, BGP, ECN, etc) - Relay community drive/mgmt (and related LTS herding) - Circpad documentation + Sponsor 2 report catalyst: week of 08/19 (2019-W34) (planned): - catching up after leave - skimming IRC highlights; please email me if you think i've missed something important - reorient on current CI status week of 08/19 (2019-W34) (actual): - made progress on #30984 (key-value lines for control replies) -- fixed some memory management issues, started improving documentation - worked some partial days (medical) week of 08/26 (2019-W35) (planned): - reviews - investigate some Jenkins failures - get #30984 ready for review (key-value lines for control replies) -- still documenting some things asn: Week of 19/08 (planned): - Read [tor-dev] [prop305] Introduction Point Behavior - Check open hackerone issue. - Finish up with reviews and merges before CCC camp. - Attend CCC camp and participate in the talk. - Speak with the onionbalance maintainer during camp to make plans for v3 onionbalance. Week of 19/08 (actual): - Replied to [tor-dev] threads - Cleared up hackerone issue. - Reviewed and revised #30924 (DoS ticket) - Finished all urgent reviews/merges but not all of them. - Worked on onionbalance: - Met with Donncha at camp and talked onionbalance. - Spoke with atagar about #31369 and reviewed his new code. - Mapped out what needs to be done in #31369 from my side. - Did the talk at camp! Week of 26/08 (planned): - Finish up reviews/merges that piled up further. - More work on stem side of onionbalance (#31369) - Find time to watch the recording from the latest mozilla meeting - Think about HS issue: #20212 ahf: - on leave Week of 22/7 (planned): - Do reimbursement - Go over all notes from Stockholm that seems relevant to me. - Follow up on pre-Stockholm items: - Continue figuring out some info on a potential Danish funder. - Continue with #5304 and #28930 Week of 22/7 (actually): - Did reimbursement - Went over all notes from Stockholm. - Followed up on pre-Stockholm items: - Continue figuring out some info on a potential Danish funder (postponed until they are back from vacation). - Continued work with #5304 and #28930 Week of 29/7 (planned): - Finish off #5304 and #28930 before going on vacation. - Review Roger's DEFCON slides. - Do you need any help from me before I leave? dgoulet: Week of 19/08 (actual): - #30924 has been revised and now merge_ready - Worked on HS timeout issues (#30200 + #28841). Built a tracing system to follow the HS dance coupled with circuit build time and timeout. Already paid off, #31490 is a bug that came out of it. - Spent time chasing a EWMA cell scheduling issue but fell off the radar after some hours, lack of time to continue. Week of 26/08 (planned): - Continue on #30200. - Address revisions needed for #30924 if any comes.

1 0

Tor Browser Release Meeting this week
by Pili Guerra 26 Aug '19

26 Aug '19

Hi everyone, A reminder of our Tor Browser release meeting happening this week on Wednesday 28th August at 18UTC. We’ll be discussing the upcoming 9.0 release as well as plans for the EOY Fundraising campaign. Please join us to discuss this and any other Tor Browser release related work. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0