March 2018 - tor-project - lists.torproject.org

No network team meetings this week
by Nick Mathewson 17 Mar '18

17 Mar '18

Hi! We're most of us likely to be traveling and/or recovering from travel this week. As such, let's not do our regular network team meeting times, and just check in day by day. Peace, -- Nick

1 0

Network team meeting notes, 5 March 2018
by Nick Mathewson 06 Mar '18

06 Mar '18

Hi! Network team meeting logs here: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-03-05-17.59.html Pad below: Network team meeting pad, 5 March 2018 Welcome to our meeting! Mondays at 1800 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Meeting notes from previous weeks: * https://lists.torproject.org/pipermail/tor-project/2018-January/date.html , search "network team" * https://lists.torproject.org/pipermail/tor-project/2018-February/001654.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001664.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001671.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001674.html Old Announcements: * 0.3.3.x is in feature-freeze. No new features (except for #24902, which has permission.). * Please, work on bugfixes! It would be great to have this release release on time. (Planned date is 15 April) * Please fill in the code subsystems spreadsheet at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Please fill in Isabela's heat-mapping exercise with areas of tor work: what are our priorities? https://pad.riseup.net/p/38VbTZUIzG4X * Team rotation roles are open for March. teor also added "Frontline Support", which they can do most of the time. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… Announcements: * Review-group-34 is now open, incorporating what is left of groups 32 and 33. https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * There are 39 tickets in review-group-34-- mostly because a lot of tickets from Tor:unspecified are pulled in. Let's try to resolve those rather than just throwing them all back. * There are 23 tickets in 033-must: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~033… . Please grab some that you can fix, * Rome coming up! If you're there for the team days, our first (net team only) meeting is ______________ at ________. * If you are around and want to help with it (this is optional!) you can join people from the team from around 3pm to 5pm on March 9th to finsih up organizing tasks for 6 months roadmap (the work on To Do that I [isabela] wrote) THINGS TO DO: * Review tickets in review-group-34. * Fix things in 033-must. * Fill out the various areas/roles/subsystems spreadsheets, if you have not done so already. * Get some rest; take care of yourselves on the way to Rome! * If you doing work related to a sponsor open this pad: https://storm.torproject.org/shared/-p-gQvABCmlABNLLWFCe77RoN9e9AAeOux532lu… * I (isabela) need your help on defining and list the work we will actually do for the next 6 months on each sponsor deliverable * Please check the sponsor8 Activity O2.3 in that pad - the list created by nick and ahf is more or less the type of list I am looking to have for the other sponsors. * For all NSF grants I added the stuff Roger wrote about what we will do next on the last report we sent the sponsor. That is there for reference. I need the people who are working in those areas to look at it and organize what work should be done for the next months, a bullet point list should be enough. * After the list of work is done for each sponsor, I will ask you to add the tickets related to that work * End goal here is to have this done so at the 6 months roadmap planning meeting we are just assigning work and organizing it in the timeline Discussion: * * US DST changes over while we're in Rome. we might want to figure out whose DST we're going to track for meeting times [catalyst] * are we doing any more planning for the pre-meeting hackfest on 3/10? [catalyst] ==== Updates: Nick: * Last week: - Jury duty consumed most of my time Tue->Fri. - Released 0.2.9.15, 0.3.1.10, 0.3.2.10, 0.3.3.3-alpha. - Tried to catch up with answering tickets and email. - A little planning for rome. - Opened several tickets for improved wakeup/timeout handling: * 25373 * 25374 * 25375 * 25376 * 25377 * This week: - Fix as many 033-must issues as I can - Grab and/or drop 034 tickets as I can - Prep for rome meetings - Travel to rome - Enjoy a little time in rome before the meeting starts pastly (50%+ offline for meeting): tl;dr: I'm talking to my coworkers about finding time and rationalizing funding for working on the torflow/bwauth problem. Working idea is currently to make something simplier than peerflow but still better than what Tor currently has. We/I will be attending the related sessions in Rome. Once we decide if/when I can work on this, I'll stay in communication with the network-team about progress and implementation details so that the transition will go even more smoothly than KIST's ahf Last week: Sponsor 8: - Roadmap document with Isa. - Wrote a patch to add a StatsReporter subsystem in Tor that can emit internal stats to external services for my phone: https://gitlab.com/ahf/tor/commit/96a1eb1dce3a82572dc09ad018955b34c47d0bb0 Misc: - Landed small patch for #25378 - Participated in PT meeting. - More messing around with PT/Windows code. - Setup a relay on a host to try the statsreporter code in a relay-setting. This week: - Get the StatsReporter code in a shape where it can be reviewed by others. - Prepare for Rome meeting and travel to Rome: - Finish Windows/PT project to demo for PT people in Rome. - See if I have overlooked any documents/roadmapping tasks before Rome. - Book Seattle meeting flights. catalyst: last week (2018-W09): - make it easier to allow Travis builds to fail silently if necessary (#25388) - Rome meeting and Seattle hackfest logistics (more time-consuming and annoying than usual because reasons) - roadmappy stuff this week (2018-W10): - more meeting prep - more roadmappy stuff - May/June hackfest logistics - Rome meeting - CoC and SoV feedback as needed Mike: Last week: - Went through controller bw events, wrote a patch for CIRC_BW (#25400) - Implemented bandwidth-based side-channel detection for vanguards This week: - Rome & travel isabela: last week - worked with nick on organizing some stuff at the pad (above at todo part) this week - at iff - trying to get as much done before rome. isis: last week: - reviewed #25268 and tested/attempted to reproduce #3940 - wrote unittests for some things in circuitbuild.c and bridges.c that were not tested - reviewed and cleaned up the rust logging code #23881 - got a working sha2 wrapper in Rust (around our C) code, but there's still linking issues #24659 - added some cleanups to the crypto.c refactor #23658 - looked into some other issues with rust builds #25341 this week: - book stuff for may hackfest - pre-roadmapping planning/organisation - review #25386 which claims to fix my linker issues for #24659 -

1 0

February 2018 report for the Tor Browser team
by Georg Koppen 06 Mar '18

06 Mar '18

Hi all! Just a short update on what the Tor Browser team worked with in February and what we are up to in March. We made an alpha release, Tor Browser 8.0a2[1], containing a new Tor alpha (0.3.3.2-alpha) and a bunch of updates to other components (Torbutton, Tor Launcher, HTTPS Everywhere, and NoScript). Apart from that we worked on fixing up Moat which allows receiving bridges from BridgeDB using the meek pluggable transport.[2] It will be available in the next alpha which is scheduled for next week for further testing. Moreover, almost all of our remaining time got spent on upstreaming as many patches as possible to Mozilla as the merge window for the next Firefox ESR (60) is closing next week. We spent time on updating our toolchains as well.[3][4][5] On the mobile side we are close to have the Orfox patches merged into our tor-browser.git repository[6] and both Tor Launcher and Torbutton integrated into it as well.[7][8] That's a first step in providing their functionality to Android users, too. The full list of tickets closed by the Tor Browser team in February is accessible using the `TorBrowserTeam201802` keyword in our bug tracker.[9] In March we hope to make further progress on patch uplifting and toolchain updates, and we will be at the dev meeting to plan for the next six months including the Tor Browser 8 release. We hope to get back to our user interface improvements which are still in the pipeline (e.g. circuit display updates[10]) while starting the countdown for Tor Browser 8 preparations: that includes finishing the rebase of our remaining patches to ESR 60 and writing new patches to address compatibility requirements and new "features" coming with the new Firefox version. All tickets on our radar for this month can be seen with the `TorBrowserTeam201803` keyword in our bug tracker.[11] [1] https://blog.torproject.org/tor-browser-80a2-released [2] https://bugs.torproject.org/23136 [3] https://bugs.torproject.org/16472 [4] https://bugs.torproject.org/25304 [5] https://bugs.torproject.org/21777 [6] https://bugs.torproject.org/19675 [7] https://bugs.torproject.org/25013 [8] https://bugs.torproject.org/25260 [9] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [10] https://bugs.torproject.org/24309 [11] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

Tor Browser team meeting notes, 5 Mar 2018
by Georg Koppen 05 Mar '18

05 Mar '18

Hi! Here are the meeting notes from our first meeting in March 2018. The chat log is on http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-03-05-19.00.log… and the items from the pad are: Monday, March 5, 2018 Discussion: - next meeting (GeKo: the plan is to have the next one on Monday March 26, 1800 UTC taking summer time into account) - isa's meeting pad: https://storm.torproject.org/shared/2RXUuAa_G4_GNy5yHFt8gjFqOv2wAJeq8-_0mQm… mcs and brade: Last week: - For #23136 (Moat integration): - Fixed #25389 (backport Subprocess.jsm runaway CPU fix (Mozilla 1370027)). - Responded to code review feedback and delivered an updated patch. - Filed some follow up tickets: - #25360 (Moat UI is hidden if there are no default bridges) - #25405 (cannot use Moat if a meek bridge is configured) - Found and filed #25362 (setup dialog opens after tor restart when TOR_FORCE_NET_CONFIG=1). - Did some preparation for the Rome meeting. Planned for this week: - Work with Arthur to find the root cause for #25331 (Test from #18912 failing). - Help with code reviews. - Work on #25405 (cannot use Moat if a meek bridge is configured). - More preparation for the Rome meeting. - Mark travels to Rome, arriving Saturday. pospeselr: Last week: - #22794 uplift to firefox (tracked in bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1441327 ) - #25147 backport of fix to ( https://bugzilla.mozilla.org/show_bug.cgi?id=1432966 ) This Week - fix #1441327 ff patch based on their CR feedback, backport said fixes back down to tor-browser - sync with Pari issues spreadsheet - more uplifts - ROME ROME ROME GeKo: Last Week: - Work on #21777 (I basically get mozilla-central cross-compiled now with the clang/minw-w64 toolchain and the result is running \o/; now we need to fix the breakage caused by enabling Stylo) - Code review for moat (#23136), the new HTTPS-E build system (#25339) and partly for merging the Orfox patches (#19675) - I got my patches for #23439 and #21321 uplifted (no mixed content blocking for .onion domains) - I am nearly done with writing an updated draft for the security control redesign proposal This week: - Begin-of-the-month team admin work - Sending the security control redesign proposal to tbb-dev - release preparations - meeting planning - #21777 - reviews, reviews, reviews - Meeting in Rome boklm: Last Week: - Fixed #25339: Install python 3.6 for building HTTPS-Everywhere - Worked on toolchain updates (#16472, #25420, #25304) - Made patch for #25422 (rbm: Give more details in "Cannot checkout" errors) This week: - Continue to work on toolchain updates - Fix #25318 (Add Tor Browser nightly builds email notification) - reviews some tickets if needed - help with building the new releases - will spend some time at IFF, before traveling to Rome tjr Landed time jittering in Nightly. Dealing with fallout. Worked on why MinGW won't run. Thought I had reproduced it not running, then it ran! Seems related to graphics (Still) I'm going to try to flip off the 2 graphics prefs, and run the tests in TC, and see if I can get consistency. I need to write up a wiki page about what (exactly) we block with fingerprinting protection. x64 build in TaskCluster - GeKo, based on your latest work: go for it, or hold off? [GeKo: Go for it. I think the clang thing is cool but there is so much to do that is left that I see it as a plan for the next esr or when we switch to the regular release cycle or maybe for Tor Browser 8.5] Something to think about: Which is more valuable to do first: a proxy bypass test harness for mobile or for desktop? [GeKo: If it's a "we'll work on that in Q3 2018"-thing then I think mobile would be good as we should have our alpha out by then and could use this test harness for ensuring there are no serious things like proxy bypasses on mobile, which is the platform I suspect will have more of those issues than desktop right now.] The light at the end of the Timer Fuzzing tunnel is starting to appear, so I want to start thinking about the 'next big thing' igt0: Last week: - #25126, update the code to use torbutton git repo and to work on Firefox m-c. - #25013, make it work as a feature extension and update the code to work on m-c This week: - Since we are following the feature extension approach I need to update the tor button proposal. - preparation for the Rome meeting. - Try out tor button in the firefox mobile sysrqb: Last week: - Sick with the flu, lost a lot of time - Nearly landed 1440789 (should land this week) - Attended (the end) of the Localization Summit at IFF - Arthur, I hear there will be a discussion about langpacks in Rome, I'm interested in that conversation This week - At IFF, talking with users, trainers, and translators - Landing 1440789 - New branch for Orfox patches merge (#19675) - Finish mobile roadmap and send email arthuredelstein: Last week: Worked on uplift: https://bugzilla.mozilla.org/show_bug.cgi?id=1433592 https://bugzilla.mozilla.org/show_bug.cgi?id=1434772 (landed) https://bugzilla.mozilla.org/show_bug.cgi?id=1441449 (revising) https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 (getting close) Worked on revising https://trac.torproject.org/projects/tor/ticket/22343 This week More uplift: https://torpat.ch/short Rebasing Flying to Rome, arriving on Saturday Georg

1 0

February User issues and bugs spreadsheet
by Parinishtha Yadav 05 Mar '18

05 Mar '18

Hello everyone! Here is the spreadsheet link with issues picked up from February: https://storm.torproject.org/shared/bRjgIahGLgu7fxTKPUDiJhXz2kze0LfQaGvpAyk… <https://storm.torproject.org/shared/bRjgIahGLgu7fxTKPUDiJhXz2kze0LfQaGvpAyk…> (The spreadsheet also contains records of progress on older issues from Nov/Dec'17 and Jan'18. Please navigate to the fourth and fifth sheet for Feb'18.) These issues have been picked up from various different sources like IRC, blog comments, stack exchange, reddit and RT. Feel free to reach out to me in case there are any updates/feedback on the issues listed. *A brief overview of the updates and progress on issues from January'17 spreadsheet:* 1. There has been great response coming in from users for the relay operators guide. 2. Tickets created/ work underway: * #25112 <https://trac.torproject.org/projects/tor/ticket/25112>: Tor Browser 7.5 is not working on Windows Vista 64bit * #20301 <https://trac.torproject.org/projects/tor/ticket/20301>: Bumping the compiler version to 6.2.0 breaks 64bit Tor Browser builds * #24197 <https://trac.torproject.org/projects/tor/ticket/24197>: Building Windows 64 Firefox with the sandbox enabled fails 3. Based on user queries from the past month and correspondence received from the browser team, guidance for using security slider and other settings being added to support portal by the community team. *Themes in the February'18 sheet:* Tor Browser 8.0a2 was released and there are some bugs around that. Apart from this, some general queries on installing and connecting, browsing and running relays. *PS: I will be holding a small session on i**nsights on user issues *during the Rome meeting, *where I'll be discussing some important themes and user problems that I've come across**. Anyone interested can join in! :)* Best, Pari ‌

2 2

Blog post on the Mumbai meetup
by Kushal Das 05 Mar '18

05 Mar '18

Hi everyone, [0]/[1] is the blog post about the meetup in Mumbai (happened in January). This was the first Tor meetup I ever attended. [0] http://kushal76uaid62oup5774umh654scnu5dwzh4u2534qxhcbi4wbab3ad.onion/posts… [1] https://kushaldas.in/posts/tor-mumbai-meetup.html Kushal -- Staff, Freedom of the Press Foundation CPython Core Developer Director, Python Software Foundation https://kushaldas.in

1 0

February 2018 report for the metrics team
by Karsten Loesing 02 Mar '18

02 Mar '18

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in February 2018. On behalf of the Tor metrics team, Karsten Made Relay Search [1] a first class citizen of Tor Metrics by hosting it on metrics.torproject.org. [1] https://metrics.torproject.org/rs.html Released Onionoo 5.0-1.10.0 [2] and .1 [3] which finally fixed broken bandwidth graphs on Relay Search for newer relays. [2] https://lists.torproject.org/pipermail/tor-dev/2018-February/012903.html [3] https://lists.torproject.org/pipermail/tor-dev/2018-February/012904.html Added new links to Tor Metrics to download graph data as CSV files [4]. [4] https://lists.torproject.org/pipermail/tor-dev/2018-February/012967.html Deployed new metrics-bot badges for countries [5] and relays [6]. [5] https://twitter.com/TorAtlas/status/963688006841454593 [6] https://twitter.com/TorAtlas/status/964104753390252032 Held a discussion with bridge operators whether bridge contact information should be public or not [7], and asked the Tor Research Safety Board for advice on making a decision. [7] https://lists.torproject.org/pipermail/tor-relays/2018-February/014444.html Released metrics-lib 2.2.0 and CollecTor 1.5.0 [8] which will allow sanitizing torproject.org web server logs once they are deployed. [8] https://lists.torproject.org/pipermail/tor-dev/2018-February/012959.html Created open mailing list metrics-alerts@ [9] for receiving automated notifications for Tor Metrics service-related alerts. [9] https://lists.torproject.org/cgi-bin/mailman/listinfo/metrics-alerts Tuned metrics-web module advbwdist, by halving the processing time and reducing the necessary memory to about 25%, to keep it operational [10]. [10] https://trac.torproject.org/projects/tor/ticket/25259

1 0

Notes from March 1 2018 Vegas team meeting
by Karsten Loesing 02 Mar '18

02 Mar '18

Notes for March 1 2018 meeting: Nick: 1) Will be at jury duty during this meeting. They assure me I'll be done serving in time for Rome, at least. 2) Not sure about how team is progressing with pre-meeting stuff. Isabela, please let me know if there's anything I need to organize for you? (isa: I might need your help to create a plan with catalyst for sponsor8 error deliverable) Georg: 1) the merge window for patches into Firefox 60 (the next ESR) is closing next week, the team is busy with that Arturo: 1) I am at workshop in Kampala on Research Methods for Internet policy research in africa. I will likely miss todays meeting, but plan to read the backlog. isabela: 1) Finished pad for TB team to organize their meetings of March 11 2) Working on Network team tasks for 6 month roadmap - plan to send general orientation for the other roadmap and meetings by EOW 3) Finished job post for User Research Coordinator (should be out next week) 4) Reviewing design mocks from Antonela so we can present new website portals at Rome 5) Reaching out to partners for in country work in the coming quarter Shari: 1) getting ready to leave for Italy 2) reviewing 2015 audit with Sue 3) finished updated budget for Sida 4) figuring out topic to apply for Facebook grant (https://research.fb.com/programs/research-awards/proposals/secure-the-inter…) 5) followed up with Elaine from Fastly 6) getting ready for Duck, Duck, Go crowdrise fundraising campaign, which launches while we're in Rome (https://www.crowdrise.com/o/en/campaign/tor-project/thetorprojectinc) 7) reviewing ED applications as they come in Karsten: 1) Added new links to Tor Metrics to download graph data as CSV files. 2) Released metrics-lib 2.2.0 and CollecTor 1.5.0 which will allow sanitizing torproject.org web server logs once they are deployed. Alison: 1) Let's finalize the details for the SOTO. I don't see topics really narrowed down. Should do we a group AMA instead? Maybe with some general topics listed on a whiteboard or something to help guide the conversation? 2) I will share out the agenda for Rome early next week. 3) HOPE wrote us back and we're working on talk/table/workshop submissions 4) Libreplanet plans are moving right along 5) Lots of work on LFI curriculum. 6) job postings for Sponsor 9 are done 7) started contacting Sponsor 9 partners :) Steph: 1) newsletter going out today 2) working on accessible onion services overview for funders 3) edited/ing a few blog posts 4) made a new banner for conferences with antonela's support 5) responding to press inquiries.

1 0