tor-project March 2019

tor-project@lists.torproject.org

20 participants
29 discussions

OONI Monthly Report: February 2019
by Maria Xynou 15 Mar '19

15 Mar '19

Hello, In February 2019, the OONI team established 3 new partnerships and published a research report on media censorship amid Cuba's 2019 constitutional referendum. Further information is provided below. ## Established new partnerships We are excited to have established new partnerships with: * Software Freedom Law Centre (India) * COMPSUDEV: Community Participation in Sustainable Development (Cameroon) * R3D: Red en Defensa de los Derechos Digitales (Mexico) ## Report on media censorship in Cuba amid 2019 constitutional referendum During Cuba's 2019 constitutional referendum, several independent media websites were blocked. We collaborated with locals on producing the following report: https://ooni.torproject.org/post/cuba-referendum/ ## OONI Probe Android 2.0.0 Incident Report We published a report to share details about the OONI Probe Android 2.0.0 bug, what we did to fully resolve it, and what we are doing to prevent similar incidents from recurring in the future: https://ooni.io/post/ooni-probe-android-200-incident/ ## OONI Software Development Guidelines Following the OONI Probe Android 2.0.0 incident, we wrote and published a document which explains the software development practices that the OONI team will be following: https://ooni.io/post/ooni-software-development-guidelines/ It is particularly important that we improve upon the testing of our apps (both in terms of unit tests and end-to-end integration tests), strengthen our quality assurance and release management workflow, and improve upon how we do code review for all of our software projects. Details about the software development practices that the OONI team (and anyone else contributing to OONI software projects) should follow are provided in our published guidelines. We also started to improve the testing of the OONI Probe Android and iOS apps by writing Unit & Integration tests: * Probe Android: https://github.com/ooni/probe-android/pull/195 * Probe iOS: https://github.com/ooni/probe-ios/pull/246 ## Beta release of MK v0.10 As a requirement to integrating a new Psiphon test into the OONI Probe apps, we have been making a number of changes to Measurement Kit (MK). We released a beta (MK v0.10) that includes these changes: https://github.com/measurement-kit/measurement-kit/releases/tag/v0.10.0-beta ## Community activities ### Censorship measurement campaigns Leading up to and during Nigeria's and Senegal's 2019 elections, our Nigerian (Paradigm Initiative) and Senegalese (ASUTIC) partners coordinated local OONI Probe censorship measurement testing. In addition to coordinating local testing, ASUTIC updated the Senegalese test list (https://github.com/citizenlab/test-lists/pull/434) and Paradigm Initiative encouraged the use of OONI Probe through their relevant guide ("How to Remain Online During Internet Disruptions" - Verifying and testing blocked websites, apps, and social media platforms): https://paradigmhq.org/download/how-to-remain-online-during-internet-disrup… Our Venezuelan partners, Venezuela Inteligente and IPYS Venezuela, continued to monitor emerging censorship events by coordinating local OONI Probe testing. They confirmed the temporary blocking of YouTube and many other services through the use of OONI Probe (as documented, for example, by IPYS Venezuela: https://ipysvenezuela.org/alerta/23f-balance-ipysve-medidas-de-censura-y-ag…). ### OONI Run button page To support censorship measurement campaigns, we set up a quick page on our website that includes OONI Run buttons: https://ooni.io/get-involved/run/ OONI Probe mobile app users can tap on these buttons to test entire country-specific test lists, as well as select social media and VPN sites. We recently added an OONI Run button to enable the testing of Wikipedia URLs as well. We will likely continue to populate this page with more OONI Run buttons over time (based on community requests). ### FOSDEM On 2nd February 2019, OONI's Elio participated at FOSDEM where he facilitated a session (https://fosdem.org/2019/schedule/event/ux_overhaul_ooni/), providing an overview of the UX overhaul of the OONI Probe mobile app. ## BarCamp Chiang Mai On 16th February 2019, OONI's Lorenzo presented OONI at the BarCamp event (https://www.barcampchiangmai.com/) in Chiang Mai, Thailand. As part of this 30-minute session, Lorenzo explained how to use OONI Probe and OONI data to examine internet censorship. Our previous research with the Thai Netizen Network and Sinar Project, examining internet censorship in Thailand (https://ooni.io/post/thailand-internet-censorship/), was also presented and discussed as part of the event. ## OONI workshop in Bangkok On 17th February 2019, OONI's Lorenzo and our local partners jointly facilitated a day-long OONI workshop (10am to 6:30pm) in Bangkok, Thailand, for local human rights defenders. The workshop covered the following: * How the internet works / types of network interference * Introduction to censorship measurement research (and potential risks) * Installing & using OONI Probe * Translating OONI Probe * Legal, social and political context from Thailand and other Southeast Asian countries * Contributing to test lists * Using OONI Explorer to find and interpret censorship measurement data * Producing research based on OONI data * Using OONI Run to coordinate censorship measurement campaigns (particularly during political events) ## Userbase In February 2019, OONI Probe was run 258,610 times from 4,544 different vantage points in 209 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ 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

Notes from March 14 2019 Vegas team meeting
by Karsten Loesing 15 Mar '19

15 Mar '19

Notes for March 14 2019 meeting: Nick: 1) All's well 2) It's going to be tricky managing without Gaba for a couple of weeks, but I think we're fine. Mike: 1) Scalability discussions; little worried about momentum and resources 2) Feeling a bit torn between explicit and implicit rolls, treading water. Arturo: 1) Back in European time 2) Working on a beta release for OONI Explorer 3) Have started the OONI Backend engineer interviews 4) Work on improvements to our data formats and next generation OONI Collector specification: https://github.com/ooni/spec/pull/128 isabela: 1) working on the launch of feedback cycle 2019 (aka first feedback cycle ever on Tor) 2) working on invite letter for dev meeting 3) working on employee handbook with Erin and other HR stuff 4) getting board book together for board meeting (need to share with them by the end of this coming week) 5) Trying to get my quarterly update out before tea time next week! 6) got LibrePlanet slides done for Steph (we will have 200 shirts for the booth plus stickers) Sarah: 1) Cryptocurrency donation page should launch today or tomorrow 2) Outreachy campaign did not raise the $6,500 needed for an intern this go around. We will plan to apply for the round that starts in December. 3) Al submitted two SOIs to DRL, a proposal to Craigslist Foundation, and will submit a proposal to the Costa Rican Embassy this week. 4) Working on projections for the remainder of FY19 and FY20 with Isa. Georg: 1) Moving towards Tor Browser 8.5 (with all the pain and fun finalizing a major release while trying to keep within the envisioned timeframe) Erin: 1) Screening for browser and OONI dev positions 2) Launching the feedback/review process Friday 3) Working with Isa this week in Seattle Pili: 1) Started working on Sponsor 8 report 2) Worked on Proposal for British Embassy in San Jose for Community Team work 3) Finished off Tor Browser 2 year vision write up 4) Started thinking about Google Season of Docs 5) A bit of work on Outreachy before we decided we weren't able to participate this round Karsten: 1) Changed metrics-web to run as a Java-only application rather than being executed by Ant (#29166). 2) Wrote integration tests for metrics-web's data-processing modules (#29425). 3) Evaluated OnionPerf measurements with regard to worst-case latency (#29773) and bandwidth (#29772). 4) Wrote more parts of the last remaining Sponsor 13 technical report that is due by end of this month. Antonela: 1) Reviewed donate.tpo/crypto 2) 8.5 Review, TBA Network Settings and TB Security Settings 3) #28800 - New Identity 4) Organizing IFF activities 5) Printing outreach material 6) Outreachy pre-proposal submitted but it will not happen 7) Working with Caroline on debriefing India and Thailand 8) Review OONI Explorer landing page with Elio 9) OONI retrospective, Tor Browser new hire interview, Mozilla/Tor monthly meeting 10) Doing things around tpo.org to launch Sue: 1) Working on second part of Sida Audit with the Auditors 2) DRL call re audit findings 2016 3) Working on new Accounting and Grants Management Policies and Procedures 4) Normal accounting stuff

1 0

Re: [tor-project] meetbot PSA
by Tom Ritter 12 Mar '19

12 Mar '19

On Tue, 12 Mar 2019 at 14:18, Antoine Beaupré <anarcat(a)orangeseeds.org> wrote: > > On 2019-03-12 06:23:25, Tom Ritter wrote: > > As an alternative to meetbot - in the future - maybe we could consider > > logbot? https://mozilla.logbot.info/ > > > > I have found it very helpful and feature full, with full text search online. > > > > We could invite it only for meetings, and/or we could start publicly > > logging public channels. > > Well, that's a whole other ballgame, for one. Sure, logging things other than meetings would be a discussion absolutely. > Second, it doesn't seem to > support "meeting" features like agenda, chair, and so on. Oh yeah, I forgot those features existed. We haven't use them in the browser meeting except to get frustrated by the chair requirement. -tom

1 0

meetbot PSA
by Antoine Beaupré 12 Mar '19

12 Mar '19

Hello! I'm your new friendly sysadmin! I hope I'm doing good. I'm also not a bot and should be able to pass a turing test on a good day. ;) I've so far prioritized my work mostly towards sysadmin-specific stuff (like rebuilding parts of the broken monitoring system and generally get up to speed with everything), but I'm sensitive to priorities people from the Tor project express, obviously... One of those recurring issue I've heard (other than "OMG Trac is pain!" of course) is that "MeetBot is down!" The service is ran by the good folks at Debian, but has fallen somewhat in disarray in recent years. All the gory details are of course in Trac: https://trac.torproject.org/projects/tor/ticket/29680 ... but the short story is that I've considered setting up a replacement when the service was completely offline. Since then, the Debian folks brought the machine back up (you can see logs at http://meetbot.debian.net/) but the bot is still struggling to return. I am hoping they bring it back up themselves and restore the service. If that doesn't happen, I might squat a VM somewhere to restore some sort of service myself within TPO. But considering the number of things I'm juggling with right now, I'd be very happy with not adding a new service to the list on my first (well, second) week on the job. So I hope people don't mind the little extra wait while the good folks at Debian figure out what they want to do with the service in the long term. As weasel says, we don't want to reimplement all the services on the internet ourselves, do we? :) So if that problem can be fixed itself, I'll be more than happy than watch it heal. If not, we'll figure something out. Note that I've made sure the ArchiveBot (from ArchiveTeam) takes a look at the site so we have a copy as well in the Internet Archive. See you around! A. PS: the best place to report problems like this is still Trac. File a ticket in the "Internal Services/Tor Sysadmin Team" and I'll definitely look at it. -- Cyberspace. A consensual hallucination experienced daily by billions of legitimate operators, in every nation, by children being taught mathematical concepts... - William Gibson

2 2

Tor Browser Vision Brainstorm: Friday 8th February @ 20:00 UTC
by Pili Guerra 12 Mar '19

12 Mar '19

Hi everyone, We’ll be holding a brainstorming session this Friday 8th February @ 20:00 UTC over on #tor-meeting to discuss our joint vision for the Tor Browser in the near future. Please join us! We would love to hear your views. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

5 7

Tor Browser team meeting notes, 11 March
by Georg Koppen 11 Mar '19

11 Mar '19

Hi! Our weekly meeting just ended, this time without meetbot as it was sick. Thus, here come just notes from the pad this time: Discussion: -browser dev hiring (GeKo: We'll do the next interview on IRC but think it's generally good to "get to know" folks we never met before via a video call before hiring) pospeselr: Last week: #25658 security level patch 29120 uplift investigated #29554, #23359 This week: #25658 fixes: right-to-left language support #29554 patch (fix about:preferences links not working correctly) #23359 patch (https everywhere adds itself back to toolbar on second launch, probably related to our torbutton code pointed out by intrigeri) tjr (probably absent) - Letterboxing: (GeKo: I'll write an email to tbb-dev, probably tomorrow, trying to get answers to all of your questions :) ) My goal for March is to do more data analysis on screen resolutions and put forward a proposal for 'We should use these set of dimensions' Before I do that; I'd like to get confirmation that this is something Tor Browser wants to at last try to ship in Alpha. My questions: - if it was ready in a 60-based Alpha would you ship it then or would you want to wait until 68? - what is the minimal viable product user experience wise? - does the margin needed different color or watermark? - do you need a button to disable it globally or after an individual resize? - do you need it to work on mobile? - for very low resolution - under 100 pixels in a dimension - does it need to do something intelligent or just not do any margins at all? - does it need a user walkthrough explainer? (Probably I think... maybe you can start thinking of how that would look?) - My current analysis is of the form https://ritter.vg/misc/ff/Content%20Resolution%20Analysis.html - See next steps in particular about defining a ftness function) - Is this an appropriate path forward? How often do you want me to stop and get review and from whom? - (I'm optimistic that this python based analysis it Is flexible enough that it can be easily changed, so I could to perform most of the analysis without bugging people) Reminder, it is in Nightly under the pref (you must add it) privacy.resistFingerprinting.letterboxing mcs and brade: Last week: - Fixed #29445 (Tor Browser is denying ESR policies.json). - Fixed #22402 (Improve the "For assistance" link). - Posted patches for #29440 (Update about:tor when Tor Browser is updated). - Posted a revised patch for #29627 (Moat: add support for obfsproxy's meek_lite). - Reviewed the Tor Launcher patch in #29430 (Use uTLS for meek TLS camouflage in Tor Browser). - Started review of #25658 (security slider replacement). - Helped with triage of incoming bugs. This week/soon: - Review #25658 (security slider replacement). - Work on #28628 (Introduce New Security Settings to users). - Investigate #29630 (TorBrowser creates empty directory in "/tmp”). - Investigate #27484 comment:13 (DDG onboarding doorhanger disappears after tab switch). - For #28044, revise proposal 102 to take into account intrigeri’s comments as well as some things we learned during implementation. - Review the Firefox updater security audit report. GeKo: Last Week: -reviews (#29194, #27486, #29445, #22402, #28329, #29572, #29440) - updated my patch for #28802 - investigated broken git repo updating in our build system (#29572) - finish begin-of-the-month team admin stuff This week: - release prep - help with reviews for the alpha release - antonela: we could need some UI guidance for the New Identity for Android feature (#28800) - how do we introduce the new security slider feature to users that already have done the UI tour? After all the bubble just says: "New to Tor Browser? Let's get started." Do we in general need a different pointer for newly introduced features? (GeKo: Antonela updates the ticket (#28628) with points that came up during the discussion) [tjr] Moz did that for the new tracking protection, it was a three step tutorial thing sisbell: Last week: - 29313: tor-android-service browser build (ready for review) - removed native build, added back in classes that Firefox android app needs - 29574 Configure Orbot project to use TOPL (ready for review) - fixes for duplicate class errors - 29575 Configure Firefox project to use TOPL (ready for review) - tested integrated APK - opened a couple of issues at TOPL project, opened issue at Orbot project regarding moving android resources from orbotservice to app module - looking to move tor-android-service project hosted on GitHub to guardianproject or torproject This Week: - Resolve bug where final bootstrap is not updating in UI in Android Browser - Work on moving resources out of orbotservice and tor-android-service libraries - submit PR for various fixes to TOPL project - respond to any code reviews antonela: Last week: - #29440 Update about:tor UI review - #25658 Security Settings UI review - #28628 Introducing the new Security Settings This week: - Mozilla/Tor monthly meeting: Anything we want to show? - 8.5 Review, TBA and TB - #28800 - New Identity - Letterboxing sysrqb: - Last week: #28329 (TBA configuration UI) BridgeDB patch review - This week #28329 testing and integration Release prep boklm: Last week: - made some patches for: - #25876 (Source release tarballs for Tor Browser) - #29572 (Fetching latest commits fails when building testbuilds) - #29675 (Nightly build should fail if "make fetch" fails) - #29667 (Add android-x86 to nightly builds) - updated patch for #26323 after review comments (Build 32bit Linux bundles on 64bit systems) This week: - continue work on #27137 and testsuite - some reviews - work on #25623 (Disable network during build) - help with build of new releases pili: Last week: - Outreachy application - UX ticket triage This week: - Start thinking about capacity planning for browser team - Start planning for OTF Onion Services proposal - Sponsor 8 Final report - Tor Browser 2 year vision write up - still very late with this!! - More UX ticket triage Georg

1 0

Network team meeting notes, 11 March
by Nick Mathewson 11 Mar '19

11 Mar '19

Hi! Here are the notes from our meeting of today. Meetbot is still down, so there's no log to attach. = Network team meeting pad! = This week's team meeting is at Monday 11 March at 1700 UTC on #tor-meeting on OFTC. Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019 On #tor-meeting on OFTC. March schedule: * Tuesday 5 March at 2300 UTC * Monday 11 March at 1700 UTC * Monday 18 March at 1700 UTC * Monday 25 March at 1700 UTC April schedule notes: * Monday 22 April is an Easter public holiday May schedule notes: * teor will be on leave at the start of May (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.) 11 Feb: https://lists.torproject.org/pipermail/tor-project/2019-February/002214.html 19 Feb: https://lists.torproject.org/pipermail/tor-project/2019-February/002225.html 25 Feb: https://lists.torproject.org/pipermail/tor-project/2019-March/002236.html 5 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002244.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… <-- filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! Here are the needs-review tickets, by reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&reviewer… 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 == 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 the 'actual point' field when you close a ticket. We need those to calculate velocity. * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbd… * Check other's people call for help in their entries. ------------------------------- ---- 11 March 2019 ------------------------------- == Announcements == - The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0. - No more backports to 0.3.3; support ended a few weeks ago! - if you're a maintainer, please update your git scripts from the tor repository! - US DST began last Sunday; let's be careful for schedules next week [catalyst: are we going to follow US DST for the Monday meetings as we have before?] yes -- previously decided that Monday meetings move with US DST; see https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam We need to prioritize sbws's reviews this month as Juga is wrapping up their work in March. == Discussion == === Fixing IPv6-only network failures === Tor Browser is going to test the new ClientAutoIPv6ORPort option in Tor Browser Alpha. (Geko says, "looking at teor's comment in #29641 it seems we need #27647 fixed first?") === Tor Meeting === Does the network team have an extra roadmap day? we will only have 3 days in total (12, 13, 14th of July) When can we book tickets? wait a little please === Policy planning === We're still seeing how the draft merge policy works: review at the end of March. Can we review it the first week of April? Let's talk about the team capacity policy when Gaba gets back? Yes. I will be back the first week of April. == Recommended links == "Tech companies could change these things to make your life easier and protect your digital security and privacy. Why haven’t they yet?" https://fixitalready.eff.org/ On gitlab release management (they have a role that rotates) https://gitlab.com/gitlab-org/release/docs/blob/master/general/monthly.md == 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 03/04 (actual): - processes https://gitlab.com/gabelula/tor-documentation-processes Week of 03/11 (planned): - tor scaling meeting - roadmap checking before leaving - traveling on the 14th teor: (online!) Week of 4 Mar (planned): Roadmap Coding (3 days per week): - Bandwidth stats for PrivCount: #29019, #17036, #29005 Roadmap Reviews: - nickm's chutney/tor CI tickets Other: - Update merge scripts to remove 033 - Large reviews - Put the merge policy on the wiki - Triage my email - Leave admin - Blocked: Stable maintainer triage and merges Week of 4 Mar (actual): Roadmap Coding (3 days per week): - Bandwidth stats for PrivCount: #29019, #17036, #29005 - CI with Chutney/Tor: #29703, #29729, #27912, #29280 Reviews: - 9/10 assigned reviews, including roadmap reviews - Didn't do #23588, because it's waiting on other tickets (see ticket for details) Other: - Bugfixes for #28656, #29643, #29706 - Revised #29640, #23576 - Ticket herding and opening bugfix tickets - Updated my user page, so the tickets are in priority order - Helped diagnose a bunch of different bugs, including #29707 in sbws - Partly Blocked: Stable maintainer triage and merges Week of 11 Mar (planned): Bug triage rotation - Write nice page with queries for bug triage rotation, like https://trac.torproject.org/projects/tor/wiki/user/teor Roadmap Coding (3 days per week): - CI with Chutney/Tor: #29729, #27912, #29280 - Backport merges for CI with Chutney/Tor - Bandwidth stats for PrivCount: #29019, #17036, #29005 - Rearrange the commits in a nice order on a bunch of new branches Roadmap Reviews: - Review nickm's parts of the CI with Chutney/Tor tickets - Other assigned reviews Other: - After chutney CI merges, do other stable maintainer triage and merges - Leave admin - If I have any time left over, review admin backlog, and plan other admin Blocked: (I wrote this list on Friday - it might be outdated) Dev work and merges are slow due to lots of CI failures: - Intermittent CI failures: Fixes needed: #29500 (circuit padding time) #29693 (circuit padding stochastic) #29437 (test-stem) Review and merge needed: #29706 (SRV memory management) Help with: Nick: Week of 4 March (planned): - Come up with a list of recommended versions - Reviews, merges. There are some big branches here, so I'll need longer than usual - Update my rup.py example code for the latest prop295 - Find some 040-must items to finish - Next steps on CI (ask teor) - Next steps on pubsub (pending catalyst review) Week of 4 March (actual): - Reviews and merges -- lots. these took a lot of time. - Made list of versions to un-recommend - Examined test determinism. Need to ask George and Mike about PRNG determinism on padding tests. - Fixed fork issues in thread-prng code (#29668) - Tons of email & meetings :/ Week of 11 March (planned): - Next steps on CI: get travis support running on chutney, and chutney in tor's travis. [Pending Teor's revisions on #27912] - Next steps on pubsub (per catalyst's review) - Work on #29357 (ActiveOnStartup option for TB) as an 040-must item - Update my rup.py example code for the latest prop295 - Sponsor 31 meeting - Scaling meeting - Possibly, kick off work on some more of my sponsor 19 and 31 stuff. - 29223 standardized abbrevs? - 29269 bridge stats? dgoulet (missing meeting): Week of 25 Feb (actual) - Proposal changes with teor on #26288. Code was put in needs_review. - BridgeDB tickets. The majority is in needs_review waiting on sysrqb. - Worked on the git maintenance scripts. - Reviews and open couple tickets. Week of 4 Mar (planned) - AFK. Mike: Week of 3/04 (planned) - Finish #29204 and #29494 - More research and scaling mails Week of 3/04 (actual): - Finished #29204 - Worked on reproducing a vanguards issue; found some onion service bugs - Lost glasses; got sick :/ Week of 3/11 (planned): - Vanguards workarounds for onion service bugs - Tor scalability - #28686 (Nick's stray review comments for wtfpad) - #28780 - flag for keeping circuit open (asn: are we sure this is actually needed?) catalyst: week of 03/04 (2019-W10) (planned): - reviews - finish up commenting on pubsub - expense reporting - make some progress on #28925 (distinguish proxy vs PT in bootstrap) if pubsub stuff works out well week of 03/04 (2019-W10) (actual): - rotations - finished POC hooking up pubsub to bootstrap -- builds but fails tests because pubsub isn't connected to mainloop yet - more comments on pubsub - chatted with juga somewhat about strategies to manage working simultaneously on multiple branches in git - updated wiki to clarify meeting times a bit better (including which canonical time zone is canonical for each meeting) week of 03/11 (2019-W11) (planned): - reviews - write up architectural comments on pubsub - work with nickm on pubsub revisions - work some more on #28925 (distinguish proxy vs PT in bootstrap) based on previous work hooking up pubsub to bootstrap help with: - nickm, progress on #28925 would go more smoothly if you can commit some patches to your pubsub pull request to hook up pubsub to the mainloop. do you think you'll have time to do this soon? - okay, will try to do it this week -nickm juga: Week 4 March (planned): - Release sbws 1.0.3 - Test all the children to Monitor relays that are not measured by each sbws instance (#28547) in the public network and fix them if need it Week 4 March (actual) - Released sbws 1.0.3 - Worked on AsyncResults have no timeout (#28864) - Worked on sbws keeps the number of AsyncResults less than the number of threads #28865) - Worked on Create an script to automate releases (#29294) - Worked on Add KeyValues to monitor relays that are not measured (#29591) - Created (unofficial) debian package/helped dirauth to set sbws(#29290) - Worked on converting correctly units, catched thanks to deploying in production sbws (#29707) - Revised and merged tickets - Created new tickets which i should get done at the end of the month - Closed tickets that do not apply anymore Week 11 March (plan) - New patch release with #29707 fix (and new unofficial debian package) - Work on or merge Stop the integration tests http server when the tests end (#28774) - Work on or merge Create an script to automate releases (#29294) - Continue with Work out how sbws can report excluded relays in the bandwidth file (#28563) - When sbws stops making progress, log a warning (#28652) - Work out how long it takes sbws to measure the network (#28983) Needs help with: - Questions in https://pad.riseup.net/p/fRWXN94cRnJDhJHBj1yt (you can just reply there) asn: [It's public holiday in Greece (clean monday). I will probably be outside for dinner tonight.] Week of 03/04 (actual): - Pushed #29221 into needs_review. - Started work on #28636. Mid-way there. - Pushed #29298 revisions. - Did merges. - Did reviews. Week of 03/11 (planned): - Do revisions for #29221, #29298. - Finish up roadmap task #29298. - Do pending merges/reviews. - Check updates on #5708. - Check new HSv3 bugs that dgoulet opened (#29665, #29669). Help with: ahf: Week of 3/5 (planned) Sponsor 19: - Finish #29207 - Talk with cohosh, gaba, and kat about Report #2 Misc: - End of month stuff: Harvest etc. Week of 3/5 (actually): Sponsor 19: - Talk with cohosh about splitting up #29207 (and that will also have to happen for #29206). - Look into GeoIP interface in Tor and how we should handle that in Snowflake (cohosh just opened #29734 for this). - Ditched trying to do JSON Schema stuff in Go for #29207/#29206 since it became too weird to work with. We should do it after the prototype works. Misc: - Reviews. - Did EOM stuff. Week of 3/11: Sponsor 19: - Report #2 meeting Tuesday. - Continue with #29207/#29206 with Cohosh. - Document protocol changes for #29207/#29206

1 0

Tor Browser Release Meeting - Wednesday 13th March @ 19UTC
by Pili Guerra 11 Mar '19

11 Mar '19

Hi everyone, Just a reminder of this week’s Tor Browser Release meeting: Wednesday 13th March at 19:00 UTC on #tor-meeting as usual PSA: Please check your UTC conversions if you’ve changed your clocks this weekend as this may be at a different time to what you are expecting :) We’re full steam ahead for the security release early next week and the 8.5 stable release at the end of the month so it’s a good time to come talk to us about that. Please come with your requests, questions suggestions… we look forward to seeing you there. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

February 2019 in sysadmin land
by Linus Nordberg 11 Mar '19

11 Mar '19

Hi Tor, Here's what February looked like to the sysadmin team. # What's been done - We have hired anarcat! - Experimenting with full disk encryption of VM's. - GitLab VM setup (re: #29402). - Migration of the CiviCRM systems to new VM's with a recent OS. - Experimenting with Prometheus for trend analysis (re: #29681). - The ordinary resolving of requests and bug reports, as can be followed better over at [tickets]. [tickets] https://trac.torproject.org/projects/tor/report/44 # Upcoming new things - Getting anarcat up and running. - Trying out NextCloud for some set of Tor people, as a replacement for SVN, Sandstorm and possibly more (re: #29415). # Fact of the month Our backup server holds system backups for 77 hosts. Currently there are 338 full backups and 11886 incremental backups consuming 13 TB. Apart from system backups, we have PostgreSQL backups for five hosts, eating another 280 GB.

3 3

February 2019 report for the UX team
by Antonela Debiasi 11 Mar '19

11 Mar '19

Hello Tor, We started February in the cold Brussels. Elio and I presented the OONI and the UX team work at the Open Design dev room during FOSDEM. We got a packed room with a lot of people interested in design. Thanks, Bernard, Victoria, and Jan for the invite! You can see our presentations here https://fosdem.org/2019/schedule/track/open_source_design/ We focused our February efforts on having everything set to launch the new torproject.org. Thanks to all the people who helped us reporting bugs and sharing feedback! https://lektor-staging.torproject.org/tpo/ The community team has been traveling through India and Indonesia, and we ran user research on those countries too. Caroline is working on reporting findings of this material, and we will share it with the lists next month. Elio has been working on the new OONI Explorer redesign for a few months and now is done and under development. Take a look at the final versions https://www.figma.com/file/Z6PtVLW7YkqcTRIRsO2Qzg/Explorer-Country-Pages In collaboration with the Community team, we created outreach material focusing on the different types of user needs and expectations we have at our user base. We wrapped this project during February, and we are going to share it with our community during IFF. Come to grab one! https://share.riseup.net/#TuZ3elR8vt8WuKHtXfrw5w Last but not least, we have a #tor-ux room now (!) We are experimenting with this channel to have kickoff of new projects, tickets triage, and discussions about the work we are doing. So, if you are interested in seeing a lot of emojis, join us! Thanks, A

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project March 2019