December 2019 - tor-project - lists.torproject.org

Anti-censorship meeting notes, 5 Dec 2019
by Philipp Winter 06 Dec '19

06 Dec '19

Here's our meeting log: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-12-05-18.00.html And here's our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday December 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. * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * 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 --------------------------- --- 5th December 2019 --- --------------------------- == Announcements == * == Discussion == * Let's talk about how we choose future STUN servers * https://bugs.torproject.org/30579 * Concerns voiced at https://trac.torproject.org/projects/tor/ticket/32597#comment:6 * Alternative strategy: https://bugs.torproject.org/25591 * Iran Internet shutdown "post mortem" * What should we have done differently? * How can we be better prepared next time? * Have a DNS based transport that works with recursive ISP-resolvers? (there's a lot of talk about iodine https://github.com/yarrick/iodine in the ooni channels) * other DNS tunnels: https://trac.torproject.org/projects/tor/wiki/doc/DnsPluggableTransport/Sur… * Gettor workflow while gitlab doesn't accept pull requests (I still didn't have time to look at that but I will look it up nextt week. --gaba) * wrt to the migration we are gathering problems here: https://pad.riseup.net/p/gitlab-migration-problems * Snowflake seems to be partially blocked in China (see #32657 and #32597) * Can we get permissions to add/modify nagios monitoring targests ourselves? * This would remove friction and alleviate load on our admins * #30946 (port bridgedb to python3) should be on our roadmap * python2's EOL is on january 1 * Emerald onion has some spare capacity and can help us out * Do we want anything snowflake-related? More proxy-go instances? == Actions == * Please add your work to our monthly report! * https://pad.riseup.net/p/bwskP7zCeW3TTxfg_O1C == Interesting links == * A guide to work with distributed teams: "When you’re running a distributed organization, assume that someone missed the email, message, announcement, or meeting." https://increment.com/teams/a-guide-to-distributed-teams/ == Updates == FORMAT! 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: 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 (2019-12-05): * Reviewed #32480, #31157, #32576 * Agreed to give a Tor presentation at my old college in Austria, during vacation in January * Lots of thinking about PT steering committee * We decided not to be a part of it * Improved obfs4 docker bridge (#31834) * Pushed new docker image 0.3 and announced it on tor-relays@ * There's already more in #32550 * Tested new default bridge from UMN; added default bridge from Georgetown; removed dgoulet's IPv6 default bridge * More work towards getting another data source for RACE, so we can study obfs4 in the wild * Filed #32622 for a better STATUS_CLIENT message in a specific case * Added a persistent cache to bridgestrap, so test results don't disappear after a restart * Testing is computationally expensive and BridgeDB's host seems underprovisioned * Reached out to UMass Amherst and UMich research groups to get scans of default bridges going * Reached out to noisebridge once again, in the hope that the default bridge sets 'bridgedistribution none' * The original maintainers are all gone :/ * Started porting BridgeDB to Python 3 * Will require lots of tedious work * Took a look at the spydermix system Next week: * Help with: * Gaba: (updated October 30th) Last week (): * grants writing This week (planned): * gitlab migration: look at issues and problems in gitlab. cecylia (cohosh): last updated 2019-12-05 Last (2) weeks: - fixed (wrote, merged, and deployed) a data race in the broker that was causing crashes (#32576) - merged and deployed collection of proxy type metrics (#31157) - finished snowflake test coverage (#29259 and #32300) - continued work on understanding snowflake health (#32545) - started investigating possible snowflake blocking in China (#32657) - read papers and made some progress on grant writing - worked on setting up some throughput tests for windows (#31971) - made more fixes to gettor script for releases (#32480) - updated web extension and web badge deployments with new translations and #31157 This week: - finish full draft of grant - continue on #29206 and #25723 - run some concrete tests for snowflake on windows (#31971) - update github gettor links (#32393) - revisit #31109 and see if there's more we need to do for that - work on snowflake test suites #25595 - continue snowflake health checks and looking at censorship in china (#32657) Help with: - review of #32300 and #29259 - gettor repo at https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor is still behind - can't make pull requests in gitlab still - permissions error for https://trac.torproject.org/projects/tor/ticket/31157#comment:14 arlolra: 2019-12-05 Last week: - add a build step / documentation for code reuse in cupcake #32499 Next week: - read up on turbo tunnel - pick a new task (#31902, #31201, #19026, ?) Help with: - review #32499 dcf: 2019-12-05 Last week: - helped debug a broker crash (#32576) - turbo tunnel in meek - noted some Gitlab migration issues at https://pad.riseup.net/p/gitlab-migration-problems - wrote a summary of the Conjure paper Next week: - decommission old broker (#32502) - turbo tunnel in meek Help with:

1 0

October and November 2019 report for the Tor Browser team
by Pili Guerra 06 Dec '19

06 Dec '19

Hi everyone! October saw the culmination of the team's hard work over the previous four months with the release of our first 9.0 stable release[1], based on ESR68. During October we made the following additional releases: Tor Browser 9.0a7 [2], 9.0a8 [3] and 9.5a1 [4]. With the 9.0 stable release we started our work towards tightly integrating Torbutton code into Tor Browser by moving the various different functionalities it provides to other, more intuitive locations. As such, you can now request a new identity from its own dedicated button on the toolbar, and configure Tor network settings, such as bridges and proxy configuration from their own dedicated Tor section within Tor Browser Preferences. We also increased the number of locales supported to 32 with the addition of Macedonian (mk) and Romanian (ro). During October we fixed all outstanding reproducible build issues in time for our stable release. However, although the 9.0 stable release build is bit for bit reproducible and we managed to get two matching builds, we have one remaining challenge to achieve consistent reproducibility as we occasionally get builds that differ. The full list of tickets closed by the Tor Browser team in October is accessible using the TorBrowserTeam201910[5] keyword in our bug tracker. In November we continued with the 68esr rebase and tying up loose ends from our first 9.0 stable release based on Firefox 68 ESR. The new letterboxing feature raised a lot of questions and issues so we continued working on bug fixes[6] on this feature and further improving the experience[7][8] for our users. We have also started picking up sponsor work once more, working on implementing Onion Services Client Authorization[9] and key storage[10] in Tor Browser. We have also been working on making it easier to access v3 onion services through the use of the Onion-Location header and have been working on a mechanism for the browser to prompt the user about onion service redirection when encountering an Onion-Location from a website[11]. In order to share these and other new features more quickly, we are working on providing automatic nightly builds[12]. This will allow us to have a faster path to share new and experimental features with users for dedicated user testing and rapid iteration. Looking ahead to 2020 and what the team wants to work on, a number of us have been working on a proposal to move away from the ESR train and onto the Firefox rapid release cycle, starting with the Tor Browser for Android transition to Fenix[13]. We would also like to take this opportunity to implement Enhanced Tracking Protection (ETP)[14] from Firefox for performance improvements, pending funding. We made two releases in November: 9.0.1[15] 9.5a2[16]. The full list of tickets closed by the Tor Browser team in November is accessible using the TorBrowserTeam201911[17] keyword in our bug tracker. We are still struggling with reproducibility issues[18] and will continue working on these during December. Additionally, we will close off the year by continuining to work on all outstanding November issues, including letterboxing work, sponsor work and automatic nightly updates. All tickets on our radar for December can be seen with the `TorBrowserTeam201912` keyword in our bug tracker.[19] [1] https://blog.torproject.org/new-release-tor-browser-90 <https://blog.torproject.org/new-release-tor-browser-90> [2] https://blog.torproject.org/new-release-tor-browser-90a8 <https://blog.torproject.org/new-release-tor-browser-90a8> [3] https://blog.torproject.org/new-release-tor-browser-90a8 <https://blog.torproject.org/new-release-tor-browser-90a8> [4] https://blog.torproject.org/new-release-tor-browser-95a1 <https://blog.torproject.org/new-release-tor-browser-95a1> [5] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… <https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB…> [6] https://trac.torproject.org/projects/tor/ticket/32308 <https://trac.torproject.org/projects/tor/ticket/32308> [7] https://trac.torproject.org/projects/tor/ticket/32220 <https://trac.torproject.org/projects/tor/ticket/32220> [8] https://trac.torproject.org/projects/tor/ticket/32325 <https://trac.torproject.org/projects/tor/ticket/32325> [9] https://trac.torproject.org/projects/tor/ticket/30237 <https://trac.torproject.org/projects/tor/ticket/30237> [10] https://trac.torproject.org/projects/tor/ticket/19757 <https://trac.torproject.org/projects/tor/ticket/19757> [11] https://trac.torproject.org/projects/tor/ticket/21952 <https://trac.torproject.org/projects/tor/ticket/21952> [12] https://trac.torproject.org/projects/tor/ticket/18867 <https://trac.torproject.org/projects/tor/ticket/18867> [13] https://github.com/mozilla-mobile/fenix <https://github.com/mozilla-mobile/fenix> [14] https://trac.torproject.org/projects/tor/ticket/30939 <https://trac.torproject.org/projects/tor/ticket/30939> [15] https://blog.torproject.org/new-release-tor-browser-901 <https://blog.torproject.org/new-release-tor-browser-901> [16] https://blog.torproject.org/new-release-tor-browser-95a2 <https://blog.torproject.org/new-release-tor-browser-95a2> [17] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… <https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB…> [18] https://trac.torproject.org/projects/tor/ticket/32053 <https://trac.torproject.org/projects/tor/ticket/32053> [19] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… <https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…>

1 0

Damian's Status Report - November 2019
by Damian Johnson 05 Dec '19

05 Dec '19

Hi all! Just a quick update on what I've been up to. Now that our HSv3 branch is finally wrapped up giving thought to what's next... https://blog.atagar.com/november2019/

1 0

The Tor Censorship Arms Race: The Next Chapter
by Roger Dingledine 04 Dec '19

04 Dec '19

Hi folks, The video from my Defcon 2019 talk ("The Tor Censorship Arms Race: The Next Chapter") is now up: https://blog.torproject.org/next-chapter-anti-censorship I'll be happy to answer questions about the talk, or about the censorship team in general, in the comments. --Roger

1 0

Network Team Meeting Notes, 25 November 2019
by Alexander Færøy 04 Dec '19

04 Dec '19

Hello, Here is a short summary of the network team meeting from Monday the 25th of November. Riseup's pad was being a bit sad last week, but it looks like my backup after the meeting was OK and was the same content when I used the time-slider on the pad :-) 1) We started out by looking at the 0.4.2 status page on Trac to see how we are doing there. 2) We went over our Kanban board. 3) We went over our review queue. 4) Alex made some announcements: please respond to Gaba's doodle and we need help looking at migrated Gitlab tickets. 5) We will begin doing interviews for the Shadow hire next week. Does anybody wanna listen in? 6) We decided not to do team meetings 23/12 and 30/12 of 2019. 7) Nobody had anything else to discuss. --- end of summary --- You can read today's network team meeting log at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-11-25-17.59.html Below are the contents of our meeting pad: gaba: (updated on november 18th) Last week (actual): s31 report This week (planned): grants proposal sponsors other reports due at the end of the month preparing for DRL implementers meeting in 2 weeks kickoff information gathering for coordinating a roadmap with almost no sponsors in december, january and february :) Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 18 November (planned): Take Time for: - Write relay/dirauth modules, tooling, and testing parts of s31 report (Deadline: 30 Nov?) - catching up on emails Roadmap: - Sponsor 31 modularisation: - Modularisation dependency tooling (#32522) - Do more modularisation (#31851 / #29211) - Sponsor 31 code reviews Other: - Bug fixes, ticket triage, and quick reviews Week of 18 November (actual): Take Time for: - catching up on emails Roadmap: - Sponsor 31 modularisation: - Modularisation dependency tooling (#32522) - Sponsor 31 code reviews Other: - Fixing work laptop Week of 25 November (planned): Take Time for: - Draft s31 report: relay/dirauth modules, tooling, and testing (Deadline: 30 Nov) - catching up on emails - post-0.4.2.4-rc backports Roadmap: - Sponsor 31 modularisation: - Modularisation dependency tooling (#32522) - Sponsor 31 code reviews Other: - Bug fixes, ticket triage, and quick reviews Week of 25 November (planned): Take Time for: - catching up on emails and IRC - post-0.4.2.4-rc backports Roadmap: - Sponsor 31 modularisation: - Modularisation dependency tooling (#32522) - Sponsor 31 code reviews Other: - Doc fixes, ticket triage, and quick reviews Nick: Week of 18 November (planned): - More documentation work. - Finish 32427 (refactor options_act_reversible). - 32139 (configuration isolation for directory authority options) - 32408 (refactor new options_act_reversible into new system.) - Regression analysis on 041-regression,042-regression tickets?? Week of 18 November (actual): - review and merge - Keep an eye on blog comments for 0.4.2.4-rc release post - Triaged my remaining 042 tickets - Identify hardware possibly donate for EOY campaign - Finish refactoring options_act_reversible() (32427) - Write paragraphs for S31 report - catch up on emails - Drop support for openssl <1.1.1 (31820) Week of 25 November (planned): - Short week due to US holiday. Not planning to be available Thursday through Sunday; please use signal if I'm needed. - Review and merge - Keep an eye on blog comments for 0.4.2.4-rc release post - analyze 0421/042 regressions, at last - List stuff I want to work on in December. - Any last-minute improvements needed for S31 wrapup. - Dirauth configuration isolation (32139) - Design for 32408 (migration path for options_act_reversible()) Mike: Since 6 November (planned): - Finish cleaning up circpad simulator - Read asn's research feedback - Get DNS recommendations for exit operators for fingerprinting blog post - Update + triage circpad bugs Since 6 November (actual): - Computer issues (mostly resolved) - Scalability meeting - Read+replied to asn's research feedback - Some review of circpad simulator - Last minute Mozilla all hands invite + booking Week of 25 November (planned): - Catch up on mail - Follow-up + summary of scalability meeting - Update, file, and triage circpad bugs - Document circpad simulator and new bugs/gotchas in circpad doc - Document intuition behind state machine choice in circpad doc Need help with/at risk of dropping this month: - Get DNS recommendations for exit operators for fingerprinting blog post - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) catalyst: week of 11/18 (2019-W47) (planned): - reviews - sponsor31 architecture doc stuff - GSoD stuff as needed week of 11/18 (2019-W47) (actual): - reviews - reviewing C reformatting output week of 11/25 (2019-W48) (planned): - public holiday 11/28 - reviews - sponsor31 wrap up - more follow up about C style stuff asn: Week of 18/11 (planned): - Review atagar's HSv3 descriptor encoding work. - Write test vectors for HSv3 descriptor encoding/decoding as stem support stabilizes. Week of 18/11 (actual): - Reviewed atagar's HSv3 descriptor encoding work (#31823). And went over a few revision rounds. Will be doing more revisions as onionbalance work proceeds. To make the actual test vectors I need to do some more onionbalance work (and in particular computing the right blinding parameters). - Implement permanent client auth credentials over the control port (#32563). More work than initially anticipated because of forward-compatibility issues and other stuff. - Triaged S27 tickets and did planning for future onion services work. - More post-OTF onion work. Week of 25/11 (planned): - Get back to onionbalance work (#31823 and #26768) - Do revisions as neede dfor the client auth control port work (#32563) - Continue S27 triaging. ahf: Week of 18 November (planned): - Shadow Simulation developer decisions/next step/interview questions - S28 tickets. - Friday is the "big day" for trying out a complete Gitlab migration to see if things go well - Catch up on things I missed to do last week. Week of 18 November (actually): - Lots of Shadow Dev stuff, but it is making progress. - Moved all tickets from Trac to Gitlab. Now begins the hunt for issues/information loss. - Spend quite a bit of time with Hiro trying to debug an issue with the Gitlab instance that leads to 503 issues. This is still ongoing. - Began re-writing some tests for #28930 Week of 25 November (planned): - Still some Shadow Dev stuff. - Follow up on Gitlab migration work with Gaba - Figure out the 503 issue on GL with Hiro - Test changes for #19327 dgoulet: Week of 18/11 (actual): - s27: #32546, #30381 (reviewed, merged), #32543. - s27: Revision on #32020 - s27: Meeting with asn, triage on all s27 tickets. - Worked on a test bed for the NetDev CFP submission. Week of 25/11 (planned): - Finalize s27-must ticket as much as possible. -- Alexander Færøy

1 0

www November 2019 report
by Hiro 04 Dec '19

04 Dec '19

What has happened in November in the Tor www world * A new language was launched on tpo! https://www.torproject.org/ca/ * Cleaned up databags in all the websites to have less issues with localizing menus and some content. * Went through a lot of localization issues. * New training materials to the community portal/training * We are trying a review/merge workflow that can be helpful and not a stopper. * Started working on planning for dev.tp.o: https://gitweb.torproject.org/project/web/dev.git/ Meeting notes for November can be found: https://dip.torproject.org/torproject/web/www-meeting-notes/blob/master/201… This summary and past and future ones can be accessed online: https://dip.torproject.org/torproject/web/www-monthly

1 0