tor-project June 2020

tor-project@lists.torproject.org

19 participants
34 discussions

Anti-censorship team monthly report: May 2020
by Philipp Winter 01 Jun '20

01 Jun '20

Hi all, Here's what the anti-censorship team has been up to in May 2020: Snowflake ========= * Tor Browser 9.5a13, released on May 22, has a major usability improvement in Snowflake that makes it possible to migrate a connection to a new temporary proxy when the one you are using goes offline. This makes it more likely that a Snowflake connection will work in the first place, and lets Snowflake be used for a longer time. <https://blog.torproject.org/new-release-tor-browser-95a13> <https://bugs.torproject.org/34043> * Started a GSoC project to implement an Android Snowflake proxy app. <https://trac.torproject.org/projects/tor/wiki/doc/SnowflakeProxyAndroid> * Started implementing workarounds for NAT incompatibility between snowflake proxies and clients. <https://bugs.torproject.org/34129> * Implemented Android reproducible build of snowflake clients. <https://bugs.torproject.org/28672> * Fixed a bug that resulted in Chrome proxies hanging. <https://bugs.torproject.org/31278> GetTor ====== * Fixed a problem where GetTor got into an infinite email loop with other autoresponders. <https://bugs.torproject.org/34286> * Fixed some bugs in the GetTor twitter responder, bringing it closer to being fixed. <https://bugs.torproject.org/27330> BridgeDB ======== * Made steady progress on wolpertinger, which helps BridgeDB build a feedback loop with OONI (and potentially other censorship measurement platforms). OONI finished its part of the implementation, and can now request bridges from wolpertinger's API. Wolpertinger then fetches OONI's test results from its S3 bucket and writes them back to BridgeDB's SQLite database. <https://bugs.torproject.org/32740> <https://gitlab.torproject.org/tpo/anti-censorship/wolpertinger> * Summarised plans for BridgeDB's future: <https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000096…> * Wrote a blog post on our most recent BridgeDB 0.10.1 release: <https://blog.torproject.org/new-release-bridgedb-010-1> * Finished monitoring tool that periodically sends email to BridgeDB's autoresponder to make sure that it's still working. <https://bugs.torproject.org/12802> * Removed "chatspeak" references across BridgeDB's UI. <https://bugs.torproject.org/31528> * Extended BridgeDB's minimalistic SQL table for blocked bridges. <https://bugs.torproject.org/34154> * Updated BridgeDB's user interface with the latest translations from Transifex. Thanks to everyone who helped translate BridgeDB to different languages! * Fixed a bug that would break BridgeDB's email autoresponder after a while. <https://bugs.torproject.org/33945> Miscellaneous ============= * Set up a monit instance that now monitors our anti-censorship infrastructure. Outage alerts are sent to the anti-censorship-alerts mailing list. <https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration> <https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-alerts> * Updated our bridge setup guide for docker after a user pointed out an issue. <https://community.torproject.org/relay/setup/bridge/docker/>

1 0

Sponsor 38 update (Shadow simulator)
by Jim Newsome 01 Jun '20

01 Jun '20

Sponsor 38: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor38 We've been primarily focused on prototyping the new process-based simulation architecture https://github.com/shadow/shadow/milestone/16: - General libc + syscall interposition plumbing is fairly stable now, including marshaling pointer arguments across the Shadow/Plugin process boundary, in both the ptrace and the LD_PRELOAD interposition mechanisms. - Settled on a logging design and implemented it. In particular we needed to address the problem of logging from our "shim" code that's LD_PRELOADed into the plugin's process. Since it's no longer in Shadow's process, we can't directly use Shadow's logger, which references internal Shadow data structures and in-memory queues. To further complicate things, some code runs both inside Shadow and inside the LD_PRELOADed library, and that code should use Shadow's logger when and only when running inside Shadow. We developed a simple plugabble logger that writes to stdout by default, uses Shadow's logging when running inside Shadow, and a "shim logger" when running inside the LD_PRELOADed shim. This also allows us to use the same logging API inside tests and support libraries. - We've gotten more syscalls and parts of libc implemented, including syscalls from unistd.h and most of the socket.h syscalls. These are the basic interfaces used by almost every network program to handle communication and file descriptor i/o. We are nearly ready to start running some multi-process networking benchmarks. We've also made some general improvements on the public Shadow branch https://github.com/shadow/shadow/pulls?page=2&q=is%3Apr+is%3Aclosed+updated…: - Added both debug and release builds to our continuous integration test matrix, helping us catch more bugs before they get merged. - Got rid of the monolithic shadow.h header, substantially speeding up incremental builds, and improving compatibility with code analysis tools. - Documentation cleanup and additions, including adding contributor guidelines. - Reduced flakiness in multi-process networking tests by moving away from hard-coded server ports. - Added additional integration tests to cover functionality being implemented in the new process-based model. - Migrated from Python 2 to 3. We also spent some time strategizing about how to use Github "milestones" and "issues" to help us plan and prioritize development work and to keep the community updated on our progress. We are still in the early stages and hope to make more effective use of these planning tools over time. Finally, we're thrilled to welcome Steve Engler to the project. Steve is starting today: Monday, June 1.

1 0

s58 - Tor Browser Security, Performance, & Usability Improvements
by Gaba 01 Jun '20

01 Jun '20

Hi! We are meeting every Monday to sync on the work that we are doing to migrate TB from Fennect o Fenix. You can read more about it at https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 Meetings are on Mondays at 18UTC. Next one is on June 8th. The meeting pad is https://pad.riseup.net/p/_kbebKhZvNcUuqxQL5NV The notes from June 1st were: Agenda Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… Look at what people need help with. https://trac.torproject.org/projects/tor/ticket/33658 Status updates: Name: What did you do last week? Anything anybody is block on? What is the plan for this week? Mike: Last week - 5/18: - Realized beta branch for FF78 had not happened until today; redoing diff - Internal priorities discussion Blocking: - Was blocked on FF78 beta branch (delayed?) but it is branched not This week - 6/01: - gecko-dev proxy audit - metrics meeting GeKo: Last two weeks: - tntegrated geckoview into android-compnents in tor-browser-build * still fighting and dealing with issues regarding backout of parts, our potential build target for the beginning etc. - moar review of 33533 Blocking: - decisions for #33939 This week: - test newly rebased patches for mozilla-beta - more testing of gckoview integration into android-components - starting with application-services integration into tor-browser-build - review of acat's rebase work sysrqb: Last week: A little work/progress on #33939: Decide which components of Fenix to rip out, disable, or use Mostly release prep for 9.5 and 10.0a1 This week: More #33939 Create branches for tor-browser-build and (maybe) torbutton Review patches for tbb tests and testsuite Review 9.5 release docs acat: Last weeks: - Fixed intermittent tests for https://bugzilla.mozilla.org/show_bug.cgi?id=1636411 (network.dns.disabled pref) - Built tbb-9.5a13-build2. - Verified fix for https://github.com/EFForg/https-everywhere/issues/19207. - Reviewed Onion-Location docs (https://gitlab.torproject.org/tpo/web/manual/-/merge_requests/1, https://gitlab.torproject.org/tpo/web/support/-/merge_requests/14 and https://github.com/torproject/support/pull/136). - Investigated/tested #34305: NoScript inconsistent behaviour in Firefox 77 - Experimented with running our tests (tbb-tests) in try: #33791. This week: - Rebase (and possibly fix) patches to ESR78 beta. - Try to uplift #33960 (Uplift patch for "32414: Make Services.search.addEngine obey FPI") - Maybe continue with #33791: Evaluate Firefox tests? -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network meeting notes, 1st June 2020
by Gaba 01 Jun '20

01 Jun '20

Hi! Network meetings are still happening every Monday at 1700UTC on #tor-meeting in irc.oftc.net We had a meeting on June 1st and here are the logs and notes. log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-01-17.00.log… pad: https://pad.riseup.net/p/tor-netteam-2020.1-keep Content of the meeting pad: == Network meeting pad! == Next meeting is at Monday 1 June 1700 UTC on #tor-meeting on OFTC. June Schedule: * Monday 1 June 17:00 UTC * Monday 8 June 17:00 UTC * Monday 15 June 17:00 UTC Welcome to our meeting! We meet each month at: Mondays at 1700 UTC On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the tor-project mailing list archive for older notes.) 23 March: https://lists.torproject.org/pipermail/tor-project/2020-April/002804.html 1 April - 4 May: we skipped meetings while transitioning TPI == Stuff to do every week == Let's check and update our roadmap: What's done, and what's coming up? Any change? All the trac tickets for the roadmap are in the team's page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam S27 - Asn & Dgoulet - ends at the end of May S28 & S30 - Continue after October - Ahf S55 - Nickm S69 - Nickm - ends at the end of May Non sponsor stuff DoS defenses = Dgoulet + Asn Library Size reduction = Ahf + Dgoulet sbws = Ahf + Juga Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Go over our 0.4.4 status page at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… . (If maint-0.4.4 were released as stable tomorrow, what would we regret?) == 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. * Check other's people call for help in their entries. Volunteers need help. Please help them when you are around. Maybe we should have times of day when different people are responders, and expectations of who helps. ------------------------------- ---- 1 June 2020 ------------------------------- == Announcements [please date] == == Discussion [please date] == [June 1st] Who is taking the s55 tickets owned by teor? - nick and david https://trac.torproject.org/projects/tor/query?owner=~teor&status=accepted&… - What to do with proposals? - discuss each one in Monday meetings. === Active Proposed Policies === * Pull Request Guidelines (stalled) === Design proposals under discussion === 315: require more fields in directory documents (still waiting [6/1]) 316: flashflow (asn and nickm are reviewing, should schedule discussion with pastly. [5/18]) 317: dns (under discussion on ML [5/18]) 318: limit protovers (waiting for more commment; needs discussion [6/1]) 319: wide everything (nick replied on ml; waiting for more discussion [6/1]) 320: tap out again - Do we have a consensus to replace this with a "deprecate v2 onion services" proposal? If so, who writes it? [6/1] protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18]) 321: happy families (need feedback [6/1]) 322: dirport linkspec (need feedback [6/1]) == Recommended links == == Updates == 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 25 May (planned): - Actually taking monday holiday off; brain is fried and a day might help me. - Finish walking onions proposal; last week. - review and merge in general - FINALLY read and reply to prop316? - Try to make a plan for protovers? Week of 25 May (actual): - Finished walking onions proposal - Review and merge a bit. - Respond wrt other proposals - Send out proposals 321 and 322. Week of 1 Jun (planned): - Send out walking onions proposal once copy-edit is done. - Ramp on on S55. - Catch up on all emails - Catch up with all review/merge - Finish triage! - look at jenkins status - can I fix coverity? if not, open a ticket. - opine on gitlab/trac stuff - advance proposal discussions - summarize code-format status, ask for team decision. ahf (afk today due to public holiday): Week of 25/05 planned: - Look into how we can start + connect to the Tor process in Fenix. - Onion-Location docs. - Get merging to tor.git. Week of 25/5 actually: - Fenix and OrbotService integration. - Onion-Location docs with Anto. Week of 1/6 planned: - Gitlab session at all hands. - Continued Fenix work. asn: Week of 25/05 (actual): - Network team work (reviews / merges / ticket work) - Catching up with email backlog. - Some work on token stuff. - Rebooting PoW work. - Spent time taking care of a personal bureaucracy. Done with this phase; will have some more to do in 10 days. Week of 01/06 (planned): - More work on PoW. - More network team work. jnewsome: Week of May 4 (actual): - Some LD_PRELOAD behavior investigation to guide shadow-Phantom design decisions - Added more tests covering next-to-be-implemented shadow-Phantom syscalls - Mentored/reviewed a volunteer PR - Kickoff OnionPerf meeting Week of May 11 (planned): - Start digging into OnionPerf - Start familiarizing myself with Shadow *usage* for Tor simulations - tor-project@ Shadow update email Week of May 11 (actual): - Worked on improving Shadow logging framework - Helped volunteer get their PR to improve tests into mergeable shape and merged - Started poking at OnionPerf Week of May 18 (planned): - tor-project@ shadow update email - finish logging improvement PR - More digging into OnionPerf. #33974: update to tgen 1.0 \o/ pastly: Week of 18 May (planned): - Finish bones of external FlashFlow repo (python?) to control tor clients that perform FF measurements - Finish bones of little-t tor changes s.t. measurement can be performed - Discuss FlashFlow with network team devs as they have questions c: Week of May 25 (planned): - close up work on #33609 - get started on other s55 tickets, potentially knock out 'easy' ones first and take it from there - update https://trac.torproject.org/projects/tor/wiki/doc/gsoc with my information -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project June 2020