December 2018 - 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

announcing the next Tor Meeting location....
by Alison Macrina 04 Feb '19

04 Feb '19

We're excited to meet and hack with the Tor community in Athens, Greece in May 2019! The meeting planners are working on finalizing the precise dates and people for the invite-only portion of the meeting, but the open days will be held 18-19 May. Mark your calendars! Alison -- Alison Macrina Community Team Lead The Tor Project

3 3

Initial roadmap for the anti-censorship team
by Roger Dingledine 25 Jan '19

25 Jan '19

Here is an early brainstorming list of the scope for our future anti-censorship team. Let us know if we left out a critical category. And of course once we have actual team members I expect they will take this initial roadmap and do something even smarter than this list. :) (1) BridgeDB: - Automated monitoring - Understand current usage patterns, consider improving the design Don't get obfs4 bridges blocked by other transports (#28655) (2) Pluggable Transports: - Improve the PT interface with Tor, to pass logs etc (#25502) [with network team] - Tor Browser can use other circumvention tools as proxies (#28556) [with browser team] - Specific PTs: Maintain obfs4proxy (like fixing the iat bug that let Kazakhstan block it) Snowflake Httpsproxy Marionette Domain front through community sites - Talk to research groups to keep in touch about their PT research work (3) Improve Tor user experience for users in censored / crappy networks: - Gettor: automated monitoring and automated updates. Improve UX. - Understanding and reducing client time to bootstrap [with network team] and other parameters that are tuned poorly for slow networks (4) Understand Tor censorship: - Tor Browser network testing mode (#23839, #28531) [with browser team] - Reachability scanning for the default (shipped in Tor Browser) bridges [with ooni] - Understand bridge load and bridge blocking (e.g. fix user counting bugs that are making our Turkey count wrong) [with network / metrics teams] (5) Help users use bridges: - Help NGOs get their users on bridges (#28015, #28526) - Tor Browser *automates* picking the right PTs [with browser team] (6) Community outreach and integration: [with community team] - [Initial list of outreach partner NGOs elided for now, since some of them have opsec needs to keep their people safe]

9 10

Fwd: [OTF-Talk] OTF is Hiring!
by isabela 22 Dec '18

22 Dec '18

-------- Forwarded Message -------- Subject: [OTF-Talk] OTF is Hiring! Date: Fri, 21 Dec 2018 09:31:15 -0700 From: Dan McDevitt <dan(a)opentech.fund> To: OTF-Talk <otf-talk(a)opentech.fund> Hey folks! OTF has an exciting job opportunity we just posted and wanted to share with you all. We’re looking for our team's next *Technology Manager / Director* to manage OTF's technical operations and be the go-to, point person for all things security. This will include managing the systems and infrastructure our team relies upon, conducting security and privacy assessments of OTF’s systems, and promoting security best practices within the OTF team, among other responsibilities. Read the full description here: https://www.opentech.fund/about/jobs/technology-manager-director/ Please feel free to help spread the word, and reach out if you have any questions. Thanks everyone and happy holidays! Dan -- Communications Coordinator Open Technology Fund | opentech.fund <https://www.opentech.fund/> Twitter: @opentechfund <https://twitter.com/OpenTechFund> *Subscribe *to OTF Today: Internet Freedom News <https://fund.us10.list-manage.com/subscribe?u=87f4d651661e6ca6ef558bce9&id=…> -- This is now the OTF-Talk mailing list (formally OTF-Projects), where past and current OTF supported projects can share information, ask questions, and more. Monthly reports should be sent to OTF-Active (the list for currently supported projects) https://groups.google.com/a/opentech.fund/d/forum/otf-active --- You received this message because you are subscribed to the Google Groups "OTF-Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to otf-talk+unsubscribe(a)opentech.fund <mailto:otf-talk+unsubscribe@opentech.fund>. To post to this group, send email to otf-talk(a)opentech.fund <mailto:otf-talk@opentech.fund>. To view this discussion on the web visit https://groups.google.com/a/opentech.fund/d/msgid/otf-talk/CAOGASDcoa3m_Rqc… <https://groups.google.com/a/opentech.fund/d/msgid/otf-talk/CAOGASDcoa3m_Rqc…>. For more options, visit https://groups.google.com/a/opentech.fund/d/optout.

1 0

Notes from December 20 2018 Vegas team meeting
by Karsten Loesing 21 Dec '18

21 Dec '18

Notes for December 20 2018 meeting: Pili: 1) Working on Counterpart International Proposal for User Testing Program in Zimbabwe 2) Sponsor 19: Started sharing tickets with the teams and doing some preliminary scheduling 3) Started organising work for gettor for early 2019 4) More updates to the Sida Phase 1 report Antonela: 1) reviewed OTF Proposal and S9 feedback docs 2) worked on snowflake 3) working on TBA + Orbot 4) wrapping november and december reports for the UX team 5) Hiro is still working on tpo.org or tpo.org/about on staging 6) working with Elio on the first iteration of wireframes for Country pages of the new OONI Explorer 7) made a draft of a PRD for Get Tor 8) my Open Source Design FOSDEM Devroom talk was accepted 9) made updates at donate.tpo.org and assets for the #oniontravels campaign Alison: 1) submitted Rightscon talk for me and Gus and others from different orgs 2) doing lots of LFI recruitment 3) Maggie is working on volunteer coordination plans 4) Maggie is also writing up what we hope will eventually become the canonical Tor vs VPN document 5) Kat is working on the second s19 report 6) Colin continued working with PIA on relay deployment and trying to resolve suspicious relay issues with OVH 7) emma helped onionshare with translations, got some more langs in the manual and on support.torproject.org staging 8) we worked on s9 follow ups Nick: 1) Scrambling to finish end-of-year stuff, including S8 and S3 reporting tasks, MOSS planning, S8 coding, and release. 2) AFAIK I have currently done everything others need for end of year, other than: * Opening tickets for initial MOSS milestones * Reviewing and responding to draft anticensorship roadmap * Code review for late-arriving code, as it arrives. * Please let me know asap if you need something not on that list. 3) I'll be storing email not addressed to me personally from Saturday through my return on Jan 2 or 3. If you need me for something from me then, please use signal or personal email. 4) Updated release plans: hoping to get 0.3.5.7 (stable) in January, along with new 0.3.3.x and 0.3.4.x releases, and the first 0.4.0.x alpha. Please make sure the network team knows if you consider any current bug to be a release blocker. 5) S8 looks to be finishing in a good state. Gaba: 1) S8 Q4 report - looked at what was done by network team and match it with objectives. 2) OONI: created tickets for one of the projects and map it to use github projects for it. 3) MOSS modularization: worked on milestones for the project with Nick and Al sent them. 4) Metrics: sent the report on collector to OTF. Before the end of the year: 1) Report on sponsor 3 2) Move s19 roadmap into something I can track. 3) Adjust the roles/responsabilites for the anti-censorship dev and lead to send to candidates. Shari: 1) Packing up my stuff from the Seattle office today. Today's my last day in the office. 2) Contacting potential major donors and asking them to give. 3) Reviewing grant proposals as needed. 4) Trying to be useful in all other ways. Karsten: 1) Published technical report "Towards modernising data collection and archive for the Tor network.": https://research.torproject.org/techreports/modern-collector-2018-12-19.pdf 2) Updated "Total consensus weights across bandwidth authorities" to only contain running relays and to also contain consensus numbers: https://metrics.torproject.org/totalcw.html 3) Updated 4 graphs containing OnionPerf data to show all sources separately rather than an aggregate number: https://metrics.torproject.org/torperf.html 4) Combined 3 graphs on consumed bandwidth into 1 graph: https://metrics.torproject.org/bandwidth-flags.html 5) Made a couple internal changes to the Tor Metrics website that will make it a lot easier to maintain in the future. Erin: 1) personnel stuff 2) tying up loose ends, getting our recruiting processes ready to be on hold for the holiday 3) office saying goodbye to Shari [sniffle, sniffle] Steph: 1) Preparing final posts and emails, planning for holiday comms. I will be online and available for much of the break. 2) I will be offline first week of Jan 3) Trying to raise $5k today through social media to reveal a surprise. 4) Working on the next newsletter so we can have it go out over the break 5) Working on 2019 comms strategy 6) Responding to press inquiries Mike: 1) Just sponsor2 dev work Sarah: 1) Reviewing grant proposals that have deadlines the first week of the year. 2) Met with DRL officers and Isa in DC yesterday. 3) Preparing a Christmas-themed blog and final YE emails. 4) Sat on a panel Monday for a Georgetown grad school class on fundraising. Drummed up interest about Tor. 5) Helping with YE campaign social media efforts. 6) Reaching out to potential major donors. 7) Preparing for a t-shirt promotion next week. 8) Working on 2019 fundraising roadmap. 9) Will be online most of next week, but might have spotty Wifi at times, so use Signal to reach me. isabela: 1) helping out with grant proposals and following up with Sida feedback on our report 2) reviewing blog posts for YE campaign 3) made the video for the challenge and also coordinated the motivation part 4) working with Sarah on fundraising roadmap 2019 5) organizing

1 0

November and December 2018 report for the UX team
by Antonela Debiasi 20 Dec '18

20 Dec '18

Hello tor, I wrapped the last two months here, so this is quite long. We joined Mozilla during All Hands in Orlando. We had insightful conversations about privacy, users and security and privacy settings. We reached a consensus about the next version of our Security Settings. With this iteration, we are trying to balance security and usability and a better understanding about what each security level trade-off is for users as well. The latest prototype allows clicks here: https://marvelapp.com/a66fg97/screen/50307815 Dunqan, an advocate designer, worked on the Onboardingto introduce our new Security Settings to users. This iteration will allow us to explain to users how security settings work and also to fix two bugs from the previous version. You can see it in action here: https://trac.torproject.org/projects/tor/ticket/28628 Tor Browser new icon implementation reached our alphas and will see the light during our stable release in TB85. Since you were part of this work, you can sneak peek how TB will look next: https://share.riseup.net/#cWuwkUMcV6fORQaj5EFYzA Wanda Arca, a designer from Argentina, made an animated version of the new TB icon, you can enjoy it here: https://share.riseup.net/#t6oppakZeK228VedKJyJTw The second alpha for Tor Browser for Android was released, and we are working towards next sprint, TBA-a3. We want to offer users a simple way to connect to the tor network and also enable censored users to decide to connect via bridges if it is needed. Some of this work is still in progress here: https://trac.torproject.org/projects/tor/ticket/28329 Elio and OONI folks are working on the new version of OONI Explorer. We iterated over the Measurement Result pages to match the concept and the layout with the recently release OONI Probe, and we are working on Country pages right now. You can see the work in progress here: https://xd.adobe.com/spec/2f585e0f-1a7e-4f6c-41f9-fa411520998e-5969/ We are planning to run usability testing in January for the new OONI Explorer Country pages. If you are a researcher or someone who use OONI Explorer a lot, we want to hear your feedback of what we are building! We joined forces with the network team to allow users to run Snowflake in more diverse ways. One of those ways will be a browser web extension. We are working on it and will be part of a huge 2019 milestone that aims to help censored users to reach the Internet. See the first intent here: https://trac.torproject.org/projects/tor/ticket/23888#comment:5 The new torproject.org is now ready for review on staging. Is still a work in progress and we aim to release it during Q119. http://lektor-staging.torproject.org/ Hiro presented Onions in Containers during DockerCon Europe 18. She talked about how .onion can grow using Docker containers and what are the benefits of doing it for end users. https://dockerconeurope18.smarteventscloud.com/connect/sessionDetail.ww?SES… And as a closure, in 2018 we released TB8 with several usability improvements, we worked on TBA to match the experience that users have in desktop, we launched support.torproject.org as the primary source for users to find answers to their questions. Also, we traveled over four countries in the global-south to raise the voices of our users and their experiences in local contexts, and we worked across teams to support them with visual, UI and UX design. As we look forward to 2019, I hope to continue offering solutions to users all over the world to reach the internet privately and safely. Happy holidays folks! A

1 0

November Communications Report
by Stephanie A. Whited 20 Dec '18

20 Dec '18

Hello Tor, Our end of year fundraising campaign was in full swing in November, and the number of posts increased across our channels. Thanks to everyone who has been helping with writing blog posts. We are trying to raise $5k today to release a surprise, so please share if you can. https://twitter.com/torproject/status/1075616816054091776 https://twitter.com/torproject/status/1075616816054091776 Nov in links and stats: Blog posts https://blog.torproject.org/strength-numbers-growing-our-board-directors https://blog.torproject.org/strength-numbers-onion-blooms https://blog.torproject.org/strength-numbers-internet-freedom-line https://blog.torproject.org/strength-numbers-community-key https://blog.torproject.org/strength-numbers-there-are-many-ways-give https://blog.torproject.org/strength-numbers-why-every-dollar-counts Twitter https://twitter.com/torproject New followers: 3,593 Top tweets https://twitter.com/torproject/status/1059523023466909697 https://twitter.com/torproject/status/1066011011772227587 https://twitter.com/torproject/status/1062712686876737536 Mastodon https://mastodon.social/@torproject New followers: 250 LinkedIn https://www.linkedin.com/company/tor-project/ New followers: 62 Facebook https://www.facebookcorewwwi.onion/TorProject New followers: 184 Instagram https://www.instagram.com/torproject/ New followers: 73 Newsletter https://newsletter.torproject.org/archive/2018-11-30-new-board-member-inter… Notable press https://motherboard.vice.com/en_us/article/zm9jd4/old-school-sniffing-attac… o/ -- 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

Network team meeting notes, 17 Dec 2018
by Nick Mathewson 19 Dec '18

19 Dec '18

Hi all! The logs of our last team meeting of 2018 are available from http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-12-17-17.58.html Below is the state of our pad: = Network team meeting pad! = This week's team meeting is at Monday at 1800 UTC on #tor-meeting on OFTC. Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1800 UTC On #tor-meeting on OFTC. December-January schedule: * Next meeting on 17 Dec, 1800 UTC. * NO MEETING on 24 Dec or 31 Dec. * Following meeting on 8 Jan 2019, 2300 UTC. (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 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002074.html 26 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002084.html 3 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002117.html 10 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002120.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… 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 * Let's try a different way of looking at proposed tickets: https://pad.riseup.net/p/network-team-triage-2018 0.3.5 (bugs only): https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… 0.4.0: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == 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 actual point when you finish a task (as well as "fix" the estimate when starting the issue). * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbd… * Check other's people call for help in their entries. << Remember that priority is Sponsor 8 - roadmap is sort out by priority >> Activity O2.5 is the one we are missing and need to be done by the end of December 2018. ------------------------------- ---- 17 December 2018 ------------------------------- == Announcements == This week's meeting is on Monday at 1800 UTC. Please don't bulk-delete all the old entries from this pad any more. Instead, delete the "planned" and "actual" for the previous week, but leave the "planned" for this week in place. Please check the dates before deleting. Gaba> Sponsor 8 Q4 REPORT : review what you worked on in the last 3 months and add any comment on it or proposal. https://storm.torproject.org/shared/E8jZ6LwgMxa9zeyOgEye3eq6ytTaFZjCCetMYm8… Teor is bringing a proposal for proposed ticket. Please make comments in the pad and we can discuss it in the first meeting in January when Teor will be present https://pad.riseup.net/p/network-team-triage-2018 Reviewer role proposal is still open for comments. gaba> I will work on it when I have a little more time to discuss it with the team in January (we need to separte process from responsabilities). https://pad.riseup.net/p/q0s3rQxVzSeZ == Discussion == * Who needs help with reviews? Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Sponsor 8 is wrapping up in December. Right now working on this: catalyst, ahf, dgoulet, teor, nick. Any of you need help with it? * Nick would like to do review & merge stuff this week. * Sponsor 31 in da house. Modularization proposal. We are creating activities for the milestones [0] and soon need to add tickets and incoporate some of them in January. It will be included in the roadmap creation in Brussels. [0] -> Sheet milestones of this document https://storm.torproject.org/shared/a-NKHPmkxDOuAGNaFpOrd3AIXJ4mDgIbL5sIjf4… * Start thinking about what we are going to do during hackweek. We can discuss in January https://pad.riseup.net/p/tor-netteam-agenda-hackweek-2019.1-keep * When are people taking end-of-year vacation? (When are you planning to get back?) * Nick: Dec 22 through Jan 1. Returning Jan 2 or Jan 3. * Gaba: Dec 24th through Jan 1st. Returning Jan 2nd. * ahf: Dec 24th to Jan 1st, returning Jan 2nd. * dgoulet: Sent on network-team list. == 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! Nick: Week of 12/10 (planned): - Try to fix as many 035 and 040 bugs as possible - Fuzz #28755 et al via (#28808) - Reschedule 0.3.5 (and 0.4.0?) release plans. Week of 12/10 (actual): - Fuzzed and revised K=V implmentation (#28755) - Reviewed and released clusterfuzz non-issue - Opened subtickets for startup performance issue (#28481), wrote patches for most. - Final 035-rc-blocker triage - Review and merge a whole lot of stuff - Revised planned dates for releases on the wiki. Week of 12/17 (planned): - Release 0.3.5.6-rc - Brook travel to brussels. I have the dates right, yeah? Jan 29 through Feb 1? - Review and merge a whole lot of stuff - Prioritize remaining 035 issues. - Snowflake spec (begin) - Early planning on modularization stuff - Followup on the openssl tickets I opened last week (https://github.com/openssl/openssl/issues/7894, https://github.com/openssl/openssl/issues/7895 ) - End-of-year checkin with various folks - Help with S8 final reporting, if needed. - Fix scan-build warnings Want help with: Mike: Week of 12/10 (planned): - Custom 0.2.9 backport of #27049 fix? - wtf-pad unittests Week of 12/10 (actual): - Work on more tests for wtf-pad. 93.5% test coverage. Week of 12/17 (planned): - Finish up wtf-pad tests - Review wtf-pad type sizes - wtf-pad negotiation tweaks - wtf-pad mechanism to keep idle circuit open to pad Want help with: ahf: Week of 12/10 (planned): Sponsor 8: - Get some help with solving the dependency issue between src/lib/* code in patch for #28179. - Update specs for STATUS with example K/V pairs from currently deployed PT's. - Get #28179 reviewed again. Sponsor 19: - Continue to debug #28726 JS/Go proxy code. Misc: - Sysadmin interviews. Week of 12/10 (actually): Sponsor 8: - Got help with solving the dependency issue between src/lib/* code in patch for #28179 from David and Nick. - Pushed updates to #28179, pending review. Sponsor 19: - Updated my setup with lots of debug info for #28726. Misc: - Did some minor tweaks for the tor-win32 scripts (enabled CI for pushes+nightly, 64-bit builds and some fixes that asn needed to run his tests). - Sysadmin interviews. - Looked at code from some of the final anti-censorship candidates. Week of 17/10 (planned): Sponsor 8: 1. Fix whatever fixes are needed for #28179 2. Submit patches for #28846, and maybe #28849 3. Get back to #27100. - Q4 reporting. Sponsor 19: - Help if there is need with some of the spec work. - Look at the last candidates code sample. Discuss next steps. asn: Week of 12/10 (planned): - Continue doing fixups on #28142: - Currently 32-bit appveyor is failing on the stochastic prob distr tests. I'm not sure what's going on there and why it's failing only on 32-bits. I have informed Riastradh on this and see what he tells me. Other than that, maybe the tests are busted on 32-bits and we have to disable them. - I have more fixups to do based on past Nick's review on #28142. - Still need to check Mike' response on #28634. Week of 12/10 (actual): - Pushed branch with #28142 fixups!!! - Riastradh fixed the 32-bit appveyor issue. - I resolved the remaining nickm review comments on PR#461. - I pushed some spec fixes based on review comments. - Rebased and squashed the fixup branch and pushed updates on trac: https://trac.torproject.org/projects/tor/ticket/28142#comment:25 - Helped with anti-censorship hiring. - Did reviews. Week of 12/17 (planned): - Do the final steps to move #28142 to merge_ready. - Finish up with anti-censorship hiring. - Do reviews. - Maybe look at some hsv3 tasks I've been neglecting due to #28142. - Will be focusing on uni stuff on Thursday/Friday. Help with: - All good. dgoulet: Week of 12/10 (planned): - Finalize/review the STATUS notification work. Will require spec changes as well as code review. - Setup a Snowflake environment to start play with it more seriously. Week of 12/10 (actual): - Review #28755 (K/V parser library) needed for #28179. - Review a series of other tickets (see Timeline). - Patch work on couple tickets and make them ready for upstream - Busy week in the bad relay land. Week of 12/17 (planned): - Finalizing s8 work with ahf. - Do a pass over 035 tickets to see what remains after the -rc. - Memory profile of 040 so we can get some data on our improvements for sponsor 8: #28020 gaba: Week of 12/10 (actual): - S8 follow up with work that needs to be done. https://pad.riseup.net/p/qPH3xF4JaHOB - 1:1s - anti-censorship position follow up - s19: draft (with roger) of a possible roadmap for anti-censorship Week of 12/17 (planned): - S8 Q4 report - anti-censorship position follow up - move anti-censorship roadmap in some format we can use to track it & assess how much of this can be done for s19 - send mail to kickoff thinking about hackweek organizing - modularization proposal: - finish milestones/tasks to send to sponsor https://storm.torproject.org/shared/a-NKHPmkxDOuAGNaFpOrd3AIXJ4mDgIbL5sIjf4… - ping people to get proposal into track tickets help with: - what did we do in S8 tickets for Q4 2018? help me translate on what it means for what you did. catalyst: week of 12/10 (2018-W50) (planned): - CI + Coverity rotation <- nick is dong this one this week - reviews - travel request for Brussels - update detailed sponsor8 progress - more progress on orconn-tracker (#27167), specifically adding and combining circuit tracking with the work so far - get feedback on #28731 week of 12/10 (2018-W50) (actual): - made a lot of progress and have a working proof of concept for orconn-tracker (#27167) that already makes substantial improvements of behavior on what we have already - booked travel to Brussels - tried to clarify some communications of sponsor8 progress - thought a lot about existing and possible future bootstrap progress phases - figured out a way to have a single set number assignments for bootstrap phases for multiple tor configurations (for now?) week of 12/17 (2018-W51) (planned): - cleaning up orconn-tracker for review -- mostly it needs some commits detangled (mostly done, after much wrestling with interactive git rebase), and more documentation in commit messages and comments, also changelogs - assess testing situation on orconn-tracker; write new tests as needed - if there's time, work on reporting intermediate application circuit building progress during bootstrap (#27104) -- a lot of the work is already in orconn-tracker - adjusting sponsor8 tickets to better reflect reality - worked through the weekend so i might take some time off (but still reachable on Signal; IRC and email higher latency) help with: - early feedback on orconn-tracker is helpful, if you're willing to look at it before i finish commenting and documenting (code and behavior won't change very much at this point) teor (offline): Week of 10 Dec (planned): High-Priority: - Need to update the fallback directory mirrors, they are causing bootstrap issues - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - And also on networks that drop packets - Continue to work on s8 bootstrap tickets - integration testing for clock skew? - chutney CI - earlier s8 bugfixes Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews Week of 10 Dec (actual): High-Priority: - Sent network team meeting time email to tor-dev, because we're back to our regular schedule - Sent pad and meeting notes to tor-project - Need to update the fallback directory mirrors, they are causing bootstrap issues - Did the fallback list merge (thanks Phoul!) Medium-Priority: - 1.0 days of sbws reviews - Metrics job applications - Other code reviews - Took a few days off due to illness Week of 17 Dec (planned): High-Priority: - Sponsor 8 tasks - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - And also on networks that drop packets - Continue to work on s8 bootstrap tickets - integration testing for clock skew? - chutney CI - earlier s8 bugfixes - Send reminder emails for team meetings at: 2300 UTC on Tuesday 8 January 2019, 1800 UTC on Mondays 14 and 21 January, miss 28 January and 4 February due to hackfest/FOSDEM our first February meeting 2300 UTC on Tuesday 11 February Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews - I might need to take some more time off Week of 17 Dec (actual): Help with: - If there's anything I urgently need to do this week, please send me a Signal message or email juga (offline): - Week 12/10 (planned) - disable connection padding in sbws' Tor (#28692) - Try enabling predicted circuits (#28701) - Explain reasons why sbws might stall and find out more (#28663) - send scanner metadata as part of every HTTP request (#28741) - Week 12/10 (actual) - disable connection padding in sbws' Tor (#28692) - Try enabling predicted circuits (#28701) - Explain reasons why sbws might stall and find out more (#28663) - send scanner metadata as part of every HTTP request (#28741) - Make info level logs more clear and consistent (#28736) - Stop allowing destination serving files without tls (#28789) - Week 17/10 (plan) - continue working on why sbws stalls and all the related subtasks (#28663) - Help with: - sbws tickets needing review: https://trac.torproject.org/projects/tor/report/72

1 0

October Fundraising Report
by sstevenson＠torproject.org 18 Dec '18

18 Dec '18

The fundraising team was very busy in October! We attended the Mexico meeting and wrote a blog <https://blog.torproject.org/reflections-tor-meeting-newbie>about my experience. Launched YE campaign - Strength in Numbers <https://blog.torproject.org/strength-numbers-double-your-donation-mozillas-…>. With Mozilla’s match, we’ve raised $100,000 so far! Thanks to Antonela and the Tor Browser team, especially Arthur and Georg, for creating and implementing the series of banners that are seen in Tor Browser. Thanks to Steph for pushing the campaign out on social media and in Tor News. We are excited to see a good amount of traffic to the donate page coming from Mastodon. Thanks to hiro and emmapeel for translating and implementing changes to the banner on torproject.org and donate.torproject.org. Thanks to Jon for being the swag guru. Thanks to Karsten and Iain for monitoring the metrics. Attended DRL Implementers’ Meeting in DC - learned about how some other organizations function and talked about how we can all collaborate. Connected with fundraisers at a lot of nonprofits to crowdsource information on accepting different types of cryptocurrency. Al has been writing. A lot. A proposal for our anti-censorship work will be submitted today. Many thanks to everyone who has worked on this. A proposal for code modularization is also about to be submitted. Next week, we’ll send out a letter to family foundations. Have a great weekend! Sarah Sarah Stevenson Fundraising Director The Tor Project sstevenson(a)torproject.org Public Key: 93B3 AC08 4257 FA3D D4BB 8E95 CC08 5DBA C015 612A

1 1