- tor-project - lists.torproject.org

May 2018 report for the metrics team
by Karsten Loesing 25 Jun '18

25 Jun '18

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in May 2018. On behalf of the Tor metrics team, Karsten Completed the draft document with graph specifications to now include all graphs on Tor Metrics. Resolved a series of smaller inconsistencies in statistics on Tor Metrics, including: number of bytes spent on directory requests [1], bandwidth histories [2], and onion services [3]. [1] https://bugs.torproject.org/26002 [2] https://bugs.torproject.org/26015 [3] https://bugs.torproject.org/26022 Extended per-graph CSV files on Tor Metrics to support ad-hoc generation of CSV files without parameters to cover more data than what's displayed in a graph [4]. [4] https://bugs.torproject.org/25383 Improved explanations of metrics and flags on Relay Search [5, 6, 7] [5] https://bugs.torproject.org/25881 [6] https://bugs.torproject.org/25854 [7] https://bugs.torproject.org/26079 Put out new releases of CollecTor and metrics-lib [8] as well as Onionoo, ExoneraTor, and metrics-web [9] to switch from Gson to Jackson as JSON library. [8] https://lists.torproject.org/pipermail/tor-dev/2018-May/013191.html [9] https://lists.torproject.org/pipermail/tor-dev/2018-May/013204.html Extended CollecTor's index.json file to include contributed data in preparation of serving metrics-related research data from the wider Tor community on Tor Metrics.

2 1

[TSoP] stem.client - status report #3
by Dave Rolek 25 Jun '18

25 Jun '18

Hi everyone! This is my third status report for the stem.client TSoP project [1]. You may see my previous reports on the tor-project ml. [2][3] This report comes a bit late - sorry about that! # Updates Last week I was feeling ill, so I didn't tackle things quite as big (long periods of concentration were hard to achieve) nor get quite as much done. ## stem.client I pushed things forward a bit on code review [4][5][6], including branching some discussion/findings out into separate tickets [7][8][9]. Still waiting on some architecture discussion [10]. ## stem, general I did a few small fixes: * document the --quiet testing flag [11] * improve reliability of an integration test [12] * address some linter findings [13] I also spent some time working on the tox configuration, although that's not push-ready, so I don't have a reference for that. ## tor protocol, general Per previous suggestion from Roger, I've been glancing through the tor-design paper [14][15][16] and updates [17][18][19] while reading the specification, and that's been helping solidify my understanding. I neglected to mention in my last update that I brought up handling of padding bytes [20] at the network-team meeting that week. There's been a bit of discussion thereon with atagar in the context of stem.client. # What's next ## stem.client Per my previous plan, I'll be tackling some not-so-architecture-dependent changes. Hoping to get some feedback on the architecture soon, and start implementing some of those changes! ## stem, general I still have a few 'dev' tickets I'd like to work on. As mentioned above, I've done some work on improving the tox configuration, so I plan to wrap that up. ## tor-spec As aforementioned, I'll push forward on the padding bytes ticket [20] into a spec change. # Other Tor things On the side, I've spent time chatting with a lot of people about tor in the past few weeks, and it's really cool to see how many people are interested in it! This has spanned a wide range of professions from journalists, to artists, to musicians, to librarians, to software developers, to students, and more (I can't even remember all of it - lots of informal discussions). The Tor Browser manual's graphic showing a connection to a website [21] has been pretty helpful for ad-hoc descriptions. And when I haven't had paper to draw on, I've used various small objects to cover up parts of the graphic to contrast Tor with a VPN, and people have been able to make the mental leap! One person already came with some pre-existing knowledge of Tor, and so with him I asked him to explain what he thought Tor was / how it worked prior to any other input / visual aid (didactic strategy of having others teach you), and he did a pretty good job! I helped set a few things straight, but it was cool to know that he'll likely be able to explain Tor confidently now to anyone else. :) # Closing As with before, I've been active and reachable over IRC, where my nick is dmr. Please don't hesitate to reach out to me via IRC or email! Thanks, Dave [1] https://lists.torproject.org/pipermail/tor-dev/2018-April/013090.html [2] https://lists.torproject.org/pipermail/tor-project/2018-May/001811.html [3] https://lists.torproject.org/pipermail/tor-project/2018-June/001830.html [4] https://trac.torproject.org/projects/tor/ticket/26227#comment:7 [5] https://trac.torproject.org/projects/tor/ticket/26227#comment:9 [6] https://trac.torproject.org/projects/tor/ticket/26227#comment:13 [7] https://trac.torproject.org/projects/tor/ticket/26420 [8] https://trac.torproject.org/projects/tor/ticket/26431 [9] https://trac.torproject.org/projects/tor/ticket/26432 [10] https://trac.torproject.org/projects/tor/ticket/26226 [11] https://trac.torproject.org/projects/tor/ticket/26421 [12] https://trac.torproject.org/projects/tor/ticket/26225 [13] https://trac.torproject.org/projects/tor/ticket/26483 [14] https://www.torproject.org/docs/documentation.html.en#DesignDoc [15] https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf [16] https://svn.torproject.org/svn/projects/design-paper/tor-design.html [17] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-1 [18] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-2 [19] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-3 [20] https://trac.torproject.org/projects/tor/ticket/26228 [21] https://tb-manual.torproject.org/en-US/media/how-tor-works.png

1 0

[TSoP 2018] Bandwidth scanner update - report #3
by juga 24 Jun '18

24 Jun '18

Hi, since report #2, these are the tasks i have worked on: Tor directory protocol: ------------------------ - started to work on specification for archiving bandwidth files [0] Bandwidth List format specification: -------------------------------------- - possible text to add regarding limiting measured bandwidth to MaxAdvertisedBandwidth [1] - fix Bandwidth file Timestamp is the latest scanner result, not the file creation time [2] little-t-tor -------------- - add test to check that descriptor is only updated on bandwidth changes when uptime is less than a day [3] - started to work on what makes some relays to advertise zero bandwidth-observed [4] Simple Bandwidth Scanner (sbws): --------------------------------- - keep previous bandwidth files and rename them to the date when they are generated [5] - run sbws with different python versions to find which ones fail with python lru_cache [6] - fix bandwidth file's earliest bandwidth [7] - fix node_id in bandwidth file to start with "$" [8] - find a bug when running sbws with python 3.4.2 [9] - find a bug when running sbws with python 3.4.5 [10] - fix a bug when there is not enough RAM [11] - suggest moving plotting scripts to other repo [12] - review limiting measured bandwidth to the advertised bandwidth [13] - review new Relay class [14] - discuss possible solutions when stem controller fails [15] - review integration test for RelayPrioritizer [16] [0] https://trac.torproject.org/projects/tor/ticket/21378 [1] https://trac.torproject.org/projects/tor/ticket/8494 [2] https://trac.torproject.org/projects/tor/ticket/26155 [3] https://trac.torproject.org/projects/tor/ticket/24104 [4] https://trac.torproject.org/projects/tor/ticket/24104 [5] https://github.com/pastly/simple-bw-scanner/issues/179 [6] https://github.com/pastly/simple-bw-scanner/issues/198, https://github.com/pastly/simple-bw-scanner/issues/193 [7] https://github.com/pastly/simple-bw-scanner/pull/187 [8] https://github.com/pastly/simple-bw-scanner/pull/188 [9] https://github.com/pastly/simple-bw-scanner/issues/194 [10] https://github.com/pastly/simple-bw-scanner/issues/203 [11] https://github.com/pastly/simple-bw-scanner/issues/195, https://github.com/pastly/simple-bw-scanner/pull/196 [12] https://github.com/pastly/simple-bw-scanner/issues/201 [13] https://github.com/pastly/simple-bw-scanner/pull/191 [14] https://github.com/pastly/simple-bw-scanner/issues/180 [15] https://github.com/pastly/simple-bw-scanner/issues/192 [16] https://github.com/pastly/simple-bw-scanner/pull/206

1 0

Tor blocked in Venezuela
by Maria Xynou 23 Jun '18

23 Jun '18

Hello, As of last night (or last morning, Venezuela-time), we've been receiving reports from locals in Venezuela that Tor is being blocked. State-owned CANTV is reportedly blocking access to Tor and obfs4. They've been running OONI Probe tests that seem to confirm this, though it remains unclear if other ISPs in Venezuela are blocking access to Tor (and Tor bridges) as well. This follows weeks of increased censorship, particularly targeting media websites (like lapatilla.com and elpitazo.com) What strategies would be relevant here? This may also be something worth thinking about for other countries where Tor is blocked as well (such as Egypt). Best, Maria. -- Maria Xynou Research and Partnerships Coordinator Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

9 11

[TSoP 2018] Ahmia status update ~ report #3
by Stelios Barberakis 23 Jun '18

23 Jun '18

Hello all, This is a status report for the development of ahmia.fi as part of tor summer of privacy. The things that have been *completed* the past two weeks are: * a migration script to automate copying Elasticsearch data from the old indices to the new ones according to the new scheme * a filter by time drop down menu, for the results page * set up the production environment on my workstation, the correct way... * some minor todos BR, Stelios -- PGP key: http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xBF6EA91B7CBE3998

2 1

Notes from June 21 2018 Vegas team meeting
by Karsten Loesing 22 Jun '18

22 Jun '18

Notes for June 21 2018 meeting: Roger: 0) I'd like to call out Tom Ritter as being really super helpful last week at Mozilla All Hands, for organizing many many meetings for us and Mozilla folks, and making sure that our time there was really efficiently well spent. Thanks Tom! 1) Can we find a better duckduckgo contact for Isa? (better than what? What does Isa need the contact for? I have contacts at DDG.- Shari) 2) Shari, followup: status of funding-by-category-by-year spelunking? (maybe I'll be able to get back to that next week. that would be nice.) 3) Shari, followup: is sida money we-have-to-spend-it-to-keep-it? (no) 4) Mike: please confirm receipt of SponsorWTFPad annual report mail [Mike - I do not have a fastlane account. In the past, I sent you and Matt a bullet list of items to become the final report.. Am I supposed to write the whole thing this time?] 5) GeKo: Shari's funding pipeline report said there's $16k left in the OTF bug bounty funding, scheduled to end in August. We can get an NCE, so no huge deal, but I wonder if we should expand our publicity for the bug bounty program? "People aren't finding security bugs as quickly as we'd budgeted for" is something Steph can use too maybe. [GeKo: More publicity sounds good to me, and, yes, doing the NCE thing as well] 6) Arturo: did we ever hear from Roya about the Michigan NSF small? Else I'll mail her and ask. (No, last update was November 2017. Though maybe that is also news to you. It seemed like it was moving forward and they asked us to submit a budget about it. I guess it's still probably a good idea to checkin and see what the status of it is. - Art.) 7) Nickm: Internet Measurement Conference (IMC) is in Boston at the end of October: https://conferences.sigcomm.org/imc/2018/ The past few years the program has listed some awesome-looking talks. I can't go because of the OTF summit, but you could! 8) I mailed a bunch of people asking who else Isa and I should connect to for our Taipei trip. Let us know if you know somebody too. Shari: 1) going through resumes for new fundraising director 2) a few followup items from board meeting 3) finalizing contract for Mexico hotel and meeting space; other meeting details 4) need to work on budget reporting for Sida 5) finally feel like I've gotten rid of emergency stuff; trying to catch up on a bunch of other stuff next week Nick: 1) SVN has become more urgent. 2) We've begun moving things around the tor codebase a bit to try to get it in better shape for future modularity/refactoring/disentanglement work. If you are maintaining any patches on Tor, now is the time to get them upstreamed. :) Mike: 1) Getting back up to speed after vacation. 2) Need to decide between prioritizing more Sponsor2 work before the report vs packaging vanguards and doing final experiments. Arturo: 1) Attended CLSI (CitizenLab Summer Institute) in Toronto where we facilitated 2 sessions 2) Interviewed 5 community members for the "OONI Community Interviews" series 3) Published a research report on internet censorship in Nigeria: https://ooni.torproject.org/post/nigeria-internet-censorship/ 4) Creating materials for an OONI MOOC 5) Formed a new partnership with the Jordan Open Source Association 6) Made a lot of progress on implementing an OONI Psiphon test 7) Progress on OONI Explorer revamp work Karsten: 1) Performed an analysis of OnionPerf data, in particular circuit build times (#25774). Alison: 1) going to the American Library Association conference tomorrow, will be telling people about LFI and Tor 2) working on meeting planning 3) LFI is in week 3 4) Colin is finalizing the PETS relay ops meetup 5) Gus and I are working on the Kenya trip for sponsor9 6) we will soon start writing docs for Tor Browser 8.0 7) still have no details from HOPE about when our talk will be, hoping to get that soon so we can coordinate our booth times Georg: 1) release preparations for stable and alpha 2) Mike: Did we get some results out of the Tor-users-are-prevented-from-solving-CAPTCHAs measurements that were supposed to get done? [About two months ago they did a scan and it was fine. But I think it may have regressed, based on my personal experience]

1 0

Job Openings at Tor Project
by Erin Wyatt 20 Jun '18

20 Jun '18

Hey, everyone! Isa taking over as ED is a real thing (!!!) so we’re ready to recruit her replacement(s). We’ve posted two new PM job openings — please help us spread the word! :) * Project Manager for Network Projects: https://www.torproject.org/about/jobs-projectmanager-network.html.en <https://www.torproject.org/about/jobs-projectmanager-network.html.en> * Project Manager with Product Experience: https://www.torproject.org/about/jobs-projectmanager-product.html.en <https://www.torproject.org/about/jobs-projectmanager-product.html.en> We are also still looking for a Fundraising Director, which is a crucial position that can be tough to fill. Please continue to share the post: https://www.torproject.org/about/jobs-fundraising-director.html.en <https://www.torproject.org/about/jobs-fundraising-director.html.en> Thank you all! Cheers, Erin Wyatt HR Manager ewyatt(a)torproject.org GPG Fingerprint: 35E7 2A9F 6655 45F9 2CB6 6624 BA0C 9400 F80F 91CE

1 0

UX Team Report - May 2018
by Antonela Debiasi 20 Jun '18

20 Jun '18

Hello Tor! The Community and the UX Team visited the beautiful Kampala last month. We met old and new Tor users from all over Uganda. Our experience with local communities allowed us to spread Tor's world there and helped us to talk directly with users to improve our product's usability. We ran Tor trainings, threat modeling, a user needs discovery activities and conducted user testing for the new browser's improvements. Thanks to our awesome community members who provided critical logistics and translation support. Juliet, Tayfor, Karen, Neema, and Robert thanks for making it possible! We were working hard with the Application Team for our next Tor Browser release both for desktop and mobile. Thanks to the development team, we have nightly builds running again. It will help us to start testing our collaborative user testing workflow where the people in our community can test specific UX improvements and report them directly to the UX team. We were at Mozilla All Hands last week. We are collaborating to offer a better, private and safe browsing experience. On infra side, we started migrating the newsletter to Lektor and styleguide so it can be static. Also, the new support portal is about to launch at support.torproject.org, so stay tuned! On behalf of the Tor UX team, Antonela *Cool Things* - Hiro wrote about how you can browse the internet privately without corporate trackers lurking around you -> https://blog.torproject.org/dont-let-facebook-or-any-tracker-follow-you-web - We are preparing ourselves for Mexico Dev Meeting with a bunch of cool activities for Product, UX and UI designers who are going to be there! - "A lack of information often equates to a lack of control". Excellent article about system's feedback from NNGroup → https://www.nngroup.com/articles/visibility-system-status

4 3

Tor Browser team meeting notes, 18 June 2018
by Georg Koppen 19 Jun '18

19 Jun '18

Hello! Status updates and news from Tor Browser land after the Mozilla All Hands meeting got discussed yesterday at our weekly meeting. The chat log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-06-18-18.01.log… The notes from our pad are: Tor Browser Meeting Notes Monday, June 18, 2018 Discussion: -"status:" update -Quo vadis sandboxing? [GeKo: sysrqb is updating the sandbox plans he had and we get together on IRC to hammer out details] -Tracking issues in Trac -release preparations (blocker 1) and 2) from last week got solved, no new ones showed up, only 3) is left for the alpha) -which UX features need to get into the first alpha - .onion padlock indicator - circuit display - Tor Browser icon update - about:tor without onboarding? -next meeting - sysrqb: Confirming, we should base TBA on 60ESR, yes? [GeKo: yes] - igt0: Thinking about TBA, are we going to release a new orbot version as well? [GeKo: No, that's still the GuardianProject's job] - igt0: Service workers added lot of new APIs, I was not able to find out tickets about it (a master ticket), Is someone taking a look? [GeKo: We don't need that for now as service worksers are still disabled in the ESR60, we have #15563 for general service workers related work] sukhe: Last Week: - Finalized #26203, #26326, #26204, #25837 (Windows build issues; merged) and prepared #23561 (NSIS 64bit) for review - Attended Summer Institute This Week: - Work on #26319 (Don't package up the whole Tor Browser in the `mach package` step), #26251 (Adapt macOS snowflake compilation to new toolchain) - I am offline on Wed June 20 mcs and brade: Last week: - Triage some new/incoming tickets: - #26346 (Update prompt from 7.5.5 to the same version) - #26350 (MacOS Tor Browser cannot bind to port) - #26375 (On Mac, cannot have Tor Browser and Tor Browser Alpha side by side) - #26381 (about:tor page does not load on first start in localized Windows bundle) - Helped with #26045 (Create a new MAR signing key for ESR60) - Helped with #26355 (Make sure only Windows users on Windows7+ are trying to use Tor Browser based on ESR60 - Completed review for #23247 (Communicating security expectations for .onion). - Continued with #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). This week: - Continue with #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). - This is going slowly, so we are trying to find a way to speed up the review. - #26381 (about:tor page does not load on first start in localized Windows bundle) GeKo: Do you want us to work on this ticket? [Please go ahead, I probably won't get to it, GeKo] sysrqb: Last week: - At Mozilla All-Hands - Participated in conversations about Firefox sandboxing - Learned about Mozilla's plans for Firefox/Gecko on Android - Many more things This week: - Push Tor Browser 60ESR branch with TBA patches for review - Work on cross-platform Tor Browser sandboxing plan - Begin auditing code for proxy-safety (#21863) GeKo: Last week: -made progress on the network audit (#22176) -help with the Windows nightly builds (we seem to be good here now as well) -went over the UX tickets relevant for tor browser 8 -fixed up my rustc ticket (#26329) and some other small stuff (#23231, #26304) -reviews (#26329, #25837, #26203, #23247, #26396) This week: -fix for #26362 (create old-style MAR files) -test Mozilla fixes for bug 1413868 and 1421081, possible backport of a crash bug fix -continuing network audit (#22176) -reviews -release preparations and building/signing releases igt0: Last week: - Tested torbutton with FF60 - started investigating strategies to detect APK tampering. (Since we are going to allow the user to install from different places #26242). This week: - Define and implement update strategy(ies) for TBA (#26242) - Consider different installation methods (#26318) boklm: Last week: - reviewed some patches: - #26329: Fix Rust cross-compilation for 32bit Windows - #26203: Adapt tor-browser-build firefox and tor-browser project for ESR 60 Windows build - #26304: Update zlib to latest version - #23231: Error in STL wrappers when building Firefox 64-bit for Windows - #26250: Bump Rust version to 1.26.1 - #23561: Fix nsis builds for Windows 64 - made patches for: - #26354: Make sure only Linux users with SSE2 support are trying to use Tor Browser based on ESR60 - #26370: Don't copy msvcr100.dll and libssp-0.dll twice - #26206: Ship pthread related dll with tor - #26396: libwinpthread we ship in Windows builds is not built reproducible This week: - help building the new releases - doing some reviews - plan travel for mexico meeting - continue investigating build issue with #12968 (HEASLR) - fill upstream binutils ticket for #26148 - continue work on some ansible roles for testsuite VMs setup (#26149) pospeselr: Last week: - Mozilla All-Hands - patch for #26039 (extension-overrides.js no long being a thing in ESR60) This week: - fix up #23247 (onion lock icons) with final bits of feedback - verify #26039 fix works - go through the outreachy intern's issues spreadsheet - #26355 arthuredelstein: Last week: - Mozilla all hands meeting - Worked on reviewing HTTP/2 code including origin frames and AltSvc This week (as described last time): - Help with build as needed - Finish a patch for https://trac.torproject.org/25555 (reimplement optimistic socks) - HTTP/2, https://trac.torproject.org/14952 - Other needed alpha/ff60-esr tickets: https://trac.torproject.org/21785, https://trac.torproject.org/26321, https://trac.torproject.org/26322 Georg

1 0

Network team meeting notes, 18 June 2018
by Nick Mathewson 18 Jun '18

18 Jun '18

Hi! You can see the chat logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-06-18-16.59.html Our weekly meeting notes are below. = Network team meeting pad, 18 Jun 2018 = 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.) == Previous notes == 23 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001747.html 30 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001750.html 7 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001760.html 14 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001769.html 21 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001806.html 11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.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! == Announcements == * 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 release! * The git master branch is now 0.3.5! == Discussion == l * From last week: Rust build tickets- #25895 needs review/testing (Catalyst is reviewing again), and #25386 now doesn't have an owner but is high priority. (NM is taking it on for a bit.) * How aggressive should we be with our code-movement refactoring stuff? == Updates == Nick: Last week: - Released new 0.3.4 and 0.3.3 versions - Opened the 0.3.5 branch - Wrote up plan for refactoring Tor's layout, in a first step towards modularity: https://pad.riseup.net/p/cJUbdx0c7IzM-keep - Made a little progress on fixing up Rust testing issues, thereby making our CI fail. :) - Did a big branch to split (most of) our structures out of or.h, as a first step in the refactoring thing. (#26383) This week: - Work on #25386 (rust test linking thing) - Try to advance "big patches" thing w/ Taylor. - Revise refactoring plan based on comments, and (I hope) begin splitting src/common - Try to learn the state of wtf-pad - Try to learn the state of wide create work. Maybe code some? - 0.3.5 ticket triage - Community friend rotation ahf: Last week: - Went to Mozilla all hands meeting in SF. - Looked at some s4 documents we wrote at the end of the sponsor period for Isa. - Looked at MacOS sandboxing after meeting the Mozilla sandbox people (created #26374) This week: Sponsor 8: - Flesh out plan for PT error reporting. Talk with the application team and the guardian project if the plan sounds good to them. Misc: - Catch up on review backlog. - Do post-travel expenses after Seattle and Mozilla all hands - CI and Coverity duty (switched with asn last week) Mike: Last week: - vacation This week: - Figure out PETS travel - Catch up on email - Catch up on trac tickets? - Vanguard performance experiments - Vanguard packagaing dgoulet: Last week: - Reviewed #20700. I'm not done, pretty big ticket (HSv3 client auth). - Started review on nickm refactoring (#26383). I should be done soon. - Mostly reviewed 034 tickets. - Discussed with asn the #24977 solution. We had a back and forth review/revision already on it. This week: - Continue ticket assigned to me in 034. But as a priority, #26383 since it is a BIG refactoring. #20700 review for early 035 merge. Then outstanding HSv3 open bugs (#24977 and #25552) - Authenticated SENDMEs (#26288 - prop289), I would like to go over the proposal to see if it is ready to be implemented (in theory it is I believe). Ideally, we get an early merge on that as well. - I'm not on any rotation this week. catalyst: last week (2018-W24): - looked over the or.h refactoring proposal a little - tried to fix the rust tests (#26245, #25386, #25378) - reviewed #25895 (Rust cross compilation) this week (2018-W25): - code review - #25507 (big contributions) with Nick - more work on #25386/#26378 (rust test linking) -- maybe we want to disable the problem test for now? komlo (offline): - Last Week - Continued to investiage #24249 (automated mechanism for type syncing), working on a comparison of our options for this week - Reviewed #26220. I will create a ticket for a community wiki page where we can track infrastructure community projects such as this per discussion with Roger. - Chatted with ahf and sysrqb about looking at libcontainer as an option for sandboxing across platforms. More investigation about current/future support for Windows is needed. - This week: - See above about todos from last week asn: [Currently travelling. Won't be at meeting today! :)] Last weeks: - Wrote code for #24977 (034 ticket) - Wrote code for #25552 (035 ticket). - Fixed small 034 ticket #26358. - Did code reviews (#26283, #26272). - Continued communication with large onion provider. This week: - Finalize any other 034 tickets under my name (i don't think there are any) - Do #26379. - Do reviews. isis: last week: - mozilla all hands & meetings with rust people - did some hackerone and trac triage - reviewed #24249 #26378 #26245 #26152 #25269 - fixed some minor rust issues #26245 #26267 this week: - going back to the large create cell mine #25651 - traveling all day tuesday, mostly working offline - taking friday afternoon off to attend a wedding

1 0