- tor-project - lists.torproject.org

Network Team Meeting Notes, 4 December 2019
by Alexander Færøy 09 Dec '19

09 Dec '19

Hello, Here is a short summary of the network team meeting from Wednesday the 4th of December 2019. 1) We started out by looking at the 0.4.2 status page on Trac to see how we are doing there. We discussed whether to release soon, since 0.4.2 is supposed to be stable the 15th of December. 2) We went over our Kanban board. 3) We went over our review queue. 4) We discussed upcoming releases. Both the 0.4.2 release, but also stable releases. We went over some tickets that might need to be backported. 5) 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-12-04-22.59.html Below are the contents of our meeting pad: gaba: (updated on December 4th) Last week (actual): s31 report (we want to send it on Friday) sV painfull report DRL implementers meeting grants proposals This week (planned): hopefully preparing roadmap activities (way behind this... sorry!) will be afk tuesday & wednesday next week sV report 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: - Check gitlab migration - 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 x2 - post-0.4.2.4-rc backports - Draft s31 report: relay/dirauth modules, tooling, and testing (Deadline: 30 Nov) - Meeting Times proposal - Check gitlab migration Roadmap: - Sponsor 31 modularisation: - Modularisation dependency tooling (#32522) - Sponsor 31 code reviews - consider clang -std=gnu99 in Travis for better C99 portability #32500 Other: - Bug fixes, doc fixes, ticket triage quick reviews, and merges - Updating CI dependencies - Python 3 upgrades Nick: 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()) Week of 25 November (actual): - Review and merge - blog comments - S31 writeup stuff - Various bugfixes - Wrote/edited blog post for giving tuesday. - Helped with walking onions proposal - Code style/quality work. Week of 2 December (planned): - Various documentation/fundraising writing - blog comments - PETS bidding - Fix needs_revision branches - Dirauth configuration isolation (32139) - C style work - Prep for stable releases, TBD Mike: 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 - Finish cleaning up circpad simulator Since 25 November (actual): - Some circpad simulator review + cleanup; a little bit more remains - Caught up on mail - Follow-up + summary of scalability meeting; related researcher mails - Updated and filed circpad bugs; some more triage + documentation remains - Brainstormed options for explicit congestion control; have some candidates - Wrote blog post draft for Website Oracles paper Week of 2 December (planned): - Update circpad docs - File DNS cache mitigation ticket for Website Oracles paper; show it to Tobias - Clear out circpad simulator TODO and review python code Need help with/at risk of dropping this month: - Deep-thought-required research project followup - (Google masque, BGP, ECN, Dennis's Mozilla video, etc etc...) catalyst: week of 11/25 (2019-W48) (planned): - public holiday 11/28 - reviews - sponsor31 wrap up - more follow up about C style stuff week of 11/25 (2019-W48) (actual): - public holiday 11/28 - some feedback to swati re gsod stuff - reviewed #32500 -- took a while to chase down origins of some "impossible" behavior - looked at #32629 - sponsor31 wrap up documentation week of 12/02 (2019-W49) (planned): - sponsor31 wrap up documentation (#32206, #32208) - reviews - more follow up about C style - GSoD stuff as needed asn: 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. Week of 25/11 (actual): - Lots of core onionbalance work. I have a dirty branch that can: - Create an onionbalance configuration file and parse it - Fetch v3 descriptors from the instances - Collect intro points and re-certify them (switch the certificates) - Upload v3 descriptors for the service instance. - Branch can be found here: https://github.com/asn-d6/onionbalance/tree/v3_dev_wip - Worked on client auth control port stuff: - Implemented permanent ONION_CLIENT_AUTH_ADD credentials for mcs (#32562) - Fixed bug that came out of this (#32667) - Implemented some more functionality for the VIEW command for mcs (#30381) - Started a [tor-dev] thread about a new requested HS anti-DoS feature: https://lists.torproject.org/pipermail/tor-dev/2019-December/014097.html Week of 04/11 (planned): - Still lots of work to be done with onionbalance. This week will be spent in making sure that little-t-tor and onionbalance compute the same hash ring. And also starting to do descriptor rotation etc. And maybe making onionbalance work over chutney. ahf: 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 Week of 25 November (actually): - Shadow Dev Hire continued. We are making progress. - Got lots of feedback from a lot of people in different teams and external contributors about issues with our migration, which needs to be fixed. - Spend some time looking into the 503 PR issue on GL with Hiro. - Talked with Hans about using GL Runners to build HTML versions of torspec.git #32627 Week of 2 December (planned): - Lots of phone interviews. - Trying to back back on track with S28. - Follow up on all the feedback we have gotten about Gitlab. - Worked a bit on a "proposal" on issues with Tor's DNS subsystem. - Got a bit involved with #32604 (Thanks Tim for the big writeup there!) 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

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

Metrics Team Meeting Notes, November 29th 2019 [includes last week releases]
by Gaba 29 Nov '19

29 Nov '19

Next meeting: *Thursday*, December 5th, 15 UTC Hi! We had our meeting on Friday November 29th (it had to be rescheduled this week). Pad for the meeting: https://nc.torproject.net/s/Znd4MkHebAznEgA Meeting Log: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-11-29-15.01.log… Agenda and Notes: collector disk space, and unreliable physical host (irl) irl asks for the disk space to be doubled: #32644 "metrics-team" keyword on IRC (karsten) we'll think about this more and make a decision next week. Pending reviews (karsten) Onionoo backends (karsten) irl asks for another backend host for onionoo-backend-02, and we keep onionoo-backend-01; we also turn off the webservers on omeiense and oo-hetzner-03 once the two new backends are running. irl and karsten are meeting on Tue, Dec 3, 15:00 UTC to set up the new backends. Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap [announcement] we are testing phase of migration to gitlab - it would be good to get people to check for possible problems https://pad.riseup.net/p/gitlab-migration-problems Releases last week: #32635: Release Onionoo 7.0-1.22.0 Interesting links: Network Traffic Measurement and Analysis Conference https://tma.ifip.org/2020/call-for-papers/ -- 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

Gitlab Ticket Migration: Help Needed
by Alexander Færøy 29 Nov '19

29 Nov '19

Hello! We are moving into the final phase of testing out our migration tool for Trac tickets to Gitlab issues. We have managed to do a "complete run" where we have taken every ticket from Trac and turned it into a Gitlab issue on our https://dip.torproject.org/ Gitlab instance. All the converted Gitlab tickets can be found at https://dip.torproject.org/ahf-admin/legacy-20/issues/ and have the same Ticket ID as on Trac. But we are not done yet. We have discovered a few formatting issues with the conversion from the Trac markup language to the Markdown markup that Gitlab uses, but that might not be everything that is wrong, but we need help with discovering the rest. Gaba have created a pad at https://pad.riseup.net/p/gitlab-migration-problems where people can report issues on specific tickets in the bottom of the pad. It would be very useful for us, if people could spend some time going over some complicated tickets they have been involved with in the past and look for the following issues: 1. Is there any loss of information: is any information from Trac *not* being converted in the Gitlab issue. Right now we are missing some information such as assignee, estimated points, and actual points. We also don't change the author of the ticket and comments right now, as that would generate too many notifications for people who are using Gitlab today. 2. Is there any formatting issues? Right now we know of at least two "classes" of formatting issues, namely an issue around {{{ }}} (code blocks) and == Title == (headlines). But we do expect to find more. Please help us out by spending a few minutes going over some of your favorite tickets and look for issues and note them down in the pad. Please describe the issue as well as possible, such that it will be easy for us to spot what the issue is and hopefully make a fix in the Ticket converter tool :-) Thank you! All the best, Alex. -- Alexander Færøy

1 1

Tor Browser Release meeting: Wednesday 27th November @ 19UTC
by Pili Guerra 27 Nov '19

27 Nov '19

Hi everyone, Please join us for the Tor Browser release meeting this week on Wednesday 27th November at 19UTC. 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

2 1