- tor-project - lists.torproject.org

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

Tor Browser team meeting notes, 26 Feb 2018
by Georg Koppen 28 Feb '18

28 Feb '18

Hi, here are the meeting notes from our last meeting on Monday, Feb 26. The log is on http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-26-19.00.log… and the items from the pad are: Discussion: Possible grant proposal for https://research.fb.com/programs/research-awards/proposals/secure-the-inter… ? pospeselr: Last week: fix for #25112 Uncovered root cause (missing wow_helper.exe), and put up a patch for review Disables sandboxing specifically for WOW64 Vista and below rather than integrating wow_helper.exe into the build since this problem 'goes away' once we move past ESR52 shortly uplift #22794 Got TryServer access setup and working for me Running tests for linux, linux64 and macos Seems like my patch may have introduced some regressions :( This week: fix regressions (if they are real) introduced by #22794 patch [GeKo: Do you have a bugzilla number for that?] [pospeselr: patch isn't yet uplifted to gecko-dev; verifying the test failures are consistent and will open a trac ticket if the failures are real; will create mozilla uplift bug once patch is passing firefox's tests] [GeKo: okay, sure] mcs and brade: Last week: - For #23136 (Moat integration): - Helped debug issues with Georg's builds. - Fixed a problem with cancel and posted a revised Tor Launcher patch. - Discussed possible support for obs4proxy's meek_lite mode (for Tails). - Reviewed a fix for #25000 (modifications to NoScript's whitelist break webextensions) - Worked with Arthur on a couple of uplift issues: - #18900 (TB 6.0a5: updater doesn't work on Linux (cannot find libraries)) - #25331 (Test from #18912 failing) Planned for this week: - For #23136 (Moat integration), discuss and fix some issues reported by Georg. - Work with Arthur to find the root cause for #25331 (Test from #18912 failing). tjr Landed a 2ms bump in nightly and beta; uplifting to ESR 52.7 This is going to cause merge failures. (Sorry.) Hide the canvas prompt unless triggered by user input is landed Arthur worked on the keyboard patch - thanks so much Fixed leak: https://bugzilla.mozilla.org/show_bug.cgi?id=1438795 Close to fixing breakage: https://bugzilla.mozilla.org/show_bug.cgi?id=1433592 Why doesn't MinGW run is a little closer, need to talk to Bob Owen Mostly have worked on Timer Fuzzing GeKo: Last week: - Slow progress on clang-based cross-compilation (#21777). I am still hitting issues faster than I can diagnose and work around them but am able to build a large chunk of m-c right now - Finished by patch for #23439 (exemption of .onion from mixed content blocking) - Worked on code review for #23136 - Thought about how to deal with the feedback for the security control redesign This week: - More work on #21777 - More code review - uplift my patches for .onion treatment in mixed content scenarios (this is Mozilla's bug 1382359) - post an updated draft for the security control redesign igt0: Last week: - Rebasing #25013 to run on mozilla central It needed a bunch of changes since firefox deprecated few APIs and removed few browser specific css. This week: - Make #25013 work on android and figure out why the about:tor is not applying the css rules Can we use a branch instead of mozilla central? thus we can run the tor browser tests with the tor patches applied. arthuredelstein: Last week: https://bugzilla.mozilla.org/show_bug.cgi?id=1438795 (checked in) https://bugzilla.mozilla.org/show_bug.cgi?id=1436226 (patched) https://bugzilla.mozilla.org/show_bug.cgi?id=1433592 (patched) https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 (patch nearly ready) Worked on https://trac.torproject.org/projects/tor/ticket/25331 This week Revise above patches for check in https://bugzilla.mozilla.org/show_bug.cgi?id=1396224 Finish https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 Work with mcs and brade to finish https://trac.torproject.org/projects/tor/ticket/25331 and then try to uplift Finish https://trac.torproject.org/projects/tor/ticket/22343 and attempt to uplift More uplift: https://torpat.ch/short boklm: Last week: - helped build and publish the alpha release (8.0a2) - fixed bug #25327 (create *-debug.tar.xz files instead of *-debug.tar.gz files) - worked on the binutils update (#16472) - started looking at data from #22346 (drop in Tor Browser update pings in early 2017 and 2018) This week: - fix #25339: Install python 3.6 for building HTTPS-Everywhere - continue working on: - toolchain updates (#16472 and #25304) [GeKo: I think we get a new tag tonight for selfrando, so we should be good for the next alpha at least] - shipping auto-updates for Tor Browser nightly channel (#18867) - testsuite updates/fixes sysrqb: - last week: - Discussed system extensions with some Mozilla devs, regarding support for legacy addons - Pushed a branch including the Orfox patches for #19675 - Updated #25260 with the current status of the TorLauncher mozbuild integration - Opened a bugzilla ticket for broken system addons on Android - https://bugzilla.mozilla.org/show_bug.cgi?id=1440789 [GeKo: good stuff. once you have a r+ you can request a check-on with the [checkin-needed] keyword (assuming you don't have Level 3 commit perms for m-c] - This week - Stop being sick - Follow up on #19675 and get patches merged - Open child tickets for everything I think we should change in the Orfox patches - Actually work on TBA roadmap/design proposal isabela: haven't finished the agenda's pad - will share it to the list today tho so folks can start organizing for rome Georg

1 0

Damian's Status Report - February 2018
by Damian Johnson 26 Feb '18

26 Feb '18

Hi all. Shorter than usual but here ya go! http://blog.atagar.com/february2018/ Cheers! -Damian

1 0

Network team meeting notes: 26 Feb 2018
by Nick Mathewson 26 Feb '18

26 Feb '18

Hi all! Meeting logs at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-26-17.59.html Meeting pad contents below. ================= Network team meeting pad, 26 Feb 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 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) * There are tons of tiny 0.3.3.x tickets. Maybe if you can do one of them in <X minutes for some small X, you should just do it? * The 0.3.4.x merge window opened on Feb 15. * Please fill in the code subsystems spreadsheet at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… If you review tickets, feel free to add a column with your name. * Please fill in Isabela's heat-mapping exercise with areas of tor work: what are our priorities? https://pad.riseup.net/p/38VbTZUIzG4X * No GSoC for Tor :'( [this time] * isis cannot attend Rome :( Announcements: * Tor Meeting starts in 2 weeks: Sunday 10 March (Hackfest) to Thursday 15 March (Unstructured Day) * Jon will book accommodation for the May hackfest (Wednesday 30th - Sunday 3rd) by the middle of this week. Then people can book flights. [catalyst: is location for hackfest still undetermined?] [dgoulet: It is Seattle, see hackfest pad for details.] [catalyst: there was talk about moving to Portland due to hotel cost] [Afaict, still Seattle. Hotel booking is ongoing so we'll notify the list once we have that settled for flight arrangements]. * Review-group-32 is open! There are 5 tickets in needs_review. https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * Review-group-33 is open! There are 5 tickets in needs_review. https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * teor moved some needs_review tickets from "Tor: unspecified" to "Tor 0.3.4", so the next review group will be a big one. Let's try not to lose needs_review tickets in other milestones! * 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… Discussion: * teor is happy to do Coverity rotations, but thinks they might need a login or a mailing list subscription. [Ask nickm if you need a coverity login; he'll make one for teor.] * #25324 (about tor-releases.git), IRC discussion last week didn't end up in favor of it. Lets not bikeshed too much but now is a good time to put in your opinion. (On the ticket, perhaps?) <-- Yes, right place to do so. * Subsystem maintainer (see spreadsheet). We should maybe assign them to developers and start using that for tickets. [ https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… ] * heatmap (review and what's next) isa can lead [ https://pad.riseup.net/p/38VbTZUIzG4X ] ====== teor: * Last week: - Finished Experimental PrivCount (it's feature-complete) - More May hackfest planning - More Proposal meetings - Designed some demo code for typical floating point issues. Rust is nice for demos in docs - Reviewed a few tickets * This week: - Test Experimental PrivCount on a live relay - Update the Network Team Useful Queries page to be more useful (WIP) https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/UsefulT… - Make trac user page that lists the tickets I'm working on in priority order - Review and revise tickets - Write some Rust. Write some floating point code. Watch rustc's output carefully nickm: * Last week: - More work on upcoming releases - More rome planning/prep with isa - bugfixes, 033-must bug triage, review, merging, etc - worked on a better protover voting algorithm. - Dove into most frequent* wakeup events and what we can do to reduce or eliminate them. [* That is, the ones scheduled with highest frequency.] - Many meetings - Skimmed my old algorithms text - Finished/published prop290 (rolling expiration of consensus methods) - Made a tor-rust-dependencies repo - Discussed releases repo (#25324) * This week: - Many meetings - Try to do security releases (0.2.9 and up). - TROVE-2018-001 review status? [catalyst: changes look ok, doing manual builds. done!] - Anything I should merge or backport before releases? [dgoulet: If you feel like it, #25316 but not that critical] - More rome prep - On call for jury duty on Tuesday. Might not be needed, but if I am, this will consume all of Tuesday, and possibly more :/ - Work on 0.3.4 issues, 0.3.3 issues - Open tickets for making events less frequent - Decide on power-saving api approach with ahf dgoulet: * Last week: - Found #25312 while working on circuitmux performance for which I opened #25328 and worked on it but nothing final (Development in ticket25328_034_01). - Some DoS ticket triage to better organize SponsorV. https://trac.torproject.org/projects/tor/wiki/org/sponsors/SponsorV - Finalized #24767 from asn's review. Now in merge_ready for nickm. - Ticket #25226 is awaiting some feedback from Roger and interesting comment to take into account from cypherpunks. - See timeline for the rest: https://trac.torproject.org/projects/tor/timeline?from=Feb+26%2C+2018&daysb… * This week: - Continue working on my 033 and 034 tickets. - New stable series will have the DoS mitigation so I'll keep an eye out for any issues arising from these releases. Mike: * Last week - Working on vanguard controller structure and feature brainstorming - Reviewed side channel attacks to see if they detected by a controller - Looks like yes, though there may be CIRC_BW/STREAM_BW mis-counting bugs - Did a bit of roadmapping for sponsor2+v. Also filled out heatmap, component owner sheets. - Coordination for upcoming OTF grant * This week: - More OTF coordination - Continued vanguards work asn: Last week: - Reviewed #17945 and #24767 and #25306! - Investigated newest SRV bug #24815 courtesy of teor. - Did some digging in #25347: our latest important guard bug. - Helped new volunteer with #6236. 6 years old easy refactoring ticket now finalized. - Some more work on guardfraction remnants #24456. - Filled out isa's roadmapping/voting exercise. Talked some more about roadmapping. Did some more spreadsheet tricks on the subsystem maintainer spreadsheet. Please fill it out if you haven't: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… This week: - More reviews and bugfixes. Particularly #25306, #25347, #24815, etc. - Organizing SponsorV work and seeing what's needed. - Wednesday: Doing Tor talk at ENS Paris with Lunar. ahf: Last week: Sponsor 8: - Wrote a script to extract main loop event stats. - Baselined idle client event loop numbers in https://docs.google.com/spreadsheets/d/1N4dRCrmvlTME615sODaeTb4lCQWKxgux2l4… - Tiny patch for Shadow https://github.com/shadow/shadow/pull/403 - Trying to wrap my head around Shadow's way of not using the main.c event loop functions and how to measure things sensibly. Misc: - More event loop and Windows experimenting. Reading MSDN. - Added Rust support and open sourced the Tor vim plug-in: https://github.com/ahf/onion-vim - Added a SyslogFacility config entry in #25355 for setting syslog facility value. - Answered team surveys. This week: Sponsor 8: - Work with Nick on more event loop and power management features. - Prepare some info for the mobile session in Rome about core Tor progress since Montreal. - Look at Isa's Roadmap email questions. Misc: - Look into #24368 (zstd tuning) (moved forward from last week). isabela: last week: start working with folks on planning sponsors (only) work for the 6 months roadmap [ahf + catalyst -> i pinged you on this] this week: hope to start converting the info on pad for sponsor tasks into trac tickets this week share share orientation for planning in rome (specially for 2019-2021 roadmap) catalyst: last week (2018-W08): - TROVE patch review - roadmappy stuff this week (2018-W09): - review tickets - travel prep - CoC and SoV feedback - are we doing Rust stuff at Rome and if so what prep should we do for it? isis: last week: - Catch up on email backlog - Prototype for Rust wrappers for SHA2 code #24659, can't get it to link to both libtor and libor-crypto for the life of me - Call/pair programming/review with komlo about the Rust logging module, I promised to take over the patch and do whatever fixups nick requested since she's quite swamped right now - Documented the setup of the moat reflector for Isa - Documented the status of the moat project (done!) :) this week: - More large create cell work #24986 to clean up my branch and show it for preliminary review - Getting the frickin linker to link the stuff - I forgot to review #25268 last week! sorry! will do this afternoon

1 0

Notes from February 22 2018 Vegas team meeting
by Karsten Loesing 23 Feb '18

23 Feb '18

Notes for February 22 2018 meeting: Alison: 1) super busy 2) Rome meeting: soliciting agenda ideas now. Please ask your teams to add their agenda ideas to the wiki: https://trac.torproject.org/projects/tor/wiki/org/meetings/2018Rome/AgendaI… I will share out the agenda during the week before the Rome meeting begins. 3) Rome State of the Onion/Tor Report plenary: we need to narrow the topics into categories (if we're leaving narrow topics, they just have to be important enough to stand on their own. Once we have categories I can work on getting people to present on them. Maybe we could have 30 minutes of speaking and 30 minutes of an AMA style Q&A. 4) HOPE: no response from HOPE organizers to my questions about when the CFP closes and how to get workshop space, etc. So those of us who are thinking about presenting at HOPE are just continuing to work on our proposals over email. 5) LibrePlanet: We are on the schedule to give a panel talk, and we will also have an exhibit booth. Now I just need to make some slides for the panel. 6) NYC Tor Meetup was great! 7) My Tor talk at Barnard College was also great. 8) We will continue the statement of values convo in Rome to help resolve some of the outstanding issues. We will vote on the code of conduct when we return so that people don't have to vote while traveling. 9) Isa let's find some time soon to talk about Sponsor 9 next steps [vixemaria yes! can we have a work meeting tomorrow on this?] [Alison: yes, morning is good for me, maybe 10 CT/11 ET or so? yes!]] 10) I'm almost ready to announce the participants in LFI, and I'm still very busy building the curriculum 11) Phoul is organizing another Tor Summer of Privacy since we didn't get picked for GSoC. He's also gonna be our Outreachy mentor this round. 12) He is also working on support portal translations and making edits to the Tor Browser manual to be in sync with TB 7.5 Nick: 1) Jury duty on Tuesday, possibly out that day unless it's canceled. 2) Team working on 0.3.3 completion stuff, roadmapping work for the future (Thanks, Isa!) Mike: 1) Vanguards dev stuff isabela: 1) We tried to use DDG as our search for support but the UX is not good at all :( - this is mega important, specially for a site that is suppose to help people. So we are going with our old plan to use solr (apache search eng). Support.tpo is very very close from launch \o/ 2) Working with network team, doing some team exercises so we are in a good shape for our plannings - we will do 2 roadmaps (1 from march-nov 2018) and another one that is a bit more related to the vision for the team 3) UX team has a lot going on for Valencia and Rome - more here -> https://storm.torproject.org/shared/FIepEQhIkrRspwAydo2sEkQ_m895cerNvlgSRV3… I will be on a call with south asia trainers talking about ux and hearing their feedback on tor browser (this is next week, it was an invite from Internews) 4) sponsor4 - looks like we will indeed finish all deliverables this time :) 5) Working on prep stuff for TB team for Rome (sponsor8 roadmap preparation and a bit of TB desktop roadmap preparation based on our SOI to DRL) - plus meeting agendas for other meetings we have scheduled for teams meeting day 6) had a few calls: OTF, EFF (getting the right license for our styleguide), sync on SIDA meetings Karsten: 1) Created new mailing list metrics-alerts@ to make monitoring of metrics-related services more transparent. 2) Asked the Tor Research Safety Board to comment on our plan to publish bridge contact information as part of sanitized bridge descriptors. 3) Set up a new host with 64G RAM for bulk data processing. Tested it for re-sanitizing web server logs with CollecTor's new webstats module. 4) Planning new releases next week. Shari: 1) lots of meeting planning 2) executive director search. 3) finishing up Sida budget 4) I'll be offline on Friday, Monday and Tuesday. Georg: 1) preparing an alpha Tor Browser release (8.0a2) with the latest tor alpha to give it wider testing 2) Arturo: If we have bad luck we need to make two releases during Rome. Do you know a place with fast upload/download for syncing the bundles? (My house? :-) ~A.) [Heh. I get back to you in case we need it, thanks. Georg] (I can also try to think of some place closer to the venue, but in any case I live about 20mins by metro/bus away ~ A.) [Luis enlabs, close to Termini station may also have fast uplink: http://luissenlabs.com/] Arturo: 1) Had a meeting with the UX team to sync up on the revamping of the OONI Probe Mobile app. 2) Made some significant improvements to the performance of OONI API and OONI Explorer that are now deployed. 3) Arturo & Maria did a presentation at Cape Town University, the slides are here: https://slides.ooni.io/2018/uct-internet-censorship-measurements/ Steph: 1) Outreachy internship application period is open 2) Edited/published volunteer spotlight on meejah that Tommy wrote. Antonela made an awesome graphic to accompany it 3) Put together first draft of one pager for funders on onion services 4) ED search press release and post 5) NYC meetup was a success

1 0

HOPE July 20-22
by George 21 Feb '18

21 Feb '18

We are currently in heavy planning for a TPO presence at HOPE in NYC. It's a large audience with many currently or potentially interested in the project. The TPO plans include: * some people replying to the CFP to do presentations on both technical and non-technical topics. * workshops on specific Tor topics. Topics can be large and small, but hands-on is good. Think "how do I install on an Android phone?" or "how do i teach others about Tor?" We queried for a table and "lounge" space where workshops could be held, and are awaiting more information. We are unclear when the CFP closes. At this point, a good core of TPO people will be attending, but more people means more workshops and bodies at the table. We are working out a lot of other details, including a Saturday night social event, a banner for the table, etc. We are maintaining a pad at https://pad.riseup.net/p/TorHOPEplanning Once we find out the status of the table/lounge and CFP closing, we can hold another #tor-meeting session and continue finalizing details. Input/comments requested, including more people interested in tabling, presenting or hosting a workshop. g -- 34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682

3 2

Network team meeting notes, 20 Feb 2018
by Nick Mathewson 21 Feb '18

21 Feb '18

Hi, all! You can find the proceedings of our latest meeting at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-20-17.59.html Our notes are below: ================== Network team meeting pad, 20 Feb 2018 Welcome to our meeting! Tuesday (normally 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/001644.html * https://lists.torproject.org/pipermail/tor-project/2018-January/001647.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001654.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001664.html Old Announcements: * 0.3.3.x is in feature-freeze. No new features (except for #24902, which has permission.). * 0.3.3.2-alpha came out Saturday 10 Feb. * Please, work on bugfixes! It would be great to have this release release on time. (Planned date is 15 April) * There are tons of tiny 0.3.3.x tickets. Maybe if you can do one of them in <X minutes for some small X, you should just do it? * We moved the hackfest 2 days later (Wednesday 30th - Sunday 3rd) to avoid clashing with Memorial Day dgoulet, teor, and isabela are organising it off-list. See the network-team list for updates. * No GSoC for Tor :'( [this time] Announcements: * Jon is booking accommodation for the May hackfest. * The 0.3.4.x merge window opened on Feb 15. * Review-group-32 is open! There are 2 tickets assigned to teor and mikeperry to review. Maybe we can move on to review-group-33? https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * Nick just made a review-group-33. Please take tickets to review. * Please fill in the code subsystems spreadsheet at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… If you review tickets, feel free to add a column with your name. * Team rotation roles was empty last week and this week, ahf have taken this week, but its empty for next week: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * isis cannot attend Rome :( * prop#245 + prop#282 meeting today (tuesday) at 23:00 UTC Discussion: - Topics - Can we remove the *.nmake files in tor.git? I have a feeling that they are unmaintained/unused? - Is all the dates final for the May hackfest? (would like to order tickets early from Europe while they are cheap). - Isabela's heat-mapping exercise with areas of tor work: what are our priorities? https://pad.riseup.net/p/38VbTZUIzG4X ====== teor: * Last week: - Implemented and tested more Experimental PrivCount circuit and onion service stats (1.5 features left, and then it's feature-complete. I hope!) - More May hackfest planning - More Proposal meetings - Detailed design and numerical analysis for uniform random in Rust, but still no code - Reviewed a few tickets, merged a chutney network for bwscanner * This week: - Final Experimental PrivCount features (no, really, this week) - Eventually make a trac user page that lists the tickets I'm working on in priority order. Add something similar to the network team queries page. - I should get time to review or revise more tickets later this week catalyst: last week (2018-W07): - reviewed #25185 (Rust cstr stuff) - learned more Rust stuff, including some doc-test things - patch for #21074 check-changes - travel logistics for Rome meeting and Seattle hackfest - CoC and SoV feedback - helped pastly with IRC moderation stuff this week (2018-W08): - work on 0.3.3 bugs - review more tickets - help out with floating point doom - update roadmappy stuff - more travel logistics - monitor CoC and SoV feedback dgoulet: * Last week: - We got #24902 backported \o/ - Discussion with armadev on #25226 for which it could be that we want a hard limit of cell queue size per circuit. - Did a branch for #17945 as a possible solution. Need feedback. - Opened and worked on #25268 to remove the cmux round-robin algorithm. - I've also started working on a branch to improve our fast path (per cell) within the cmux subsystem. It touches also #25152. Not ready for merge or anything, it was more experimental to see how that would play out. - Worked with asn on the subsystem maintainer sheet. *PLEASE FILL IT UP* - A little bit of May/June Hackfest logistics with Jon. - Was quite a week for bad relays so spent some time there. - Helping atagar with some HSv3 questions and examples for Stem integration - Sent to tor-dev@ my 034 enhancement plans: https://lists.torproject.org/pipermail/tor-dev/2018-February/012949.html - Some ticket triage including 033-must tagging. See timeline: https://trac.torproject.org/projects/tor/timeline?from=Feb+20%2C+2018&daysb… * This week: - Hope to work on 034 enhancement so we can get them early in the merge window. Especially the scheduler stuff. - 033 tickets are still a reality. - Get #24767 in a merge_ready state (asn did a first review) Nick: * Last week: - Too many meetings ;) - Worked on TROVE fixes, rust protover fixes, etc. (See network-team-security, #25250, #25251) - Opened 0.3.4, merged much of backlog. - Administrative stuff for roadmapping/planning - Conferred with isabela about roadmapping etc. * This week: - Pre-announce next week's security releases - Prep for next week's security releases - Review and merge more. - Finish 0.3.3 fixup triage [033-must, continued] - Write up an implementation plan for improved hibernation backend, based on https://gist.github.com/ahf/d22a4a98abe4651d07181a993cebdd21 [continued] - Get an official repo for tor-rust-dependencies - Get an official repo for tracking "latest stable", "latest alpha", etc asn: Last week: - Helped with roadmapping. Revived subsystem maintainer spreadsheet. Please fill it out if you haven't: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… - Triaged tor-hs and tor-guard tickets of 033. - Arranging Tor seminar at ENS Paris at the end of February with the help of maker. - Reviewed #24767. - Reviewed #24343. - Reviewed #21425. This week: - More roadmapping fun. - More reviews/bugfixes. - Think about HS statistics that we could gather (reply to teor's email). Mike: Last week: - Reorganizing and refactoring vanguards repo - Reviewed #22926 - Reviewed guardraction code - are we sure we want to rip it out rather than just disable torrc? [asn: i think we want to rip it off to simplify the codebase. otherwise we could keep it lingering on until and if we have firepower to fix it...] [mike: do we believe that a new from-scratch implementation will be simpler?] [asn: no. i think we just realize we wont ever have enough time to fix it and maintain it] [mike: hrmm.. that seems defeatist and potentially wasteful :/] [asn: might be. it's just that the code has been sitting around for many releases and it's been broken and no one wants to fix it or maintain it. also dirauth ops are complaining about the python script and we should tell them to kill it] [mike: it seems like disabling and deprecating the python script can be separate from removing all of the functionality from tor-core... is this the type of thing that will always be easier to do in an external program, because of statekeeping?] [asn: yes it's because of statekeeping that we do it as external. and i agree that perhap disabling the python script is separate from removing code from tor. as an argument for keeping it, the guardfraction tor code is fairly isolated and abstracted from the rest of the code] ahf: Last week: Sponsor 8: - Walked over S8 roadmap tasks. - Baselined some memory usage experiments with Shadow+dtrace that was done with tor+simpleperf before. - Made a Tor/Orbot APK where Tor stores its log on the device and the device periodically submit some grep'ed lines to a web service. Misc: - Reviewed: #25095 - Went over the different documents discussed at last meeting + the subsystem survey. - Discussed some PT enhancements after the PT meeting in #tor-dev. - Played around with Windows API's and cross compilation of Tor for Windows. This week: Sponsor 8: - Baseline event loop statistics and all the client tests in Shadow Misc: - Look into #24368 (zstd tuning). - Help out with some bugfixing. - Next weekend I hope to get a prototype/demo running with a PT subprocess that can do logging via tor. isis: last week: - finished moat work #24432 - dumped all the unallocated bridges into the new moat distributor to kickstart it #25246 - reviewed #25150 and #24658 and #25071 - tiny fix for duplicate header inclusion #25271 - began making rust wrappers for our C digest code #24659… can i include a new dependency on the digest crate? - researched the safety of zero-sized types accross FFI boundaries this week: - documenting moat reflector setup somehow as much as possible? - continuing large create cells #24986 impl - continuing rust digest wrappers #24659 - continue scheduling proposal meetups and have meetings - meeting this week with teor about prop#245 and prop#282 (and whomever else would like to join) (at 23:00 UTC today) isabela: last week: - started the roadmapping process - today will talk about voting on priorities - met nick o/ - met roger o/ this week: - continuation of roadmapping process - organize first draft of tasks for 6 months roadmap - send out feb network testing emails

1 0

Tor Browser team meeting notes, 20 Feb 2018
by Georg Koppen 20 Feb '18

20 Feb '18

Hi, Here are the meeting notes for the Tor Browser meeting on 20 Feb (we had no meeting last week). The chat log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-20-19.00.log… And here come the notes from our pad: Tuesday, February 20, 2018 tjr Spent a lot of time on Timer Rounding and Fuzzing. Spending yet more time on it, but made good progress.. Got a patch written to hide the canvas prompt unless triggered by user input https://bugzilla.mozilla.org/show_bug.cgi?id=1376865 The Keyboard layout patch has problems. It's still leaking data: https://bugzilla.mozilla.org/show_bug.cgi?id=1438795 It breaks a lot of stuff (see Duplicates also): https://bugzilla.mozilla.org/show_bug.cgi?id=1433592 I.... don't really understand this one. Arthur can you walk me through it? (Arthur says: Sure. After the tbb meeting?) Made headway on "Why doesn't MinGW run" - but need assistance debugging https://bugzilla.mozilla.org/show_bug.cgi?id=1411401#c17 Added a MinGW 32 Opt build to TC and am working on a x64 Build There is a draft for the Fingerprinting Protection Help Page https://bugzilla.mozilla.org/show_bug.cgi?id=1397757 mcs and brade: Last week: - Completed some code reviews: - #15599 (Range requests used by pdfjs are not isolated). - #22614 (Make e10s/non-e10s Tor Browsers indistinguishable). - #22659 (Changes to `intl.accept.languages` get overwritten). - For #23136 (Moat integration): - Confirmed that the BridgeDB Moat distributor is now working (thanks Isis!). - Posted a patch for #19910 (Rip out optimistic data socks handshake variant (#3875)). - Found and fixed #25266 (PT config should include full names of executable files on Windows). - Created some test builds for the Moat feature and posted them. Planned for this week: - Debug #23136 (Moat integration) which is not working for Georg. - Review some more patches. - Triage the Tor Launcher bug list (set priorities, close outdated tickets). GeKo Last weeks - Worked on #21777 (I finally got a Tor Browser build somewhat running on Windows by using a clang-based cross-compiler) - Reviews - Release preparations for the alpha This week - More work on #21777 (trying to get mozilla-central built with the new clang-based cross-compilation toolchain) - Reviews - Getting 8.0a2 out - Think about summarizing the security slider discussion we had so far and moving the topic forward - Finally writing the tests for my mixed content blocker .onion patch (#23439) sysrqb -Last week: - Worked on #25260 - merging moz build files into tor-launcher - This ticket is becoming something...different, so I may repurpose it - We had an unofficial group meeting on Monday and discussed some stuff about mobile - Worked some more on the TBA roadmap - This week - Finish TBA roadmap - Continue working on #25260 - Start porting Orfox patches onto mozilla-central - Should we takeover responsibility for Orfox (and release Orfox updates) while we work on TBA? pospeselr: Last weeks: synced with Pari on February's spreadsheet regarding Tor Browser Worked on #25112 - sandboxing issue on Vista Tracked down point of failure (ntdll patching), investigating fix GK: could you ping me offline with the info you mentioned having on getting debug symbols working in windows builds basically printf debugging atm which is fine for now but would like to be more efficient in the future [Full-fledged debug builds are broken right now (but mozilla-central should have that fixed (https://bugzilla.mozilla.org/show_bug.cgi?id=1372958 has the details). Your best bet with a debugger right now is using the optimized build we usually build, however with stripping disabled; make sure you have --disable-strip in your .mozconfig and if you package a build you need --disable-install-strip as well; bobowen is the windows related sandboxing guru and e.g. in #boxing and pretty helpful if you want feedback for patch ideas GeKo] pospeselr: --disable-install-strip was the missing piece, thank you! confirmed fix for #24341 (ubuntu build issue) This week: uplifting patch for #22794, fix for #25112 more bug fixes for the bug gods igt0: Last week: - Investigated the #25247, I was not able to reproduce neither in my machine nor in a debian virtual machine. (Tried different resolutions and pixel densities) - Looked into the https://bugzilla.mozilla.org/show_bug.cgi?id=942652 , the ticket is out to date, good part of the firefox code is already updated to use configured proxy, except the sync code. I am now looking into the sync background service, there is a bug about using a different http lib https://github.com/mozilla-mobile/FirefoxData-android/issues/4 - sysrqb: I assume we'll want to disable Sync at compile-time, so we may not need to do a lot - igt0: interesting, I found these tickets https://trac.torproject.org/projects/tor/ticket/7188 and https://trac.torproject.org/projects/tor/ticket/10368 , i am not sure it reflects the current state. (where it can be enabled for sync bookmarks, passwords and history) This week: - Help sysrqb to write the TBA roadmap/documentation - Contact the Mozilla team working in the sync service about #942652, to make sure we are aligned what is the proper solution. boklm: Last weeks: - worked on some patches for: - Bug 25020: add a tbb_version.json file - Bug 25178: re-enable windows-x86_64 build in 'make testbuild' - Bug 24879: enable fetching of new commits by default for nightly builds - started working on updating binutils (#16472) and gcc (#25304) This week: - help with build of the new alpha release - continue working on: - toolchain updates (#16472 and #25304) - shipping auto-updates for Tor Browser nightly channel (#18867) - testsuite updates/fixes arthuredelstein: Last weeks: - Uplifted patches to Mozilla (checked in) https://bugzilla.mozilla.org/show_bug.cgi?id=1433357 https://bugzilla.mozilla.org/show_bug.cgi?id=1433517 https://bugzilla.mozilla.org/show_bug.cgi?id=1432907 https://bugzilla.mozilla.org/show_bug.cgi?id=1433507 https://bugzilla.mozilla.org/show_bug.cgi?id=1344613 https://bugzilla.mozilla.org/show_bug.cgi?id=1433030 https://bugzilla.mozilla.org/show_bug.cgi?id=1434666 https://bugzilla.mozilla.org/show_bug.cgi?id=1433523 Also worked on (but not finished): https://bugzilla.mozilla.org/show_bug.cgi?id=1438795 https://bugzilla.mozilla.org/1330467 This week: Current remaining patches for uplift: https://torpat.ch/short More uplift! Two bugs mentioned above, and try to finish/uplift https://trac.torproject.org/22343 isabela: - Submitted on Feb 12 SOI to DRL for TB desktop work (small grant - nothing too crazy, implement ux work from anto/otf grant and keep up with mozilla releases/security stuff) - organize team roadmap prep work for Rome - will share more this week (let me know if you have any questions) - moving some work w/ TB team to March because ux team has to get website work done by rome - prep for team meeting day in rome (should we create pads and share stuff before hand or prepare an agenda for the meetings?) Georg

1 0

Network team meeting moved to Tuesday (this week only)
by Nick Mathewson 16 Feb '18

16 Feb '18

Hi! Our regular Monday 1800 UTC meeting on #tor-dev will happen on Tuesday instead this week. (Monday is a US holiday.) peace, -- Nick

1 0