- tor-project - lists.torproject.org

Changes to the Tor Exit List service
by Iain Learmonth 09 Mar '20

09 Mar '20

Hi, We will shortly be decommissioning the server that ran TorDNSEL and Tor Check until now. The TorDNSEL software will be replaced on the new server with software we will be able to more easily maintain going forward. Service operators using the Tor Exit List service may need to take action to avoid service interruption, details are contained later in this post. ## For exit relay operators: The primary change that comes with the new software is that exit policies are no longer considered when deciding if an IP address is to be included in the list. If we have observed an exit relay using an IP address through our active measurements, this will be listed as an exit relay in the new service regardless of the exit policy. For exit relay operators that also route their own traffic via their exit relay's IP address and have exit policies specifically to deny access to services that block Tor traffic, such that those services will allow you to connect without Tor, this will no longer work. We recommend using a dedicated IP address for your exit relay. That allows your ISP to more easily recognize that abuse complaints and DMCA notices can be forwarded to you to be quickly responded to with a boilerplate response, as opposed to cutting off your Internet access or providing your personal information to the copyright cartels. ## For service operators: Depending on how you obtain exit address information, you may need to take action to avoid service interruption. If you are using CollecTor or Onionoo, these interfaces will remain unchanged and are already compatible with the new setup. If you are using the DNS exit list service or the bulk exit list exporter then you may need to make changes. ### DNS exit list The good news is that this service now behaves closer to a typical DNS-based list service and so it may be easier to integrate into your use-case now, and no longer require a custom implementation. The old DNS exit list would have lookups that look like: <reverse client ip>.<server port>.<reverse server ip>.ip-port.exitlist.torproject.org For services that are accessed via multiple IP addresses, e.g. IRC networks with multiple servers or websites behind load balancers, this leads to service operators needing to perform multiple lookups in order to have confidence that an IP address is not an exit relay. Instead, services can now use this simplified service: <reverse client ip>.dnsel.torproject.org, just like other DNS list services (https://en.wikipedia.org/wiki/Domain_Name_System-based_Blackhole_List ). If a client IP address is a Tor exit relay, the service will return with an A record of 127.0.0.2. You'll also be able to look up a TXT record with the fingerprint of the relay to learn more about the individual relay. Note that some IP addresses are shared between multiple exit relays, they will still only have one A record but may have multiple TXT records, one for each fingerprint. If an IP address is not known in the Tor network, the response will contain a NXDOMAIN (no such domain) status. For example: ------------------------------------------------------------------------ $ dig +noall +comments +answer 199.72.247.162.dnsel.torproject.org ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46707 199.72.247.162.dnsel.torproject.org. 1080 IN A 127.0.0.2 ------------------------------------------------------------------------ $ dig +noall +comments +answer 199.72.247.162.dnsel.torproject.org txt ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29451 199.72.247.162.dnsel.torproject.org. 1095 IN TXT "B34CC9056250847D1980F08285B01CF0B718C0B6" ------------------------------------------------------------------------ dig +noall +comments +answer 198.81.40.188.dnsel.torproject.org txt ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2678 ------------------------------------------------------------------------ *The old DNS exit list service will be turned off on the 1st April 2020. Please ensure you have updated to the new service before this time.* ### Bulk exit list changes The bulk exit list exporter also used to consider exit policies, but will now return all exit relay IP addresses regardless of the query made. You should not need to make any modifications if you are using this service but you may find that you can remove some complexity from your client if you were filtering by service before. You can fetch a list of all exit IP addresses seen from: https://check.torproject.org/torbulkexitlist This list is updated at most once every 40 minutes depending on the number of exit relays in the network at the time, fetching it every hour would be reasonable. Thanks, Iain.

1 0

Network Team Meeting Time Changes
by Alexander Færøy 09 Mar '20

09 Mar '20

Hello all, The US have moved from Standard Time to Daylight Time and we have updated the meeting times for the weekly network team meetings. Please see an updated list at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam All the best, Alex. -- Alexander Færøy

1 0

Notes from Vegas Meeting MARCH 5 2020
by Erin Wyatt 06 Mar '20

06 Mar '20

Vegas Team Meeting Notes March 5 2020: + NEW BUSINESS - Should we cancel or reschedule the NY gathering from April or not? Resolution: Maybe we'll move it to May and hope for the best. - SVN people SVN! Can we move it to nextcloud? Resolution: tl;dr: we’ll keep it for now. + GENERAL NOTES Georg 1. Network health work 2. Alex's and my talk at foss-north got accepted (https://foss-north.se/2020/schedule.html#slot19) yay! Antonela 1. Donation flow changes in www and tor browser 2. S27 is almost done 3. Slowly starting with S30 4. End of the month duties 5. Sent peer-feedback 6. Writing onion browser review 7. Reviewing OTF Learning Lab work Anarcat 1. more work on libvirt/ganeti migration (#33085) 2. more work on check.tpo replacement 3. peer feedback work 4. taxes form wrangling 5. more gitlab patch review, hiro is finalizing the migration of the test instance to a new server right now! 6. znc irc bouncer debugging (#33483) 7. CiviCRM mail rate expansion monitoring (#33189) 8. more routine work (PGP key expiries, mail delivery problems #33413, etc) Roger 1. Mike: I told Jim Newsome that when you have your act together, you'll be reaching out to him to describe our use cases and wishlists and goals for what we want from Shadow. That way he can have them in mind as he makes Shadow improvements, and who knows maybe he'll even lead the activities you ask for. 2. I'm planning to not submit a Defcon talk this year, since "every other year" is a fine rate for me. I am imagining to submit a CCC talk instead (finally). If you have opinions, please help me think through what is best to submit. Gaba 1. Traveling: should we cancel or reschedule the NY gathering from April or not? 2. SVN people SVN! Can we move it to nextcloud? 3. Sponsor 30 check-in 4. Trac is up to date in my inbox 5. or library size reduction coordination 6. update time allocation usage 7. network team retrospective 8. peer feedback 9. gitlab follow up Alex: 0. I will not be at this meeting as I'm traveling home from a conference in the other side of DK at this time. 1. Feedback writing and making sure I have received everything from folks as it comes in. 2. Network Team retrospective went well. 3. Going to dive into our new Gitlab setup on Friday. 4. End of month tasks. 5. Talking about Tor today in Aarhus with the Danish engineering union and on Wednesday at the University College in Odense. 6. Some follow ups from 1:1's, but the team seems to be doing good. Steph 1. Finishing peer and self feedback 2. Catching up on DoH stuff so I feel more comfortable contributing. Matt and I will be talking about it more today so we can write a response. 3. Wrote an op-ed for Bitcoin Magazine 4. Newsletter went out Friday. GR did some testing and now it goes out in 3 hours and not 24. 5. Wrapped up Outreachy mentoring with annalee_! She completed projects of updating the press list and fixing blog tags. Submitted final feedback 6. Working with OTF learning lab on dark web demystifying. Also working internally to connect larger onion services goals. 7. Social media 8. Helping with NY event coordination Sarah 1. Moving ahead with details for San Francisco and NYC events while monitoring covid19 developments. 2. Peer feedback. 3. Grants team working on DRL and OTF proposals. 4. Taking over fundraising related tasks from Jon. isabela 1. 1st round of interview for ED assistant candidates (2nd round will be this coming week) 2. Reviewing proposals due this week (DRL Scalability work / DRL w/ tails and guardian project / OTF browser work) 3. continue to work on invites for EFF party and creating a plan b in case of covid-19 intervention :) 4. Writing self feedback 5. multiples 1:1 - including irl 1:1 w/ matt in nyc pili 1. End/Start of month maintenance tasks: Tor Browser february report, trac backlog review, etc... 2. S9 sync 3. Moving github sponsors forward 4. Dealing with GSoC queries and updating ideas list accordingly 5. DRL Proposal 6. OTF Proposal revisions 7. Applied to the Learning Lab to showcase new features from Onion Services project 8. Trying to figure out if we're going to have someone from Tor attending a writing sprint for an online digital security training course 9. Some work on the dev portal - Dev teams should expect a request for feedback in the next few weeks :) 10. Peer and self feedback 11. Tor Browser Release meeting this week ewyatt: 1. Reminder: all written feedback due tomorrow, March 6th (self, team lead, and peer) 2. Traveling, scrambling to get things together. I will be working remotely for most days (my time is on the AFK calendar) 3. Making progress on Exec Assistant recruiting 4. Still haven't gotten PTO's out, but it's still in top 3 spots on my list, hoping to get to it soon! 5. Contracts updates (still working on) Karsten: 1. Exit scanner transition almost complete. \o/ 2. Added dirbytes reported by dirauths (#33065), deployment still in progress. Mike: 1. Helping with DRL proposal 2. Working on employee feedback 3. Untangling a decade of Tor organizational dysfunction, so I can get back to fixing its technical dysfunction. Gus: 1. Reviewing Cleopatra's work (RT and documentation updates). Final feedback is due March 9. 2. Contacted partners that submitted proposals for our Tor Village and asked them if they want to be part of remote training program. 3. Traveling tonight for a workshop with journalists. 4. Submitted Tor activity to CryptoRave 5. Folks from a non-profit asked us if we can write a comment about strong encryption and human rights 6. Sponsor9 sync meeting 7. Still writing peer feedback 8. Outreachy: new contribution period starting today. We have two projects this round: https://trac.torproject.org/projects/tor/wiki/Outreachy 9. Reviewing DRL proposal. 10. Community Team is organizing a new Documentation Hackathon. plz open more tickets: https://lists.torproject.org/pipermail/tor-project/2020-March/002748.html Nick 1. Hoping for releases in 5-10 days. 2. Starting on walking onions writeup 3. Wrapping up feedback. I might be late, but not by more than a day or two 4. Went to event on decentralized web yesterday. Interesting people, but I might have gained more had I known which days other stuff was happening. I should learn from this. 5. NYC event- go or no go? Matt: 1. Collect team feedback 2. Moar Tor Browser releases 3. OTF Tor Browser proposal 4. (Beginning) W3C involvement 5. Conversation about engaging in IETF discussions around IP privacy \o/ 6. Writing peer feeback

1 0

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