tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

December 2018 in sysadmin land
by Linus Nordberg 14 Jan '19

14 Jan '19

Hi Tor, The sysadmin and services team presents its December. # What's been done - Improvements to our list of services [0]. - New VM'S for CiviCRM ready for use. - The ordinary resolving of requests, as can be followed better over at [1]. [0] https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure [1] https://trac.torproject.org/projects/tor/report/44 # Upcoming new things - Will be seing some of you in Brussels [2]. [2] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Brussels # Fact of the month Reading the sysadmin team wiki [3] will make you a better informed user. Providing material to it might make it even more useful! [3] https://help.torproject.org/tsa/

1 0

OONI Monthly Report: December 2018
by Maria Xynou 13 Jan '19

13 Jan '19

Hello Tor world, During December 2018, the OONI team wrapped up the year by preparing for the upcoming OONI Probe mobile app launch, making a series of improvements to Measurement Kit (our network measurement library) and by implementing an orchestra endpoint for test lists. ## Prepared for OONI Probe mobile app launch Following the public beta release of the revamped OONI Probe mobile apps in November, we spent December preparing for the stable release in January 2019. This involved: * Fixing bugs reported as part of the beta testing. * Improvements to how we managed translations in the mobile apps via: https://github.com/ooni/translations * Coordinating translations & joining the OONI Probe Office Hour on the Localization Lab Mattermost channel to address translator questions (https://www.localizationlab.org/blog/2018/12/11/ooni-probe-office-hour). We're extremely grateful to the Localization Lab for their great support in coordinating translations! ## Test list orchestra endpoint We added a dedicated ooni/orchestra API endpoint for provisioning OONI Probes with URLs to be tested: https://github.com/ooni/orchestra/pull/58 & https://github.com/ooni/orchestra/pull/57. This allows for a more dynamic and quick update of test lists on mobile devices and it's a first step towards rolling out OONI Probe Orchestration. ## Measurement Kit ### Released Measurement Kit v0.9.1 We released a new version of Measurement Kit: https://github.com/measurement-kit/measurement-kit/projects/2. This new version contains bug fixes and improvements over version 0.9.0 and will be included in the upcoming release of the mobile apps. ### Improved DNS engine in Measurement Kit We wrote the foundation for a new DNS engine in Measurement Kit. The requirements for this new DNS engine have been documented in https://github.com/measurement-kit/measurement-kit/issues/1689. We have implemented these requirements in a separate repository (https://github.com/measurement-kit/mkudns), which we plan on integrating in Measurement Kit v0.10.0 or v0.11.0. This new engine will allow us to save the content of sent and received UDP DNS packets, and will also allow us to timestamp network events. We will use this code when running some OONI tests to collect low level data useful to understand censorship. We are specifically planning on submitting base64 encoded packets to the OONI pipeline for further analysis and for historical records. ### Rewritten iOS integration layer We have created a new repository (https://github.com/measurement-kit/mkall-ios) for integrating Measurement Kit with the iOS apps. This new repository has been designed with OONI Probe for iOS in mind but could potentially be beneficial to any other project using Measurement Kit. The gist of this rewrite is that now the app can use Objective C code directly to interact with Measurement Kit. The code in mkall-ios will take care of mapping the Objective C requests to Measurement Kit's internal APIs. This change is great for us because it allows us to decouple the implementation of the OONI app from Measurement Kit internals. In turn, this improvement allows us to increase our code velocity, i.e. the speed at which we can change mutually independent parts of the code base by minimizing the surface over which changes propagate. The upcoming version of OONI for iOS will use this repository. We're working to implement similar changes for Android too. ## Updated the test list of the Democratic Republic of Congo (DRC) In preparation for the Democratic Republic of Congo's elections in late December 2018, we carried out research and coordinated with locals to update the country's test list. The updates can be viewed here: https://github.com/citizenlab/test-lists/pull/420 The CD test list was also updated earlier (November 2018) thanks to URLs provided by community members: https://github.com/citizenlab/test-lists/pull/413 ## IEEE publication Earlier in 2018, we published a research report on internet censorship in Nigeria, in collaboration with Paradigm Initiative: https://ooni.torproject.org/post/nigeria-internet-censorship/ A version of our research report was published in the IEEE Internet Policy Newsletter (December 2018 edition): https://internetinitiative.ieee.org/newsletter/december-2018/measuring-inte… ## OONI blog post for Tor Strength in Numbers blog series In support of the Tor Project's end-of-year fundraising campaign, we published a blog post, "Strength in Numbers: Fighting Internet Censorship", which is available here: https://blog.torproject.org/strength-numbers-fighting-internet-censorship Our blog post was translated to Russian and cross-posted by Roskomsvoboda: https://roskomsvoboda.org/43616/ ## Community activities ### MAMI Active Measurement Hackathon in Scotland OONI's Simone traveled to Aberdeen, Scotland, to participate at the Measurement and Architecture for a Middleboxed Internet (MAMI) Active Measurement Hackathon on 5th & 6th December 2018. The goal of the 2-day hackathon was to share knowledge and experience in internet measurement between OONI and MAMI. Information about the hackathon is available via MAMI's blog post: https://mami-project.eu/index.php/2018/12/20/mami-active-measurement-hackat… ### EngageMedia's OONI blog post The Philippines' EngageMedia published a blog post about OONI, explaining OONI Probe and encouraging local communities to participate in censorship measurement research. Their blog post is available here: https://www.engagemedia.org/blog/ooni-measure-censorship ## Userbase In December 2018, OONI Probe was run 298,455 times from 4,527 different vantage points in 209 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

Nyx Release 2.1.0
by Damian Johnson 12 Jan '19

12 Jan '19

Hi all, I'm pleased to announce Nyx 2.1.0. This is a fixup release that corrects issues uncovered over this last year... https://nyx.torproject.org/changelog/index.html#version-2-1 Cheers! -Damian

1 0

December 2018 report for the Tor Browser team
by Georg Koppen 11 Jan '19

11 Jan '19

Hello! This is the last report for our work done in 2018. In December we made two releases, Tor Browser 8.0.4[1] and 8.5a6[2]. Besides updating component like Tor (to 0.3.4.9) and OpenSSL (to 1.0.2q), Tor Browser 8.0.4 contained many backports from patches tested in our alpha series. The most important ones were a fingerprinting defense against protocol handler enumeration[3], enabling Stylo for macOS users[4], and setting the sandboxing level on Windows back to 5[5]. Tor Browser 8.5a6 got exiting updates on the Android side: It's been the first release that is being built reproducibly[6] and has multi-locale support in a single .apk.[7] Besides working on releases we outlined our further mobile work towards the next milestone, TBA-a3, which should bring us close to the shape we want Tor Browser for Android to be in. All tickets tracked for this task can be found under the `TBA-a3` keyword.[8] For the desktop side we made further progress on our QA efforts[9] and our security settings redesign[10]. The full list of tickets closed by the Tor Browser team in November is accessible using the `TorBrowserTeam201812` keyword in our bug tracker.[11] In January there are three big tasks we'll focus on. The first is getting our mobile code into shape for the third milestone. Secondly, we try to get as much done as possible for our security settings redesign. Thirdly, efforts are under way to replace our mingw-w64/gcc toolchain with a newer one based on mingw-w64/clang for Windows to be able to keep pace with the changes in Firefox code.[12] Additionally, we plan to start working on making Tor Launcher and Torbutton compatible with the next Firefox ESR (which is supposed to be 68).[13][14] All tickets on our radar for this month can be seen with the `TorBrowserTeam201901` keyword in our bug tracker.[15] Georg [1] https://blog.torproject.org/new-release-tor-browser-804 [2] https://blog.torproject.org/new-release-tor-browser-85a6 [3] https://trac.torproject.org/projects/tor/ticket/1623 [4] https://trac.torproject.org/projects/tor/ticket/26475 [5] https://trac.torproject.org/projects/tor/ticket/26381 [6] https://trac.torproject.org/projects/tor/ticket/25164 [7] https://trac.torproject.org/projects/tor/ticket/26843 [8] https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~TBA… [9] https://trac.torproject.org/projects/tor/ticket/27105 [10] https://trac.torproject.org/projects/tor/ticket/25658 [11] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [12] https://trac.torproject.org/projects/tor/ticket/28716 [13] https://trac.torproject.org/projects/tor/ticket/28044 [14] https://trac.torproject.org/projects/tor/ticket/10760 [15] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

Notes from January 10 2019 Vegas team meeting
by Karsten Loesing 11 Jan '19

11 Jan '19

Notes for January 10 2019 meeting: Gaba (offline in a conflict resolution workshop): 1) S8 reports 2) Anti-censorship position decided. 3) Network team 3.1) modularization project and anti-censorship project starting 4) Collecting funding proposals for a couple of grant opportunities Arturo: 1) Will be releasing OONI Probe mobile 2.0 next week and working towards that 2) Published a blog post together with CAIDA on internet disruption in Gabon https://ooni.torproject.org/post/gabon-internet-disruption/ 3) Formed a partnership with ASUTIC from Senegal: https://twitter.com/OpenObservatory/status/1083096397161742336 isabela: 1) Sent invoice for Mozilla match 2) Helping organize fundraising 2019 roadmap 3) Working on 'there is no dark web' strategy -> 4) Working on response for OTF onion services proposal 5) Coordinating f2f meeting with Sida and presentation to Sida staff about Tor and our work with them (jan 30th) 6) Coordinating follow up with Mozilla - outcomes from our meeting at the All Hands 7) Follow up with media inquires and connecting with major donors Georg: 1. Dealing with backlog after vacation 2. Where are we with our blog comments policy? [see my update - Alison][Looks good - Georg] Sarah: 1) Working on campaign results and will send with December Fundraising report today. 2) Thanking campaign donors. 3) Connecting with major donors. 4) Planning for major donor and monthly donor program launch. 5) Granted funding for modularization work. 6) Al submitted a proposal for UX work. 7) Plotting out 2019 grant/foundation strategy. Alison: 1) Alison is working on all things LFI -- recruitment, curriculum revisions, website stuff 2) lots of Sponsor9 stuff happening -- upcoming travel and contact with partners 3) Colin is planning a relay operator meetup at FOSDEM 4) Maggie is working on volunteer coordination 5) We are all adding our ideas to a doc for the DRL SOI Antonela: 1) working on TBA8.5a 2) reviewing OTF onion services proposal 3) organizing Usability Research for 2019 4) reviewing tpo.org and tpo.org/about staging 5) asked sarah for the tpo.org/sponsors content 6) working on our new 2019/2020 outreach material 7) working on illustrations for tpo.org 8) preparing my talk for Fosdem 9) working on OONI country pages 10) Added a list of ideas at the DRL SOI doc 11) preparing next week Mozilla Monthly meeting, we will do a recap of what happened in All Hands Roger: ===Things I did: - Reviewed three more Usenix Security submissions; discussion continues. - Did three more safety board reviews / assessments. - Helped do further revisions of our RACE proposal; kept talking to our PM. - Advised Rob and Micah on a Shadow proposal we're hoping to do. - Helped move forward the anticensorship team selection. - Pulled together and submitted our Sponsor3 final report and outcome document. - Wrote two team mission-roadmaps (anti-censorship and network health). - My Fosdem main-track talk got in - I asked Antonela to help clean up my Tor slides. - Paul and I might go to NYC in March to debate Tor with NYPD folks. - Dealt with email disasters. Still somewhat ongoing. Let me know if I've dropped something. ===Questions for this group / things on my todo list: - I still need to do our SponsorM reports. That's now back to pending on me. - Should each vegas team try to write an equivalent mission-roadmap, like the two above? Could help with focusing mission, with identifying gaps, with fundraising, and with community engagement. - Should we write a 2018 annual report? It's been a while. - Can we have an employee handbook? Or even just a list of resources all in one place? I only learned last week that I can log in to adp and see my paystubs. - I have continued to drop the ball on answering the financials blog post comment full of questions that we would be smart to embrace transparency about. FYI in case anybody wants to step in or help out. - Should we take notes on the steps to a proper fundraising campaign, while it's still fresh? And/or do a retrospective. Like, there are several steps we should have started much earlier. [I am working on results and takeaways. - Sarah][I had in mind not just a retrospective, but a checklist for next time, with timing advise. -Roger] - Is somebody following the "Orbot trac consolidation" thread? Gaba or Pili maybe? Sue: 1) Finalizing month/quarter ending financial information to be able to bill our funders. 2) Did a massive reconciliation of expense reimbursements for employees and as of today will have paid out all expenses to employees that had been missed since October 2018. If you find any expenses that you feel you have not been reimbursed for please email accounting@ and I will follow-up with you directly. 3) Can I ask that team leads re-emphasize to all employees that they need to put in expense reimbursements on the current week’s time sheet and not on previous time sheets. This is how expenses are missed. As noted in my presentation in Mexico City if you have an expense for December, and it is January, you should include it on this week’s time sheet in January. Also, please add the date of the actual expense in the comments section. 4) Working on hiring contractor to assist with accounting work. 5) Finalizing 6/30/2018 audit. 6) Responded to DRL about 2016 audit findings, awaiting their response. Erin (Offline for meeting, at dispute resolution workshop with Gaba!): 1) Moving forward with anti-censorship team hiring (announcement soon) 2) Misc. personnel stuff Nick: 1) put out releases 2) building up to feature freeze on 15 Jan for 0.4.0.x 3) S8 is done; S19 and S31 are still ramping up. Steph: 1) blog posts: final count post up today 2) responding to some press inquiries 3) working on comms strategy 4) tried to share a FOSDEM stand and asked them to reconsider us to no avail. We were told by a rep we could have a "Birds of a Feather" meeting after a talk instead, but I havent heard back how to sign up for that -- if anyone finds out, lmk! and i'll keep digging 5) drafting a more specific Tor stories survey 6) social media, as always! Pili: 1) Sponsor 8 Q4 report 2) Collecting funding ideas for 2019 from teams. 3) Tor Browser Release meeting 4) Trying to get my head around budget for teams :) 5) Helping with response for OTF onion services proposal Karsten: 1) Started extending OnionPerf towards pluggable transport support. 2) Started refactoring R code in metrics-web to make it more maintainable. Mike: 1) Working on getting as much Sponsor2 (circuitpadding) stuff done by 0.4.0 freeze as possible 2) Helping with modularization plan

1 0

Topics on Internet Censorship and Surveillance (TICS): Call for Contributions
by juga 10 Jan '19

10 Jan '19

Hi, this might be of your interest: https://www.iaria.org/conferences2019/filesICN19/TICS.pdf Cheers, juga.

1 0

community team highlights -- November and December
by Alison Macrina 09 Jan '19

09 Jan '19

Behold! November 2018 Community Team highlights Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Community Portal and Support Portal ================================================================== In November we finished migrating the Tor Manual to Lektor and replaced the old manual. We updated the Tor manual screenshots to match the new UI, and added new info to the manual based on Maggie's user advocacy research. We also started creating community portal outreach kits with the UX team. Library Freedom ================================================================== Alison held weeks 23-26 of the first Library Freedom Institute cohort. The cohort worked on their final projects which were presented in December. Alison began working on recruitment for LFI cohort 2 (which will take place in 2019). We are also redesigning the Library Freedom website so that it's 50% Library Freedom Project and 50% Library Freedom Institute. Outreach/Sponsor9 ================================================================== We finalized some of our Sponsor9 travel dates for 2019. Gus continued coordination with partners in Argentina, Brazil, India, Thailand, and Indonesia. A number of us worked on the Sponsor9 Phase 1 report. Gus has also been coordinating a Tor volunteer project with the University of Sao Paulo (USP). Gus held a security workshop at BIENAL in Sao Paulo. dmr held the Aaron Swartz Day celebration in Ann Arbor @ AADL with Cryptoparty Ann Arbor. Kushal announced the dgplug Pune privacy meetup India (Kushal). Gus also held a Tor training with journalists (ABRAJI) ( https://blog.torproject.org/events/tor-training-abraji-sao-paulo). Sponsor19 ================================================================== Kat submitted the initial Sponsor19 report to the funder. Volunteers ================================================================== Maggie has been working on creating better volunteer onboarding and tasks, including trac tags for first time volunteer tasks and more. December 2018 Community Team highlights Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Community Portal and Support Portal ================================================================== We continued work on the community portal outreach kits, and followed up with the sysadmins about the support portal search function. emma moved the glossary to the support portal. Maggie worked on a Tor vs. VPN document for inclusion on the support portal. Localization ================================================================== emma, Erin, and Gus worked on organizing an AMA with Localization Lab in January. emma worked on a localization blog post. Library Freedom ================================================================== Alison wrapped up the first cohort of LFI in the first week of December. Now we're working on an analysis of the program and a curriculum review. The application period for LFI cohort two began December 10 (libraryfreedomproject.org/lfi). Alison is recruiting from various library organizations and on Twitter. She's also still working on the Library Freedom website redesign. Finally, we published an LFI EOY blog post at the end of December. Volunteers ================================================================== Maggie continues to work on volunteer onboarding and tasks with each team. Gus continued recruitment for the USP volunteers. Outreach and Sponsor9 ================================================================== Gus continued coordination with partners in India, Thailand and Indonesia, Argentina, and Brazil. Gus gave talks at Criptofesta Sao Paulo (https://blog.torproject.org/events/criptofiesta-sao-paulo), Criptofesta Salvador (https://blog.torproject.org/events/criptoaxe-salvador), Criptofesta Brasilia (https://blog.torproject.org/events/criptocerrado-brasilia), and a few private privacy workshops in Sao Paolo and Rio. Alison attended Mozilla All-Hands December 3-7. Alison submitted a RightsCon proposal for a panel of security activists from various organizations. Sponsor19 ================================================================== Kat started working on the second report for this sponsor. Relay Advocacy ================================================================== Colin resumed running once a month IRC relay operator meetings. He also started planning the FOSDEM relay operator meet-up. Steph and Colin are working on updating the relay flyers. Colin continues to work on communicating with OVH regarding relays without contactinfo added to the network. Finally, Colin has been working with Bill from EFF on a Tor relay challenge. -- Alison Macrina Community Team Lead The Tor Project

1 0

December 2018 report and January 2019 plans for the metrics team
by Karsten Loesing 09 Jan '19

09 Jan '19

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in December 2018 as well as a few expected highlights for the current month, January 2019. On behalf of the Tor metrics team, Karsten December 2018: Published technical report "Towards modernising data collection and archive for the Tor network" [1] and implemented a prototype replacement [2]. [1] https://research.torproject.org/techreports/modern-collector-2018-12-19.pdf [2] https://github.com/irl/bushel Published end-of-year campaign blog post "Strength in Numbers: Measuring Diversity in the Tor Network" [3]. [3] https://blog.torproject.org/strength-numbers-measuring-diversity-tor-network Updated the "Total consensus weights across bandwidth authorities" graph to only contain running relays and to also contain consensus numbers [4, 5, 6, 7]. [4] https://metrics.torproject.org/totalcw.html [5] https://bugs.torproject.org/28137 [6] https://bugs.torproject.org/28328 [7] https://bugs.torproject.org/28352 Updated 4 graphs containing OnionPerf data to show all sources separately rather than an aggregate number [8, 9]. [8] https://metrics.torproject.org/torperf.html [9] https://bugs.torproject.org/28603 Combined 3 graphs on consumed bandwidth into a single visualization using stacked area charts [10, 11]. [10] https://metrics.torproject.org/bandwidth-flags.html [11] https://bugs.torproject.org/28353 Found a bug [12] that broke bandwidth history graphs at the end of November 2018 and that subsequently caused glitches in the user number graphs, and re-imported missing data from November and December 2018. [12] https://gitweb.torproject.org/metrics-web.git/commit/?id=9dd35e29084ed9380c… Made a couple internal changes to the Tor Metrics website that will make it a lot easier to maintain in the future, including Java rewrites of the censorship detector [13] and parts of the advbwdist module [14], and using readr's read_csv() rather than R's save() and load() to speed up drawing graphs [15]. [13] https://bugs.torproject.org/21588 [14] https://bugs.torproject.org/28801 [15] https://bugs.torproject.org/28799 January 2019: Extend OnionPerf to support measuring with a pluggable transport. Deploy a fourth OnionPerf instance to improve vantage point diversity. Write a Tech Report that gives an overview of the Tor Metrics codebases. Use Java 8 date-time functionality [16] in more Tor Metrics codebases. [16] https://bugs.torproject.org/23752 Share more code between the modules providing data for Tor Metrics graphs [17]. [17] https://bugs.torproject.org/28342

1 0

Network team meeting notes, 8 Jan 2019
by Nick Mathewson 09 Jan '19

09 Jan '19

Hi! You can find our meeting logs here. http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-01-08-22.58.html Below are the contents of the meeting pad = Network team meeting pad! = This week's team meeting is at Tuesday at 2300 UTC on #tor-meeting on OFTC. Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1800 UTC On #tor-meeting on OFTC. January schedule: * No meeting on 31 Dec or 1 Jan * Following meeting on 8 Jan 2019, 2300 UTC. * Meeting on 14 Jan, 1800 UTC * Meeting on 21 Jan, 1800 UTC * No meeting 28 Jan; (some of) the team will be at a face-to-face meeting. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 3 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002117.html 10 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002120.html 17 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002127.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? <-- Check who is doing what on s19 and s31 on January. url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Including sbws: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… Core Tor/sbws is now part of the bug triage, CI, and reviewer assignment roles * Let's try a different way of looking at proposed tickets: https://pad.riseup.net/p/network-team-triage-2018 0.3.5 (bugs only): https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… 0.4.0: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == General todo == Please don't edit this pad with trolly stuff; if you do, you will force us to use a private pad again, even though it will make us sad. == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases * Remember to fill up actual point when you finish a task (as well as "fix" the estimate when starting the issue). * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbd… * Check other's people call for help in their entries. ------------------------------- ---- 8 January 2019 ------------------------------- == Announcements == * Teor is bringing a proposal for proposed ticket (discussion during hackweek?). https://pad.riseup.net/p/network-team-triage-2018 * We are going to start weekly checkins on anti-censorship work starting next week. I will send a mail later about it <gaba> == Discussion == * Who needs help with reviews? Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * we need a sbws reviewer for January that is not teor. who? * Sponsor 31 in da house. Modularization proposal. We have the milestones [0] and need to add tickets and start them in January. It will be included in the roadmap creation in Brussels. [0] -> Sheet milestones of this document https://storm.torproject.org/shared/a-NKHPmkxDOuAGNaFpOrd3AIXJ4mDgIbL5sIjf4… - Who is going to be doing them? * Closing tickets. Let's briefly come to an agreement on this. (closing tickets and opening new ones if there is something remaining from the old one). * S8 tickets need to be move to some other place. Who can do it this week? * Drafting Hackweek agenda. Let's find a day to meet and create the agenda. * draft agenda https://pad.riseup.net/p/tor-netteam-agenda-hackweek-2019.1-keep * poll to decide on a date https://www.systemli.org/poll/#/poll/qm6aFNWRZP/participation?encryptionKey… * Retrospective for S8 work https://pad.riseup.net/p/14rdcvvjS5ue * Network team needs and Priorities pad for DRL funding opportunity https://storm.torproject.org/shared/cDDK_EyXoIZoiOzt3YSRo3cCme0C-JAZe5nCdvb… == Recommended links == 35c3 talk on internet history with an economics perspective https://media.ccc.de/v/35c3-10019-internet_the_business_side#t=3729 == Updates == NOTE NEW FORMAT! Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: Week of 01/01 (actual): - read mails and organize work to be done by me Week of 01/07 (planned): - back into 1:1s - anti-censorship position follow up - S8 Q4 report - modularization proposal - s19 - hackweek agenda Needs help with: - getting all the tickets mark as sponsor8 out of it (close them or have them somewhere else). Some of them may go into s19. https://trac.torproject.org/projects/tor/query?status=!closed&sponsor=Spons… - please add points to the tickets you already have done (thanks dgoulet for doing it here https://trac.torproject.org/projects/tor/ticket/28020 and thanks people that added them to the spreadsheet) teor: Week of 21 Dec, 4-8 Jan (actual): High-Priority: - Sponsor 8 tasks - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - And also on networks that drop packets Week of 7 Jan (planned): High-Priority: - PrivCount proof of concept (#29004 and related tickets) Medium-Priority: - (no sbws reviews, I need to focus on PrivCount before the hackfest) - Maybe some code reviews if I get time - Sponsor 8 tasks - are these important enough to do anyway? - Ask metrics to monitor bootstrap speed - Tweak bootstrap settings to work when lots of fallbacks are down - And also on networks that drop packets Help with: - Can anyone help with PrivCount before the hackfest? (There's some work in progress code in #29004 for review) - Who can take my code reviews if I run out of time to do them? Nick: Week of 1 Jan (planned): - ? Week of 1 Jan (actual): - Worked on stable releases, backporting, etc - Solve an android compilation issue - Merged and reviewed a bunch of code Week of 7 Jan (planned): - Stable releases 0.3.3.11, 0.3.4.10, 0.3.5.7 - 28142 review and merge wtfpad patch - Help on snowflake startup issues - revise pubsub branch, time permitting, for S31 - dgoulet: Week of 01/01 (actual): - Worked only Friday after coming back from holidays. Was all about bad-relays, emails and administrative tasks. Week of 01/07 (planned): - prop289: Authenticated SENDMEs. Working on #26840 to start with. - Discussion with arma/nickm about #26871 which lead to open #29023 that is a ticket to implement a fast PRNG. - Updated the spec for #28180, they are in needs_review. ahf (will be missing at the meeting): Since last time: Sponsor 8: - Got the big parts of s8 finished. Still missing a few spec changes. Misc: - Met with HC and Benjamin from TGP and went over what has happened since last we met that is relevant for mobile: dormant mode, memory usage, etc. Week of 1/17 (planned): Sponsor 8: - Review David's spec changes for the PT STATUS/LOG messages (#28181, #28182). - Fill out q4 report and points for s8 tickets we did in q4. Sponsor 19: - Working on a document to describe how the broker works and how the WebRTC protocol work at a high level to give people some idea about the API's used for the JS/Go proxy and the Snowflake client. - Debug an issue where the JS proxy will become idle and no data progress is made during bootstrap (and thus also after bootstrap). Misc: - Next step for sysadmin hire with Linus/Hiro. - See if there is S8 tickets that makes sense for S19(?) Mike: Since last time: - Wrote code to prevent circuitpadding from attempting to renegotiate after failure. - Did final triage of outstanding Sponsor2 padding issues. - Reviewed asn's circuitpadding tickets (#28780 and #28634) - Reviewed other tickets Week of 1/17 (planned): - Fix up issues from circuitpadding reviews - Help asn with #28780 and #28634 catalyst: week of 12/17 (2018-W51) (planned): - cleaning up orconn-tracker for review -- mostly it needs some commits detangled (mostly done, after much wrestling with interactive git rebase), and more documentation in commit messages and comments, also changelogs - assess testing situation on orconn-tracker; write new tests as needed - if there's time, work on reporting intermediate application circuit building progress during bootstrap (#27104) -- a lot of the work is already in orconn-tracker - adjusting sponsor8 tickets to better reflect reality - worked through the weekend so i might take some time off (but still reachable on Signal; IRC and email higher latency) week of 12/17 (2018-W51) (actual): - finished #27167 - opened new tickets to clean up after #27167 week of 12/24 (2018-W52) (actual): - TPI holiday week of 12/31 (2019-W01) (actual): - TPI holiday 12/31, 01/01 - reviewed some small tickets - made progress on cleaning up control-spec changes for new bootstrap phases - minor debugging on IRC of mysterious tor restarts - #28929 (typo fix for new bootstrap message) week of 01/07 (2019-W02) (planned): - finish up control-spec changes for new bootstrap phases - continue cleaning up sponsor8 bookkeeping - move relevant things from sponsor8 to sponsor19 - review more pubsub stuff as it comes up - think about more long-term stuff - ticket reviews

3 2

Tor Browser meeting, 7 Jan 2019
by Georg Koppen 08 Jan '19

08 Jan '19

Hi everyone! Yesterday we had our first Tor Browser meeting in 2019. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-01-07-18.58.log… and the notes from our pad are below: Discussion: -upcoming releases/Tor Browser 8.5 (GeKo: 1/29 and 3/19 are the next release dates; 8.5 stable could get out at the end of march then) -larger project planning: tor-launcher/torbutton -> webextensions -> inclusion in tor-browser directly (GeKo: we plan to nail down the final plan next week; mcs/brade will lead the tor launcher efforts, and igt0 and GeKo will look into Torbutton) tjr - We're going to nominate this for backport: Bug 1446472 - privacy.resistFingerprinting is true blocks QR code (canvas) on web.whatsapp.com without any notice - If Tor wants it earlier you could bring it in at your leisure - mingw-clang - Working on --enable-sandbox on esr: I thought I had this working already but I guess not. - To do this, I need to backport a bunch of build patches so I can backport pdb generation =( - Working on --enable-accessibility in -central - Hit a weird runtime failure jacek thought he fixed. - USENIX reviews taking time. But finding fun ideas to maybe do sometime in the future! - Determined a small path forward for rust code that uses networking APIs: https://bugzilla.mozilla.org/show_bug.cgi?id=1376621#c12 - I'm not certain how much different this is from Tor's current activity; but something to try... - Expected leave is end of month, could be earlier depending GeKo: -back from vacation -did stay away from my computer (mostly) -worked on the mingw-w64-clang toolchain (bug 28716) This Week: -finish up #28716 -test the mingw-w64-clang toolchain with Firefox code we ship and provide a proper patch for switching the nightly Firefox build part to it (#28238) -begin-of-the-month-admin dance -timesheets! -reviews -finally comment on the ideas in doc for #3600 -pospeselr: Can you take over the work on the security settings redesign (#25658)? I fear I will get again distracted while trying to help with TBA-a3 and other stuff and we should get the redesign into 8.5 if possible. - pospeselr: yes can do! (Great, thanks! GeKo) mcs and brade: Past three weeks: - More work on #28885 (notify users that update is downloading). - Responded to nickm's tor-dev message r.e. tor's new dormant mode. [Do we need a ticket for Tor Browser related work that needs to be done in the wake of it? - GeKo Yes. I will create a ticket. -mcs] - Provided some feedback on the Tor Browser developer job announcement draft. - Took some time off for Christmas / end of year. - Worked on end of quarter/end of year administrative tasks. - Helped a little with bug triage. This week: - Finish end of quarter/end of year administrative tasks. - Continue working on #28885 (notify users that update is downloading). pospeselr: Past N weeks: - knocked out sick for a lot of it :( - initial Tor Browser uplift sync w/ arthur, tjr, ethan, and steven - feedback from CRs: - #12885 (windows jumplists broken) - discovered we've a disk leak for all windows versions, put up a patch that will fix future clean installs and created a new issue for cleaning up upgrades - created ticket #28996 to find and delete jumplist storage files - basically to fix this on existing installs we need to scrape all the files in a particular user directory, look for 'Tor Browser' strings in them, and delete them is this sort of approach a good patch for Tor Browser or is this too 'hacky' ? (GeKo: if we can be sure just to deal with jumplist files, that's okay with me)V - #25702 (tb icon re-branding) - regarding general icon weirdness and cropping/scaling: on linux there seems to be a lot of weird window-manager specific issues surrounding how the 'Icon' entry is handled in the Tor Browser .desktop file - both gnome and cinnamon use a cropped and scaled-down version of the tb icon in some places (alt-tab, taskbar window list, window overviews) but the correct icon in others (in the file-browser) - seems to be a caching issue since the places where the icon is broken doesn't update when the source icon or the Icon entry is updated - only hypothesis around the various window-manager icon caching issues is that our self-modifying .desktop file might be fucking with things, but would need to dig deeper - general solution for the cropping issue in-browser and the installer (you can see the same cropping issue in the windows installer) is to just update the assets and give a bit of margin around the edges (Sounds good to me. I guess we should try to stay away from as many rabbit holes as we can here. :) - GeKo) #3600 (redirect cookie isolation) - synced with steven about work his team has done in this space, but disappointed to find out they don't have anything 'as well thought out as your doc' - best way forward for now seems to tjr's suggestion: "Allow Redirects, but Neuter Their Tracking Ability" This Week: - meetings meetings: uplift, release - #25702+#28546 (rebrand) : update patch to add some margin to icons to work-around the squashed circle edge issue - #25658 (security settings redesign) - look into back-porting 1446472 (Should be fair game for the next alpha due on 1/29 - GeKo) igt0: Past three weeks: - Started the UI side of Circuit display for mobile(#25764) - Vacations! This week: - Finish the UI side of the circuit display(#25764) - Integrate the circuit display UI (Java/Android) with the logic side(torbutton/javascript). (#25764) boklm: Since last meeting: - fixed some testsuite issues: #27115, #28876, #28904 - vacations This week: - continue work on testsuite (fixing all tests, or temporarily disabling them if they require more work), and binutils issue pili: - Happy new Year everyone! This week: - catching up with email - Sponsor 8 report - Looking ahead at funding proposals due in the next few months - Tor Browser Team Priorities and needs pad for DRL SOI due 2nd Feb: https://storm.torproject.org/shared/DWoSG7f1qUTdhXz1l9i7bL-SYxIe00fB_a16l44… - Starting to think about Sponsor 19 Browser related work - Tor Browser Release meeting this week - anyone we want input from that we should invite? (GeKo: maybe the fundraising folks to make sure what we should do with the banner and what should come afterwards) anto: Past N weeks: - #28329 TBA + Orbot - matt, could we sync about what is needed from me here now? - #23888 Snowflake web extension - someone in this team will/want to work/review it? (GeKo: Review should be possible; we'll coordinate what we can/should do here) sisbell: Last week: - #29003 - Investigated goptbundle integration into tor-browser-build. Did some initial work, (Pluto2/goptbundle about 1 week of work to fully integrate) - #27609 - Evaluate Tor Onion Proxy - have initial tor-browser-build project setup. - #28803 - Integrate building PT - Got patches done to build with tor-browser-builds. Created gradle downloads file. Still need goptbundle integration and packaging. This Week: - #29003, #28803 sysrqb: EOY and Last week: Worked on FastLane configuration Reviewed Google Play comments and reviews A little vacation and much family time This week: Write email about Google Play reviews and comment Open tickets for the comments, as needed Create patch for FastLane stuff At Real World Crypto (RWC) this week TBA onboarding stuff Georg

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project