- tor-project - lists.torproject.org

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

meetings and laptops
by S. Banerian 30 Jun '17

30 Jun '17

In view of possibilities of issues with laptops and travel, I was wondering if folks had taken access issues into account in planning meetings. I, for one, likely will not try to take a laptop into the US. Thoughts? stefani

1 0

Notes from June 29 2017 Vegas team meeting
by Karsten Loesing 30 Jun '17

30 Jun '17

Notes for June 29 2017 meeting: Alison: 1) Community Team roadmap progress -- still identifying goals and dependencies for the rest of the year. Main priorities are the dependencies and thinking about better ways to have communication channels with devs. 2) Potential new support hire planning with the comms team and the community team 3) Trusteer and Tor Browser situation -- some Windows 10 users can't open TB with Trusteer (anti-fraud, required by banks) software enabled. Colin is digging into this, hoping to have a full update soon. This issue is making me think broadly about support to developer feedback. 4) Support wiki -- hope to have this out next week. Making final edits, writing blog post now. Roger: 1) I did some of my logistics/bureaucracy stuff this past week, but much remains: SponsorR paper to review, PETS paper to review, Defcon slides to write, three NSF reports to start 2) Membership guidelines discussion is proceeding. I think we're getting good feedback so far, and there is work to be done. 3) Brad, Isa, Shari, are we all set with that government certification thing? 4) If you need a Defcon ticket, I might be able to swing a few. Let me know. 5) I'll be seeing Isabela in person right after this meeting, and probably Alison a bit after that, if you need us to discuss anything. Steph: 1) First more donor-focused email newsletter going out in 1-2 weeks. Working with Giant Rabbit to get set up on CiviCRM; they have to create an unsubscribe capability for sending newsletters. I'm creating the template now. Will start monthly, possibly become more frequent. Will be fed by previously published content: blog posts, jobs, press, events, etc. 2) Will be moving press list to CiviCRM; Giant Rabbit is building out with chosen fields now Nick: 1) Putting out releases this week with fixes for TROVE-2017-006. Affects 0.3.0 and later. TBB releases will be warranted IMO. 2) Wanting to resolve license status of torspec: https://trac.torproject.org/projects/tor/ticket/18788 What to do? Should I grab a copyright person? 3) We're starting a "must have regression tests for bugs" policy; let's see how it goes. Other teams might want to watch and see whether they want one too. 4) Wrt fiscal year closing soon: let's not be quiet if anybody's timesheets/reports are late. Instead let's reach out to them right away, so we don't leave Sue & Brad hanging. 5) Should I approve timesheets? How? 6) Working on getting point-of-contact for PT issues. 7) Discussing how we can interact better with external developers/teams who write big patches. Arturo: 1) OONI measurements API now uses as a backend the new data processing pipeline: https://github.com/TheTorProject/ooni-measurements/pull/22 2) Next week we will be making a new ooniprobe mobile release that adds support for sending push notifications to users informing them of things happening in their country/network, asking them to collect more data. Shari: 1) Did some budget work and readjusting expenses based on new fiscal year starting next week. 2) Working with communications team to get our voice right. (nickm offers to help) 3) Back to the drawing board with strategic planners. 4) Working with Erin on updating employment and other Tor policies. 5) Pulling together a team and talking with Giant Rabbit about our end-of-year fundraising plans. Karsten: 1) Released Tor Metrics Library 2, blogged about it, completed Sponsor X award that ends June 30, 2017. Mike: 1) At Mozilla all hands this week. They are excited to work with us. The overall mood seems much more favorable to us than in years past. Isabela: 1) Working on spreadsheet with time allocation for network team and sponsors. 2) Website redesign contract soon coming in for review, to be signed mid-August. Brad: 1) Preparing for year-end close process (fiscal year ends 6/30) 2) Transitioning to new payroll provider for US-based employees effective 7/1

1 0

Is anybody going to Defcon?
by Roger Dingledine 28 Jun '17

28 Jun '17

I'm giving a talk, and I think I can get some of us in for free if I work at it. Let me know if you're a Tor person and you're going and you'd otherwise be needing to pay for registration yourself. --Roger

2 1