March 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

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

February 2019 User Feedback Report
by wayward 03 Apr '19

03 Apr '19

Hey, team! Welcome to the February 2019 user feedback report! I hope your winter is as close to over as mine is. For more information on what users and community members were talking about this month, check out the February/March 2019 User Feedback pad [1]. TL;DR: There didn't seem to be much user feedback that we haven't seen in previous months. Users seem to be experiencing relatively few new issues with TB 8.0.6 compared to past releases. - Reddit is mostly buzzing with the same questions we usually see. I'm also seeing quite a bit of confusion from Android users who aren't sure which Android app they should use (Orfox? TBA? Orbot?). - Tor is still broken for screen readers. [2] Now, on to the feedback! Scroll further down to see a summary of Reddit posts, some points from Google Play Store reviews, a list of the most common Stack Exchange tags from the month, and a collection of some notable issues and bugs mentioned by users in January. --- Most common questions on Reddit: - Which Android/iOS app should I use? - Do I need to download both 'Orbot' and 'Tor Browser for Android' on Android? - Why can't I connect/why aren't my bridges working? --- TBA Reviews & Feedback on Google Play Store: The average review score is still at 4.2 stars. It seems like users are still unsure how and when to use bridges in TBA. We can address these questions in the future TBA manual. --- Most common stack exchange tags: tor-browser-bundle: 18 this month configuration: 16 this month relays: 8 this month tor-install: 6 this month anonymity: 5 this month connection: 5 this month --- Notable bugs, fixes, & issues mentioned by users: #27503 [2] - Disabling accessibility on Windows breaks screen readers - OPEN #29175 [3] - Tor 0.3.5.x mishandles empty socks5 auth - CLOSED #27604 [4] - Relocating the Tor Browser directory is broken with Tor Browser 8 - OPEN #27249 [5] - Tor 8.0a won't let user log in to Disqus - OPEN #27543 [6] - QR code on http://web.whatsapp.com is only shortly visible in Tor Browser 8 - CLOSED, but mentioned by a user on the blog [7] - reopen? #28802 [8] - Integrate PTs and bridge support into Tor Browser - NEEDS REVIEW --- That's it for the month of February! If you want to know more, please do check out the February/March 2019 User Feedback pad [1] or reach out to me via email (waywardwyrd at riseup dot net) or IRC (wayward). Thanks for reading! I'll see you all back here next month! - wayward ------ Annotations: 1. https://storm.torproject.org/shared/x1INkZCd4pYQHZ_Y3Vr9_lQxjMj5FjsZ9754h1N… 2. https://trac.torproject.org/projects/tor/ticket/27503 3. https://trac.torproject.org/projects/tor/ticket/29175 4. https://trac.torproject.org/projects/tor/ticket/27604 5. https://trac.torproject.org/projects/tor/ticket/27249 6. https://trac.torproject.org/projects/tor/ticket/27543 7. https://blog.torproject.org/comment/280063#comment-280063 8. https://trac.torproject.org/projects/tor/ticket/28802

7 11

Notes from March 28 2019 Vegas team meeting
by Karsten Loesing 29 Mar '19

29 Mar '19

Notes for March 28 2019 meeting: Roger: 1) PETS will have stipends available again this year. So if you are wanting to stay in Stockholm for PETS, consider putting together a stipend proposal. I will plan to get more details up on the website soon. 2) My debate with New York law enforcement last week, and my keynote at the identity conference this week, both went really well. I now have a pile of business cards I should follow up with. 3) Fyi, there's a board meeting tomorrow. 4) The overdue NSF reports are now in and approved. That saga is over. Let's do better for the next ones. :) 5) I delegated a request-for-Tor-talk-in-Europe to speaking@tpo. Are the right people on that list still? [answer: maybe we should merge it with comms, or maybe we should expand the list to include more variety of people. Neither list has anybody from Europe on it, for example.] 6) I've been running into a bunch of "threat intelligence" companies at recent conferences, and of course they're still hyping the dark web. We need to figure out a way to get the incentives aligned with these companies and their marketing teams. I might start by saying yes to a talk invite for a NYC-based company, and try to bring Isa along to take the momentum from my talk and try to build it into something. 7) We probably ought to sort out how we want to proceed with the NYU interactions. 8) I'm meeting with Philipp in person on Tuesday to talk through some of the anticensorship team roadmap vision things. 9) Did we make a decision on whom to recommend for the next Mozilla All-Hands? Is there a deadline for that? 10) Do we have any feedback on the feedback process? Feedback on tea time? Georg: 1) We got Pwn2Own-related releases out last week 2) Progress on finalizing Tor Browser 8.5 3) We have a new website, great! Do we plan to have a post-mortem? It might be beneficial for setting up the remaining portals and for future transitions 4) Gaba: https://blog.torproject.org/making-diversity-default-open-source-world has a ton of unhandled comments. I guess we'd need to figure out next time who is dealing with comments beforehand if the author is not available? Antonela: 1) We launched tpo.org yesterday 2) Made S27 OTF kickoff. 3) Tor Browser 8.5 release 4) Making IFF next week. Nick: 1) Libreplanet went fairly well. Lots of people interested in hacking on Tor. Bunches of people who hadn't heard of Tor. A user interested in v3 onion service usability. 2) Talking at Tufts next weekend: discussion about a policy student paper on taxonomy of "accountable anonymity" proposals. 3) Are we supposed to be doing anything to drive peer review? I just got my first peer review request. (Do you mean, as a team lead, if you're supposed to be reminding people? If yes, no. You don't need to drive it -- people have their info and should be ok. -ewyatt) isabela: 1) Spoke at 2 panels at Libreplanet and worked at booth last weekend. 2) Prepared for Board meeting tomorrow (friday 29th) 3) We got the Onion services contract w/ OTF! 4) Reviewing all reports that are due this week. 5) Finalized the invite list and almost done with sending invites 6) Worked on new website blog post. Sarah: 1) Still getting a nice stream of cryptocurrency donations and talking with two donors who are considering gifts >$5k. 2) Attended Data Privacy Summit in DC yesterday. 3) Sending a letter to small foundations who have given in the past, but not recently and will include some individuals for whom we have postal mailing addresses. 4) Set up welcome email for people who join our email list. First one went out to 10k people who joined in March. Alison: 1) LibrePlanet was good (I spoke at one Tor session and one Library Freedom session, also helped at the booth) 2) gave a talk on onion services to Temple University law students yesterday 3) otherwise, I'm entirely focused on Library Freedom Institute right now 4) community team is focused on the community portal right now 5) taking care of some preparations for RightsCon 6) preparing to work on some new funding ideas with Al and Sarah 7) question about feedback process: team leads are supposed to get feedback from their whole teams, but also one person "from the team" should be in group of three peer reviewers. Does this mean team leads should be reviewed by their whole team +2 or their whole team +3? Erin: 1) Paperwork, lots of paperwork. And emails. 2) Recruiting/screening for open positions 3) General HR stuff Mike: 1) working on Tor scalability strategy 2) Vanguards issues 3) Figuring out travel Karsten: 1) Published our last remaining technical report for Sponsor 13 which concludes this project. 2) Trying to upgrade TorDNSEL enough to run on Debian stable. Do we know any friendly Haskell developers who would be able to spend a few hours on doing smaller updates (e.g., apparently Data.HashTable has been removed in Haskell 7.8 and we need to switch to the hashtables package; things like this)? 3) Preparing for upgrading op-ab to a more recent OnionPerf version that supports v3 onion services. Arturo: 1) Working on the OONI Explorer revamp 2) Pipeline related work to support OONI Explorer 3) Preparing for IFF next week 4) Integrating a psiphon test into OONI Probe Steph: 1) talking about the new website! sent to press 2) working on the community portal 3) newsletter done and will be out in the next couple days 4) responding to inquiries 5) cryptocurrency page updates and related inquiries 6) spoke at libreplanet last weekend, helped with the booth 7) worked on a new welcome email for newsletter subscribers. added signups from recent conferences Sue: 1) Finalizing the Short Period 990 2) Finalizing the Sida Attestation Audit 3) General Accounting processes 4) Worked at the Libreplanet booth for a little bit on Saturday Pili: 1) At Infracon in Barcelona this week meeting lots of fantastic people 2) We got the website out! :) 3) Sponsor 27 Kick Off meeting 4) Sponsor 8 Final report final touches 5) Following up on Google Season of Docs 6) IFF next week

1 0

Tor Browser Release Meeting: Wednesday 27th March @ 1900UTC
by Pili Guerra 26 Mar '19

26 Mar '19

Hi everyone, Just a reminder of the Tor Browser Release meeting tomorrow (Wednesday 27th March) at 1900UTC on #tor-meeting. 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

February Communications Report
by Stephanie A. Whited 26 Mar '19

26 Mar '19

o/ In February, several comms folks gave interviews which are TBA. We launched a new survey to collect more #TorStories. We applied to be a vendor at Def Con and are still waiting to hear back. We helped with the upcoming launch of TPO and our new cryptocurrency page. Feb in links and stats: New blog posts https://blog.torproject.org/new-release-onionshare-2 https://blog.torproject.org/how-has-tor-helped-you-send-us-your-story Twitter https://twitter.com/torproject New followers: 3,358 Top tweets: https://twitter.com/torproject/status/1096408973425680384 https://twitter.com/torproject/status/1091407168316809216 https://twitter.com/torproject/status/1101229636187492353 Mastodon https://mastodon.social/@torproject New followers: 400 Instagram https://www.instagram.com/torproject/ New followers: 121 LinkedIn https://www.linkedin.com/company/tor-project/ New followers: 65 Facebook https://www.facebookcorewwwi.onion/TorProject New followers: 223 Newsletter https://newsletter.torproject.org/archive/2019-02-27-tor-stories-sharing-fi… Notable press https://gizmodo.com/i-cut-the-big-five-tech-giants-from-my-life-it-was-hel-… https://www.equaltimes.org/undertaking-the-crucial-task-of -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Key ID: 39A876AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

Tor Browser team meeting notes, 25 March
by Georg Koppen 25 Mar '19

25 Mar '19

Hello everyone! Our weekly Tor Browser meeting just ended and, as usual, here come the link to our IRC log http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-03-25-18.32.l… and the content from our pad: Week of March 25, 2019 Discussion: - adjusting meeting time (eu is doing the daylight saving thing the coming weekend) (GeKo: We'll switch to 17:30 UTC as our meeting time; I'll announce that on tbb-dev later this week) - blockers for 8.5 (GeKo: We restructured our `tbb-8.5` tickets so that it is clearly visible what are blockers for the next alpha (`tbb-8.5-must-alpha`) and what are blockers for the stable release (`tbb-8.5-must`)) - Letterboxing (GeKo: We'll get around June to help with that and test on esr60 already) tjr - investigated getClientRects. The finding indicate that there are active fingerprinting issues from this and similar APIs that leak at least major OS version (win7 vs win10) and some OS settings. I don't *think* it's used by ad network fingerprinting (yet?) though. https://bugzilla.mozilla.org/show_bug.cgi?id=1507879 - Investigated math routines. Confirmed these leak at least major OS version, maybe minor. On Linux it probably leaks distro or system libraries Don't think it leaks hardware information - Investigated chrome:// leak. Confirmed it leaks OS and browser version. Don't think it leaks anything else except maybe language mcs and brade: Last week: - Reviewed patch and commented in #29790 (Add build option to store profile in HOME directory). - Followed up on Mozilla bug 1434666 (updater failing on Linux — cannot find libraries). (GeKo: nice that rstrong would want to help us. We should take up that offer in case we need it :) Maybe some patch uplifting help or something) - Worked on #27484 (Onboarding: unintuitive not-navigation buttons). - Monitored #28925 (Core Tor: distinguish PT vs proxy for real in bootstrap tracker). This week: - Review patch for #29825 (Intelligently insert the Security Level button) - Finish patch for #27484 (Onboarding: unintuitive not-navigation buttons). - Begin #29768 (Introduce new features to users in Tor Browser). sysrqb: Last week: Release prep and release (x2) #28329 (more UI changes) Worked on #29238 (prevent crash after update) Briefly looked at #29859 (App crashes when playing video on Twitter) Looked at #29866 ("Request Desktop site" should use Desktop UAS) This week: Continue working on #28329, #29238, #29859 Discuss localization things Look at F-Droid again boklm: Last week: - Helped with building and publishing new releases - Fixed the resource-timing, user-timing and user-timing-worker tests for #27137 - Fixed #29812 (.mar files for 32-bit Linux are missing for 8.5a9) - Started adding android-x86 to the download page (#29845) This week: - Finish fixing #27137 and disable all currently failing tests - Finish fixing #29845 (Add android-x86 to the download page) - Make some patch for #26907 (Guard against failures during MAR file generation) - Fix #29868 (tor-browser-build fails in container-image-windows-i686 attempting to install package python-future) GeKo: Last week: - release prep (we got 4!! releases out this week; thanks for everyone who helped, in particular on the weekend) - wrote a patch for #26498 and backported a mozilla patch for android (#29843) - worked on #28622 (Tor Browser branding for Android) - tracked down #29859 (Playing videos on Twitter is not working and freezing the mobile browser) - investigated backporting the JS Poison patch (#29049) - worked on improved authenticode timestamping (#29614) - looked over sponsor 8 final report (draft) and upcoming funding proposal for esr transitioning work This week: - finishing #28622 - fix WebGL related issues (#29246) - try to come up with something for #29859 - reviews Pili: Last week: - Sponsor 8 report - Preparing for S27 kick off - Google Season of Docs This week: - Infracon - Finish off Sponsor 8 report - S27 Kick Off - Google Season of Docs - start writing some ideas down pospeselr: Last week: patch for #29825 (fix for upgrade path in #25658, inserts/moves torbutton and security level button, rather than resetting to defaults) begin investigating #27503 (broken screenreaders on win) filed #29868 (python-future no longer exists in jessie-backports) This week: #27503 fun sisbell: Last week: - Included Android PT Support in TOPL: (thaliproject#86) - Upgrade for Android Q (thaliproject#85) - needed to break apart tor executable directory from config dir due to security changes in Android Q. Updated to tor-android-binary 03.5.8-rc dependency - Fixed bridges API (and pulling of bridges text file from android resources) (thaliproject#78) - Added custom config of torrc for Java TOPL (thailiproject#78) - needed this to keep project in sync with Android changes This Week: - #27609 - integrate latest TOPL changes to tor-android-service - Submit TOPL PR - Fix merge conflict in tor-browser-build Orbot project - Test PT support working in browser - Review changes in Orbot main project to see if we should merge any back over antonela: Last week: - TB8.5 - #27484 - Onboarding - Done - #29768 - Introducing new features - Duncan uploaded a version, will review this week - Security Setting Tor Browser manual update is ready to go This week: - #28622 - TBA icon - #28329 - Network Settings, Bootstrapping Animation - #29768 - Review - Introducing new features - Debugging TB8.5a9 Security Settings - Prep for IFF, TBA user testing Georg

1 0

February Fundraising Report
by Sarah Stevenson 25 Mar '19

25 Mar '19

Hello people of Tor! The fundraising team accomplished a lot in February. ## Grants First off, the grants team submitted a full proposal to OTF for UX improvements and we should hear back about the final determination soon. Some additional work was done on a proposal for onion services through OTF (originally submitted in July 2018) and we are pleased that this grant has now moved into the contract phase. We also sent introductory letters to the Overbrook Foundation and the Sigrid Rausing Trust. We heard back from NLnet that they unfortunately did not accept our proposal to improve the Tor exit scanner. They did move our proposal to fund part of the Browser team’s ESR migration work to the second round, and we should hear whether or not we were accepted for funding soon. We also submitted a proposal to New Media Ventures for LFP/LFI, and it moved to the second round, but it was unfortunately not accepted. ## Wiki We now have a Fundraising Team Wiki! Check it out here <https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam>. We have also made updates to the Sponsors Wiki which is linked from that page. I still have to finish documenting the past YE campaigns, but they will be up there soon. Let us know if there is anything you would like to see in this space. We also want to call out the Grant Work Flow process <https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view?usp=…> our team uses to prospect, apply for, and manage grants, so you can get an idea of what our team (along with Project Managers and the Finance team) is doing behind the scenes as we apply for funding. ## Special Appeal We tried raising money to cover the cost of an Outreachy email, but had limited success with an email and push on social media. We plan to apply for their session that begins in December. ## Cryptocurrency The cryptocurrency donation page <https://donate.torproject.org/cryptocurrency> launched March 18th, but this has been a culmination of work that began last fall. So far we have raised over $10,000 from the page and have received nice buzz on Twitter. We’ll report more on these efforts and results next month. Let us know if you have any questions or suggestions. - Fundraising Team

1 0

Notes from March 21 2019 Vegas team meeting
by Karsten Loesing 25 Mar '19

25 Mar '19

Notes for March 21 2019 meeting: Georg: 1) We got our planned releases out (8.0.7 and 8.5a9) 2) We might need to release security updates quickly this week depending on today's pwn2own results 3) Worked together with ln5 on our upcoming NextCloud evaluation (https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure…) 4) Release preparations for 8.5 Sarah: 1) Cryptocurrency page launched and we've raised over $10k from it so far https://donate.torproject.org/cryptocurrency. We have gotten a nice buzz on Twitter and Steph will promote from the Tor twitter account once a few edits are made to the page. 2) New monthly giving page should be ready next week and I'll use that to invite groups of past donors to convert their giving to monthly. 3) Al is beginning to work on LOIs to a few human rights focused foundations as well as one that provides funds for European travel. Antonela: 1) tpo.org - Fixing UI things, closing issues, reviewing small devices. 2) tpo.org - Call for translators was released this week, reviewing ES. 3) Tor Browser 8.5a Release: TBA Network Settings, TB Security Settings 4) Tor Browser 8.5 Release: #27484, #29768, #27399 5) Security Setting Tor Browser manual update is ready (thanks wayward!) 6) Gave a talk on Tuesday at Cyborgrrrls encuentro tecnofeminista, Mexico. 7) Prep for IFF: TBA user testing, outreach material is on the presses, making localized outreach material to be available for print and/or share in .pdf (thanks emmapeel!) 8) Working on Personas with Duncan. 9) Reviewing Caroline's reporting from India and Thailand. 10) Tickets triage for ux-team tickets is complete, waiting for pili's next steps. Nick: 1) 0.4.0.3-alpha to come out Friday, most likely. 2) Libreplanet this weekend: will be around for Saturday, but not Sunday. Mike: 1) Excited about leading tor scalability+performance; working on mail for Isa, Nick, Roger to review before sending Steph: 1) prepared the State of the Onion presentation for LibrePlanet. In Cambridge Fri-Sun. 2) preparing for website launch. Writing launch blog post. 3) reviewed the new cryptocurrency page 4) responding to inquiries isabela: 1) Dev Meeting -> we start to send invites to employees, contractors and board members. We will send the rest of invites this week and coming week. This bit of delay is mainly on me who need to finish the draft and invite list for jon to email people. 2) preparing board book for next board meeting on March 29th 3) getting things ready for LibrePlanet Sue: 1) Working on financials for Board Books 2) Normal accounting stuff (invoicing funders, paying bills) 3) Working on rewrite of the Accounting Manual Pili: 1) Sponsor 8 Final draft 2) Getting people organised for Google Season of Docs 3) Preparing for S27 Kick Off meeting next week 4) Preparing to run capacity planning exercise for Browser Team 5) Finalising tpo.org and working on getting community portal content written 6) Next week I'll be at Infracon in Barcelona 7) Week after next I'll be at IFF in Valencia Erin: 1) launched EE feedback process, working w/ Isa to answer some lingering questions 2) browser & OONI dev screening 3) general HR stuff

1 0

Network team meeting notes from 18 March 2019
by Nick Mathewson 19 Mar '19

19 Mar '19

Hi! Our logs are at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-03-18-17.00.html Our meeting notes are below: ======= = Network team meeting pad! = This week's team meeting is at Monday 18 March at 1700 UTC on #tor-meeting on OFTC. Welcome to our meeting! First meeting each month: Tuesday 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. March schedule: * Tuesday 5 March at 2300 UTC * Monday 11 March at 1700 UTC * Monday 18 March at 1700 UTC * Monday 25 March at 1700 UTC April schedule notes: * Monday 22 April is an Easter public holiday May schedule notes: * teor will be on leave at the start of May (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 list archive for older notes.) 19 Feb: https://lists.torproject.org/pipermail/tor-project/2019-February/002225.html 25 Feb: https://lists.torproject.org/pipermail/tor-project/2019-March/002236.html 5 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002244.html 11 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002252.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… <-- filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! Here are the needs-review tickets, by reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&reviewer… Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Including sbws: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… Core Tor/sbws is now part of the bug triage, CI, and reviewer assignment roles == 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. * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbd… * Check other's people call for help in their entries. ------------------------------- ---- 18 March 2019 ------------------------------- == Announcements == - The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0. - No more backports to 0.3.3; support ended a few weeks ago! - if you're a maintainer, please update your git scripts from the tor repository! - US DST began last Sunday; let's be careful for schedules next week [catalyst: are we going to follow US DST for the Monday meetings as we have before?] yes -- previously decided that Monday meetings move with US DST; see https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam We need to prioritize sbws's reviews this month as Juga is wrapping up their work in March. == Discussion == === Fixing IPv6-only network failures === Tor Browser is going to test the new ClientAutoIPv6ORPort option in Tor Browser Alpha. (Geko says, "looking at teor's comment in #29641 it seems we need #27647 fixed first?") teor says, Tor Browser should test in an alpha as soon as possible, so we know if we need to do #27647 I added a comment on the ticket: https://trac.torproject.org/projects/tor/ticket/29641#comment:7 (I sometimes miss pad and IRC comments, tickets are much better.) == Recommended links == "Tech companies could change these things to make your life easier and protect your digital security and privacy. Why haven’t they yet?" https://fixitalready.eff.org/ On gitlab release management (they have a role that rotates) https://gitlab.com/gitlab-org/release/docs/blob/master/general/monthly.md For next week: On gitlab time-based releases, and why developers and users like them: https://about.gitlab.com/2015/12/07/why-we-shift-objectives-and-not-release… == Updates == NOTE NEW FORMAT! 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: Week of 03/04 (actual): - processes https://gitlab.com/gabelula/tor-documentation-processes Week of 03/11 (planned): - tor scaling meeting - roadmap checking before leaving - traveling on the 14th teor: (offline except for the first meeting each month) Week of 11 Mar (planned): Bug triage rotation - Write nice page with queries for bug triage rotation, like https://trac.torproject.org/projects/tor/wiki/user/teor Roadmap Coding (3 days per week): - CI with Chutney/Tor: #29729, #27912, #29280 - Backport merges for CI with Chutney/Tor - Bandwidth stats for PrivCount: #29019, #17036, #29005 - Rearrange the commits in a nice order on a bunch of new branches Roadmap Reviews: - Review nickm's parts of the CI with Chutney/Tor tickets - Other assigned reviews Other: - After chutney CI merges, do other stable maintainer triage and merges - Leave admin - If I have any time left over, review admin backlog, and plan other admin Week of 11 Mar (actual): Bug triage rotation - Triaged a whole bunch of backports that were in the wrong milestone - Tried to keep up with the bugs in #tor-bots: I was busy, I might have missed something Roadmap Coding (3 days per week): - CI with Chutney/Tor: #29729, #27912, #29280, #22132 Roadmap Reviews: - Review nickm's parts of the CI with Chutney/Tor tickets - Other assigned reviews: I have one review to catch up on next week - I need to write extra tests for it. - Picked up some sbws reviews - Tried to help with sbws #28563 - Logged a bunch of bugs that are causing CI failures - Proposal reviews: prop#199 / #29801 Other: - Mainline merges - Merged most of the backport backlog, there is one merge remaining for next week (All the other backports need another alpha before they can merge) Week of 18 Mar (planned): Roadmap Coding (3 days per week): - CI with Chutney/Tor: #29729, #29761 - Backport fixes needed for CI with Chutney/Tor to Tor 0.2.9 - Bandwidth stats for PrivCount: #29019, #17036, #29005 - Rearrange the commits in a nice order on a bunch of new branches Roadmap Reviews: - Review nickm's parts of the CI with Chutney/Tor tickets - sbws reviews Other: - Other assigned reviews - Do mainline merges, and the remaining backport merges from last week - Do remaining reviews from last week - Leave admin - Add a travis test for stem (it's a copy of the chutney test, but using the stem command) Week of 18 Mar (actual): Roadmap Coding (3 days per week): - CI with Chutney/Tor: #22132, #28203, #29729 and children if needed Roadmap Reviews: - test proposed sbws design, suggest a new design, do sbws reviews Other: - review and design work on prop#199 - automatic IPv6 connection improvements - review #29036, #29434, #29073 - try to explain #29500 better - Leave admin - Work out how Tor's new feedback process works - Work out the new travel rules - other emails - triage and merge backports - ticket herding - assign 040-must tickets to people Help with: - If someone would like to work through the PrivCount changes with me, that would be really helpful. Otherwise I will defer them until after the Chutney/Tor CI. Blocked: Dev work and merges are slow due to lots of CI failures: - Intermittent CI failures: Fixes needed: #29500 (circuit padding time) #29693 (circuit padding stochastic) #29437 (test-stem) Nick: Week of 11 March (planned): - Next steps on CI: get travis support running on chutney, and chutney in tor's travis. [Pending Teor's revisions on #27912] - Next steps on pubsub (per catalyst's review) - Work on #29357 (ActiveOnStartup option for TB) as an 040-must item - Update my rup.py example code for the latest prop295 - Sponsor 31 meeting - Scaling meeting - Possibly, kick off work on some more of my sponsor 19 and 31 stuff. - 29223 standardized abbrevs? - 29269 bridge stats? Week of 11 March (actual): - Revised travis+chutney branches - Revised pubsub branch - Implemented #29357 (activeonstartup) - Meetings (various) - Review and merge (lots) - Slides for libreplanet Week of 18 March (planned): - Prepare for libreplanet on saturday - Reviews and merging. - Work on several 040-must items. - Testing PRNG determinism code (29732) - Possibly, kick off work on some more of my sponsor 19 and 31 stuff. - 29223 standardized abbrevs? - 29269 bridge stats? - Time permitting, adl/rup revisions - If catalyst is available, initial design chat on config.c refactor. - Review a paper for PETS - Get ready for an 0.4.0.3-alpha around the end of the week. Help with: - Please have a look at the tickets labeled 040-must. Are you the very best person to do one, or to explain why it is not a "must"? dgoulet (missing meeting): - AFK. Mike: Week of 3/11 (planned) - Vanguards workarounds for onion service bugs - Tor scalability - #28686 (Nick's stray review comments for wtfpad) - #28780 - flag for keeping circuit open (asn: are we sure this is actually needed?) Week of 3/11 (actual): - Sick + errands piled up from recovery - Lots of Tor scalability discussion & thought - Little bit of work on vanguards workarounds Week of 3/18 (planned): - Scalability planning & discussion - Catch up with asn's wtf-pad work, finalize plan for keeping circuits open (#28780) - Taking friday off catalyst: week of 03/11 (2019-W11) (planned): - reviews - write up architectural comments on pubsub - work with nickm on pubsub revisions - work some more on #28925 (distinguish proxy vs PT in bootstrap) based on previous work hooking up pubsub to bootstrap week of 03/11 (2019-W11) (actual): - reviews - asked for feedback from tbb-team on #28925 (distinguish proxy vs PT in bootstrap) - more pubsub improvements - figured out a way to unit-test pubsub-using code (maybe not optimal) - some annoyances related to practracker.py week of 03/18 (2019-W12) (planned): - try prototyping #28925 solution using pubsub but in a way not too difficult to back port to 0.4.0 - CI+Coverity rotation - reviews - checking for any remaining loose ends in pubsub review juga: Week 11 March (planned) - New patch release with #29707 fix (and new unofficial debian package) - Work on or merge Stop the integration tests http server when the tests end (#28774) - Work on or merge Create an script to automate releases (#29294) - Continue with Work out how sbws can report excluded relays in the bandwidth file (#28563) - When sbws stops making progress, log a warning (#28652) - Work out how long it takes sbws to measure the network (#28983) Week 11 March (actual) - Continue with Work out how sbws can report excluded relays in the bandwidth file (#28563) - When sbws stops making progress, log a warning (#28652) - Work out how long it takes sbws to measure the network (#28983) - Closed tickets that doesn't apply anymore and change some tickets' milestones - Recover a destination when it stops failing (#29589) - Document that authorities are not measured by default (#29722) Week 18 March (plan) - Continue with Work out how sbws can report excluded relays in the bandwidth file (#28563) - Work on Ignore bandwidth file lines with "vote=0" (#29806) - Create a blog post about work done and future work (#29724) - Continue with DirAuths should expose bwauth bandwidth files (#21377) asn: Week of 03/11 (planned): - Do revisions for #29221, #29298. - Continue work on #29298. - Do pending merges/reviews. - Check updates on #5708. - Check new HSv3 bugs that dgoulet opened (#29665, #29669). Week of 03/11 (actual): - Got #29298 and #29221 revised and merged. - More revisions for #28636 - Did merges/reviews. Got #29665 merged. - CI role. Fixed #29792, #29527, #29747. - Started work on #28634. Made some draft padding machines for hiding RP circuits. Also written a log-scraping program that analyzes HS circuits. More work needed. Will be working on this for the rest of the month. Week of 03/18 (planned): - Continue work on #28634. - Do merges/reviews. - Get #28636 finalized. - Fix prob_distr coverity issues. Help with: - Mike can you check that my rationale in https://github.com/torproject/tor/pull/788#discussion_r266450359 is correct? ahf: Week of 3/11 (planned): Sponsor 19: - Continue with #29207/#29206 with Cohosh. - Document protocol changes for #29207/#29206 Week of 3/11 (actually): Sponsor 19: - Talk about GeoIP interface with cohosh - Early review of #29734 - Added branch for listening on WebSockets in the Broker, now working on JSON message layer (#2907/#29206): - Started looking into WebSocket layer between Broker and Proxy (#29736). - Trying to wrap my head around an issue that I thought was related to the token bucket handling between WebRTC/WebSocket, but was a local network issue. Misc: - Created PR for #29036. - Closed #29737. Week of 3/18 (planned): Sponsor 19: - Second review of #29734. - Continue with #29207. Misc: - Network team bug triage. - Get Gitlab to run :-S - Talk with Erin, Cohosh, and Gaba about what we do with performance review for anti-censorship team.

1 0