- tor-project - lists.torproject.org

Notes from July 6 2017 Vegas team meeting
by Karsten Loesing 07 Jul '17

07 Jul '17

Notes for July 6 2017 meeting: Nick: 1) From last week: Should I approve timesheets? How? Roger: 1) Who do I tell about operations task ideas, like "we should make a standardized slide template based on the style guide stuff from Elio" [Steph: I'm working on templates] 2) In talking with Alison last week I proposed that the community team re-focus on: "Helping the rest of the world help Tor". So helping relay operators is in, and helping activists and advocates is in, and helping volunteers get oriented is in. But support should shift to whichever team makes the thing being supported, and in general we should be watchful for the community team accumulating "all the stuff that involves interacting with users", because that's a poor way to draw the line. We're still early in the refocusing plan, but you heard it here first. 3) Membership policy is slowly proceeding (and I think that's ok). 4) Isa and I worked out new time allocation recommendations for the network team 5) geko: did you know about https://launchpad.net/~webupd8team/+archive/ubuntu/tor-browser -- that some random person is packaging tor browser for ubuntu, and not keeping up? Which team should be interacting with these people so they either do it right or stop? [GeKo: No, I did not; regarding the team question: it seems to me it could be a good start if someone from the community team would reach out to those people. Depending on how that goes it seems to be fine to involve folks from the Tor Browser team] 6) Alison and I picked up the "speakers bureau" idea again. Her next step is to get the notes from when we talked to Biella. 7) Privacy sensitivity training as an onboarding topic. We should make sure all our new people understand about Facebook "like" tracking, about web cookies in our html mass mails, and in general about the expectations from our community. 8) Status of the comms support person funding proposal? Alison: 1) More on Roger's point 2: I am going to organize a meeting with all of the people who currently work on support so that we can better coordinate channels, documentation, feedback to devs, and the like. 2) Tor Meeting: I sent the most recent invite list to vegas-leads. Are these ready to go out now? Can we move on to creating the meeting schedule? 3) Today I'm doing a webinar about Tor for Drexel University's Libraries and Archives Student Association 4) Finishing up a short grant to support graphic design work and printing costs for some posters and handouts for LFP. 5) Follow up on Roger's point 6: I am waiting for Biella to get back from vacation to give me those notes. 6) Need to connect with Steph and Tommy about publicizing the support wiki. 7) Are we still interested in having an unconscious bias training? Those trainers got back in touch with me. 8) Working on onboarding docs for "FOSS/Tor culture" which will complement what Isa is doing with privacy onboarding (see Roger's point 7). Arturo: 1) Ran out of disk space on one of our pipeline related machines, but appear to not have lost any data during that date contrary to previous belief. See: https://github.com/TheTorProject/ooni-sysadmin/issues/116 2) Following Leonids lead we have started documenting various sys-admin related incidents to learn from them and mitigate them in the future: https://github.com/TheTorProject/ooni-sysadmin/issues?q=is%3Aopen+is%3Aissu… 3) ooni-probe mobile app with notification support is coming together nicely. We are testing an alpha build for iOS and working on getting an alpha build for Android. 4) Next generation ooni-pipeline is moving forward. We are optimistically aiming to have an MVP deployment (with the new measurements interface running) deployed by CLSI: https://github.com/TheTorProject/ooni-pipeline/pull/62#issuecomment-3126377…. If you are a user (or would like to be a user) of ooni-measurements API you should check out: https://github.com/TheTorProject/ooni-measurements/blob/8a3bc04779514170168…. Georg: 1) We got out (or are about to get out) new Tor Browser releases picking up new tor versions; I am happy how this worked out while I was away from the keyboard 2) We tried to move the browser developer job application process forward; hopefully concrete next steps will happen next week 3) Can we move forward with the bug bounty program? I owe the hackerone folks an email outlining our plan [GeKo: the plan is to get back to HackerOne coordinating the public launch] Steph: 1) I'm creating brand aligned templates for documents and presentations, will eventually make their way to media.torproject.org 2) Working on first newsletter template, message about delivery change, content. Giant Rabbit still working on creating unsubscribe capability 5) Upcoming campaigns: sha2017, bug bounty, support wiki. 6) Will participate in net neutrality day of action next week https://www.battleforthenet.com/july12/ 7) Have been working back through press inquiries, responding to all new requests with feedback from Shari 8) Worked with asn to polish wilmington blog post, published and share Shari: 1) working on final report on donation database grant and edits for other proposals 2) had initial talk with Giant Rabbit folks about this year's crowdfunding campaign Karsten: 1) Cleaned up a little after the end-of-month sprint by updating to new metrics-lib, updating Metrics website, updating to new Debian stretch libraries. 2) Started making plans for current month; current plan is to focus on CollecTor development this month and do some maintenance tasks that piled up over the last six months. Mike: 1) Can we get an official TBB build machine? ( https://trac.torproject.org/projects/tor/ticket/22764#ticket, elsewhere) [GeKo: Yes, please] 2) Talking with researchers, getting padding code ready for PETS meeting. Brad: 1) Working on the year-end close process and preparation of financial reports 2) Sue and I both have a long backlog at the moment, so apologies for any delays in responding to questions sent to the accounting@ alias 3) Please approve time/expenses in Harvest for assigned employees no later than Tues July 11 4) It's important that we get all expense reports covering JAN-JUN by the end of this month

1 0

Tails report for June, 2017
by intrigeri 07 Jul '17

07 Jul '17

Hi, we've just published the Tails report for June, 2017: https://tails.boum.org/news/report_2017_06/ I'm attaching a simplified HTML version for your offline reading pleasure :) Cheers, -- intrigeri

1 0

Sukhbir's June 2017
by Sukhbir Singh 06 Jul '17

06 Jul '17

Hi, In June, I worked on the following: * Tor Messenger - Released Tor Messenger 0.4.0b3: https://blog.torproject.org/blog/tor-messenger-040b3-released - Started working on the transition to ESR52. We are trying to reuse the components from Tor Browser itself by using rbm (which is what we have been using for the Tor Messenger builds.) This is going to form the major part of the work this month. * TorBirdy Worked on the following tickets: #20978 #21880 #22318 #22566 #22567 #22568 #22569 * Community - Continued working on planning Tor outreach in India with an NGO; more details later once it is finalized. - Giving two Tor talks in Toronto in August: https://lists.torproject.org/pipermail/tor-community-team/2017-June/000048.… -- Sukhbir

1 0

June 2017 grants report
by Tommy Collison 05 Jul '17

05 Jul '17

Hello, Tor! For those of you who don't know me, I'm the new grant writer -- I work closely with the communications and community teams. Here's what I got up to in my first full month on the job. ## June 2017 - Onboarded @ Tor, put a face and a name to folks I've been following/interacting with for years. - Met folks at the network team meeting in Wilmington [1]. Started thinking about how to make it easier & faster to onboard people into the Tor community. - Familiarized myself with Tor's current grants and sponsors. - Submitted a grant to improve & expand Tor Metrics. - Familiarized myself with Foundation Center, a resource for grant-writers to find funders in their fields [2]. - Started a bunch of grants due this month. TC -- [1] https://blog.torproject.org/blog/network-team-hackfest-wilmington-watch [2] http://foundationcenter.org

1 0

UX team summary for June 2017
by Linda Naeun Lee 05 Jul '17

05 Jul '17

Hi all: June felt like a productive month, mostly due to the organizational processes in place! This was the first month of weekly ticket triages *and* team meetings, which gave us a better sense of what is going on in the organization and how to prioritize our work. This month, we spent a majority of our efforts redesigning the new blog. We made design changes to update the look and feel of the website, as well as making some changes to make it easier to read blog posts and comments. The corresponding tickets are: https://trac.torproject.org/projects/tor/ticket/22510, https://trac.torproject.org/projects/tor/ticket/22392, https://trac.torproject.org/projects/tor/ticket/22395 We also iterated the first design of tor launcher according to Linda's previous research, and started to schedule content discussions for torproject.org. We were working on torproject.org stuff pretty centrally the last couple of months, but we're shifting to prioritize the tor launcher work since that has funding and a deadline while the torproject.org effort does not. Linda also attended Mozilla all-hands and talked with firefox about uplifting features, and had great discussions with Arthur, Nathan, and Amogh about what UX work to collaborate on! Exciting. Cheers, Linda N. Lee Current Key: https://pgp.mit.edu/pks/lookup?search=lindanaeunlee GPG Fingerprint: FA0A C9BE 2881 B347 9F4F C0D7 BE70 F826 5ED2 8FA2

1 0

SponsorR Status Report June 2017
by George Kadianakis 05 Jul '17

05 Jul '17

Hello, here is the June 2017 report for SponsorR: - We merged prop224 code that does additional validation of ed25519 pubkeys to defend against impersonation/fishing attacks: https://trac.torproject.org/projects/tor/ticket/22006 - Marked the first chunk of prop224 service-side code as ready for final review: https://trac.torproject.org/projects/tor/ticket/21979 - Published and reviewed more prop224 groundwork code: https://trac.torproject.org/projects/tor/ticket/22727 https://trac.torproject.org/projects/tor/ticket/22726 - Discussed some design issues with the directory system of prop224. Some work is required here to verify that the new behavior is good and specify it in the spec: https://lists.torproject.org/pipermail/tor-dev/2017-June/012336.html https://trac.torproject.org/projects/tor/ticket/22735 https://trac.torproject.org/projects/tor/ticket/22736 - Fixed an annoying hidden service crash bug: https://blog.torproject.org/blog/tor-0308-released-fix-hidden-services-also… - Started reviewing and testing of the client-side descriptor-fetching code for prop224: https://trac.torproject.org/projects/tor/ticket/21403 We are now working on the client-side introduction part of prop224.

1 0

June 2017 report for the metrics team
by Karsten Loesing 04 Jul '17

04 Jul '17

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in June 2017. On behalf of the Tor metrics team, Karsten Published a blog post to announce the release of Tor Metrics Library 2 [1]. [1] https://blog.torproject.org/blog/tor-descriptors-la-carte-tor-metrics-libra… Released Tor Metrics Library versions 1.8.0 [2], 1.8.1 [3], 1.8.2 [4], 1.9.0 [5], and finally 2.0.0 [6] with numerous changes as described in the change log [7]. [2] https://lists.torproject.org/pipermail/tor-dev/2017-June/012299.html [3] https://lists.torproject.org/pipermail/tor-dev/2017-June/012305.html [4] https://lists.torproject.org/pipermail/tor-dev/2017-June/012322.html [5] https://lists.torproject.org/pipermail/tor-dev/2017-June/012342.html [6] https://lists.torproject.org/pipermail/tor-dev/2017-June/012362.html [7] https://gitweb.torproject.org/metrics-lib.git/plain/CHANGELOG.md Completed all remaining Sponsor X deliverables running from July 2016 to June 2017 [8]. [8] https://trac.torproject.org/projects/tor/wiki/org/sponsors/SponsorX

1 0

June 2017 Transifex report
by Colin Childs 04 Jul '17

04 Jul '17

Hi everyone, Below is the monthly Transifex report for June, 2017: ### Report Attached are daily, weekly and monthly translation graphs. The Y axis is "source words". 13.60K source words 3,319 collaborators 154 languages 42 Project resources 6 languages at 100% completion (across all 42 project resources): Chinese (Taiwan) (zh_TW) French (fr) French (Canada) (fr_CA) Norwegian Bokmål (nb) Spanish (es) Turkish (tr) -- Colin Childs Tor Project https://www.torproject.org Twitter: @Phoul

1 0

Network team meeting notes, 3 July 2017
by Nick Mathewson 04 Jul '17

04 Jul '17

Hi; we had our regular meeting. Logs here: http://meetbot.debian.net/tor-dev/2017/tor-dev.2017-07-03-17.00.html And updates below: =================== Network team pad, for 3 July Meeting (or 4 July, for those in UTC+5 or later) Notes from last week's meeting: * https://lists.torproject.org/pipermail/tor-project/2017-June/001217.html (Did we do what we had planned?) Announcements and reminders: * review-group-19 ? * There are still ? tickets in 0.3.1.x, including ? in status "new" with no owner. We need to get 0.3.1.x done! * Timesheets and expenses today, please!!! * Remember to take slots in the rotation: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Reminder - isabela will be off the rest of week Things we should talk about: * I want a Windows tor developer for Christmas, but I think we'll get mobile first -teor * TROVE-2017-007 is openbsd only; need backport advice. Could use a backport team in general. -nickm * We should talk about regression tests, timing, etc -nickm Tasks for after the meeting: * teor (not online): Last week: * Started collecting entry and exit stats with PrivCount 1.0.2 * Wrote draft PrivCount Tor code to count middle circuits and cells * Helped out with tor security fixes * Tried to help out with relays stuck with low measurements #22741 #22798 #22744 https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow * Reviewed some of the circuit padding code This week: * Implement and test rendezvous circuit counts in PrivCount (We'll find out the rough usage of Tor2web and Single Onion Services) asn [Will not be home today during the meeting times.] Last week: - Did lots of reviewing on #21979. Still not done but getting there. Comment posted. - Fixed #22006 based on nick/isis review and now it's merged upstream. - Addressed coverity issue #22746. - Reviewed #15554, #22726, #22727. - Continued prop247 simulation. Started making first graphs. Adversary models are still pretty rough. - Opened #22735 and #22736 about prop224 and desc overlap period. - Wrote Wilmington blog post. Still unpublished. This week: - Finish #21979 review. Start next service-side review. - Continue prop247 simulation. - Publish wilmington blog post. nickm: Last week: * Security updates for TROVE-2017-006; new releases for 0.3.0 and 0.3.1. * Review, triage, merge, misc bugs. * Fuzzed tor_inet_pton, to no avail, since I was on linux. * Hardware issues ate a bit of my time. * Learned about harvest some. This week: * More 0.3.1 bugfix work. :p * Isabela sent me the time allocation spreadsheet betwen now and end-of-yearish. I should get it out to everyone today! * Prioritizing code review, then sponsor8 preliminaries and other code triage for 0.3.2 * It would be nice to program something. * Review time-allocation thing with everyone * Figure out whether I'm supposed to be reviewing timesheets? ahf: Last week: Sponsor 4: - Landed fix for #22702 and #22751. - Reviewed: #22752, #22719, #22797 - Started a measurement for Sponsor 4 with a Tor compiled without LZMA and Zstandard support. - Started to land updates to dir-spec.txt for prop #278 in GL/ahf/torspec/tree/prop278-in-dir-spec (#22275) Misc: - Wrapped my head around our release process. Tried to help Nick out with the release for 0.3.0.x and 0.3.1.x. - Testing of releases on OS X, FreeBSD, and Linux. - Switched from text file notes for the week to Harvest. Seems good so far. - Did everything needed before the end of the fiscial year (I hope! Items are "pending approval"). This week: - Help out with 0.3.1 issues: - Go over the Sponsor 4 measurement issues and figure out: which is solved by the current knowledge and data we have, which can be solved easily with some modifications, and figure out if there is any of them that requires any modifications to Tor that we don't currently have. - Look into the mobile proposal email from Isa. haxxpop: last week: - tried to understand fuzzing framework, but i still don't understand it much this week: - I will try to continue doing fuzzing catalyst: Last week: * bug triage * Updated TorOnTrac keywords from pad * #22745 Started regression testing discussion * #22762 reviewed komlo's edits (coding standards make check expectations) * #22773 stem fix for random nicknames on 64-bit platforms * [sponsorM] Tor Launcher UX meeting * Reproduced #20532 pluggable transport bypass; can anyone else replicate? * Opened #22743 for ed25519 point validation documentation This week: * Nail down which days I'm taking off this month for moving and notify people * Still some stem issues with lack of system tor * Look more at 0.3.1 tickets pastly: last week: PrivCount this week: rebase + squash KIST in a reasonable way dgoulet: Last week: - Put #21979 in needs_review. Big step towards prop224 service merge. - Couple of prop224 groundwork tickets have been filed which are in merge_ready - Worked on #17242 specifically the client introduction code. Out of this work, #22781 was borned and I finalized that branch this morning. - A discussion with asn on engineering details of prop224 including the overlap period and service management of introduction point. - Review some tickets in the review group 19. This week: - Continue forward with service branch merge/review - Keep going on client prop224 implementation (#17242). - I'm on triage/coverity duty this week. We are a month away from our soft deadline to have a working prototype which is not that much so expects LOTS of prop224 on my side in the coming days/weeks. komlo: Last week: - Worked on #22762, will finish this week - Had to deal with a fair amount of work/personal things so focused on that. This week: - Writing a follow up to the Rust team about our next steps, what we need to work out on our end, any ways they can help - Adding logging to Rust protover - Wondering what is the best way to mock in Rust for testing, it would be nice to learn if Servo has any good practices - Look at #22745 isabela: last week: - sent sponsor4 report - sent nick time distribution spreadsheet - met f2f with roger this week: - coordination of nsf reports today and off the rest of the week

1 0

Websites tickets triage - a.k.a. weakly cleanup
by Silvia [Hiro] 30 Jun '17

30 Jun '17

Hi, I'd like to organise a weekly websites component ticket triage. It will be held on #tor-project, ideally in the evenings (UTC speaking). I am thinking to start this coming Thursday (6th of July) at 19.00. If this tentative day and time doesn't work and you would really like to be around for the weekly cleanup, please let me know. Talk soon, -hiro

2 1