February 2020 - tor-project - lists.torproject.org

Are there countries where using Tor is illegal?
by Cristian Consonni 11 May '25

11 May '25

Hi, (Sorry if this question has already been asked in the past, feel free to point me to the relevant resources.) I know that the legal FAQs by the EFF state that: «we believe that running a Tor relay — including an exit relay that allows people to anonymously send and receive traffic — is legal under U.S. law.»[1] I also know there is a list of countries for which there is legislation that exclude communication service providers from liability. They are indicated in the Legal of the Tor Exit Guidelines page[2], they are USA, Germany, Netherlands, Austria, France, and Sweden. >From some articles in the press[3a][3b] it may be illegal - depending on how you interpret the wording[*] - to use Tor (and other technologies such as VPNs or proxies) in the UAE, with fines ranging in the millions of dirhams (hundreds of thousand of dollars). A couple of weeks ago it was discussed - on this list as well - that a law was introduced to the state parliament to ban Tor[4a][4b]. This follows a case of some months ago of a Russian Tor exit node operator being arrested for inciting mass riots and terrorism[4c][4d]. The idea of blocking VPNs or Tor seems to have already been considered in the past[4e]. This infographic about pluggable transports[5] suggests access to the Tor network is censored or limited in China, Uzbekistan, Iran, and Kazakhstan. Tor being censored orblocked may be different from it being illegal. What about other countries? Is there a place where I can find more about this topic? Cristian [1]: https://www.torproject.org/eff/tor-legal-faq.html.en [2]: https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines [3a]: http://www.emirates247.com/news/emirates/dh500-000-fine-if-you-use-fraud-ip… [3b]: http://news.softpedia.com/news/people-caught-using-vpns-tor-or-proxies-in-t… [*]: «Whoever uses a fraudulent computer network protocol address (IP address) by using a false address or a third-party address by any other means for the purpose of committing a crime or preventing its discovery» [4a]: https://lists.torproject.org/pipermail/tor-talk/2017-June/043293.html [4b]: https://trac.torproject.org/projects/tor/ticket/22055 [4c]: https://lists.torproject.org/pipermail/tor-talk/2017-April/043109.html [4d]: https://techcrunch.com/2017/04/24/dmitry-bogatov-tor-russia/ [4e]; https://torrentfreak.com/vpn-and-tor-ban-looming-on-the-horizon-for-russia-… [5]: https://www.torproject.org/images/PT/2016-07-how-to-use-PT.png

4 3

Tor Browser Team Meeting Notes, 06 January 2020
by Matthew Finkel 13 Apr '20

13 Apr '20

Hello everyone, Our first meeting of 2020 was held on 6 January. 2020 will be an exciting year for Tor Browser! We have a busy year ahead of us and we're hitting the ground running. The logs are available at http://meetbot.debian.net/tor-meeting2/2020/tor-meeting2.2020-01-06-18.29.l… Summary: 1) Discussed how we can move forward with implementing per-site settings 2) Discussed how long it will take before we start writing 2020 instead of 2019 on documents 3) Discussed future plans for Namecoin integration (adding more platforms, timeline for adding in Alpha, etc.) With regard to (3), Namecoin is currently available in Tor Browser Nightly builds on Gnu/Linux 64-bit. Please provide feedback is you try it! ================================ Week of January 6, 2020 Discussion: How long will we be dating things 2019 when signing documents? Will this decade be as roaring as the 1900s version? - if it will be, is that a good thing pospeselr: Last weeks: - #31855 (remove end of year fundraising campaign) - small progress on Mozilla 1601040 and 1594455 This week: - continue baby-sitting above Mozilla tickets - #30570 (implement per-site security settings) - what do folks think about the discussion in the ticket? - tldr: looks like to build something consistent with the design laid out there requires a lot of work basically reimplementing what NoScript does, or heavily refactoring/redesigning NoScript's internals :/ - look into umatrix extension as an alternative to NoScript - put umatrix findings in a doc or on the ticket mcs and brade: Last few weeks: - #32636 (Clean up locales shipped with Tor Launcher). - Code review for #31855 (Remove EOY Campaign from about:tor). - Sponsor 27 work: - #19757 (permanent storage of client auth keys and associated management UI). - Time off for Christmas and end of year. This week/upcoming: - #19757 (permanent storage of client auth keys and associated management UI). boklm: Last few weeks: - Made patches for: - #32768 (Create a build-infos.json file containing firefox platform_version and buildid) - #32805 (Make creation of downloads.json optional) - Worked on #25102 which is almost finished (Add script to sign nightly build mar files, generate update-responses xml and publish the new version) - Looked at blog comments This week: - Help with publishing new releases - Finish work on #25102 (script to sign nightly build mar files, generate update-responses xml and publish the new version) and remaining things for #18867 (Ship auto-updates for Tor Browser nightly channel) - Try #32768 (Make script to optimize upload and download of Tor Browser releases) - Look at macOS signing situation sysrqb: Last few weeks: Mostly distracted by holidays, family, etc. Preparing releases for this week This week: Releases Reviewing roadmap for Q1 2020 Finishing remaining items we didn't finish last year Jeremy Rand: Last few weeks: #30558 is merged, yay. Attended 36C3; gave a talk and workshop; ran into boklm there :) This week: Ponder next steps for Namecoin now that the initial merge to Linux Nightly has happened. ================================ - Matt

1 11

S27 (Onion Services) Meeting today: Tuesday 18th February @ 15UTC
by Pili Guerra 03 Mar '20

03 Mar '20

Hi everyone, We will be meeting to discuss this project today as usual. Please join us! 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 1

Notes from Vegas Meeting FEBRUARY 27 2020
by Erin Wyatt 28 Feb '20

28 Feb '20

Vegas Team Meeting Notes FEBRUARY 27 2020: + NEW BUSINESS - Do we have plans/timeline for migrating from trac to gitlab.torproject.org? Plans, yes; timeline, not really. We need to consult teams to decide what can move and when. You should only work in trac for now until we finally migrate --gaba + GENERAL NOTES Antonela: 1. Reviewing DRL proposal 2. Wrapping S27 3. Writing peers feedback 4. Following up Tunde's travels. Put in contact with Gaba to facilitate a NC account for his research data. 5. Following up with Nah about user research, reviewing user research templates for communities 6. IFF Tor village: Sent some invites to fav community members to encourage them to submit a proposal 7. S30 OONI design tasks 8. Do we have plans/timeline for gitlab.torproject.org? ^see above 9. Reviewing the new Onion Browser for iOS Anarcat: 1. hiro put the new gitlab instance online, and it works! almost ready for migration from dip.torproject.org 2. more automation work: started testing Fabric, and automating host retirement and reboot procedures 3. finalized new ganeti node (fsn-node-04, #33081) and started migrating hosts from old unifolium (kvm2 out of 5, #33085) 4. retired savii.torproject.org (#33441) and build-x86-07.torproject.org (#33442) 5. meta-policy process adopted inside team: https://help.torproject.org/tsa/policy/tpa-rfc-1-policy/ 6. setup new VM for check.tpo replacement (!) #33362 7. normal routine (email creation, server reboots, ircbouncer support, patch reviews) Georg: 1. Network health work is moving forward 2. First batch for feedback is ready, more to come for next week Pili: 1. Working on all of the documents required for the DRL proposal 2. Reviewing S27 status, deliverables and releases as we enter the final month of the project - starting to think about how we can share and present this work with the wider community. 3. S27 February report 4. GSoC wrangling 5. Outreachy wrangling 6. Some Season of Docs follow up as our technical writer finishes her long running project 7. Need to pick up IFF wrangling again 8. Blog migration meeting Gus: 1. Network health: contacted relay operators from latin america. 2. Submitted Outreachy project: "Help Tor support our users". Please update: https://trac.torproject.org/projects/tor/wiki/Outreachy 3. Training program: contacted new partners in India, Colombia and Uganda. 4. Reviewing Cleo's work, also it's her last week, internship ends now, March 3. isabela: 0. Focus on invites to our fundraising happy hour event on March 26 at EFF - if you can help w/ invites ping us! 1. Selection of candidates for first round of internview (to the ed assistant position) / Working on job post for office admin position 2. Following up on personnel stuff 3. Following up w/ proposals (OTF, DRL, Dial, etc) 4. Trying to finish draft of Membership Program proposal sarah 1. Invites and logistics for San Francisco 2. Invites and logistics for NYC lunch April 13 3. Assisting with DRL and OTF proposals 4. Working on peer feedback 5. Met with Joe Hall last week 6. Meeting with Nikita from Omidyar next week 7. Making minor edits to donate language on website to increase organic (non-monthly) donations 8. Zcash funding for walking onions is in hand Steph 1. Updated fundraising deck for SF meetings. Will be making 2 sets of slides for bitcoin2020 and eff event 2. Working with OTF Learning Lab on a page to debunk the dark web 3. Working with annalee_ on a vpn post -- final outreachy week upon us! 4. Next newsletter finished -- going out tomorrow. 5. Did a livestream / community call with Zeal about Tor and walking onions Gaba 1. DRL proposal 2. SF meeting 3. Finally got up to speed on trac 4. Roadmaps 5. Gitlab new server is done by hiro. Testing new installation. The plan is to move it from dip into gitlab.torproject.org next week. 6. IFF follow up 7. Sound Track this week: https://www.youtube.com/watch?v=vtCk4sNgj48 Matt: 1. Picked up Tor Browser Mac OS X signing problem 2. Tor Browser 9.5a6 release (soon) 3. Started conversation with DuckDuckGo 4. Began having conversations about websites blocking Tor Browser users 5. Another OTF round of feed 6. Tor Browser migration is progressing (slowly, but steadily) 7. S27 work is progressing nicely (new features in every alpha release) Alex: 1. Team seems to be doing fine. 2. GSoD is over. Swati did very well IMO. 3. Been doing peer reviews, but still missing 1/3 of them. 4. Hiro got new Gitlab server up and running. Will be working on migrating Trac tickets to the new instance now. Nick: 1. trying to roadmap my next 3-6 months. 2. starting on walking onions spec next week 3. going to do a panel with wendy next wednesday about decisionmaking in dentralized organizations Mike: 1. Worked on scalabilithy proposal 2. Conversations about role priorities 3. Starting to plan March travel Erin: 1. Working on contract updates, tax forms, and alllll the other things 2. Moving forward with Exec Admin screening 3. Personnel stuff

1 0

Anti-censorship team meeting notes 27 February 2020
by Cecylia Bocovich 27 Feb '20

27 Feb '20

Here is our meeting log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-27-17.59.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday February 27th 18:00 UTC Weekly meetings, every Thursday at 18: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. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam Past meeting's notes can be found at: https://lists.torproject.org/pipermail/tor-project/ GetTor's roadmap: https://dip.torproject.org/groups/torproject/anti-censorship/gettor-project… Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Projects from sponsors we are working on: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 ------------------------- --- February 27th 2020 -- ------------------------- == Announcements == == Discussion == - We want to run a session during IFF to get people to circumvent censorship. We were thinking of getting people to connect to a censored network, e.g by providing a router that censors in different way; and try to access the internet or some sites or something. We would need some advice/help to set something like this up -- Pili & Gus - Source code from 2017 experiment (few hundred users, Windows only, simulated censorship with a local firewall, used an instrumented Tor Browser to record mouse clicks): - https://github.com/lindanlee/PETS2017-paper - see experiment/firewall.bat and experiment/gen-firewall - see the screenrecording directory - see the session/pre/videos directory for videos and detailed notes of a pre-study - see the setup directory for other setup notes (don't remember what exactly) - paper: https://censorbib.nymity.ch/#Lee2017a - Source code from 2015 experiment (5 users, one on one, no censorship, just browser usability): - git clone https://www.bamsoftware.com/repo.eecs.berkeley.edu/tor-ux.git/ (see README and tasks.html) - videos: https://people.torproject.org/~dcf/uxsprint2015/ - blog post: https://blog.torproject.org/blog/ux-sprint-2015-wrapup == Actions == == Interesting links == NDSS 2020 PDFs are online https://www.ndss-symposium.org/ndss-program/2020-program/ "Detecting Probe-resistant Proxies" https://www.ndss-symposium.org/ndss-paper/detecting-probe-resistant-proxies/ https://sfrolov.io/papers/ndss20-frolov.pdf "Decentralized Control: A Case Study of Russia" https://www.ndss-symposium.org/ndss-paper/decentralized-control-a-case-stud… https://censoredplanet.org/russia https://github.com/net4people/bbs/issues/20 "Measuring the Deployment of Network Censorship Filters at Global Scale" https://www.ndss-symposium.org/ndss-paper/measuring-the-deployment-of-netwo… "SymTCP: Eluding Stateful Deep Packet Inspection with Automated Discrepancy Discovery" https://www.ndss-symposium.org/ndss-paper/symtcp-eluding-stateful-deep-pack… "MassBrowser: Unblocking the Censored Web for the Masses, by the Masses" https://www.ndss-symposium.org/ndss-paper/massbrowser-unblocking-the-censor… == Updates == 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: (last updated before 2020-01-09) Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation phw: This week (2020-02-20): Will be gone until our Mar 12 meeting. Merged and deployed BridgeDB's Python 3 port (#30946). Retired scramblesuit, obfs3, and fte from BridgeDB. Refactored email distributor check tool for #12802. Wrote OONI patches for new default bridge. Reviewed #23225. Next week: Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones Help with: Gaba: () Last week (): This week (planned): cecylia (cohosh): last updated 2020-02-27 Last week: - sent grant to some external reviewers - even more grant revisions - worked on debugging proxy-go CPU issues (#33211) - refactored and debugged snowflake throughput check (#32938) - snowflake + turbotunnel dogfood - merged and deployed gettor refactor (#33191) This week: - finish up snowflake throughput check (#32938) - take care of go module for snowflake (#33330) - Aggregate and write up a report of snowflake throughput changes - write up snowflake scaling thoughts for mailing list - work on gitlab issues with gettor (#33034) Needs help with: - are we good with #33211? dcf: yes arlolra: 2020-02-13 Last week: - merged the client part of #19026 Next week: - maybe the proxy parts of #19026 - pick another task? Help with: - dcf: 2020-02-27 Last week: - used snowflake-turbotunnel bundles and fixed problems (#33336, #33401) - wrote invitations to test the revised snowflake-turbotunnel bundles - https://lists.torproject.org/pipermail/tor-talk/2020-February/045499.html - https://ntc.party/t/invitation-to-test-turbo-tunnel-snowflake-packages/378 - merged the fix to ignore 0.0.0.0 client addresses (#33385) - filed a pull request to deprecate the go-webrtc repo https://github.com/keroserene/go-webrtc/pull/110 - investigated a required upgrade of the App Engine reflector (#33429) - helped debug high CPU usage in proxy-go (#33211) - helped debug a reported failure to connect in China (#33219) Next week: - DNS-over-HTTPS prototyping Help with: cjb: 2019-02-27 Last week: - got feedback on #31011! Next week: - #31011 grew into "get tor to parse extra-info docs and their transport lines", am learning how to do that with help from teor - poke at golang snowflake proxy Android app Help with: - perhaps it makes sense to split out the bridge-side change in #31011 from the bridgeauth-side change, since the bridgeauth-side change will take longer, and the bridge-side one will take time to ship and get people updated to..? agix:2020-02-20 Last week: - Submitted fix for #31967 - Worked on #31876 Next week: - Submit first draft of #31876 Help with: -

1 0

Metrics Team Meeting Notes, February 27th 2020
by Gaba 27 Feb '20

27 Feb '20

Hi! We had our weekly metrics team meeting today and it was very short. The next one is going to be on March 5th at 1500 UTC. The pad for the meeting in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The log is http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-27-15.01.log… The agenda and notes for today are: ------------------------------------- Agenda Thursday, February 27th, 15 UTC ------------------------------------- * Changes to DNSBL service: https://lists.torproject.org/pipermail/tor-relays/2020-February/018189.html * What is the status on exit scanner? * we have deployed a new machine, check-01.torproject.org and this is currently running the new exit scanner software cheers, gaba -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

S27 (Onion Services) Meeting today: Tuesday 25th February @ 15UTC
by Pili Guerra 25 Feb '20

25 Feb '20

Hi everyone, Here’s your usual reminder about this meeting. Looking forward to discussing progress! 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

Network health meeting notes, 24 Feb 2020
by Georg Koppen 25 Feb '20

25 Feb '20

Hi! Yesterday, we held another weekly meeting to discuss network health issues and keep us in sync. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-24-19.00.txt Additionally, here come the status updates and discussion items showing what we were up in the previous week and what is planned for the coming one: Discussion: * Guidelines on ethical operating a relay with operators [deferred to next week, GeKo] * https://lists.torproject.org/pipermail/tor-relays/2020-February/018154.html * https://lists.torproject.org/pipermail/tor-relays/2020-January/018040.html * How do we proceed with the bridges part of #32672? [after dealing with the relay part, let's look at the data and then based on that move forward, probably with contacting operators, too, GeKo] GeKo: Last week: - finished a good deal of the simplification of the bad relay rejecting process (#33182) - looked over the DRL and sbws proposal - worked on #32672 (rejecting 0.2.9.x and 0.4.0.x) - looked over ggus's questionaire for relay operators - small review for #33361 - sbws prep This week: - getting up-to-speed for sbws review/work - making scripts for better bad relay rejecting available to others - more work on #32672 - feedback reviews Gaba Last week: - DRL propoposal on scalability (we got the SOI accepted and working on proposal) - tor-relays mailing list moderation dgoulet Last week: - Confirmed things on #32672 - Opened and patch for #33361 Georg

1 0

Network Team Meeting Notes, 19 February 2020
by Alexander Færøy 24 Feb '20

24 Feb '20

Hello, Here is a short summary of the network team meeting from Wednesday the 19th of February 2020. 1) We started out with roadmap. 2) Reviews seemed alright. 3) We went over our 0.4.3 status page. Nick asked the question "if we called maint-0.4.3 a release candidate tomorrow, what would we regret not fixing?" 4) We talked about what to do with circpad tickets. Mike and George will talk about what to do here. 5) We talked about using Shadow for some hard to reproduce issues. 6) Nobody had anything else to discuss. --- end of summary --- You can read the network team meeting log at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-19-22.59.log… Below are the contents of our meeting pad: Nick: Week of 10 Feb (planned): - Work on paper with Ian and Chelsea (revisions due 15 Feb) - Finish review on PETS artifact (due 15 Feb) - Review Teor's proposal 313 - Revise: - TROVE-2020-002 - 33104 -- SIGNAL ACTIVE patch - 32921 -- C style branch - Other patches on 0.4.3 - Release 0.4.3.2-alpha - Continue bug retrospective. Finish? - Open merge window for 0.4.4 - Resolve more 043-must/should tickets - Integrate revisions to prop295 before I forget completely Week of 10 Feb (actual): - Finish paper with Ian and Chelsea. (Tech report is now out) - Review pending proposals and patches. - Numerous meetings - Revise patches for merge in 0.4.3 - Continue revising C style branch patch - Released 0.4.3.2-alpha - Opened merge window for 0.4.4 - Worked on 0.4.3.x tickets - Worked on bug retrospective - Worked on git tooling a little Week of 17 Feb (planned): - Lots of code review - Continue bug retrospective? - Work on relay/dirauth modularization stuff - Any C style work to do? Pending for later: - Try to do a personal roadmap for next 3-4 months - Write policy notes catalyst: week of 02/10 (2020-W07) (planned): - reviews - more research and commenting on #32921 - follow up on .github repo stuff (#32335) week of 02/10 (2020-W07) (actual): - researched innards of emacs C mode somewhat (especially regarding escaped newline alignment) - split some stuff out of #32193 (multiple gitlab CI improvements) - looked a little bit into #32622 (misleading bootstrap message for certain TLS handshake failures) -- probably not actually easy - good meeting about C style stuff and better scoping #32921 - more gsod stuff (#33188) - initial manpage sorting checker script (#33339) week of 02/17 (2020-W08) (planned): - TPI holiday 02/17 - reviews - more gsod stuff as needed - writing feedback - create follow up ticket(s) for stuff out of scope for #32921 - dig a bit more into #32622 week of 02/17 (2020-W08) (actual): - TPI holiday 02/17 - more gsod review (#33275) ahf: Week of 10/2 2020 (planned) - Get over a flu. Going in the right direction. - Review a lot of sbws tickets. - Finish TROVE issue. - Work on wiki migration on GL. Help hiro with migration if she needs that. - Write email about a discussion I had with Peter Stuge and Linus at FOSDEM. Week of 10/2 2020 (actually) - Backlog of different things from the week before: email/irc. - A few reviews. - Work on TROVE issue. - Wrapping my head around sbws/shadow. - Hacked on wiki migration for GL. Week of 17/2 2020 (planned) - Write email about a discussion I had with Peter Stuge and Linus at FOSDEM. - Hack on 0.4.3 tickets. - If the new GL instance comes up before Friday, try to do a run of ticket migrations to it to see if things are better. Write email to tor-project@ with an update. - Look into crash issue in #32729 asn: Week of 10/02 (planned): - Finalize handling of TROVE-2020-003 - Get back to onionbalance v3. - Get #32709 merged - Finish reviews Week of 10/02 (actual): - Finalized TROVE-2020-003 - Finalized #32709 Week of 17/02 (planned): - Get back to OBv3. - Get #32709 merged. dgoulet: Week of Feb 3rd (actual): - Reviews and merges - HS client auth issues. Worked on fixes: #33139, #33148 - Worked on #28992 HS ticket. - More work on #33072 and #33029. Launched a discussion on the dirauth list to decide for backport on those. - Sponsor27 meeting. Wrote a summary of the new SOCKS5 extended error in #33035. - Some work on the network health side to help GeKo transition. - Went over the TROVE and responded on network team security list. - HackerOne report. Week of Feb 10th (planned): - Backport work for #33072 and #33029. - Update #32910 with latest discussion with nickm about the tracing API and code structure. - Will start doing some slides for NetDev 0x14. Diagrams of some tor low level internal codes are needed so I need to start early. Gaba: Last week (actual): - reduce scalabiltiy project to fit new requirements - sbws grant proposal - run behind trac again Week of February 19th (planned) - scalabiltiy project risks - sbws grant proposal - run behind trac teor: (online first meeting of the month, offline at the usual meeting time) Week of 10 February (planned): Important: - Write Draft of Proposal 313: Relay IPv6 Statistics (#33159) - Revise Proposal 313 based on reviews - respond to emails and IRC Roadmap: - open Sponsor 55 tickets for required work - based on proposals - with updated estimates - make existing tickets children of Sponsor 55 parent tickets Other: - Ticket triage, backport deciding, quick code reviews - Python 3 reviews / helping new contributors Week of 10 February (actual): Important: - Write Proposal 313: Relay IPv6 Statistics (#33159) - Revise Proposal 313 based on reviews - Merge Proposal 313 - Create Sponsor 55 tickets, doing estimates, and writing a rough implementation order - respond to emails Roadmap: - made some existing tickets children of Sponsor 55 parent tickets - found a relay bandwidth stats bug that affects our bandwidth and connection stats (#33201), so I guess it's Sponsor 55. - Turns out it's not a bug, it's a misleading comment. - test IPv6 in CI (#33195 and children) - fix protocol version sorting issue (#33285) - help tom with info about IPv6 relays for consensus health (#33266) - Start designing chutney reachability tests (#33232) Other: - Ticket triage, backport deciding, quick code reviews, merges - Python 3 reviews / helping new contributors - Help with manual page rewrite (#33188) - Help with git scripts (#32121, #33284) - Help with 0.4.3 logging fix (#33087) Week of 17 February (planned): Important: Roadmap: - chutney relay IP4 reachability self-tests (#33232) - Add an ipv6 mixed network to chutney and tor - #32588 Setting ORPort [ipv6]:auto mistakenly advertises port 94 - Maybe #33220 Prop 311: 3. Allow Relay IPv6 Extends Other: - Ticket triage, backport deciding, quick code reviews and ticket help - Back to normal code reviews (thanks everyone for letting me focus on Sponsor 55 proposals!) - Python 3 reviews / helping new contributors Week of 17 February (actual): Important: - tor-relays moderation - list moderation was taking a lot of time, and I need to focus on Sponsor 55, so I'm stepping away from list moderation for a while Roadmap: - Make consensus voting more resistant to late votes (#4631) - chutney relay IP4 reachability self-tests (#33232) - Add an ipv6 mixed network to chutney and tor (#33334) - Update the default chutney networks for new tor features (#33376) - Use chutney's diagnostics in Tor's CI (#33353, #32792) - Require all nodes to bootstrap (#33378) - Working on: Require all relays in the consensus - Next up is: Remove AssumeReachable 1 from relays - chutney and tor changes to improve chutney tests Other: - Ticket triage, backport deciding, quick code reviews and ticket help - Back to normal code reviews (thanks everyone for letting me focus on Sponsor 55 proposals!) - Python 3 reviews / helping new contributors - Some quick bug fixes Mike: week of 10 Feb (actual): - Still figuring out Reasearch Janitor role priorities - Performance funding proposal work week of 19 Feb (planned): - Investigate/reproduce circpad shutdown bugs (#30992 and chutney warns); plan some fixes - Mull over Research Janitor responsibilities and priorites - Maybe review metrics-team tickets jnewsome: week of 02/03 (2020-W06) (planned): week of 02/03 (2020-W06) (actual): - Onboarding logistics - Fleshed out Shadow sponsor page a bit https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor38 - Fixed some Shadow compiler warnings and bugs (https://github.com/shadow/shadow/issues/711 and related issues) week of 02/10 (2020-W07) (planned): - Enable -Werror in Shadow, suppressing existing warnings if necessary (https://github.com/shadow/shadow/issues/711) - Add clang compile to CI - Fix remaining tests that listen on hard-coded ports (https://github.com/shadow/shadow/issues/718) - Start planning Shadow TCP redesign week of 02/10 (2020-W07) (actual): - Fixed some additional warnings in Shadow, but haven't enabled -Werror yet. Now planning to only enable it in CI - Investigated possibility of running Shadow CI inside Docker containers. Ran into issues with elfloader. Deferring for now since elfloader is planned to go away. - Created Github CI action for shadow-plugin-tor (shadow-plugin-tor@head against with fixed versions of shadow and tgen) week of 02/17 (2020-W08) (planned): - Extract shadow-plugin-tor CI core logic into a shell script - Set up shadow repository to also run the shadow-plugin-tor CI (shadow@head against fixed versions of shadow-plugin-tor and tgen) - Suppress remaining compiler warnings in Shadow and enable -Werror in CI - Start looking at TCP module and planning refactor/redesign -- Alexander Færøy

1 0

Notes from Vegas Meeting FEBRUARY 20 2020
by Erin Wyatt 21 Feb '20

21 Feb '20

Vegas Team Meeting Notes FEBRUARY 20 2020: + NEW BUSINESS ewyatt: - We have a ton of the old "This is what a Tor supporter looks like" shirts and a ton of OONI shirts, and not a lot of space to store them. What should we do with them? * Can we give them away at the networking event in SF and NY? Yes in SF, no in NY. * We need to figure out how to build a stock in Europe for events there so we can sell there too. gus: - Totem project invited Tor Project to build some online courses for their platform. * Gus will follow up with them to see how we can collaborate. + GENERAL NOTES ewyatt: 1. We have a ton of the old "This is what a Tor supporter looks like" and OONI shirts at the office, and not a lot of space to store them. What should we do with them? 2. Working on employee contracts updates. 3. Administrative Assistant job posting to be posted soon. 4. Emailed EFF for help on the IP section of the employee handbook. 5. We owe people PTO balance updates - will try to get those out next week, so please make sure your timesheets in Harvest are complete and up to date sarah: 1. Meeting in person with Joe Hall from ISOC today. 2. Met with Xavier from Open Collective Foundation. 3. Working on next fiscal year's budget projections. 4. Events in San Francisco and NYC moving along. 5. Updating donation acceptance policy for next week's meeting. Steph: 1. Working with annalee_ on a vpn post 2. Updating our fundraising deck for upcoming meetings: updating old pages, adding 2 new 3. Chasing down some corrections in a story 4. Blog posts: IFF CFP, solving network security goals 5. Announced Walking Onions grant from ZCash 6. Participating in a livestream with Electric Coin next week 7. Other editing: job post, visa letter Philipp (on vacation) 1. Finally wrapped up Python 3 port of BridgeDB, which took a lot of time 2. Sponsor 30 business as usual Pili 1. Mostly working on the DRL proposal 2. Organising blog "reboot" 3. Tor Browser release planning 4. General trac gardening and other maintenance tasks 5. We didn't get accepted for GSoC again :( Nick: 1. Walking onions tech report (joint work with Ian & Chelsea) is out. This is similar to our paper (under submission). 2. Trying to make sure that we've got development priorities straight for April+. Mike: 1. Worked on role description mail 2. Working on circpad network-team bugs 3. Available to help with DRL, nlnet, etc proposals. Just ping me with questions Georg: 1. Digging out of backlog after being afk a bit 2. network health work Antonela: 1. Back from afk time = inbox love 2. Wrapping S27 work: closing my bits on remaining tickets, testing builds, following up the conversation with the Learning Lab. 3. The DV ballot passed. I'm talking with Soraya at EFF to learn how let's encrypt updates reach certbot releases. 4. Following up with Tunde (ICFP). He is traveling running interviews this week. 5. A new iteration of torproject.org/download is live > https://www.torproject.org/download/ 6. Met Internews to learn about their USABLE program and plans for this year. Alex: 1. Team seems to be doing well. 2. Started having 1:1's again after missing them after FOSDEM and me being sick last week. 3. Status update with Gaba and Nick. 4. Trying to wrap my head around both Shadow and SBWS still. 5. Working on 0.4.3 tickets. Gaba: 1. DRL Scalability proposal writing 2. SF networking event invites 3. Sponsor follow up 4. Running behind Trac 5. Sync on capacity and priorities with Alex and Nick. 6. Getting my turn into trying to kill SVN 7. Sound track for this week: https://www.youtube.com/watch?v=FwuQamWm6ME anarcat: 1. new server setup (fsn-node-04) in progress 2. improved on server bootstrapping process (cut down number of steps in half!) 3. audited nagios puppet module to work towards puppetization (#32901)1 4. SVN next steps discussion 5. random routine stuff: package installs (#33295), DNS updates (#33308), RT root noises (#33314), gitlab puppet work patch review Karsten: 1. Released Onionoo 7.0-1.24.0, 7.1-1.24.1, and 8.0-1.25.0. Matt: 1. Maybe releasing another Tor Browser Alpha update next week with more S27 (onion service usability) features 2. Sketching Tor Browser roadmap for next ~4 months (will probably organize a meeting in the near future) 3. Learning much about our signing infrastructure and thinking about how we can improve it (and our signing process overall) isabela: 1. back from vacation, catchin up on everything Gus: 1. Reaching out possible partners for DRL proposal. 2. Spreading the news about Tor Village in IFF and also answering people who contacted us. Blog post: https://blog.torproject.org/tor-village-iff-2020-call-proposals 3. Network health: Reviewing EFF Legal FAQ. 4. Network health: organizing workflow to contact relay operators running old tor versions (0.2.9.x and 0.4.0). Contacted relay operators from mexico, costa rica, brazil, chile. 5. Reviewing Cleo's work in RT and documentation PRs. 6. Did a Tor workshop last saturday with a community network in Sao Paulo state. 7. Offline next monday and tuesday (local holiday)

1 0