tor-project August 2018

tor-project@lists.torproject.org

19 participants
27 discussions

Notes from August 30 2018 Vegas team meeting
by Karsten Loesing 31 Aug '18

31 Aug '18

Notes for August 30 2018 meeting: Alison: 1) Mexico City meeting planning!!! Hoping to get the open days blog post out on Friday or so (with Spanish translation, need someone's help with that). We have lots of great things going on on the open days, including sessions in English and in Spanish, sessions for newcomers, and a relay operator meetup. I will be sharing the invite-days schedule draft as soon as I hear back from a couple of people who had major collisions. Then I will help people with making changes. There is lots of free time in this schedule and lots of places for adding new sessions!! I have been coordinating with teams about the team meeting day so if you haven't yet, please let me know when your team needs to meet on Sept 29. It's okay if you wait and do this yourself once I share the schedule but it may be easier to get those times to me now in case you need other teams at your meetings. I will also soon start planning the State of the Onion talk for the invite and open days, and will need to coordinate with all of you. Other than that we are just working on last minute odds and ends. If you need anything related to the meeting, just ask! 2) Starting to think about roadmapping at the meeting, looking forward to meeting with our new project manager(s). 3) LFI: We are in week 13! We just covered email privacy, next week we'll be talking about some more basic security stuff and also making a list of best practices for talking to lawmakers about privacy-related stuff (getting their support for privacy tech and practices, both locally and nationally, and how to communicate with them when bad things like Cambridge Analytica happen). After that we're talking about how to teach privacy to youth. We just sent out tshirts and pins to everyone who asked for them! 4) Gus is in Kenya with Helen already beginning trainings! Very exciting! Sarah: 1) Organizing current grant info and researching future opportunities in preparation for in-person grant meeting in Seattle 9/10-9/11. 2) Interviewing grant writers. 3) Completed MDF final report and will submit today. 4) Finalized plan with Giant Rabbit to optimize email lists and subscription process. 5) Beginning to compile information to complete state registrations necessary for fundraising. 6) YE campaign - Thinking about having a "rush"day where we have a $20K match (outside of the Mozilla match). Roger: 1) I was reminded of Micah Lee's https://github.com/firstlookmedia/gpgsync while trying to help some folks think through our new website. Maybe we have enough non-expert gpg users at Tor now that we should consider using it as an org? 2) I worry that trac has gone unusable for new users. That is, pretend you're a new user with a bug to file, and you want to show up and make an account and file a ticket. The barriers we've put up against jerks are turning away the real users too. :( [Ideas during brainstorming: we can set up a central web page to explain the situation to people. But a web page to explain that the user experience sucks will only help so much. Another floated idea was to encourage new people to file their tickets on github and then we could migrate them or something.] Steph: 1) working on the newsletter for this month 2) tba blog post ready 3) going over website copy for TPO with Antonela and Isa 4) talked with Sarah and Giant Rabbit about email lists 5) planning our def con badge. have included Antonela and ahf in the thread with the volunteer to discuss some options 6) blog post on mexico city open days in final steps 7) talking through processes / workflow between comms, ux, other teams 8) wrote press release for tb8, finalizing outreach plan isabela: 1) got some reports out still has at least 2 I want to finish by early next week. 2) balancing current projects priorities - we are about to do 2 big launches that involves work done for the past year (work done by community, ux, browser teams) 3) building documentation for new peeps (onboarding for pms) and for all peeps related to reorg and how the new workflows will look like 4) exercising my 'task delegations' and trying to get some things out of my to do list (asked Karsten for help on one of this tasks and I'm looking on whatelse can be delegated) 5) I need devs to finalize the programming languages at the anti-censorship team job post so we publish it. 6) sync with Erin on performance review process at tor and general onboarding deck 7) will build a calendar for folks to know what i am doing and when in Mexico and book 1:1s with me if they want to Karsten: 1) Continued testing ExoneraTor database changes. 2) Put out ExoneraTor version 3.0.1 with a fix to links to nearby IP addresses. 3) Started making plans for the team day in Mexico City. Mike: 1) Development work on vanguards; sponsor2 padding stuff; core-tor Georg: 1) Tor Browser 8 release preparations 2) First alpha for Tor Browser on Mobile should finally go out soonish(TM)

1 0

Network team meeting notes from 27 Aug
by Nick Mathewson 28 Aug '18

28 Aug '18

Hi! You can find the logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-08-27-16.59.html Below are our notes from the meeting. = Network team meeting pad! = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) 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 == 11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html 18 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001835.html 25 June: https://lists.torproject.org/pipermail/tor-project/2018-July/001863.html 2 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001866.html 9 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001884.html 16 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001888.html 23 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001926.html 30 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001928.html 6 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001936.html 13 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001947.html 20 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001954.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * 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… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! [but see discussion] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == 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 ------------------------------- ---- 27 August 2018 ------------------------------- == Announcements == """ Sponsor8 ends on Dec 31, and we have some deliverables that needs to make 035. The 035 merge window closes on Sept 15. With that in mind, we need to prioritize these deliverables, and ask some folks to step out from rotations and most code reviews for the next month or so, so we can get it all done. Code reviews will also prioritize sponsor8 work, so, some reviews might be delayed and not added to the weekly review spreadsheet. For the rest of us, we don't intend that reviews and rotations should take up your whole life. If you're spending more than 20% or so of your week on reviews and rotations, then we might need to recalibrate. Talk to Nick and Isa if that sounds like the situation you're in. We will resume normal team operations once we get the sponsor8 deliverables done :) thank you for the understanding. """ Sbws can match torflow! Here are our current sbws design questions: https://lists.torproject.org/pipermail/tor-dev/2018-August/013402.html We fixed some failures in chutney, tor 0.3.4 and tor master. Please pull the latest chutney, and base new branches on the latest tor. == Discussion == Who do we want at the teams day at the Mexico City meeting? (teor suggests: staff, and people who are making significant contributions to core tor, sbws, etc.) Have we missed anyone? Is it too late to ask? - Alex from the Rust team is planning to join, but noting him here to make sure we send an official invite Accepting PRs not on Github: [komlo] - It is hard to review PRs that don't have Travis output- how do we feel about requiring PRs on github for external contributors so that we can see the status of Travis builds? Is there a non-github alternative where we can still see Travis output? Is this something that should be in our Coding Standards? [catalyst: i'm inclined to agree. PRs on our GitHub repo also run Appveyor and Coveralls CI, which not everyone has enabled on their forks. in practice, when i review a non-GitHub patch or contribution, i usually push a version to my fork and make a PR so that CI runs.][Asking for PRs and/or creating PRs as needed sounds like it can be a community hero thing. -nm][+1 -teor] == Updates == Nick: Last week: - Got NSS working. It now passes all its tests, and a chutney network bootstraps, and a client connects to the network. Going to add a bunch more tests, and hunt down a couple of memory leaks, but I think we've got a good start here. Timeline for review? [catalyst: i can hand off to ahf if he's willing] - Helped diagnose timing issues in voting w mixed chutney networks (27146) - Looked at memory profiles, and opened subtickets & subsubtickets for #26630. (We're wasting a lot of memory in our directory code.) - Helped diagnose bridge bootstrapping issues w chutney on 0.3.4 (27080) - Reviewed and merged a bunch of stuff - Released 0.3.4.7-rc. New release date for 0.3.4.8: How about September 10? [works for me -teor] - Bug triage. Cleared out tickets in "- Select a component" and tickets without a milestone; worked on incoming tickets. - Fixed a crash caused by new openssl not liking some of the tricks in test_tortls.c (#27226) This week: - Actually write the sidechannels whitepaper that I said I'd finish last week :/ - NSS: add a bunch more tests, and hunt down a couple of memory leaks - NSS, Privcount, etc: revisions based on reviews, if any - Work on one or more memory reduction tickets under #26630 and #27243. - Taking off Thursday. - More review and merging teor (offline): last week: - sbws can match torflow's results (next step: design feedback) https://trac.torproject.org/projects/tor/attachment/ticket/27135/20180826_0… Thanks to juga and pastly for all their hard work! - Fixed broken bridge tests in chutney (#27080) - We changed consensus timings between 0.3.3 and 0.3.4 (#27146) - Helped with Rust linking (#27272, #27273, #27274) - Other fast fixes, reviews, and ticket triage - Helped purge old trac admin accounts this week: 0.3.4: - Review the fixes to the vanguards patch (#25573) - Get chuntney working in mixed 0.3.3/0.3.4 networks (#27146) - maybe we should run chutney in travis CI? (#20647) - our macOS time API seems to return weird results on i386 (#26987) - Create an updated list of fallback directory mirrors (#24786) 0.3.5: - PrivCount in Tor: blinding and encryption (#22898: reviews, fixes, design meeting) - bwauth work (#27135) dgoulet: Last week: - Worked on #27246 for Sponsor 8. - Worked on #27215 which makes the HS default version to 3 in 0.3.5. - Memory profiling of Tor client. From the results, nickm opened #27243 and the childs for improvements. For the curious: https://people.torproject.org/~dgoulet/volatile/perf/ - Reviewed HS client authorization branch (#20700). Almost done after the on-disk design now in the spec. Hoping to have a potential merge candidate this week. - Reviewed a series of tickets (see Timeline). This week: - Keeping myself available for #20700 next revision (client HS auth). - Review anything related to S8 tor client memory optimization. - Possibly also help asn on the HS open bugs if time permit. - Work on prop289 if time allows it. asn: Last week: - Wrote patch for #26980. This was a reliability issue for HSv3 because it was causing descriptor upload failures. Patch has been merged, and my HSv3 has been functioning well ever since. - Review #23576, #13843, #24880, #22958. - Was away from Monday and up to Wednesday. This week: - Start working on "onion services open issues" blog post with Mike. My plan is to start by writing an early draft, and then pass it to Mike for feedback. Rinse and repeat. - Get client auth (closer to) merged. - Try to get some time to seriously look into #25882. This is the main reliability issue we have in HSes (v2/v3) right now, and it's quite fundamental because it's caused by simple circuit timeouts. Diagnosing and fixing this issue is probably some work since it requires a stressed out HS. ahf Last week: - Returned to Tor after some vacation. This week: - Sponsor 8: - Get back on track with #25502 (PT error reporting) - Figure out where we are with memory optimization. - Look into Nick's NSS work. - Misc: - Go over review backlog. komlo (offline): - Last week: - Rough draft of a peer reivew checklist for research on Tor, will finish this in a month after I can meet with Ian to discuss. Once we have this I'll pair with Mike to finish this up and publish - RustConf catch up (sent an email to get Alex up to speed so he can help with diagnosing build issues) - This week: - Ad-hoc Rust ticket review, there are a lot of small tickets that need review haxxpop (offline): - Last week: - Discussed the client auth code with dgoulet - This week: - Revise the client auth pr according to the comments catalyst: - last week (2018-W34): - ran into #27226 on macos. reviewed Nick's fix - made some progress on #22266 (bootstrap progress reporting) - this week (2018-W35): - community guide rotation [to nickm] - more on #25502 and #22266 (bootstrap progress reporting) - more home maintenance backlog Mike: Last week: - Updated #25573 (half-closed connection id tracking) based on review - Kept digging into #27066. Have a potential stopgap fix. - Rebased WTF-PAD branch onto master This week: - Look over and reply to sbw mail - Continue work on WTF-PAD as per https://github.com/mikeperry-tor/tor/blob/adaptive_padding-rebased_0.3.5/PA…

1 0

Tor Browser team meeting notes, 27 Aug 2018
by Georg Koppen 27 Aug '18

27 Aug '18

Hi! Our weekly Tor Browser meeting just finished. Here are the notes, as usual. The IRC log is found on http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-08-27-17.59.log… and the pad items are below: Monday August 27, 2018 Discussion: - Status of sandboxing discussion? [GeKo: We pick this up again after the releases are out] - Next meeting [GeKo: next meeting is Tue 9/4, 1800UTC due to Labor day in the US] mcs and brade: Last week: - Investigated and posted a fix for #27221 (Tor Browser 8.0a10 wants to update to 8.0a10). - Spent a little time looking at #25694 (Improve the user experience of updating Tor Browser). - Worked on desktop onboarding: - Filed and fixed #27283 (default uitour permission does not work with 1st party isolation). - Created a patch for #27213 (Update about:tbupdate to new (about:tor) layout). - Completed our patches for #26962 (new feature onboarding). This week or soon: - Out of the office: - This Thursday and Friday (August 30 and 31). - Next Thursday and Friday (September 6 and 7). - Follow up on #26962 (new feature onboarding). - Comment in #27214 (Update descriptions for onboarding). - Do what we can for #25694 (Improve the user experience of updating Tor Browser). - Fix some of the about:tor and onboarding issues that are mentioned in #27301 (TB8.0a10 UI Bugs). - Review our notes from #22074 (undocumented bugs since FF52esr) and file additional tickets if necessary. - Do some testing for #26251 (Adapt macOS snowflake compilation to new toolchain). GeKo: Last week: -reviews -network code review -being at the Tails summit -helped debugging the TB8-is-caught-in-an-endless-loop-no-windows-bug (#27261) This week: -start building tb8 -finish network review -PSA: I made be harder available in the internet as usual between wed-sat due to travel and family obligations sysrqb: Last week: Worked on TBA-alpha preparations Reviewed mobile onboarding Began working on #26982 (httpclientandroidlib leaks information about Android version) Looked at Android specific about:config preferences (#27256) This week: Patch reviews Maybe TBA-alpha release, maybe? More of #27256 and #26982 Oh, and may be AFK on Wednesday. tjr: Not much. Waiting on reviews for mingw-clang, and feedback from jacek on https://bugzilla.mozilla.org/show_bug.cgi?id=1483762 The NSS stuff we needed in -esr60 sounds like it will land sometime soonish, so that would unblock landing build jobs there too Fission stuff. Keeping an eye out for Tor concerns =) igt0: Last week: Sent a bunch of updates to #25696 - Copy - Colors - Update configuration More updates to the mobile preferences - #27220 - #27271 This week: Finish about:tor once for all More alpha bugs sukhe: Last Weeks: - #13373 (RUNPATH), #24465 (libatomic): (related tickets) compiled but running tests boklm: we set `chrpath -d $LIB` in projects/firefox/build because of #22242. so how should we handle that for Firefox since we remove the RUNPATH later? Should I just manually set `chrpath` or should we let the RUNPATH added by selfrando, or selectively remove that? I had initially set selfrando to 0 so didn't discover it. but then later I saw in the code that if selfrando is enabled, we remove the RUNPATH for Firefox [boklm: not sure yet how to handle that. Can you post your current branch in the ticket?] sukhe: sure, thanks. - #26476 (Windows crash): continuing with the log comparisonz This Week: - #27061 (langpack) when ESR 60.2 is released - happy to help with 8.0 release including rebasing, building, testing :-) - Continue the above tasks boklm: Last week: - worked on #26149 (Add some ansible roles for tor browser testsuite setup) - helped investigate updater issue (#27221) and tested the fix made by brade and mcs - investigated and started fixing an rbm issue (#27265) This week: - work on #26149 (Add some ansible roles for tor browser testsuite setup) - reviews if needed, and help with the 8.0 release After this week: - out of the office from 2018-09-06 to 2018-09-13 (included) sisbell: Last Week: Investigated how to remove download dependencies during android gradle build Created program to generate keyrings for android build files downloaded from bintray This week: Create program to generate section of RBM config for android build dependencies Create program to collect sha hashes for dependencies downloaded from google repo and add to RBM config [boklm: not sure generated rbm config will be easy to maintain. Maybe this script could be doing the download directly instead of writting rbm config?] Verify that RBM is no longer downloading dependencies as part of the build [boklm: Could you start splitting commits from your branch (for instance, one for adding stretch to debootstrap-image, for adding android-toolchain, for adding the new platform definition to rbm.conf, for fixing the rust build, etc ...), so we can start reviewing them, and merge the parts that are ready?] pospeselr: Last Week: - investigated #26381 (about:tor not loading on first boot in localized builds) - filed bug with mozilla ( https://bugzilla.mozilla.org/show_bug.cgi?id=1485836 ) - tjr: I have no idea. bob is out today (bank holiday) but should be back tomorrow. - Was there something about this only triggering when TB was installed to a 'special folder'? - pospeselr: nope, it's a timing issue related to tor-launcher and sandboxing on windows [GeKo: the idea was that the desktop folder might be treated differently with sandboxing level >= 3 as the cypherpunk reported this is not a problem in different folders] - root cause still a mystery This Week: - continue digging into #26381 - try to identify which sandboxing setting is exposing the race condition - dig into the tab creation logic and see if I can get some sort of idea of what the actual failure is - fiddle around with the tor-launcher code and see if I can figure out what exposes the issue from there - investigate whether installing to other folders makes issue go away arthuredelstein Last week: - Wrote patch for #21787 - Performed audit for #26611 (verify no locale leaks in ESR60 `Intl` APIs) - Wrote patches for #27268 (preferences cleanup), #27262 (Remove more HTTP pipelining preferences) and #27257 (In Tor Browser prefs, "dom.network.enabled" should have been ...) - Opened and close #27291 (NoScript not working on TBB/ESR60 on Windows) after investigation - Tracked down #26561 (Onion images are not displayed) - Tracked down #26670 (Cannot allow Canvas Image Extract in tbb 8.0a9) - Wrote patch for #27276 (Update security slider to follow NoScript protocol change) - Posted strings for #27097 (Add "Tor News" newsletter signup link in Tor Browser) - Started investigation of wasm (we will disable for first stable release) - Met with Tor uplift team This week: - Fix #26561, #26670, #26520 (NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser) - Create Tor Newsletter link (#27097) - More ff60-esr fingerprinting resistance things as time allows - Whatever's needed for next release Georg

1 0

[TSoP 2018] Ahmia status update - report #7
by Stelios Barberakis 27 Aug '18

27 Aug '18

Hello all, This comes in late, sorry about that, we had some issues deploying the recent changes. The new things that we have integrated since the last report are: --- Ahmia Site --- * Integrated Page Popularity algorithm (based on backlinks). The goal here is to improve the sorting (of the results), by pushing the popular pages a bit higher. Tuning the formula to combine page popularity score with the IR (information retrieval) score, optimizing for all cases, is a black art. It will need a lot of testing. It's currently deployed as a silent feature (you need to append &r <https://ahmia.fi/search/?q=onion+routing&r> at the end of the url), so that we can evaluate the results we get on the production environment, before making it the default. Current results are not great, but they are promising, and I am confident that we will further improve it (some ideas are listed in the reference). [1] * Improved django validators and added v3 onion support (that applies for the domains added by user only, since the crawler and index were already working with v3) [2] * Improved statistics figures by increasing the width and adding grid lines [3] * Updated travis configuration to match the current development [4] I am really glad and thankful that I had the chance to participate in this summer of privacy program. I suppose this is the last report for this summer, however there are still things that I plan to work on, so I will continue to participate on ahmia development in my own pace. The OFTC channel is currently active, which means that we are open to any ideas, suggestions etc. Best Regards, Stelios [1] https://github.com/ahmia/ahmia-site/issues/30 [2] https://github.com/ahmia/ahmia-site/pull/34 [3] https://github.com/ahmia/ahmia-site/pull/36 [4] https://github.com/ahmia/ahmia-site/pull/42 -- PGP key: http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xF9A1BD9B4DDEBDEF

2 1

Notes from August 23 2018 Vegas team meeting
by Karsten Loesing 27 Aug '18

27 Aug '18

Notes for August 23 2018 meeting: Georg: 1) Tor Browser 8.0a10 got out; got good feedback and good bug reports 2) The first Tor Browser for Mobile alpha is about to get out 3) We scrambling to our feet to fix all the things we need to have fixed for Tor Browser 8.0; tentative release candidate build start next Wed/Thu; code freeze next Wed; the release date is 9/5 isabela: 1) Interviewing Grant Manager and Grant Writer candidates 2) Meeting with Mozilla on research about Tor brand perception and convincing points 3) Reviewing lots of copies! Tor Browser desktop and mobile alpha releases, newsletter banner and other docs folks needed me to review related to campaigns 4) Still working on sponsors reports and invoices - got some out, still behind on a couple of them 5) Prep-work for week of sept 10th in Seattle meeting w/ finance and fundraising teams 6) Board meeting last Monday (8.20) my first one :) finally 7) Continue to work whenever I can on PMs onboarding (they should start mid Sept so I have some time) 8) Plan on sending Alison some session ideas this week (sorry I'm behind on this) Steph: 1) TBA and website copy 2) blog editing 3) someone we met at def con has offered to make a badge for us! talking through options — is there someone with electronics design or firmware experience to talk through some options? 4) talking over email list optimization, newsletter signup banners Sarah: 1) Working on MDF report and will finish first draft by tomorrow. 2) Completed update of torproject.org/donate. Giant Rabbit should make this live today. 3) Working with Steph to better track upcoming conferences and speaking engagements. I'd ideally like to start building in major donor luncheons and other visits to existing travel. 4) Optimizing email list creation and clarifying usage in Civi as well as making the subscribe/unsubscribe process easier for the user. 5) Collecting and organizing past YE campaign materials and results to begin putting together this year's plan. Mike: 1) Will review Roger's updated Sponsor2 report today (just saw the mail). 2) Still pondering research developer position. I might work on a draft JD to see what people here think? [Sounds good to me, GeKo] Alison: 1) I'm working on LFI curriculum changes for next year and starting to think about end of year recruitment. 2) Organizing MX agenda emails into an initial draft schedule, will be sharing with everyone very soon and then folks can edit as they wish. 3) Gus is getting everything ready for his Kenya trip. 4) He is also working on some outreach efforts for Mexico (Oaxaca, Mexico City) 5) Outreachy has ended, but we're encouraging our two interns to stick around. 6) Colin is working on a plan for regular relay operator meetings. He will pilot it with two a month to address different timezones. 7) Jaruga, Colin, Tommy, and Gus are working with emmapeel to add more languages to the TB manual. Karsten: 1) Started cleaning up all five major metrics codebases based on static code analysis. 2) Rebased a two-years old ExoneraTor branch with major improvements to the database schema that will hopefully not only reduce database size but also minimize variance of query response times. Nick: 1) Mostly hacking 2) We're focused on sponsor8 deliverables for our sep15 merge deadline; other stuff may be slowed in Tor. 3) I hope to have another 0.3.4 out by the end of the month -- maybe a release, but that depends on bugs and the complexity for fixing them.

1 0

July Community Team update!!!!!
by Alison Macrina 22 Aug '18

22 Aug '18

July 2018 Community Team highlights Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Tor Meeting ================================================================= In July we continued to plan the Mexico City meeting, with special emphasis on the open days. Outreachy and Summer of Privacy ================================================================== Jaruga continued work on documentation (her work can be tracked here [1], and Cy continued collecting Tor user issues from around the web [2] Library Freedom Institute ================================================================== Alison covered weeks 5-9 in LFI and made plans for our in-person meetup in NYC. You can follow our progress, too [3]. We also started working with Mozilla to bring the Glass Room Experience to North American libraries. Tor talks and outreach ================================================================== We had a great time at the HOPE conference in NYC! Lots of people stopped by our table, we held an excellent informal workshop about running relays, and you can check out our "official" panel talk here [4]. Gus held a Tor meetup at FISL in Porto Alegre, Brasil [5]. He also began planning a few other Tor outreach/UX events -- in September he'll conduct outreach and workshops in Nairobi, Kenya, Oaxaca, Mexico, and Mexico City. He also translated the Tor training slides into pt-BR! Relay advocacy ================================================================== Colin held a relay operator meetup at PETS in Barcelona. Around 40-50 people attended that and an onion workshop, and then everyone went to an afterparty at a local bar. He got great feedback from local operators and a few commitments to running new relays! Colin, Jaruga, and nusenu worked on keeping the relay operator wiki updated. Colin began work on system to collect new relay operator contact information in order to send monthly "welcome" / "thank you" emails. He also worked on updating the fallback directory list Colin also started working with a developer on possibly reviving Tor weather. He also began initial planning for a relay operators meetup in Mexico City during the meeting, as well as a larger relay community summit. User support and localization ================================================================== emmapeel started as localization coordinator, and Colin helped get her onboarded and hand off localization tasks. The support portal had its "soft launch" and we worked on updating the content with some of the information Cy found in researching user issues. Gus and emmapeel worked on a localization content workflow for the portal [6]. We created new TB 8.0 content for the Tor Browser manual and started working on localization. Other stuff ================================================================== We changed the meeting time to Mondays at 1600 UTC to be friendlier to more timezones. ================================================================== [1] https://tor.dial.ga/ [2] https://ethercalc.org/fk4bgj7ntrbj [3] libraryfreedom.chat (read only) [4] https://livestream.com/internetsociety/hope/videos/178158095 [5] https://blog.torproject.org/tor-meetup-porto-alegre-brasil [6] https://lists.torproject.org/pipermail/tor-community-team/2018-July/000195.…

1 0

Minutes from June 20th meeting
by biella 21 Aug '18

21 Aug '18

Hi all, Here are the June 20th 2018 Tor board minutes, approved Monday. I will be pasting our minutes in the body and providing the permanent link to them and as I mentioned sending them out shortly after our board meetings. Regards, Biella https://gitweb.torproject.org/company/policies.git/plain/minutes/TPI_Board_… Tor Board Meeting Minutes for June 20, 2018 Phone/Video Meeting called to order at 16:00 UTC Present: Shari Steele, Matt Blaze, Ramy Raoof, Cindy Cohn, Linus Nordberg, Biella Coleman, Nick Mathewson, Julius Mittenzwei, Megan Price, and Roger Dingledine 1. Administrivia – Approval of April 16, 2018 minutes. Matt moved the motion, Megan seconded, all voted in favor. RESOLVED: minutes from April 16, 2018 approved. – Approval of March 12, 2018 minutes with amended time from 17:00 UTC/16:00 Rome to 16:00UTC/ 17:00 Rome time. Biella moved the motion, Matt seconded, all voted in favor. RESOLVED: minutes from March 12, 2018 approved. – Discussed potential dates for Mexico City Board meeting with current proposal being: October 1st closed meeting and October 2nd in the morning for the open meeting. 2. Executive Director Transition Overview – Job descriptions for two project manager positions and fund raiser have been drafted and circulated. 3. Personnel Overview – Shari provided an overview of personnel status. 4. Finances – Shari went over 2017-2018 financials and proposed budget 2018-2019. – Went over future/upcoming Tor Budget for July 1 2018 to June 30 2019. Biggest change is an increase in salaries/benefits and to accommodate new hires. – Approval of 2018-2019 budget: Megan moved the motion, Cindy seconded, all voted in favor. RESOLVED: 2018-2019 budget approved. 5. New Board Members – Cindy will be proceeding to follow up for inviting potential candidate to Mexico City. Ramy left at 13:30 6. Other Business – With feedback in place, Biella will be finishing finalization of meetings minutes for release. Meeting Adjourned at 13:41 UTC

1 0

Fwd: Call for ideas: What should be in the Internet Health Report?
by Matthew Finkel 21 Aug '18

21 Aug '18

FYI. (I also replaced the clicktrackers in the below email) ---------- Forwarded message ---------- From: Mozilla <Mozilla(a)e.mozilla.org> Date: Tue, Aug 21, 2018 at 2:27 PM Subject: Call for ideas: What should be in the Internet Health Report? To: matthew.finkel(a)gmail.com Dear Mozillians, Today the Internet Health Report team is launching a Call for Ideas <https://internethealthreport.org/yourideas/>-- an opportunity for friends, allies, and readers to suggest the topics that deserve coverage in the next Report. The Internet Health Report <https://internethealthreport.org/2018/> is a check up on the internet. It includes research and stories from people all over the world on how the internet is working for good--or bad--in their lives. * We invite everyone to submit ideas <https://docs.google.com/forms/d/e/1FAIpQLScjVdkx69izq7NbaiHfrh_GiDtYVqaYYnq…> before September 14. * We’re mainly looking for research, articles, and inspiring initiatives to make the internet healthier, but also suggestions about issues people don't hear enough about. We accept ideas on our website <https://internethealthreport.org/yourideas/> (anonymous or public) or by Twitter message (use the hashtag #internethealth). To kick- off the campaign we will host a Twitter chat today (August 21)* 1pm - 2:30pm ET (7 - 8:30PM CEST)*. We hope you will join! Just follow the conversation led by @mozilla. *Please help us spread the word in your communities and among friends who care about the health of the internet.* Here is an example tweet you can use: 🚨 Mozilla is hosting an #internethealth Report Call for Ideas 🚨 You can recommend what topics — from facial recognition to cyberwarfare — should be investigated in 2019 Report. Reply with ideas + links to studies or projects we should examine or visit https://mzl.la/ideas The Call for Ideas is available in 4 languages (English: https://mzl.la/ideas // French: https://mzl.la/idees // Spanish: https://mzl.la/tusideas // German: https://mzl.la/ideen), but submissions can be from anywhere in the world and in any language. We hope you'll join us on Twitter or get your ideas over to us before September 14th. Working for a healthier internet is a team effort. A big thank you for being part of the team. The IHR team (Solana, Kasia, Jairus) ------------------------------ * You're receiving this email because you're a registered Mozillian. We'll send you timely and occasional organizational news and updates - meant just for Mozillians. If you do not wish to receive these updates, please unsubscribe here <https://click.e.mozilla.org/?qs=434b787285796223cb44611de89db42b894961b4abb…>. We do some aggregate tracking <https://click.e.mozilla.org/?qs=434b7872857962231855305363464b18ffc116e671e…> on these emails to improve the experience. If you would like to opt out of tracking please update your email preferences <https://click.e.mozilla.org/?qs=434b787285796223cb44611de89db42b894961b4abb…> to text only. Read the Mozilla Privacy Policy <https://click.e.mozilla.org/?qs=434b787285796223eaa5632e7b5773baea58179e303…> here.* Mozilla 331 E. Evelyn Avenue <https://maps.google.com/?q=331+E.+Evelyn+Avenue+%0D%0AMountain+View,+CA+940…> Mountain View, CA 94041 USA -- Matthew Finkel

1 0

Tor Browser team meeting notes, 20 Aug 2018
by Georg Koppen 21 Aug '18

21 Aug '18

Hi! We had another Tor Browser meeting yesterday. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-08-20-17.59.log… And here are the notes from our pad: Tor Browser Meeting Notes Monday August 20, 2018 Discussion: -tommy: Tor Browser for small businesses -reminder: sessions for Mexico - Mozilla viewport size quantization: https://bugzil.la/1407366 - viewport fingerprinting for mobile (igt0: I know sysrqb opened a bug, I wonder if we fix it for mobile, it will make the sites terrible) (GeKo: That's #27083. Let's discuss the drawbacks/improvements compared to our current solution there, in general I think mobile is no showstopper here) mcs and brade: Last week: - Finished #26514 (intermittent updater failures on Win64). - Worked on desktop onboarding: - Updated our patches for #26961 (new user onboarding). - Updated out patches for #27082 (enable a limited UITour). - Worked on #26962 (new feature onboarding). - Answered updater questions for #25485 (libstdc++.so.6: version `CXXABI_1.3.11' not found). - Sent Alison some ideas for the Mexico City meeting agenda. - Helped with triage of incoming bugs. This week: - Continue working on #26962 (new feature onboarding). - Scope the work and determine what we have time to implement for #25694 (Improve the user experience of updating Tor Browser). - Review our notes from #22074 (undocumented bugs since FF52esr) and file additional tickets if necessary. - After the Tor Browser nightly builds include the network team's fix for #26876, do some testing for #26251 (Adapt macOS snowflake compilation to new toolchain). GeKo: Last week: -release preparations and release help -helped with mobile reviews and testing (we are close!!) This week: -help with the mobile release where needed -monitoring our blog etc. for 8.0a10 fallout -trying to finish network code review -starting to the Tails summit on Saturday -planning the work for remaining two weeks before 8.0 hits the ground -igt0, sysrqb, sisbell: should we get together to plan the post-first-tba work? (GeKo: the decision was, yes, maybe later this week after the alpha is out) -reminder: please do your daily status updates on #tor-dev (/me status: fixing everything) -pospeselr: it seems #26450 fell through the cracks? Was that ready for review again after my initial pass? (GeKo: no, all is good) sysrqb: Last week: - Release preparations for first alpha version of TBA - Reviewed #25696 - Android onboarding - Reviewed #26884 - torbutton on android - Clarified #26314 - Mobile TB landing page - Attended RustConf - Started creating Android signing key for Alpha release(s) - #26536 - Revised Android permissions - #24796 - Worked more on Investigating Account Manager patch - #26858 This week: - First TBA Alpha release - Finish #26858 - Bug fixing... arthuredelstein: Last week: - Finished audit of HTTP2/AltSvc (#14952) - Finished audit of User Timing API (#26598) - Patches for "Add ca, ga, id, is, nb locales for Tor Browser" (#27129) - Patched "UI locale is detectable by button width" (#24056) - Patch for "Add new Tor Browser locales to our website" (#27151) - Reviewed #26456, #26833, #26628, #26655 - Met with the Tor Uplift team - Updated https://torpat.ch/locales and https://torpat.ch/support-locales This week: - More fingerprinting protections for ff60-esr - Review https://bugzilla.mozilla.org/show_bug.cgi?id=1333933 for unpatched items - Any patch reviews needed - Optimistic SOCKS? (GeKo: that won't be in 8.0 as we need more testing than our schedule provides. It's therefore not high prio but we should work on it during our 8.5 dev time) boklm: Last week: - fixed some testsuite tickets: - #27133: update useragent string in fp_navigator, useragent and settings tests - #27122: fix slider_settings tests - made patch for #25485 (replace firefox by a wrapper script) and tested it - made patch for #27178 (add support for xz compression in mar files) - helped build and publish 8.0a10 release This week: - continue working on #27105 (Fix Tor Browser testsuite for esr60) and subtickets - look at #12968 (HEASLR) PSA: I'm planning to be afk from 2018-09-06 to 2018-09-10, just after 8.0 release igt0: Last week: - Did several UX iterations on #25696 (On boarding) - Fixed issues in the #26884 (sec settings) - Iterated again in the about:tor for mobile(I am trying to avoid to change lot of gecko code) - Reviewed some code This week: - Finish about:tor (#27111) (I am testing in on tablets) - Update XPInstall to bypass the addons signature checks pospeselr: Last week: - #26874 (smb leak) uplift (was actually a bug introduced by another Mozilla patch, so they're handling it) - reviewed boklm's #27045 [boklm: can you post the logs from the error you get? pospeselr: done!] - rustconf on the 16th and 17th, successfully indoctrinated into the cult of rust - a bit of investigation into #26381 (about:tor page not loading properly in localized windows bundle) This week: - continue #26381 investigation sisbell: Last Week: Attended RustConf on 16-17 Created program to parse android dev file. Found indexes on class annotations differ between builds. This week: Parse data sections of dex file to get more info on deltas between builds. sukhe: Last Weeks: - #26476 (Windows crash): still investigating, doing log comparison now between TC and tor-browser builds - Looking at #24465 (Snowflake bundle libatomic; revision) and #27061 (langpack) - Merged #27152 (fxc2 update; small change) This Week: - Continue the above tasks Georg

1 0

Network team meeting notes, 20 Aug 2018
by Nick Mathewson 20 Aug '18

20 Aug '18

Hi! You can find our logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-08-20-17.00.html Below are the notes from our meeting today: = Network team meeting pad! = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) 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 == 11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html 18 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001835.html 25 June: https://lists.torproject.org/pipermail/tor-project/2018-July/001863.html 2 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001866.html 9 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001884.html 16 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001888.html 23 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001926.html 30 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001928.html 6 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001936.html 13 Aug: https://lists.torproject.org/pipermail/tor-project/2018-August/001947.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * 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… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! [but see discussion] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == 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 ------------------------------- ---- 20 August 2018 ------------------------------- == Announcements == """ Sponsor8 ends on Dec 31, and we have some deliverables that needs to make 035. The 035 merge window closes on Sept 15. With that in mind, we need to prioritize these deliverables, and ask some folks to step out from rotations and most code reviews for the next month or so, so we can get it all done. Code reviews will also prioritize sponsor8 work, so, some reviews might be delayed and not added to the weekly review spreadsheet. For the rest of us, we don't intend that reviews and rotations should take up your whole life. If you're spending more than 20% or so of your week on reviews and rotations, then we might need to recalibrate. Talk to Nick and Isa if that sounds like the situation you're in. We will resume normal team operations once we get the sponsor8 deliverables done :) thank you for the understanding. """ If anyone has an opinion on bwauth scaling and how sbws needs to match torflow, please contribute to: * https://github.com/pastly/simple-bw-scanner/issues/182 * Trac #27135 We don't want to be making last-minute changes to the design. == Discussion == Do these tickets block 0.3.4: - our macOS time API seems to return weird results (#26987, #27139) - did we break the consensus between 0.3.3.9 and master? (#27146) [I've tried to opine on these tickets. -nm] == Updates == Nick: Last week: - NSS TLS stuff. Got X509 working (?). Worked on TLS initialization. - Worked on roadmap revision - Met about congestion control alternatives - Review & merge a bunch of patches - Initial (messed up) bisecting on #27080 This week: - Draft a whitepaper about datagram-related attacks - NSS TLS: maybe finish the implementation? - Help work on 034 blocker tickets. teor (offline): last week: - PrivCount in Tor: blinding and encryption (#24629, #26972) - bwauth mentoring (mainly https://github.com/pastly/simple-bw-scanner/issues/182 and #27135) - Reviewed the large vanguards patch (#25573), and other code reviews (#23588, #15188, #22747, #27190 #27191) - Worked on bridges are broken in 0.3.4 and master (#27080) - our macOS time API seems to return weird results (#26987, #27139) - did we break the consensus between 0.3.3.9 and master? (#27146) - I was on leave for a local holiday on Wednesday this week: - Keep on trying to fix bridges are broken in 0.3.4 and master (#27080) - PrivCount in Tor: blinding and encryption - reviews, fixes, design meeting - other reviews and revisions rest of 0.3.5: - work out the earliest rust version tor supports, and add CI for it - Implement PrivCount in Tor noise generation (#26637, maybe #26398) - Merge PrivCount in Tor komlo (offline): - Last week: - Gave a talk about Rust, had a lot of conversations about how to move forward with some existing Rust issues. Will be sending updates/syncs this week - This week: - Finish writing a draft for a peer review checklist, will work with Mike on adding his input/finalizing this - Look over recently-opened Rust tickets (thank you to the people opening these and adding improvements!) haxxpop: - Last week: - The client auth code is ready for review and test. Even thought the test still fails on Windows but I think we can review and test the code while I fix this issue. The code is in https://github.com/torproject/tor/pull/36 - This week: - One thing that we haven't discussed about yet is how clients generate their keypairs (how the command will look like). After discussing about this, I think I will implement it. catalyst: - last week (2018-W33): - CI/Coverity rotation - reviewed some more of teor's CI changes - PM candidate interviews - more digging in bootstrap related code for #25502, #22266 - this week (2018-W34): - design meeting organizer rotation - #25502, #22266 (bootstrap progress reporting improvements) Mike: Last week: - Continue discussions about congestion control - Make sure Sponsor2 report is good for submission - Chat with Tobias Pulls about adaptive padding implementation variants - Code reviews This week: - Help with anti-censorship hiring process - Update #25573 - Keep digging into #27066 - WTF-PAD proposal update - Research website update - Vanguards/onion service security blog post with asn?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project August 2018