tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

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

25 Mar '19

Hello everyone! Our weekly Tor Browser meeting just ended and, as usual, here come the link to our IRC log http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-03-25-18.32.l… and the content from our pad: Week of March 25, 2019 Discussion: - adjusting meeting time (eu is doing the daylight saving thing the coming weekend) (GeKo: We'll switch to 17:30 UTC as our meeting time; I'll announce that on tbb-dev later this week) - blockers for 8.5 (GeKo: We restructured our `tbb-8.5` tickets so that it is clearly visible what are blockers for the next alpha (`tbb-8.5-must-alpha`) and what are blockers for the stable release (`tbb-8.5-must`)) - Letterboxing (GeKo: We'll get around June to help with that and test on esr60 already) tjr - investigated getClientRects. The finding indicate that there are active fingerprinting issues from this and similar APIs that leak at least major OS version (win7 vs win10) and some OS settings. I don't *think* it's used by ad network fingerprinting (yet?) though. https://bugzilla.mozilla.org/show_bug.cgi?id=1507879 - Investigated math routines. Confirmed these leak at least major OS version, maybe minor. On Linux it probably leaks distro or system libraries Don't think it leaks hardware information - Investigated chrome:// leak. Confirmed it leaks OS and browser version. Don't think it leaks anything else except maybe language mcs and brade: Last week: - Reviewed patch and commented in #29790 (Add build option to store profile in HOME directory). - Followed up on Mozilla bug 1434666 (updater failing on Linux — cannot find libraries). (GeKo: nice that rstrong would want to help us. We should take up that offer in case we need it :) Maybe some patch uplifting help or something) - Worked on #27484 (Onboarding: unintuitive not-navigation buttons). - Monitored #28925 (Core Tor: distinguish PT vs proxy for real in bootstrap tracker). This week: - Review patch for #29825 (Intelligently insert the Security Level button) - Finish patch for #27484 (Onboarding: unintuitive not-navigation buttons). - Begin #29768 (Introduce new features to users in Tor Browser). sysrqb: Last week: Release prep and release (x2) #28329 (more UI changes) Worked on #29238 (prevent crash after update) Briefly looked at #29859 (App crashes when playing video on Twitter) Looked at #29866 ("Request Desktop site" should use Desktop UAS) This week: Continue working on #28329, #29238, #29859 Discuss localization things Look at F-Droid again boklm: Last week: - Helped with building and publishing new releases - Fixed the resource-timing, user-timing and user-timing-worker tests for #27137 - Fixed #29812 (.mar files for 32-bit Linux are missing for 8.5a9) - Started adding android-x86 to the download page (#29845) This week: - Finish fixing #27137 and disable all currently failing tests - Finish fixing #29845 (Add android-x86 to the download page) - Make some patch for #26907 (Guard against failures during MAR file generation) - Fix #29868 (tor-browser-build fails in container-image-windows-i686 attempting to install package python-future) GeKo: Last week: - release prep (we got 4!! releases out this week; thanks for everyone who helped, in particular on the weekend) - wrote a patch for #26498 and backported a mozilla patch for android (#29843) - worked on #28622 (Tor Browser branding for Android) - tracked down #29859 (Playing videos on Twitter is not working and freezing the mobile browser) - investigated backporting the JS Poison patch (#29049) - worked on improved authenticode timestamping (#29614) - looked over sponsor 8 final report (draft) and upcoming funding proposal for esr transitioning work This week: - finishing #28622 - fix WebGL related issues (#29246) - try to come up with something for #29859 - reviews Pili: Last week: - Sponsor 8 report - Preparing for S27 kick off - Google Season of Docs This week: - Infracon - Finish off Sponsor 8 report - S27 Kick Off - Google Season of Docs - start writing some ideas down pospeselr: Last week: patch for #29825 (fix for upgrade path in #25658, inserts/moves torbutton and security level button, rather than resetting to defaults) begin investigating #27503 (broken screenreaders on win) filed #29868 (python-future no longer exists in jessie-backports) This week: #27503 fun sisbell: Last week: - Included Android PT Support in TOPL: (thaliproject#86) - Upgrade for Android Q (thaliproject#85) - needed to break apart tor executable directory from config dir due to security changes in Android Q. Updated to tor-android-binary 03.5.8-rc dependency - Fixed bridges API (and pulling of bridges text file from android resources) (thaliproject#78) - Added custom config of torrc for Java TOPL (thailiproject#78) - needed this to keep project in sync with Android changes This Week: - #27609 - integrate latest TOPL changes to tor-android-service - Submit TOPL PR - Fix merge conflict in tor-browser-build Orbot project - Test PT support working in browser - Review changes in Orbot main project to see if we should merge any back over antonela: Last week: - TB8.5 - #27484 - Onboarding - Done - #29768 - Introducing new features - Duncan uploaded a version, will review this week - Security Setting Tor Browser manual update is ready to go This week: - #28622 - TBA icon - #28329 - Network Settings, Bootstrapping Animation - #29768 - Review - Introducing new features - Debugging TB8.5a9 Security Settings - Prep for IFF, TBA user testing Georg

1 0

February Fundraising Report
by Sarah Stevenson 25 Mar '19

25 Mar '19

Hello people of Tor! The fundraising team accomplished a lot in February. ## Grants First off, the grants team submitted a full proposal to OTF for UX improvements and we should hear back about the final determination soon. Some additional work was done on a proposal for onion services through OTF (originally submitted in July 2018) and we are pleased that this grant has now moved into the contract phase. We also sent introductory letters to the Overbrook Foundation and the Sigrid Rausing Trust. We heard back from NLnet that they unfortunately did not accept our proposal to improve the Tor exit scanner. They did move our proposal to fund part of the Browser team’s ESR migration work to the second round, and we should hear whether or not we were accepted for funding soon. We also submitted a proposal to New Media Ventures for LFP/LFI, and it moved to the second round, but it was unfortunately not accepted. ## Wiki We now have a Fundraising Team Wiki! Check it out here <https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam>. We have also made updates to the Sponsors Wiki which is linked from that page. I still have to finish documenting the past YE campaigns, but they will be up there soon. Let us know if there is anything you would like to see in this space. We also want to call out the Grant Work Flow process <https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view?usp=…> our team uses to prospect, apply for, and manage grants, so you can get an idea of what our team (along with Project Managers and the Finance team) is doing behind the scenes as we apply for funding. ## Special Appeal We tried raising money to cover the cost of an Outreachy email, but had limited success with an email and push on social media. We plan to apply for their session that begins in December. ## Cryptocurrency The cryptocurrency donation page <https://donate.torproject.org/cryptocurrency> launched March 18th, but this has been a culmination of work that began last fall. So far we have raised over $10,000 from the page and have received nice buzz on Twitter. We’ll report more on these efforts and results next month. Let us know if you have any questions or suggestions. - Fundraising Team

1 0

Notes from March 21 2019 Vegas team meeting
by Karsten Loesing 25 Mar '19

25 Mar '19

Notes for March 21 2019 meeting: Georg: 1) We got our planned releases out (8.0.7 and 8.5a9) 2) We might need to release security updates quickly this week depending on today's pwn2own results 3) Worked together with ln5 on our upcoming NextCloud evaluation (https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure…) 4) Release preparations for 8.5 Sarah: 1) Cryptocurrency page launched and we've raised over $10k from it so far https://donate.torproject.org/cryptocurrency. We have gotten a nice buzz on Twitter and Steph will promote from the Tor twitter account once a few edits are made to the page. 2) New monthly giving page should be ready next week and I'll use that to invite groups of past donors to convert their giving to monthly. 3) Al is beginning to work on LOIs to a few human rights focused foundations as well as one that provides funds for European travel. Antonela: 1) tpo.org - Fixing UI things, closing issues, reviewing small devices. 2) tpo.org - Call for translators was released this week, reviewing ES. 3) Tor Browser 8.5a Release: TBA Network Settings, TB Security Settings 4) Tor Browser 8.5 Release: #27484, #29768, #27399 5) Security Setting Tor Browser manual update is ready (thanks wayward!) 6) Gave a talk on Tuesday at Cyborgrrrls encuentro tecnofeminista, Mexico. 7) Prep for IFF: TBA user testing, outreach material is on the presses, making localized outreach material to be available for print and/or share in .pdf (thanks emmapeel!) 8) Working on Personas with Duncan. 9) Reviewing Caroline's reporting from India and Thailand. 10) Tickets triage for ux-team tickets is complete, waiting for pili's next steps. Nick: 1) 0.4.0.3-alpha to come out Friday, most likely. 2) Libreplanet this weekend: will be around for Saturday, but not Sunday. Mike: 1) Excited about leading tor scalability+performance; working on mail for Isa, Nick, Roger to review before sending Steph: 1) prepared the State of the Onion presentation for LibrePlanet. In Cambridge Fri-Sun. 2) preparing for website launch. Writing launch blog post. 3) reviewed the new cryptocurrency page 4) responding to inquiries isabela: 1) Dev Meeting -> we start to send invites to employees, contractors and board members. We will send the rest of invites this week and coming week. This bit of delay is mainly on me who need to finish the draft and invite list for jon to email people. 2) preparing board book for next board meeting on March 29th 3) getting things ready for LibrePlanet Sue: 1) Working on financials for Board Books 2) Normal accounting stuff (invoicing funders, paying bills) 3) Working on rewrite of the Accounting Manual Pili: 1) Sponsor 8 Final draft 2) Getting people organised for Google Season of Docs 3) Preparing for S27 Kick Off meeting next week 4) Preparing to run capacity planning exercise for Browser Team 5) Finalising tpo.org and working on getting community portal content written 6) Next week I'll be at Infracon in Barcelona 7) Week after next I'll be at IFF in Valencia Erin: 1) launched EE feedback process, working w/ Isa to answer some lingering questions 2) browser & OONI dev screening 3) general HR stuff

1 0

Network team meeting notes from 18 March 2019
by Nick Mathewson 19 Mar '19

19 Mar '19

Hi! Our logs are at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-03-18-17.00.html Our meeting notes are below: ======= = Network team meeting pad! = This week's team meeting is at Monday 18 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, when daylight saving time changes 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.) 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 11 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002252.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. ------------------------------- ---- 18 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?") teor says, Tor Browser should test in an alpha as soon as possible, so we know if we need to do #27647 I added a comment on the ticket: https://trac.torproject.org/projects/tor/ticket/29641#comment:7 (I sometimes miss pad and IRC comments, tickets are much better.) == 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 For next week: On gitlab time-based releases, and why developers and users like them: https://about.gitlab.com/2015/12/07/why-we-shift-objectives-and-not-release… == 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: (offline except for the first meeting each month) 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 Week of 11 Mar (actual): Bug triage rotation - Triaged a whole bunch of backports that were in the wrong milestone - Tried to keep up with the bugs in #tor-bots: I was busy, I might have missed something Roadmap Coding (3 days per week): - CI with Chutney/Tor: #29729, #27912, #29280, #22132 Roadmap Reviews: - Review nickm's parts of the CI with Chutney/Tor tickets - Other assigned reviews: I have one review to catch up on next week - I need to write extra tests for it. - Picked up some sbws reviews - Tried to help with sbws #28563 - Logged a bunch of bugs that are causing CI failures - Proposal reviews: prop#199 / #29801 Other: - Mainline merges - Merged most of the backport backlog, there is one merge remaining for next week (All the other backports need another alpha before they can merge) Week of 18 Mar (planned): Roadmap Coding (3 days per week): - CI with Chutney/Tor: #29729, #29761 - Backport fixes needed for CI with Chutney/Tor to Tor 0.2.9 - 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 - sbws reviews Other: - Other assigned reviews - Do mainline merges, and the remaining backport merges from last week - Do remaining reviews from last week - Leave admin - Add a travis test for stem (it's a copy of the chutney test, but using the stem command) Week of 18 Mar (actual): Roadmap Coding (3 days per week): - CI with Chutney/Tor: #22132, #28203, #29729 and children if needed Roadmap Reviews: - test proposed sbws design, suggest a new design, do sbws reviews Other: - review and design work on prop#199 - automatic IPv6 connection improvements - review #29036, #29434, #29073 - try to explain #29500 better - Leave admin - Work out how Tor's new feedback process works - Work out the new travel rules - other emails - triage and merge backports - ticket herding - assign 040-must tickets to people Help with: - If someone would like to work through the PrivCount changes with me, that would be really helpful. Otherwise I will defer them until after the Chutney/Tor CI. Blocked: 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) Nick: 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? Week of 11 March (actual): - Revised travis+chutney branches - Revised pubsub branch - Implemented #29357 (activeonstartup) - Meetings (various) - Review and merge (lots) - Slides for libreplanet Week of 18 March (planned): - Prepare for libreplanet on saturday - Reviews and merging. - Work on several 040-must items. - Testing PRNG determinism code (29732) - Possibly, kick off work on some more of my sponsor 19 and 31 stuff. - 29223 standardized abbrevs? - 29269 bridge stats? - Time permitting, adl/rup revisions - If catalyst is available, initial design chat on config.c refactor. - Review a paper for PETS - Get ready for an 0.4.0.3-alpha around the end of the week. Help with: - Please have a look at the tickets labeled 040-must. Are you the very best person to do one, or to explain why it is not a "must"? dgoulet (missing meeting): - AFK. Mike: 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?) Week of 3/11 (actual): - Sick + errands piled up from recovery - Lots of Tor scalability discussion & thought - Little bit of work on vanguards workarounds Week of 3/18 (planned): - Scalability planning & discussion - Catch up with asn's wtf-pad work, finalize plan for keeping circuits open (#28780) - Taking friday off catalyst: 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 week of 03/11 (2019-W11) (actual): - reviews - asked for feedback from tbb-team on #28925 (distinguish proxy vs PT in bootstrap) - more pubsub improvements - figured out a way to unit-test pubsub-using code (maybe not optimal) - some annoyances related to practracker.py week of 03/18 (2019-W12) (planned): - try prototyping #28925 solution using pubsub but in a way not too difficult to back port to 0.4.0 - CI+Coverity rotation - reviews - checking for any remaining loose ends in pubsub review juga: Week 11 March (planned) - 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) Week 11 March (actual) - 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) - Closed tickets that doesn't apply anymore and change some tickets' milestones - Recover a destination when it stops failing (#29589) - Document that authorities are not measured by default (#29722) Week 18 March (plan) - Continue with Work out how sbws can report excluded relays in the bandwidth file (#28563) - Work on Ignore bandwidth file lines with "vote=0" (#29806) - Create a blog post about work done and future work (#29724) - Continue with DirAuths should expose bwauth bandwidth files (#21377) asn: Week of 03/11 (planned): - Do revisions for #29221, #29298. - Continue work on #29298. - Do pending merges/reviews. - Check updates on #5708. - Check new HSv3 bugs that dgoulet opened (#29665, #29669). Week of 03/11 (actual): - Got #29298 and #29221 revised and merged. - More revisions for #28636 - Did merges/reviews. Got #29665 merged. - CI role. Fixed #29792, #29527, #29747. - Started work on #28634. Made some draft padding machines for hiding RP circuits. Also written a log-scraping program that analyzes HS circuits. More work needed. Will be working on this for the rest of the month. Week of 03/18 (planned): - Continue work on #28634. - Do merges/reviews. - Get #28636 finalized. - Fix prob_distr coverity issues. Help with: - Mike can you check that my rationale in https://github.com/torproject/tor/pull/788#discussion_r266450359 is correct? ahf: Week of 3/11 (planned): Sponsor 19: - Continue with #29207/#29206 with Cohosh. - Document protocol changes for #29207/#29206 Week of 3/11 (actually): Sponsor 19: - Talk about GeoIP interface with cohosh - Early review of #29734 - Added branch for listening on WebSockets in the Broker, now working on JSON message layer (#2907/#29206): - Started looking into WebSocket layer between Broker and Proxy (#29736). - Trying to wrap my head around an issue that I thought was related to the token bucket handling between WebRTC/WebSocket, but was a local network issue. Misc: - Created PR for #29036. - Closed #29737. Week of 3/18 (planned): Sponsor 19: - Second review of #29734. - Continue with #29207. Misc: - Network team bug triage. - Get Gitlab to run :-S - Talk with Erin, Cohosh, and Gaba about what we do with performance review for anti-censorship team.

1 0

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

18 Mar '19

Hello! Our weekly Tor Browser meeting ended a couple of hours ago and, as usual, here comes the link to our IRC log: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-03-18-18.31.l… and our meeting notes from the pad are: Tor Browser Meeting Notes Week of March 18, 2019 Discussion: sysrqb: Move meeting 1 hour earlier? (GeKo: We'll start with that on 4/1 and I'll announce the change to tbb-dev) feedback process GeKo: Last Week: - release prep - many reviews for #28329 and #27609; reviewing #29794, #25658, #28628, #27478, #29440, #29758, #26323, #25876 - updated patch for #28802 - wrote small patch for better NoScript integration (#29021) - worked on NextCloud test This Week: - Firefox 68 will be developed in mozilla-central (GeKo: pospeselr will look at https://torpat.ch/ and figure our what tickets at bugzilla need to get filed and which patches we should try to upstream) - more reviews - work on mobile bugs - release signing pospeselr: Last Week: Finished the #25658 patches (Security Level button!) This Week: Update the torbutton part (of #25658) to 'intelligently' add the new Security Level button to the toolbar, rather then resetting everything to our defaults Catch up on all the not-programming work I'm supposed to be doing Get back into the windows swing of things investigate #27503 (broken screen readers on Windows) Write up a quick patch for #28996 (jump list disk leakage fix on Windows) mcs and brade: Last week: - Finished #28628 (Introduce New Security Settings to users). - Finished #29440 (Update about:tor when Tor Browser is updated). - Reviewed patches for #25658 (security slider replacement). - Helped with other code reviews. - Participated in Tor Browser developer interview. This week/soon: - Note: We will be out of the office (and mostly afk) this Thursday and Friday (March 21 and 22). - Look at #29790 (Add build option to store profile in HOME directory). - Follow up on Mozilla bug 1434666 (updater failing on Linux (cannot find libraries). - 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. boklm: Last week: - helped build new releases - made some patches for: - #29758: Build firefox debug infos for linux-i686 - #25623: Disable network during build - revised patch for 26323: Build 32bit Linux bundles on 64bit Debian Wheezy - worked on some fixes #27137. Now checking if the tests still fail when enabling the corresponding prefs. - answered tor-packagers email about "torbrowser package on NetBSD" (still awaiting moderator approval) and opened #29790 This week: - help with publishing the new releases - fix #27137 and disable all currently failing tests sysrqb: Last week: More work on #28329 Release prep This week: More of the same sisbell: Last week: - 29313: tor-android-service browser build - downgraded tor to 0.3.4.9, generated new dependency list, new patch to remove ndk build, fixed torservice to work with older library - 29574 Configure Orbot project to use TOPL - cleaned up and broke apart patches, fixed some mismatched dependency versions - 29575 Configure Firefox project to use TOPL - upgraded dependencies list - tested integrated APK (orbot working but proxy not connected to) This Week: - Resolve proxy not found in browser - Add obfs4proxy to tor-android-service aar - Fix latest merged conflict in orbot project for browser build - respond to any code reviews antonela: Last week: - 8.5 Review, TBA and TB - #28800 - New Identity - https://trac.torproject.org/projects/tor/ticket/28800#comment:8 This week: - Moar on 8.5 - #27484 - Onboarding - #29768 - Introducing new features - Security Setting Tor Browser manual update is ready for review - who should review it? (GeKo: pospeselr and I can take a look, too, besides Steph) https://pad.riseup.net/p/ZsGRD4yM5pshKddf75IR-keep - TBA #27399 - Leading Orfox users to Tor Browser Android - Reading more about Letterboxing What is the priority for Letterboxing? Which Tor Browser version will release it? (GeKo: not sure yet which alpha but I hope we can test it furthre and help Mozilla by shipping something in May maybe) pili: Last week: - Tor Browser vision exercise write up - Tor Browser release meeting - Sponsor 8 final report This week: - Sponsor 8 final report - Sponsor 27 prep - Google Season of Docs - any ideas for projects for a technical writer for ~3 or ~5 months? FPI documentation? Others? (GeKo: helping with our design doc might be good) - Start prep for Tor Browser Team capacity planning session Georg

1 0

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project