tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

January and February 2019 report and March 2019 plans for the metrics team
by Karsten Loesing 04 Mar '19

04 Mar '19

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in January and February 2019 as well as a few expected highlights for the current month, March 2019. On behalf of the Tor metrics team, Karsten January and February 2019: Held an in-person meeting in Brussels to make plans with other teams and to make a new roadmap for the next six months [1]. [1] https://storm.torproject.org/shared/TsgBadLSfM8uh_aftPjxmR_rm0a8E-4UQ2HEa_l… Performed a one-off analysis of existing OnionPerf measurements with special focus on slow runs, timeouts, and failures [2, 3]. [2] https://people.torproject.org/~karsten/volatile/onionperf-metrics-2019-02-0… [3] https://people.torproject.org/~karsten/volatile/onionperf-metrics-2019-02-2… Started drafting guidelines for adding data to Tor Metrics [4]. [4] https://bugs.torproject.org/29315 Presented Tor Metrics at FOSDEM 2019 [5]. A transcript of the presentation is also available [6]. [5] https://fosdem.org/2019/schedule/event/monitoring_anon/ [6] https://iain.learmonth.me/blog/2019/2019w064/ Continued to document considerations for privacy-preserving safe measurements of live networks [7] to be included in an IETF Internet Draft on the topic [8]. [7] https://github.com/irl/draft-safe-internet-measurement/issues [8] https://datatracker.ietf.org/doc/draft-learmonth-pearg-safe-internet-measur… Took ownership of OnionPerf development. The canonical repository is now hosted on git.tpo [9] and is mirrored to GitHub [10] to accept pull requests (and to later run CI). [9] https://gitweb.torproject.org/onionperf.git/ [10] https://github.com/torproject/onionperf Added a "single-shot" mode to OnionPerf to enable easier testing during development and towards use in CI environments [11]. [11] https://github.com/torproject/onionperf/pull/1 Improved test coverage for OnionPerf [12]. [12] https://github.com/torproject/onionperf/pull/4 Added support for testing v3 onion service performance in OnionPerf [13]. [13] https://github.com/torproject/onionperf/commit/c8b0fc22809900ee35938ee7f89e… Continued working on second report for Sponsor13 [14, 15] [14] https://bugs.torproject.org/29648 [15] https://bugs.torproject.org/29649 Ported the research portal content to a Hugo static site [16] and deployed a staging version for feedback [17]. [16] https://bugs.torproject.org/26838 [17] https://research-staging.torproject.org/ Established a new research@tpo alias [18] to allow for external researchers to contact Tor people that manage the Research Portal/Mailing List. [18] https://bugs.torproject.org/29557 March 2019: Add integration tests [19] for the data-processing modules powering the Tor Metrics website. [19] https://bugs.torproject.org/29425 Write a specification document for exit lists [20]. [20] https://bugs.torproject.org/29624 Replace advertised bandwidth distribution graphs by consensus weight distribution graphs [21]. [21] https://bugs.torproject.org/29330 Presenting Tor Metrics at the Scottish Networking Event [22] on the 12th March. [22] http://scone.cs.st-andrews.ac.uk/wiki/ Attending IETF 104 and presenting the above Internet Draft on safe measurement [23]. [23] https://www.ietf.org/how/meetings/104/

1 0

Tor Browser team meeting notes, 4 Mar 2019
by Georg Koppen 04 Mar '19

04 Mar '19

Hi all! We just had a short weekly meeting and I wanted to share the meeting notes, as usual. The IRC log can be found at: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-03-04-18.29.l… and the items from our pad are: Discussion: - next releases (GeKo: we won't get to another alpha release before the Firefox security bugfix release on 3/19, alas :( ) mcs and brade: Last week: - Posted patches for #28044 (Integrate Tor Launcher into tor-browser). - Posted a patch for #29627 (Moat: add support for obfsproxy's meek_lite). - Reviewed patch for #29120 (media.cache_size causes some media to load extremely slowly). - Debugged #29535 (Context menu does not open on New Tab). - Provided some feedback for #27484 (Onboarding: unintuitive not-navigation buttons). - Helped with triage of incoming bugs. This week/soon: - For #28044, revise proposal 102 to take into account intrigeri’s comments as well as some things we learned during implementation. - Fix #29445 (Tor Browser is denying ESR policies.json) - Investigate #29630 (TorBrowser creates empty directory in "/tmp”) - Begin work on #29440 (Update about:tor when Tor Browser is updated). - Investigate #27484 comment:13 (DDG onboarding doorhanger disappears after tab switch). - Review the Firefox updater security audit report. sysrqb: Last week: some release prep Worked on F-Droid release process Worked on TBA UI improvements and crash (28329) BridgeDB admin TOPL integration and OrbotService This week: Finish next iteration of TBA bootstrapping UI Some BridgeDB patch reviews Helping with TBA PT integration (if needed) sisbell: Last week(s): - 29575 - Create tor-browser-build for Firefox with TOPL libraries: Resolved duplicate class problems. Transitive use of class files is OK. Transitive use of resources is a problem (meaning an embedded dependency aar of an embedded dependency) . I believe I finally have a solution (see below, Next Week same issue). - Testing of tor-android-service. Latest code is not passing bootstrap complete message correctly to UI. This is largely cosmetic but needs to be resolved. - responded to sysrqb code review comments. Opened issues at TOPL project for tracking. - Investigated building of tor for Android. Looked into and prototyped use of ndk-build for tor dependencies: openssl and libevent. This Week: - 29575: To resolve missing resource issues, I’m going to put orbot and tor-android-service and topl into the local artifact repo as part of the Firefox build, rather than the mobile/android/app. I believe gradle treats repo transitive resources differently. I’m also going to put dependent projects aar libraries as compileOnly scope (provided) so that we are guaranteed to only have one copy. - Create new branch with latest changes to tor-browser-build - More testing - Resolve open issues at TOPL I'd like to move most of the resources from tor-android-service to orbot app, since tor-android-service doesn't use them. (GeKo: We should talk to the guardianproject folks about that; sisbell will write an email to nathan and hans outlining where we are and where we are heading towards to keep them in the loop) boklm: Last week: - finished patch for #26323 (Build 32bit Linux bundles on 64bit systems) - worked on some patches for #27137 (tbb-testsuite: fix the navigation-timing, performance-observer, resource-timing, user-timing tests) - looked at CVs of browser developer candidates This week: - continue work on #27137 and testsuite - work on #25623 (Disable network during build) - some reviews pili: Last week: - Tor Browser Release meeting - Tor Browser Vision Brainstorm Pt II - Browser dev hiring CV pre-screening This week: - Still trying (and so far failing) to take an easy week after India - Write up Browser Vision Brainstorm notes - Start writing Sponsor 8 (TBA) final report antonela: Last week: - reviewed #28329 - TBA UX/UI network settings - reviewed #27484 - Onboarding navigation This week: - pili and I will triage ux-team labeled tickets \o/ - review TBA and TB sec settings pospeselr: Last week: - reviewed browser dev cvs - #25658 work - macos build for anto - initial tor-browser patch for this ready today This week: - #25658 tor-browser patch later today - #25658 tor-button patch - code reviews - #29120 ready for uplift now GeKo: Last week: - wrote some patches for mobile related issues which I encountered while reviewing #28329: #29632, #29633, and a patch for pluggable transport/bridge support on mobile (#28802) - reviewed #29210 and #28329 (still ongoing) and #28685 - work related to job application This week: - finish reviewing #28329, reviewing as much as I can to get into the next alpha - begin of the month team admin stuff Georg

1 0

Notes from February 28 2019 Vegas team meeting
by Karsten Loesing 01 Mar '19

01 Mar '19

Notes for February 28 2019 meeting: Pili: 1) Finishing off Browser, Community and UX teams' Vision exercises 2) Organising India Feedback and User Testing materials 3) Working on Outreachy application 4) Following up after GSoC rejection and preparing to improve next year's application 5) Brainstorming dev meeting invites with teams 6) Tor Browser hiring pre-screening and organising feedback gathering 7) Reviewed Hiring at Tor process document 8) Helped with a couple of SOIs for Community team 9) Might try to take half days next week to recover from India and will probably just attend meetings Steph: 1) Preparing Def Con vendor application. 2) Answering questions for Mozilla’s Internet Health Report. 3) Latest newsletter went out yesterday. 4) Prep for LibrePlanet. 5) Inquiries. 6) Working on Outreachy application with Pili. 7) Preparing for website launch, reviewing illos. Gaba: 1) Metrics team: - Discussed sponsors/funding for metrics team 2) OONI - Looked at CVs for hiring backend developer 3) Network team - calculating capacity - gathering dev policies 4) Anti-censorship team - kat's report 5) Setting up meeting for discussion on priorities around scaling Sarah: 1) Working on e-appeal for Outreachy sponsorship. No luck securing funds from past major donors. 2) Writing new welcome email. 3) Finishing Fundraising Team Wiki. 4) Dealing with bad actors testing cards on donate page. 5) Working with Giant Rabbit to make changes to the donate page. 6) Met with Pia from Open Collective. We will keep this on our radar as an option for crowdfunding. 7) Grants team is working on two SOIs for DRL as well as follow-up for a couple other proposals that have advanced to the next round of consideration. Sue: 1) Financial Audit is complete, report sent to Board for review and comment 2) Invoicing for NYU and Upenn 3) General payroll and disbursement processing Nick: 1) New releases came out last week 2) Working on CI stuff to get integration tests running 3) We're experimenting with new merge policies, to see what happens when we have more people merging code isabela: 1) finished reviewing the auditor report w/ sue 2) invitation process for dev meeting - asked Alison to help and 'do her thing' :) as she has done this process a bunch of times 3) Added some new 1:1s to my schedule :) if you want to have one too please reach out! 4) Writing ED quarterly update 5) Doing 'money machine' team tasks: review documentation of our processes, follow up w/ Sida, and proposals drafting. 6) Working on FY budget for july 2019 - june 2020 7) will be in seattle for the week of March 11 and will be in full vacation mode :) for 2 weeks in november (7-21) (GeKo: yay, vacation!) Karsten: 1) We're planning to replace advertised bandwidth distribution graphs with consensus weight distribution graphs to reduce maintenance effort (#29330). If somebody wants to suggest a better plan, please do so soon! Before we move on we'll check whether consensus weight and consumed bandwidth are proportional. Erin: 1) Back from vacation. Playing catch-up. 2) Working on browser dev and OONI dev recruiting 3) Coordinating w/ Linus to onboard new sysadmin. Announcement soon. 4) Other HR stuff. Mike: 1) Sponsor2 work 2) Tor scalability discussions 3) Research discussions Georg: 1) Where are we with our blog policy? Can we announce it officially (if we have not) and make sure it takes effect? 2) Hiring policies 3) Sue: could you get back to me regarding my mail with the payment question for my vacation? Yes, will do. (GeKo: thanks) Alison: 1) Working on LFI application review 2) Gus and emma are in Indonesia 3) Working on website materials Antonela: 1) Finished Outreach Material - https://share.riseup.net/#sn028ht41RD--vTGPPzTCA 2) Coordinating with Arturo and Elio OONI Explorer next steps 3) OTF approved, UX team roadmap updates 4) Working on Personas with dunqan 5) Working on https://github.com/torproject/tpo/issues with hiro 6) Coordinated user research for Thailand with emmapeel and ggus, debriefing India with pili and caroline 7) Reviewing TBA for next alpha release

1 0

Network team meeting notes from 25 Feb 2019
by teor 01 Mar '19

01 Mar '19

Hi, A reminder: Next week's team meeting is at a different time. Tuesday 5 March at 2300 UTC on #tor-meeting on OFTC. Our logs are available at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-02-25-17.58.html Below are the contents of our pad: = Network team meeting pad! = This week's team meeting is at Monday 25 February at 1800 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. February schedule: * Monday 25 February at 1800 UTC March schedule: * Tuesday 5 March at 2300 UTC * Monday 11 March at 1800 UTC * Monday 18 March at 1800 UTC * Monday 25 March at 1800 UTC (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.) 8 Jan: https://lists.torproject.org/pipermail/tor-project/2019-January/002155.html 14 Jan: https://lists.torproject.org/pipermail/tor-project/2019-January/002170.html 22 Jan: https://lists.torproject.org/pipermail/tor-project/2019-January/002184.html 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 == 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 now: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… * 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 actual point when you finish a task (as well as update 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. ------------------------------- ---- 25 February 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 ends on Thursday! - Tor was not accepted for GSoC this year. == Discussion == When we assign reviews, can we skip people who are on leave? === Tor Meeting === - Brainstorming Tor meeting invites - is there anyone that we're working with a lot that we want to make sure is invited? === Policy planning === * We don't have a great way to set and adopt development/support policies. How would we feel about this: Let's have policies start out as "draft". If we think a policy could maybe work out, let's call it "experimental", post it publicly, and try it out for a limited amount of time. And then let's see whether we need to amend it or adopt it or discard it entirely based on network-team rough consensus. [leftover from last week] * Next steps with getting ourselves a merge policy? == Recommended links == == 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 02/19 (actual: • - look at releases estimation • - look at processes and make a proposal on decision making (so far all documentes found here https://gitlab.com/gabelula/tor-documentation-processes) • Week of 02/25 (planned): • - continue on https://gitlab.com/gabelula/tor-documentation-processes • - track sponsors & update roadmaps on wiki for each sponsor teor: (offline) Week of 18 Feb (planned): Roadmap Coding (3 days per week): - PrivCount proof of concept (#29004 and related tickets) <-- are related tickets in the roadmap? I guess is 29027 and 27908 - unit tests for extra-info documents (#29018) Other: - Reviews - Email, IRC, and ticket backlog - Finish travel reimbursements - Ask metrics to monitor bootstrap speed (from Sponsor 8, but worth doing anyway) - If we get bad results, tweak bootstrap settings to work: - when lots of fallbacks are down, and - on networks that drop packets (deferred from Sponsor 8, we'll only do it if it is necessary) Week of 18 Feb (actual): Roadmap Coding (3 days per week): - Finished #29017 - stats bug fix, and it was merged. - Finished #29018 - a related stats bug fix, refactor, and unit tests for extra-info documents (PrivCount preparation) Other: - Finished travel reimbursements - Email backlog: draft proposal and policy comments, admin, etc. - Ticket herding - Skimmed IRC backlog Week of 25 Feb (planned): Roadmap Coding (3 days per week): - Plan my coding tasks after trimming Sponsor V Other: - Make Sponsor V smaller (24 points) - must be done before I start new coding tasks! - Send out release capacity meeting time - Blocked: Merge some merge_ready tickets - Blocked: Stable maintainer triage and merges - Leave admin (deferred) - Large reviews (deferred) Week of 25 Feb (actual): Roadmap Coding (3 days per week): - Get bandwidth counters working (#29019 and children) Other: - Send out release capacity meeting time - Email backlog: draft proposal and policy comments, admin, etc. - Revise proposed tickets process - 7/9 assigned reviews, including sbws reviews, and small reviews - Did some extra reviews (#29280, #28525) - Found some issues with the transition plan for prop289 (#26288) - Tried to help fix #29500 (circuit pad test failures) - Make Sponsor V smaller (24 points) - Re-plan roadmap coding - Fix some urgent CI bugs (#29530, #29599, #29601) - Work out merge process, set up merge environment - Do some backport merges (#29145, #29599) - Blocked: backport merges are slow, due to #29601 (needs_review) and #29500 (needs fix) Help with: - Gaba, do you want to share your release capacity calculations before the meeting? <--- oh, I didn't see this. I will share them next week. (gaba) - mikeperry, can you please fix #29500? (circuit pad test failures) The CI failures are making backports difficult. - Can someone please review #29601, so we can speed up Appveyor? Nick: • Week of 18 Feb (planned): • - Write final onionbalance-with-v3-onionservices proposal (thanks, asn and dgoulet!) • - Finish personalization proposal • - Change master to 0.4.1; create maint-0.4.0 and release-0.4.0 branches (done) • - Write proposed policy for merging stuff (done) • - Discuss proposed merge policy; make public version. • - Releases for 0.3.3 and later. • - Merge and announce fix for TROVE-2019-001 (thanks dgoulet) • - Discuss chutney+ci findings with teor. • - Update pubsub branch as needed/useful. Check in with catalyst. • - Start looking at bridge stats status for #29269 • - meet with researchers about datagrams, performance, etc. Mike, please answer the scheduling email ASAP? • - Reply to a large pile of emails • - ADL discussion • - Prop 300 • - Consensus options proposal idea • - and so much more... • - Decide what is left in 0.4.0. I need help here. • - CI / Coverity rotation: look at jenkins failures (like #29534), OSS-fuzz timeouts, etc • Week of 18 Feb (actual): • - Found a bug in v3 onion service spec conformance with asn; possibly making onionbalance-with-v3 proposal unnecessary. • - Sent Teor a draft personalization proposal; got feedback. • - Sent around proposed merging policy • - Releases for 0.3.3 and later with announcement for TROVE-2019-001 • - Worked on a chutney-and-ci plan with teor • - Discussed scheduling, datagrams, etc • - Lots of review and merging • - Worked on Jenkins failures • - Triaged 0.4.0 with dgoulet • Week of 25 Feb (planned) • - Respond to ADL folks • - Lots of email • - More reviews: catch up • - Discuss merging policy • - Work on map_anon test breakage (29534) • - Chutney CI work dgoulet: Week of 19 Feb (planned): - Adapt #26288 (prop289) to use the new fast PRNG. Wrote a bunch of unit tests as well for that branch. - Triage 0.4.0 tickets with nickm - Finalize the TROVE-2019-001. - Discussions with Mike on #29494. - Discussed with researchers cell scheduling. Week of 25 Feb (planned) - Talked with asn about OnionBalance v3. - Put #26288 in needs_review. - Help Mike finalize #29494. - BridgeDB tickets! Most important! Mike: Week of 2/18 (planned) - Get #29204 branch ready for dgoulet - Hopefully start on #28780 - Vanguards package announcementready for dgoulet Week of 2/18 (actual): - Got #29204 branch ready for dgoulet - Implemented sketch of #29494 - Tried to reproduce #29500 in wine, did not get it to trigger Week of 2/25 (planned): - Discuss #29494 ideas with dgoulet - Hopefully start on #28780 - Investigate potential vanguards false positive Need Help With: - Running unittests under Windows try to reproduce #29500 (Wine was insufficient) catalyst: week of 02/18 (2019-W08) (planned): - expense reporting - #28226 review - other reviews week of 02/18 (2019-W08) (actual): - medical bureaucracy - more review of #28226 - new ticket #29537 about intptr_t round trip issue that came up during #28226 review - some review of #29299 (sbws country) [juga, is it ok if i review by only reading through the code? i don't have an easy way to set up a test environment][juga: yes] week of 02/25 (2019-W09) (planned): - expense reporting (probably for reals because various statements have closed with posted transactions that were previously pending) - reviews - proof of concept of adapting some bootstrap reporting code to pubsub as part of #28226 review help with: - dgoulet, is there anything you need to relay to me about #29276 before you disappear? • [dgoulet: Oh.. I didn't had that ticket on my stack. So what I think needs to happen is to upgrade to latest requirements.txt, fix the issues and release. I already • have identified one issue from running my own BridgeDB with latest so should be easy.] juga: Week 18 Feb (planned): - Continue with Adapt bandwidth file classes to be compatible with stem (descriptors, etc) documents (#29057) - Work out how long it takes sbws to measure the network (#28983) - When sbws stops making progress, log a warning (#28652) - Prepare presentation for the DemoDay - Revisions Week 18 Feb (actual): - Continue with Adapt bandwidth file classes to be compatible with stem (descriptors, etc) documents (#29057) - Work out how long it takes sbws to measure the network (#28983) - When sbws stops making progress, log a warning (#28652) - Prepare presentation for the DemoDay - Merge all `needs_review` branches in a dev branch and run it in the public network Week 25 Feb (plan): - Merge pending tickets in 1.0 milestone - 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 asn: Week of 02/18 (planned): - Move towards finishing up #29298 after getting Mike's feedback. - Discuss more about WTF-PAD future. - Start looking into roadmap task #29221. - Do reviews. - If time permits, read Tim's response to "walking onions" thread wrt onion services. Week of 02/18 (actual): - Did revisions on #29298 after Mike's review. I think this is probs ready after a final review and a squash. - Discussed onionbalance proposal with dgoulet and Nick. Interesting developments I need to write down. - Discussed merge policy. - Discussed [tor-researchers] mailing list processes with Iain and Chelsea. - Did reviews. Week of 02/25 (planned): - Get #29298 merged. - Do roadmap item #29221. - Start scoping down open 040-must bugfixes like #29527 and #28970. - Write down the onionbalance v3 discussion. Help with: - Mike can you handle the appveyor #29500 bug? ahf: Week of 2/18 (planned) Sponsor 19: - Send feedback to Kat about Report #2. - Collect some feedback from arma & cohosh about Broker.markdown. - Begin the work on protocol changes in the Snowflake codebase together with cohosh. Week of 2/18 (actually) Sponsor 19: - Read over report #2 and noted down some issues. - Got feedback from Cohosh on #28848 (broker documentation) - Begun work on #29207 (proxy/broker protocol) - Looked into React and Material UI for Antonela's Snowflake WebExtension UI. Week of 2/25 (planned) Sponsor 19: - Update Broker.markdown with Cohosh's comments on #28848 and close it. - Continue work on #29207. - Work with Cohosh on the Marionette bridge instance for the application team (#26920) - Talk with Kat and Gaba about Report #2 Misc: - Solve bootstrap-with-PT cancelling crash on Windows on #29562 - Try to reproduce asn/mikeperry's issue from #29500 on Windows

1 0

Damian's Status Report - February 2019
by Damian Johnson 28 Feb '19

28 Feb '19

Hi all! Here's my status report for this last month (I miss the days when everyone wrote these...). https://blog.atagar.com/february2019/

1 0

Tor Browser Vision Brainstorm: Part II
by Pili Guerra 26 Feb '19

26 Feb '19

Hi everyone, We’re going to have the second part of this visioning exercise this Friday 1st March at 19:00 UTC on #tor-meeting. During the first part we discussed why we need a Tor Browser and some potential directions for the Tor Browser for the future. For this next session we will discuss our current users and how Tor Browser helps them with a view to the problems they will have in future and how we can continue serving them. We will also discuss where the Tor Browser fits into the Tor Project and what value it provides to TPI as an organisation. Additionally, on a more personal note, it would be good if everyone can think about the following questions to answer during the meeting, or even before on this thread: - why are you excited to work on Tor Browser - why you care about it - what positive change Tor Browser should bring about, and - how will Tor Browser shape the future. I’m excited 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

1 0

Next Tor Browser Release meeting: Wednesday 27th February @ 19:00 UTC
by Pili Guerra 26 Feb '19

26 Feb '19

Hi everyone, Just an email to let you know that there’ll be NO Tor Browser Release meeting next week. Instead our next meeting will be on Wednesday 27th February @1900UTC over at #tor-meeting on OFTC. I will send a reminder email closer to the time. 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 1

User Feedback Report - January 2019
by Maggie 26 Feb '19

26 Feb '19

Hey, team! Welcome to the January 2019 user feedback report! I hope 2019 is treating you well so far. For more information on what users and community members were talking about this month, check out the December 2018/January 2019 User Feedback pad [1]. TL;DR: There were a bunch of releases this month, and a few user bug reports in the blog post comments. Reddit was about the same as always (with a focus on VPN and fingerprinting questions), and RT brought in a lot of questions about problems connecting with bridges. - The question I see most often across platforms is 'why can't I connect to Tor?'. I think we should provide more information to users when they run into problems connecting. Ideally, we would implement error messages that let users know exactly what's wrong, and what they can do to fix it. Until then, it would be very useful to have a guide to finding and understanding Tor logs. I've opened a trac task for this [2]. I will need some assistance from the browser/applications team, so if you're able/willing to help teach me how to read these logs better, please reach out! - Reddit is mostly full of the same questions we saw last month (i.e. 'will doing x allow me to be fingerprinted?' & 'my bridges aren't working - what do I do?'). Hopefully the second problem can be addressed by the Tor log document proposed above. - Tor is still broken for screen readers. I've been receiving some messages about this in RT from folks affected by the issue. They're having to use TB 7 instead of TB 8, since updating breaks screen reader compatibility. Now, on to the feedback! Scroll further down to see a summary of Reddit posts, some points from Google Play Store reviews, a list of the most common Stack Exchange tags from the month, and a collection of some notable issues and bugs mentioned by users in January. --- Most common questions on Reddit: - Will doing _____ allow me to be fingerprinted? - Why can't I connect/why aren't my bridges working? One Reddit user is having a lot of trouble connecting from Turkey [3]. --- TBA Reviews & Feedback on Google Play Store: The average review score is still at 4.2 stars. Some people are a bit confused about bridges - it seems they don't know what to do once they run into connection issues. We should provide some more guidance, perhaps in the form of links to information about bridges. Some users were still experiencing crashes in January when saving files, as well. --- Most common stack exchange tags: configuration: 20 this month tor-browser-bundle: 15 this month connection: 11 this month hidden-services: 7 this month relays: 7 this month --- Notable bugs, fixes, & issues: #27503 [4] - Disabling accessibility on Windows breaks screen readers - OPEN #29238 [5] - TBA: Prevent crash following upgrade - OPEN #28705 [6] - Tor Browser on Android is crashing on newer Android devices (>= Android N) by file download - CLOSED #29175 [7] - Tor 0.3.5.x mishandles empty socks5 auth - CLOSED #29327 [8] - TypeError: hostName is null on about:tor page - CLOSED --- Other user suggestions: - "I want to suggest making a personalized .iso distro for people that want to run relays...We should be able to download something that is already configured with everything you need software wise to run the relay. The only thing we should have to do is open up the correct ports for port forwarding in our router. If this was procedure, I think there would be many more relays and exit nodes than there are." - "I understand why you've rolled Orbot into TB, but can you add an option to use the "legacy", separate Orbot into the settings? I used to have TB as the default browser on my 'droid, but now that every time I open it I have to sign into a second instance of Orbot (as a big chunk of traffic from my phone is Torified, I have Orbot on all the time) - since this takes a long time, I've resorted to using Firefox Klar/Focus." - "I want to set Tor Android Alpha to clear all personal data on exit so I went to Privacy -> Clear private data on exit. It works except for Downloads, which get un-ticked every time I re-launch Tor. It's probably a minor issue as other things like history and cookies do get cleared and stay like that. Although to be honest it would be nice to just have a single setting for always-on Private Tab whenever I launch Tor." (notably, I have not been able to reproduce the issue they describe with Download privacy settings resetting after a restart.) --- That's it for the month of January! If you want to know more, please do check out the December 2018/January 2019 User Feedback pad [1] or reach out to me via email (waywardwyrd at riseup dot net) or IRC (wayward). Before signing off, I'll leave you with this gem of a post [9]. Thanks for reading! I'll see you all back here next month! - wayward/Maggie pronouns: she/they | twitter: @meochaidha <https://www.twitter.com/meochaidha> pgp: 0626 9C68 D0CC 1A5B E41B 72F2 615E B878 975C 4CDC ------ Annotations: 1. https://storm.torproject.org/shared/CsGcDVAvB32NeawrrziFcprx22gp9EjUscJ61hm… 2. https://trac.torproject.org/projects/tor/ticket/29584 3. https://www.reddit.com/r/TOR/comments/alecre/turkey_cannot_connect_to_tor_w… 4. https://trac.torproject.org/projects/tor/ticket/27503 5. https://trac.torproject.org/projects/tor/ticket/29238 6. https://trac.torproject.org/projects/tor/ticket/28705 7. https://trac.torproject.org/projects/tor/ticket/29175 8. https://trac.torproject.org/projects/tor/ticket/29327 9. https://www.reddit.com/r/TOR/comments/akqh58/when_i_think_of_tor/

1 0

Tor Browser meeting notes, 25 Feb 2019
by Georg Koppen 25 Feb '19

25 Feb '19

Hi everyone! Our weekly Tor Browser meeting just finished. Here come the link to the IRC log (http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-02-25-18.29.l…) and, as usual, the contents of our meeting pad: Week of February 25, 2019 Discussion: - Brainstorming dev meeting invites - is there anyone that we're working with a lot that we want to make sure is invited? - Tor Browser dev hiring process - Tor Browser vision exercise part II scheduling (GeKo: presumably on Friday 3/1 1900 UTC; pili nails that down) boklm: Since last meeting: - helped with publishing of the new releases, signing of the alpha, and following blog comments - reported #29476 (Add RecommendedTBBVersions to the new website) - reported #29550 (Tor nightly fails to build for Windows) - reviewed #25849 (Ship tor in Tor Browser nightly builds for Windows with Rust enabled) - fixed #29556 (nightly builds and testsuite emails) - reviewed #27210 (TBA - Support i386 target) - made patch for #29579 (Fix typo in projects/tor/build) - made patch for #28685 (Tor Browser for Android needs a more dynamic Build ID) This week: - try to finsh patch for #26323 (Build 32bit Linux bundles on 64bit systems) - continue work on testsuite - some reviews - look at CVs of browser developer candidates mcs and brade: Last week: - Made progress on #28044 (Integrate Tor Launcher into tor-browser). - Finished #27486 (Onboarding: "Visit an Onion" creates an "about:blank" loading page) - Debugged #29497 (After tor crash, firefox.exe shoots up to 50+% cpu usage) - Provided feedback on the browser developer hiring criteria (brade) and on some of the candidates (mcs). - Helped with triage of incoming bugs. This week/soon: - Make patches available for #28044 (Integrate Tor Launcher into tor-browser). - #29430 (meek-lite support in TL) - Review the Firefox updater security audit report. sisbell: Last week(s): - 29080: PR for TOPL accepted and merged - 29312: Create tor-browser-build for TOPL (in review) - 29313: Create tor-browser-build for tor-android-service (in review). Involved additional changes to packaging and proguard use. Made tor-android-service gradle build more configurable. This replaces orbotservice - 29574: Modify Orbot project in tor-browser-build to use TOPL (in review) - 29575: Create tor-browser-build for Firefox with TOPL libraries (in progress). - Resolving some issues around duplicate classes in dependencies. This Week: - 29575 - complete this - Testing APK - Start looking at changes of new Orbot UI to see what changes may need to be made pospeselr: Last week(s): #seattle-snowmagedeon2019 - built snowman - fell on ice - snow in the eyes - made a custom build for pili and antonella with #25658 changes - filed #29554 (about:preferences links do not function properly, needed for #25658) - most of the way done with #25658 - built alpha builds; a bit of a shit-show as i686 linux refuses to build on my machines - boklm: I neglected this a bit to focus on getting pili's macos build out, but everything matches on my end apart from the macos mar-tools (which doesn't quite seem right, given that all the other macos builds match) This week: - tonight! upoad macos mar tools file for boklm diff - uplift #29120 (neglected this one last week) - get a patch up for #25658 - hopefully fix #29554 GeKo: Today: - started to cut down my backlog - reviewed #29759 - wrote patches for #27210 and #29467 This week: - more backlog cutting down - reviews and help with mobile work - release prep (hopefully) - new month team admin stuff pili: Last week: - Mainly security settings user testing in India! This week: - Tor Browser release meeting - Tor Browser vision exercise part II - Organising and sharing India user testing and workshop notes - Onion Services proposal got accepted by OTF! - NLNet proposal for ESR migration got through to the second round Antonela: Last week: - Testing TBA - Preparing TB usability research in India and Indonesia This week: - #29440 - Update about:tor when Tor Browser is updated - Could we have some of these bridge decisions in TBA? sysrqb, sisbell, igt0, geko? [GeKo: yes, this sounds like something we should consider and build upon Anto: Awesome] https://lists.torproject.org/pipermail/tor-dev/2019-February/013708.html - Start digesting user research from India sysrqb: Last weeks: Put #28329 in review (TBA bootstrapping) Reviewed (most) TOPL patches Nearly have a F-Droid build ready for submission Worked on fastlane integration and auto-generating screenshots This week: Finish F-Droid submission patch Continue work on fastlane integration Review other tba-a3 tickets Georg

1 0

Update on Tor Meeting - where & when
by isabela 23 Feb '19

23 Feb '19

Hello Tor, I just want to share that we will be partnering with KTH Royal Institute of Technology in Sweden for our first Tor Meeting in 2019. It will take place in Stockholm and dates are July 11 to 15, where: * July 11 - people arrive * July 12 - meeting day * July 13 - meeting day * July 14 - meeting day * July 15 - people leave This meeting will have 3 days, not 5. This is not a change that will affect other Tor meetings, we are doing this just for this one to keep ourselves on budget. I will be sharing more information about the meeting, and what we are hoping to do that is open for the public since there won't be open days. You might have notice that our meeting is ending right when PETS[1] starts (in the same place). I will be sharing more information as we get things organized. Cheers, isabela [1] https://petsymposium.org/2019/index.php

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project