June 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

PSA: flood attack against OpenPGP certificates underway
by Antoine Beaupré 30 Jul '19

30 Jul '19

Hi, Since the Tor project uses OpenPGP and GnuPG extensively in its operations, I figured it was important to let the community know of an ongoing attack against the keyserver infrastructure and GnuPG. The longer story is available on dkg's blog here: https://dkg.fifthhorseman.net/blog/openpgp-certificate-flooding.html ... but a summary is that at least two prominent OpenPGP users have seen their public key flooded with thousands of signatures, to the point where their keys are now completely unusable. I recommend you consider taking the following immediate actions, either: 1. in the short term, disable automated key refreshes on your keyring (either through Parcimonie or manual scripts calling `gpg --refresh` in some other way), or; 2. switch to the new keys.openpgp.org keyserver, by setting the following in your `gpg.conf`: keyserver hkps://keys.openpgp.org/ The first action should only be used in the short term, to allow you to evaluate your options. It might mitigate the problem (unless you somehow allow the nasty keys to enter your keyring some other way), but it will mean you will not be aware of the precious revocation certificates users post when their key is compromised, so it's not an acceptable solution in any way. The second action has been tested as mitigating the problem, but has several downsides as well: a. it does not store UIDs unless they are verified and asked for explicitly (workaround: keys can be shipped in-band with Autocrypt or found through other mechanisms like WKD, Web Key Discovery) b. it does not store UID signatures at all, which will impact the web of trust (workaround: same as point a, and you should send signed keys by email anyways to verify ownership of the UID, using tools like caff, pius, gnome-keysign or monkeysign) c. GnuPG cannot read refresh keys from keys.openpgp.org (workaround: use the custom patch shipped in Debian experimental, see Debian bug #930665) d. it does not currently receive updates from the SKS pool (workaround: upload key updates to keys.openpgp.org directly as well as the SKS pool) Note that keys.openpgp.org has been seeded with the global SKS keyserver datastore, so it contains all the keys you would expect to be present on the latter, except they are sanitized to avoid this problem. I encourage users to: 1. upload their keys to the keys.openpgp.org keyserver 2. either switch to keys.openpgp.org by default or carefully review their key fetching configuration to make sure it is not vulnerable to this attack 3. review dkg's article and make sure your own keys are not affected by this problem If you have fetched an hostile key and GnuPG has become unusable, you can recover by deleting the key with: gpg --delete-key C4BC2DDB38CCE96485EBE9C2F20691179038E5C6 Note that this may take anywhere from 20 minutes to an hour. And then fetch dkg's key via WKD: gpg --locate-keys dkg(a)fifthhorseman.net or his website, <https://dkg.fifthhorseman.net/dkg-openpgp.key>. The other known key affected by this problem is Robert J, Hansen's key, with the fingerprint "CC11BE7CBBED77B120F37B011DCBDC01B44427C7". As far as I know, torproject.org infrastructure has not been affected in any way by this attack. We carefully monitor keys we allow in our keyring which should be sufficient to mitigate this attack. A. PS: to check if your key is affected *without* importing it into your keyring, you can use the following command: FINGERPRINT=0x8DC901CE64146C048AD50FBB792152527B75921E # for example mine KEYSERVER="http://pool.sks-keyservers.net/" URL="$KEYSERVER/pks/lookup?op=get&search=$FINGERPRINT&options=mr&fingerprint=on&exact=on" curl -sSL "$URL"| gpg --list-packets | grep -c '^:signature packet:' This counts the number of signatures on your key. A reasonable number is less or around a thousand. dkg's key has now around 55 000 signatures on his key, which (naturally) causes some trouble in all OpenPGP implementations. -- Antoine Beaupré torproject.org system administration

6 8

April Fundraising Report
by Sarah Stevenson 17 Jul '19

17 Jul '19

Hello - below is the Fundraising team’s April update. Let us know if you have any questions! ## Grants The biggest news in the world of grants is that our proposal to DRL for anti-censorship work was approved. Al also submitted a proposal to CS Fund/Warsh Mott Legacy, Rights, and Governance that was declined and a proposal to Wallace Global on which we are still awaiting a response. We are also waiting to hear a response back from the DIAL Open Source Center about funding for the ESR migration. In these monthly updates we will begin informing you about proposals we intend to submit in the next month in case anyone might have comments or concerns about the funders, or connections that might help our chances. As a reminder, our grant work flow can be found on the Fundraising Team Wiki[1]. We plan to submit proposals to Media Democracy Fund, who have been funding us for several years now, the Reva and David Logan Foundation, NLnet, and The Charles Léopold Mayer Foundation for the Progress of Humankind. We welcome any and all feedback sent to grants(a)torproject.org <mailto:grants@torproject.org>. We have been working to better communicate with our grant program officers and, to that end, we sent our first Sponsors Newsletter[2]. The intent is to demonstrate the full impact of our work to funders who may only be familiar with specific projects. We plan to send the next newsletter after the meeting in Stockholm. Additionally, Isa and Sarah met with Michael Brennan from the Ford Foundation and are planning a follow-up meeting in June with others from Ford. ## Small Foundations / Major Donors In an effort to get lapsed major donors and small foundations to donate again, we sent a solicitation letter via postal mail. We included a nice insert, created by Steph, featuring Tor stories that we plan to use for acknowledgements that need to be sent in the mail. We’ve seen a small response. We sent a version of the Sponsors Newsletter to current major donors to let them know how impactful their giving has been. ## Monthly Giving / Defenders of Privacy We launched a donation page dedicated to monthly giving[3]. This will allow us to promote the Defenders of Privacy program and try to convert one-time givers into monthly givers. We currently have 334 people in the group who generated $3,438 in income in April. We will send a three-part series of emails to one-time givers beginning in May and will offer a new sticker or patch (yet to be determined) in the second invite. I will keep you updated on the growth of this program. ## Website Since the new website was launched at the end of March, we have been tracking the number of unsolicited donations from the website. That number decreased about 30% with the new site design. Our theory was that the Donate button was less noticeable, so at the end of April, Antonela changed the design and added a yellow Donate button in the header and footer. Since that change was made, donations are now almost double what they were per day before the website redesign. ## Administrative We have been working with a company called Labyrinth on making sure we are registered to fundraise in each of the 50 US states. This is a requirement that can result in fines if you are not properly registered. The process is a bit arduous since each of the states has different requirements. Thankfully, the process is almost complete for this year. ~ Fundraising Team [1] https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view <https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view> [2] https://crm.torproject.org/civicrm/mailing/view?id=158 <https://crm.torproject.org/civicrm/mailing/view?id=158>[3] https://donate.torproject.org/monthly-giving <https://donate.torproject.org/monthly-giving>

1 2

RACE meeting notes, 27 June 2019
by Philipp Winter 27 Jun '19

27 Jun '19

These are the first meeting notes for Tor's RACE project, which is our Sponsor 28. If you have no idea what this is, then fret not, for it is all documented in our wiki: <https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28> Here are our meeting logs: <http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-27-18.00.html> And here is our meeting pad: # S28: Resilient Anonymous Communication for Everyone Information about the sponsor: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 Next meeting: Thursdays 1800 UTC (every 2 weeks) at #tor-meeting The goals for this periodic meetings are: 1. share what is happening with the rest of organizations in the project 2. share progress on Tor side 3. get the monthly report started ----------------- JUNE 27TH ----------------- TECHNICAL REPORT FOR APRIL-JUNE: https://nc.riseup.net/apps/onlyoffice/s/MdNwgWk8CL8FBis What Philipp did: * Attended RACE brainstorming meeting about obfs5 * Updated description of https://bugs.torproject.org/30716 with feature ideas * We decided to first study the "long tail" of network traces because it will inform our obfs5 design * Filed https://bugs.torproject.org/30986 * Lots of reading to get up to speed on PT spec and obfs4 issues * Reached out to PT spec implementers to see what suggestions they had * Only one person responded :( What Philipp will do: * Understand PT spec issues on Android (sysrqb and nathan know the details) * Help Micah with studying the "long tail" of network traces * Maybe also reach out to a new contact at a network provider What cohosh did: - Attended brainstorming meeting - Attended integration meetings - Shared PT spec with other groups What gaba did: - read mails is the only thing :) - update roadmap (trying to keep track of what you all are doing)

1 0

Anti-censorship meeting notes, 27 June 2019
by Philipp Winter 27 Jun '19

27 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-27-17.00.html And here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 27th 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://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Our roadmap consists of a subset of trac tickets. * Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team" * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 27th June 2019 ---- --------------------------- == Announcements == * Sponsor 28 (RACE) next meeting will be on June 27th 1800 UTC at #tor-meeting Agenda/Notes: https://pad.riseup.net/p/tor-censorship-S28-keep * Please add your June 2019 highlights for our monthly reports here: https://pad.riseup.net/p/h4FrASe8pVEaAfmUs_IG == Discussion == * Problems with bridges. BridgeDB unusable? * what tickets people are working on right now? * 9316 BridgeDB should export statistics * 30441 Stop BridgeDB from handing out offline bridges * what needs to be done to have it usable? * Let's test our obfs4 setup guide by asking people on tor-relays@ to set up new obfs4 bridges? * snowflake webextension update? #30931 ? == Actions == * == Interesting links == Censorship-Resilient Proxy Distribution Using Game Theory https://www.ndss-symposium.org/ndss-paper/enemy-at-the-gateways-censorship-… == 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: (gettor days are Thursday) This week: Next week: Past week: phw: This week (2019-06-27): * Sent "call for new obfs4 bridges" email to tor-relays(a)tp.o. * One person contacted me directly after setting up a new bridge. They thought the instructions worked very well. * Worked on #30931 so arlo, dcf, cohosh, and I can all manage our snowflake webextension * Arlo already submitted the extension to Firefox and Chrome! * Worked with more operators of broken obfs4 bridges. * Sent ten of BridgeDB's unallocated obfs4 bridges to activist for manual distribution. * Lots of work on #30441, to stop BridgeDB from handing out offline bridges. * The problem may have fixed itself? * Blacklisted 53 broken obfs4 bridges. * Added debug log messages and discovered bot that's scraping bridges. * Brainstormed obfs4 improvements over at #30716. * For now, we decided to understand the "long tail" of network traffic first (#30986) * Once we have a better understanding of the long tail, we'll continue with obfs5 * Attended RACE call in which we discussed all of this. * Filed #30946 to port BridgeDB to Python 3. * Published blog post that introduces the anti-censorship team and our Sponsor 19 report. * https://blog.torproject.org/tors-new-anti-censorship-team-defending-open-in… * Lots of help from gaba and stephw! * Had a brief look at the popularity of an active probe's cipher suite over at #30500. * Caught two probes that had a different cipher suite; one quite common, but not the other * Pushed a feature branch for our BridgeDB metrics (#9316) which is now in 'needs_review'. Next week: * More RACE work (PT spec and network trace "long tail") Help with: * Try requesting different types of bridges from bridges.torproject.org and let me know if you got 0 bridges. Gaba: (updated 2019-06-20) Last week: * tor meeting schedule intil the meeting This week (05/30): * bridgedb plan * sponsor 28 update ahf 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. kat5: Last week (May 20): This week (May 27): dcf: 2019-06-27 (will miss today's meeting) Last week: Next week: - try the Snowflake WebExtension - publish post-sanitization broker logs (#30731) Help with: cecylia (cohosh): last updated 2019-06-27 Last week: - got snowflake client to use pion/webrtc (#28942) - continued investigating the fixes we need in pion for the large message drops - addressed dcf's feedback on the sequencing layer (#29206) - worked on Turn On/Off toggle for web extension (#30934) Next week: (AFK on Monday) - try to figure out if there are any popular STUN servers in places where googles are blocked - move forward with sequencing layer (#29206) - continue work on improvements to pion/webrtc (#28942) - webextension translations (#30310) - some serious snowflake dogfood - familiarize self with PT spec Help with: - broker stats (#21315) code review - review of #30934 - review of fixes in #29206 but i can keep moving forward with it - review of work so far with #28942 catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 week of 06/20 (actual): - mostly sponsor31 - helped ahf with some bootstrap stuff week of 06/27 (planned): - mostly sponsor31 arlolra: 2019-06-27 Last week: - a bit of snowflake webextension This week: - getting the webextension published (#30931) Next week: - review #30934 Help with: - fixing our websocket server implementation (#30998)

1 0

Tor Browser team meeting notes, 24 June 2019
by Georg Koppen 25 Jun '19

25 Jun '19

Hello! Here come the notes from our latest weekly Tor Browser meeting. Our IRC log can be found on: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-24-17.32.l… Apart from the usual discussion about topics that are/were relevant in the upcoming and past week the log contains some report back from All Hands as well, for those of you who are interested in that. Additionally, here come the items from our pad: Discussion: -upcoming macOS signing changes (GeKo: mcs/brade will start looking closer at the actual requirements; we have #30126 for tracking) -state of the Windows bundle (GeKo: see: https://www.windowscentral.com/how-enable-controlled-folder-access-windows-… for starters as it might be (part) of the underlying problem; I filed #30976) GeKo: Last week: - All Hands and a bit release help (many thanks to boklm for managing the whole fuck-up essentially himself) This week: - catching up with backlog - review, review, review - get all Linux patches for ESR 68 toolchain into reviewable shape mcs and brade: Last week - Worked on #30000 (Integrating client-side authorization to onion services v3). - Continued to work on the Onion Services client auth prompt (#30237). - Commented in #30943 (Show Tor Browser version on Android). This week: - Review for #18101 (IP leak from Windows/macOS UI dialog with URI). - at the same time, test Snowflake on macOS 10.9.x. - More work on the Onion Services client auth prompt (#30237). - We plan to post work-in-progress patches this week and then work with Antonela on UX. - Soon: #29197 (remove use of overlays from Tor Launcher) - Soon: #30429 (ESR 68 Rebase — updater patches). pili: Last week: - Frontdesk message forwarding ;) - We had some messages from Windows - There's also some interest on continuing development on Tor Messenger - And some bug reports This week - Tying up loose ends before vacations - afk from 26th June - 1st July - are we on track for the fundraising banner to be released with the next security update? (GeKo: acat will work on that this week) acat: Last week: - Addressed review changes for https://bugzilla.mozilla.org/show_bug.cgi?id=467035, now waiting for review. - Continued torbutton cleanup/refactor (#28745) - Patch for Properties in dom/locales/$lang/chrome/ allow detecting user locale (#30683). This week: - File uplift bugs for suitable rebased ESR68 patches (start with #24056, #23104, #26353, #26514, #21830). - Continue torbutton cleanup/refactor (#28745) - Add Fundraising Banner with next TBB security update (#30577) boklm: Last week: - building, signing, releasing some releases - started looking at rebasing #28672 (Android reproducible build of Snowflake) on #30334 (build_go_lib for executables) - started looking at #30320 child tickets (Adapt Tor Browser toolchains for Firefox 68 ESR) This week: - look at remaining failing testsuite tests - fix reproducibility issues of snowflake build for android (#28672) - look how we can build 32bit mar-tools: https://trac.torproject.org/projects/tor/ticket/30321#comment:10 - look at how to upload tor browser releases on archive.org for #29697 pospeselr: Last week: - seem to have tracked down all the issues in widl preventing screen readers from working - posted candidate builds with all the patches applied - started fixing widl patches based on feedback from wine devs This week: - finish up widl changes - figure out what needs to happen to get updated widl into mingw - update tor-browser-build's 27503.patch to final widl version antonela: This week: - Looking at https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~Tor… issues - TBA - what we will do with #24920? and #30540? Any updates on #29955? - TB - ESR68 - reviewing acat proposal (#10760) - TB - Banner for donations is done, waiting for approval (#30577) - S27 - reviewed #30024, waiting for onion auth wip for review - planning a Tor Browser prioritizing user problems session for the dev meeting sysrqb: Last week: All Hands Laptop hard-drive corruption This week: Laptop data recovery 68esr rebase Read backlog from the last week sisbell: Last week: - #30607: Testing Android Q problems on actual device - tor loads and runs fine. Firefox 60 is incompatible with Android Q. Will need to wait until 68. - #Did clean update of gradle dependencies for topl/tor-android-service for toolchain This Week - Move toolchain and related projects changes to GeKo branch - # 30199 tor-android-service cleanup - #Submit PR to TOPL - #Follow up about TOPL mirror Georg

1 0

Network team meeting notes, 24 June 2019
by Nick Mathewson 25 Jun '19

25 Jun '19

Hello! You can read the logs from yesterday's meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-24-17.00.html Below are the contents of our meeting pad. = Network team meeting pad! = This week's team meeting is at Monday 24 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 24 June at 1700 UTC July schedule: * Wednesday 3 July 2300 UTC * Monday 8 July at 1700 UTC * (In-person meeting 12-14 July) * Monday 22 July 1700 UTC * Monday 29 July 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 list archive for older notes.) 28 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002338.html 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html 10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html 17 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002365.html == Stuff to do every week = * How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… * 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://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… Click on 'all boards' and then the network team one. Filter by your name and check the 'in progress' column is correct. * 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… Any blocker from last week? == 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. ------------------------------- ---- 24 June 2019 ------------------------------- == Announcements == [REMINDER] WIP Schedule for Tor meeting https://nc.riseup.net/s/FFkikRBmKDZyLw9 The master branch is now 0.4.2.x. 0.4.1.x development continues on maint-0.4.1 and release-0.4.1. 0.3.4.x is now end-of-life. Summary the mail thread on proposal from Dgoulet https://nc.riseup.net/s/gQGT8kjNgt3C6cd == Discussion == Retrospective on Thursday. How people want to do the retrospective? (please vote) jitsi +1 +1 irc other? #29697 Anybody up to team with boklm to coordinate archive.tpo Please update https://pad.riseup.net/p/network-team-draft-CI-role and vote yes/no on the change into a permanent role for CI. Can we start soon? Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity ahf -> catalyst coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) Looking at coverity -- it seems our builds may have been stuck. I've cancelled the stuck builds. Also, they say they are going to have a planned outage to upgrade their backend, starting today and lasting about 3-4 days. Friday would be a good day to have another look. -nm jenkins Travis teor did some work on stem failures, we need to add a control message trace to tor to diagnose (#30901) waiting for catalyst's advice, because they are refactoring this code Appveyor Bug triage teor -> ahf Everything seems ok, I might have missed some patches and things earlier in the week. == Recommended links == == 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: Last week (actual): . gitlab This week (planned): . sponsor 31 adjustment with new tickets . more gitlab Help with: teor: (offline at the usual meeting time) Week of 17 June (planned): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fix existing open tickets where I have added the sponsor - Fallback directory mirror list rebuild (#28793) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - merge chutney pull requests - disown or quick fix tickets: I should only be owner on tickets I will work on in the next month - bug triage rotation Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Low-Priority: - backlog: router_have_consensus_path() logs an incorrect "no exits in consensus" (#27448) - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Week of 17 June (actual): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fixed some existing open tickets where I have added the sponsor - some code reviews - merged some chutney pull requests - Fallback directory mirror list rebuild (#28793) - draft list - need to work out why the list is so short this time (#30952) - some bug triage - sbws triage and fixes - Fixed PT extra-info bugs introduced in 0.4.1.1-alpha and 0.2.7.2-alpha (#30956, #30958) - disowned some tickets, more next week Important: - reviews of new onion service DoS code - designed API for pool abstraction - work on proposal/questions for possible trac migration - travel prep - process changes Week of 24 June (planned): Urgent: - fix existing open tickets where I have added the sponsor - Continue fallback directory mirror list rebuild (#28793) - need to work out why the list is so short this time (#30952) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - disown or quick fix the rest of my tickets: - I should only be owner on tickets I will work on in the next month - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Week of 24 June (actual): Urgent: - Important: - Low Priority: - Help needed: - catalyst, do you have advice on: - add tor controller trace logging to diagnose stem hangs (#30901) [catalyst: i'll try to look at it this week] Nick: Week of 17 June (planned): - Summarize employee feedback - PETS review - 0.4.0.6 release, maybe. - Reply to proposals 303 through 305, maybe. - Reviews and merges - 29211 -- refactor configuration code. - 29280 -- needs_revision, chutney in ci code - 27801 -- review proposed API for launching sockets with embedded tor - 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Week of 17 June (actual): - Code reviews - PETS review - Work on various 29211 subtickets. (configuration refactoring) - Start summarizing employee feedback. (4/6 done) - Defer 0406 release; start 0413 release - try to catch up with backlog Week of 24 June (planned): - Retrospective on Thursday - More 29211 work - 0413 release - attempt: Reply to proposals 303 through 305, maybe. - attempt: review 27801 api - attempt: 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Mike: Week of 6/17 (planned): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/17 (actual): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/24 (planned): - Bitcoin conference - code reviews - Catch up on mail catalyst: week of 06/17 (2019-W25) (planned): - reviews - control.c refactoring week of 06/17 (2019-W25) (actual): - chatted with ahf re #28930 (msybe reorder some PT/proxy bootstrap phases) - bureaucracy - wrote up #30911 to document some inbound email problems - cleaned up my owned tickets a little week of 06/24 (2019-W26) (planned): - CI+Coverity rotation - reviews - take a closer look at dgoulet's "radical changes" email thread - help teor with #30901 (control port trace logging for debugging test-stem hangs) - more bureaucracy - starting Stockholm trip prep - hopefully have time to work on control.c refactor asn: Week of 06/03 (planned): - Finalize s27 o2a1. - Help organize our AllHands experience. - Fix #30578 circpadding bug (041-must). - Do more work on HS DoS. - Some more travel prep for allhands. Week of 06/03 (actual): - Finally managed to get #30381 in needs_review. - Wrote some scaling emails. - Worked on #30578 (041-must). - Did some work on HS DoS: https://lists.torproject.org/pipermail/tor-dev/2019-June/013873.html - Cleaned most of my review backlog, but there is still more. - Merged prop304 to torpec. Week of 06/10 (planned): - #30381 is now in needs_revision. Need to do that. - More prepping for AllHands. Flying out on Sunday. - Try to do some work on s27 #26294 (intro point rotation dos) - Still got reviews hanging. In particular #30382. - I also got lots of hanging merges... Help needed: - teor, I still have troubles mapping all the pieces of #22029 in my brain. Perhaps at some point you can take over the review of that ticket, and I can take one big review from you? I don't see you having any big reviews this week, so perhaps we can wait until next week. teor says: I assigned myself as reviewer on this ticket. neel is still working on it, when he finishes, I will split off some of the small features so other people can review them. ahf Week of 17/6 (planned): Network team: - Finish off patches for #29736 so we can discuss the big changes at the Thursday meeting. - Continue with #28930. Misc: - Figure out what needs to be doing on some of the PT spec tickets I have. Week of 17/6 (actually): Network team: - Discussed #29736 and authentication patches during anti-censorship team meeting. - Rebased and discussed current changes for #28930 with catalyst and decided next step. - Wrote patches for CI build failures for Stem and Chutney in #30928. - Figured out next steps for #5304 Week of 24/6 (planned): Network team: - Continue iteration of #28930 and discuss progress with catalyst. - Write Tor patch for #5304 (spec is OK) - Bug Triage duty. - Work a little bit on 'untrac' (a small tool to import Trac tickets into Gitlab that Gaba and I talked about during my 1:1 last Friday). juga(offline): Week of 05/20 (planned) - Add Tor version to the bandwidth file (#30196) Week of 05/20 (actual) Week of 06/03 (plan) - Continue with #30406: Refactor header constants in sbws to use Stem's one dgoulet: (might be offline, getting sleep has been very rough in the last days...) Week of 06/10 (actual): - Tested and experimented with #15516. Had to wait a bit to get new machines from a friend at a hosting provider in order to start limited bw relays. Thanks to ahf for providing assistance with his fast relays. - Wrote prop305 (on tor-dev@) about ESTABLISH_INTRO parameters. See #30790. Thanks from teor/asn for early feedbacks! - Merges and reviews as always. Week of 06/17 (planned): - Finalize #30382 from asn's review. - Continue work on #15516. I'm hoping to drop the experimental results on the ticket, finzlie the branch for upstream merge. And then move on to prop305.

1 0

S27: Onion Services meeting this week: Tuesday 18th June
by Pili Guerra 25 Jun '19

25 Jun '19

Hi everyone, This is a reminder of our fortnightly S27: Onion Services project meeting happening this Tuesday 18th June at 15UTC on #tor-meeting. Please join us if you’d like to participate or feel free to just lurk :) 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

2 4

Anti-censorship meeting notes, 20 June 2019
by Philipp Winter 20 Jun '19

20 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-20-17.00.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 20th 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://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Our roadmap consists of a subset of trac tickets. * Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team" * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 20th June 2019 ---- --------------------------- == Announcements == * Sponsor 28 (RACE) next meeting will be on June 27th 1800 UTC at #tor-meeting == Discussion == * do we want to move to gitlab for snowflake? (try only with one component for now) --> we are going to wait until the issue of "guests filling tickets in gitlab" is resolved. * gaba created https://dip.torproject.org/anti-censorship/pluggable-transports/snowflake/b… * Let's test our obfs4 setup guide by asking people on tor-relays@ to set up new obfs4 bridges? * WebSocket in Snowflake: next steps. (ahf) * trac management: can we 'own' tickets only when we are working on them? if you are interested in a ticket then add yourself to cc. * is #23888 going to be able to happen on time? do we need to take it? == Actions == * == 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: (gettor days are Thursday) This week: Next week: Past week: phw: This week (2019-06-20): * Reviewed #21315 (publish some realtime stats from the broker?) * Mostly implemented #9316 (BridgeDB should export statistics) * Got a frontdesk account and had a look at bridge-related tickets * With Cecylia's help compiled summary of what we know about the GFW and active probing * Pinged ICLab team again to see if they can periodically scan at least our default bridges * Sent more emails to PT implementers * So far only one response * Tested #23888 (Creating a Snowflake WebExtension addon) and left feedback * Went through old tor-dev@ threads to compile feedback on improving the PT spec Next week: * More work on moving forward with PT spec * More thinking about improving obfs4 * Get #9316 reviewed * Create a blog post for our sponsor 19 report #2. Help with: * Brainstorming features of obfs4 successor, and how to improve PT spec Gaba: (updated 2019-06-20) Last week: * playing with gitlab for snowflake: https://dip.torproject.org/anti-censorship/pluggable-transports/snowflake/b… * prepare tor meeting schedule This week (05/30): * ahf Last week: - Talked with Cecylia about WebSocket + authentication patches in https://github.com/ahf/snowflake/tree/features/websocket_r5 and what we should do next. (#29736 and friends) - Hack on #28930 This week: - Work on #28930 kat5: Last week (May 20): This week (May 27): dcf: 2019-06-20 Last week: - brainstormed some problems with the PT spec (https://bugs.torproject.org/29285#comment:5 ) - wrote ideas about protocol versioning and backward compatibility (#30704) - reviewed sequencing layer (#29206) - added meek-azure bridge, meek-azure CDN, and snowflake-broker CDN to the infrastructure survey Next week: - will be mostly offline next week, will miss 2019-06-27 meeting - look at WebExtension changes in https://bugs.torproject.org/23888#comment:24 - publish post-sanitization broker logs (#30731) Help with: cecylia (cohosh): last updated 2019-06-13 Last week: - submitted some PR's for pion/webrtc - starting modifying our snowflake code to use pion/webrtc as the library (#28942) - started familiarizing myself with Chutney - took a look at the snowflake webextension changes (#23888) Next week: (AFK on Friday) - update default STUN configuration (#26348) - address dcf's feedback on the sequencing layer (#29206) - continue work with integrating/evaluating pion/webrtc (#28942) - familiarize self with PT spec Help with: - broker stats (#21315) need a metrics team review (should we deploy what we have and store the output locally?) - browser team help for mingw toolchain (#25483) catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 arlolra: 2019-06-20 Last week: - nothing This week: - a bit of snowflake webextension Help with: - getting the webextension published (#30931)

1 0