tor-project March 2020

tor-project@lists.torproject.org

23 participants
52 discussions

Metrics Meeting Notes, March 5th 2020
by Gaba 05 Mar '20

05 Mar '20

Hi! We had our weekly metrics team meeting today. The next one is going to be on March 12th at 1500 UTC. The pad for the meetings in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The agenda and notes for today are here: ---------------------------------- Agenda Thursday, March 5th, 15 UTC ---------------------------------- Feedback due tomorrow (karsten) Exit List Service Change Announcement (irl) https://trac.torproject.org/projects/tor/ticket/33510 https://pad.riseup.net/p/exit-scanner-transistion-announcement-keep Needs review tickets (karsten) https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Defect tickets (karsten) https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… Roadmap (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-05-15.02.log… -- 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

Anti-censorship team meeting notes 05 March 2020
by Cecylia Bocovich 05 Mar '20

05 Mar '20

Here is our meeting log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-05-17.59.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday March 5th 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 meetings' 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 ------------------------- --- March 5th 2020 -- ------------------------- == Announcements == Snowflake got a mention on privacytools.io: https://www.privacytools.io/browsers/#addons Tor participating in Google Summer of Code, ideas page: https://community.torproject.org/gsoc/ == 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 == https://ooni.org/post/2020-iran-blocks-farsi-wikipedia/ "Over the last days, between 2nd to 3rd March 2020, OONI measurements collected from 6 different networks in Iran showed that access to the Farsi edition of Wikipedia (fa.wikipedia.org) was temporarily blocked by means of DNS tampering and SNI filtering." "The Farsi edition of Wikinews (fa.wikinews.org) has remained blocked ... It’s worth highlighting that the mobile version of the Farsi language edition of Wikipedia (fa.m.wikipedia.org) remains accessible, as does the English version of Wikipedia (en.wikipedia.org)." == 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-03-05 Last week: - implemented snowflake throughput check (#32938) - updated snowflake webextension and badge with new translations - wrote a patch for gitlab issues with gettor (#33034) - added a go module to snowflake (#33330) - grant edits - responded to GSoC emails - looked at old pcaps for clues about why some proxies fail This week: - maybe continue work on throughput check (#32938) - tbb patch for #33330 - implement update notification for proxy-go instances (#32677) - Aggregate and write up a report of snowflake throughput changes (#32545) - revise GetTor message body (#9036) Needs help with: - review of #33034 (hiro?) - review of snowflake tickets #32938 and #33330 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-03-05 Last week: - turned off the unused snowflake-reg-test.appspot.com reflector (#33429) - posted a workaround for snowflake-turbotunnel packages updating themselves (#33336) - helped diagnose a snowflake stall when there are multiple SOCKS connections (#33519) Next week: - review go.mod for snowflake (#33330) - review snowflake throughput tests (#32938) - work on a fix for multiple SOCKS connections (#33519) - maybe make new packages with 9.5a7 when that's out Help with: cjb: 2019-03-05 Last week: - went ahead with removing the bridgeauth-side change from #31011 so that ticket can be split out Next week: - poke at golang snowflake proxy Android app Help with: agix:2020-03-05 Last week: - Still on #31426 - Fixed #31528 - I have summarized the errors and difficulties I encountered when setting up BridgeDB and noted some small fixes and suggestions for improvement Next week: - Continue on #31426 - Checkout the BridgeDB Port to Python3 Help with: - I changed the references in #31528 but responses like "Uh, oh spaghettios!" have already been translated into different languages. How should I handle that? - Just to clarify, what is the preferred way for you guys to submit a fix? Should I just push my branch or submit a patch as an attachment on the ticket?

1 0

Dip down for 1 hour approx today March 5 1400 UTC
by Hiro 05 Mar '20

05 Mar '20

Hi all, We have to migrate dip to a different VM and the service might be down for about 30/60 minutes today March 5 around 1400 UTC. What will you have to do? Mostly nothing except waiting for the service to come back. If when the service is back you notice some issues please open a ticket on Trac under the git component and assign it to me. We will try to copy everything over, but it might happen that you will have to re-add your ssh key to your profile or your profile pic (if you have changed that in the first place). The "new gitlab" will be available at gitlab.tp.o and dip.tp.o will redirect to it. I will send another email when everything has been migrated. Talk soon, -hiro

1 1

Tor Project will be participating in GSoC under the DIAL Open Source Center
by Pili Guerra 05 Mar '20

05 Mar '20

Hi everyone, I just wanted to let you all know that Tor Project will be participating in Google Summer of Code this year under the DIAL Open Source Center umbrella organization[1]! Please check out our project ideas page[2] and help us spread the word to any interested students. Thank you! Pili [1] https://hub.osc.dial.community/t/google-summer-of-code-2020-open-source-cen… <https://hub.osc.dial.community/t/google-summer-of-code-2020-open-source-cen…> [2] https://community.torproject.org/gsoc/ <https://community.torproject.org/gsoc/> — 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

S30 Meeting on Tuesday March 10th at 1800 UTC [Empowering Communities in the Global South to Bypass Censorship ]
by Gaba 03 Mar '20

03 Mar '20

Hi! We are meeting on March 10th for the S30 project [0]. The meeting will be at 1800 UTC in #tor-meeting, irc.oftc.net The agenda and notes will be at https://pad.riseup.net/p/sponsor30-agenda-notes-Y1-keep cheers, gaba [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 -- 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

help needed: open more tickets for next DocsHackathon
by emmapeel＠torproject.org 03 Mar '20

03 Mar '20

In the Community Team we were happy with the results of the Documentation Hackathon of last year, so we are planning to do it again for the last week of March - 23 to 28. https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH… The DocsHackathon served to update our docs and test our reviewing/updating processes, we learned a lot and documented the website development as well. And on top of that, we engaged with new contributors that supported us with their brainpower. Thanks to all participants of last and next DocsHackathon! We are tagging some issues we see on the different bug trackers, and that we think will be easy to do for a newcomer trying to improve our documentation. https://trac.torproject.org/projects/tor/query?status=!closed&component=Web… https://dip.torproject.org/torproject/web/support/issues?label_name%5B%5D=D… But maybe you want to add more. That would be great! Please create a ticket here: https://trac.torproject.org/projects/tor/newticket - Component: Webpages/Support You can tag issues with the docshackathon keyword, or also propose it by email/irc if you feel unsure. See this search to get an idea of what are we looking for: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~doc… Thanks in advance! emmapeel P/S: Remember that the Spaghetti Monster kills a kitten each time you open a duplicated ticket!

1 0

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

Tor Browser Release meeting this week: Wednesday 4th March @ 19UTC
by Pili Guerra 03 Mar '20

03 Mar '20

Hi everyone, We’ll be having our Tor Browser release meeting this week. Please join us on Wednesday 4th March @ 19UTC on #tor-meeting. Thank you! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

February 2020 report for the Network Health team
by Georg Koppen 03 Mar '20

03 Mar '20

Hello! Highlights in February from the network health side were: 1) We finished our roadmap. For finding out what we have in our pipeline for the coming weeks have a look at our team site[1] or our bug tracker:[2] the keyword to look for/keep in mind is `network-health-roadmap-2020Q1`. 2) Together with the network team we tried to get traction (again) to complete the remaining pieces for our new bandwidth scanner, sbws, so it can finally get deployed on all of our bandwidth authorities. 3) As usual somewhat unexpected items show up. This time we got busy with starting to contact relay operators running obsolete Tor versions, 0.2.9.x and 0.4.0.x, which we plan to reject from the network soon.[3] For March we have planned to make substantial progress on sbws and finish the preparations for rejecting relays running 0.2.9.x and 0.4.0.x from the network (there are probably bridges running those Tor versions, too, which we should try to get to upgrade before we pull the switch). Additionally, I plan to pick up work to get an overview of DNS failures at exit relays and act upon that[4][5], and I want to look closer at issues of our bad relay scanners and fix them[6]. Georg [1] https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam [2] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… [3] https://trac.torproject.org/projects/tor/ticket/32672 [4] https://trac.torproject.org/projects/tor/ticket/32864 [5] https://trac.torproject.org/projects/tor/ticket/33179 [6] https://trac.torproject.org/projects/tor/ticket/33180

1 0

Network health meeting notes, 3 Mar 2020
by Georg Koppen 03 Mar '20

03 Mar '20

Hi! Yesterday, we held our first weekly sync about network health issues in March 2020. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-02-19.00.log… What we were up to in the previous week and what we plan for the coming one (plus discussion items we had) can be found below: Discussion: Guidelines on ethical operating a relay with operators * https://lists.torproject.org/pipermail/tor-relays/2020-February/018154.html * https://lists.torproject.org/pipermail/tor-relays/2020-January/018040.html [GeKo: ggus will start contacting folks to figure out where we are here] Changes to DNSBL service: https://lists.torproject.org/pipermail/tor-relays/2020-February/018189.html Is everybody ok with this changes? [GeKo: Looks good to me] Statuses: GeKo: Last week: - getting up-to-speed for sbws review/work - making scripts for better bad relay rejecting available to others (see: #33182) - more work on #32672 - feedback reviews This week: - more sbws work - looking at the bridges situation for #32672 - resume work on #32864 and maybe start improving Arthur's exit scanning (#33179) - feedback reviews - look at ggus' Tor legal questions pad - maybe pick up #33009 gus: Last week: - Contacted relay operators from Latin America. Some of them replied and updated their relays. - Worked on EFF Legal FAQ - this is ready - https://pad.riseup.net/p/tor-legal-questions-keep This week: - Start to contact relay organizations so we can share our census form. - Send our commenets about EFF Legal FAQ to EFF. juga: Last week: - Worked on #30899 include the commit hash in the sbws version - Revised #30196 Add the tor version to the sbws bandwidth file header - Started #30726 Missing relay keys in bandwidth file spec Next week: - Continue with #30726 Missing relay keys in bandwidth file spec - Continue with Revised #30196 Add the tor version to the sbws bandwidth file header - Continue with #30735 Work out which relays are ignored by all sbws instances - Introduce sbws to gk? Georg

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project March 2020