- tor-project - lists.torproject.org

Notes from April 11 2019 Vegas team meeting
by Karsten Loesing 12 Apr '19

12 Apr '19

Notes for Apr 11 2019 meeting: Roger: 0) I had a good meeting with phw last week, to get him going on the new anti-censorship team. 1) Need some Apple contacts? For making webkit adhere to Tor Browser guidelines, or for helping get rid of the fake Tor Browsers on the app store? [I think we do, at least if we have them we should give to guardian project and mike tigas -isabela] 2) I keep encountering threat intelligence CTOs who admit that their company's marketing team is misleading people about "the dark web" and how it relates to Tor. It seems to me that we should be able to align the incentives from the marketing teams better: all it takes would be one of them realizing that they can differentiate themselves by pointing out that "all the *other* ones are misleading you". Next possible steps include doing a joint blog post with one company that wants to, and/or doing a talk to an NYC-based threat intelligence company. 3) May 1 is the deadline for mainline Defcon talks. I am pondering submitting one -- a retrospective of some sort maybe. A brainstorming session seems smart. Gaba: 1) follow up on sponsor 13 reporting. 2) worked over a summary from ideas for funding for grants strategy meeting. 3) looked at capacity for network team for the year. 4) follow up on tor-scalability (will open mailing list today) 5) started weekly syncs with phw Georg: 1) Work on Tor Browser 8.5 2) Helping OTF with proposal review and recommendations 3) Dealing with HackerOne bug bounties and additional HackerOne help with out bug bounty program Nick: 1) team continues to be somewhat strained for resources, but great work is still getting done. 2) I'll be off from next wednesday through the following monday (17th through 22nd), though I could be available for meetings if really needed and we schedule in advance. Pili: 1) Sponsor 27 organisation 2) Google Season of Docs - started filling out application form - working on fleshing out projects - blog post - recruiting mentors 3) New Website Launch Retrospective 4) Working on funding ideas for teams Alison: 1) Refining LFI curriculum 2) Making the public announcement about the new cohort soon 3) Still redesigning the website 4) Writing a piece on facial recognition for ALA Choose Privacy Week 5) Gus is traveling; we will go to Mexico together in May Steph: 1) Helped with irl’s and juga’s blog posts 2) Responded to inquiry about CIPA 3) Will be presenting at a cryptocurrency gathering (post Ethereal Summit) doubling as a Tor fundraiser in NYC may 15. Gman will join me. 4) def con prep 5) Talking with a librarian at the Brooklyn Public Library about possibly running a workshop or talk isabela: 1) I have been sick this week so I am behind on some things. 2) Catch up to do list, emails and meetings. 3) Plan on start inviting people on 'waiting list' of dev meeting invite list. 4) Plan to meet w/ Alison to kick off the process to organize the schedule for the dev meeting. 5) Work on Sida phase3 plan and review proposal for general ops fund Sarah: 1) More admin to finish up state registrations. 2) Sending out new welcome email to new email list subscribers. We are now up to 45,424 people on the main email list. 3) Al submitted proposals for general operating funds from the CS Fund and funds for ESR migration from Open Source Center. 4) Researching Handshake details 5) Postal letter to lapsed major donors and small foundations went out last week. Sue: 1) General Accounting processes Erin: 1) General HR stuff Karsten: 1) Decide how to proceed with TorDNSEL replacement: a) our hope to upgrade the Haskell code from 7.6 to 8.0 did not work out; b) the rewrite is at least a few weeks away if we want it to work properly; c) the metrics team might take ownership of the oldstable VM from the admins, but running machines is not what we're good at; d) we could let it die and put up the replacement once we have it, even though that will make at lot of people sad; e) we get an extension for the shutdown as long as we make progress (Brexit style); f) do a quick-and-dirty thing (maybe exitmap + stem + some duct tape, possibly leaving out the DNS server at the beginning) that keeps working until we have the proper rewrite in place. Antonela: 1) Coordinating user research in Colombia with Nah and Gus 2) Reviewing Caroline's report for Q1 user research 3) Preparing outreach material in Spanish to print for Colombia 4) website tickets triage, working on /download 5) S27 meeting, starting with O2A1 6) Following up with IFF people 7) Working on TB8.5 release 8) Working on OONI Explorer ux issues with Arturo 9) Reviewing community.torproject.org 10) Reviewed research.torproject.org with irl Mike: 1) Trying to organize next tor-scalability meeting 2) network team development 3) @steph: vanguards should be in the next debian/stable and debian backports; I would like to do a blogpost and tweet when that happens. Not sure if it will happen this week or next yet. [great, lmk when you've got a draft -steph]

1 0

Anti-censorship meeting notes, 11 April 2019
by Philipp Winter 12 Apr '19

12 Apr '19

Here are our meetings logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-11-20.00.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday April 11th 20:00 UTC Weekly meetings every Thursday 20:00 UTC on #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == THE Anti-censorship Roadmap (kanban board): https://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… <-- a subset of tasks from trac that the team is working on. Roadmap by topic: https://storm.torproject.org/shared/KXkqlNP8ouNks_ey5khZKUSbNj9ZoidXmEp80OD… Gettor Roadmap: https://storm.torproject.org/shared/rhsSl_3Pb253HPqoCdFiAdmXQ57NUG_BLvBCxqF… Roger's thoughts on anti-censorship's priorities: https://storm.torproject.org/shared/kU83M2pQehsnQZPzR_mwmYslAijqKgYNOEak57T… Komlo's thoughts on anti-censorship's plan: https://pad.riseup.net/p/CensorshipTeam-Planning-keep PTO Calendar: Ask gaba for the link and keep it up to date with when you are not going to be around. ------------------------------ ---- 11th April 2019 ---- ------------------------------ == Announcements == * A reminder to change owner of ticket to yourself in trac if you are working on that ticket. == Discussion == * What GetTor-related material should we include in Sponsor 19 & in anti-censorship team roadmap? <-- move this discussion for next week. * hiro wants to be the new mantainer of GetTor. Do we have a backup maintainer? * Do we want a (public) anti-censorship team mailing list? We can use it for: * Coordinating team meetings * Making it easy for people to contact the team (e.g., in case of censorship events) * Hopefully, a public mailing list does not discourage anyone * Publishing our monthly team reports * Bringing up and discussing related anti-censorship efforts (e.g., v2ray tool) * Pointing out when something in our docs or processes is broken * How can/should this overlap with the traffic-obf Google mailing list? * How are we going to manage code reviews? So far asn helped. * reviews will be assigned in this weekly meeting. * On Monitoring infrastructure <-- let's bring this conversation to next week. * Let's add https://trac.torproject.org/projects/tor/ticket/30121 to our roadmap backlog? Anything else to add/edit to the roadmap? * Plan for project maintainership * We should strive for two maintainers per project * dcf: should we remove serene's snowflake.git commit access? Not used since March 2017. https://bugs.torproject.org/30044#comment:2 shows the users with commit access. Cf. #30138 regarding an admin account. == Actions == == Updates == FORMAT! Name: Last week: - What you worked on last week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. phw: This week (2019-04-11): - Got my own bridgedb and bridgedb-admin repos. Started reading code and re-assigning tickets to me. - Inquired about status of ICLab and if the project could help us scan our bridges. - Wrote a small script that helped us analyze the throughput of a download over time. - Figured out who runs our default bridges and contacted operators of broken bridges. + See https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/DefaultBridges + Filed #30121 to improve how we manage list of default bridges. + Some progress in #30006, which is about monitoring our default bridges. - Started working on a fix for #26154. Breaks many unit tests -- more thinking required. Next week: Help with: - #28655 review (If a bridge supports obfs4, don't give out its other flavors) - Need to talk to sysrqb and/or dgoulet to learn more about BridgeDB deployment. Gaba: This week (04/11): ahf (gonna be missing at the meeting, but will read backlog): Last week (2019/4/4): - Meeting with gaba, cohosh, & phw Monday - Went over roadmap items in new roadmap docs. - Lots of tiny network team tasks. - Continued work on #t/#29206. This week (2019/4/11): - Mostly network-team tasks so far. Was off Wednesday. - Gitlab/LDAP access have been established. - Continue to hack on #29736 (and transition it off to cohosh too) - Gaba and I talked at our 1:1 Friday that I'll return to network team tasks only in May. kat5: Last week (April 8): - Brought phw up to speed about reports - Figured out where various content came from - Thought about what to remove and what to keep - A little more Snowflake and BridgeDB content This week (April 11): - Started GetTor content - Copy editing - Conditionalized URLs - Figure out what's left Help with: (I will sort these questions out over email.) - Need ahf to review (at least certain sections of) the report. - I think I should include arma and dcf1 in the author list because I took text from tickets they wrote and I think I should include catalyst because they gave me text that I used, but I don't want to do that without consent. - ON HOLD -> need direction - private bridge guide for NGOs (hold off until we figure out a strategy for making set-up easy) not sure where this is nor what should heppen next dcf: 2019-04-11 Last week: - reviewed proxy-go deadlock patch in #25688 - participated in discussion about Snowflake monitoring in #29863 - merged goptlib LOG branch (#28940) - made accounts for phw on bridge and broker (#29985) - filed a ticket to remove serene from Snowflake bridge admin (#30138) Next week: - have meek-client-torbrowser signal exit by closing child process stdin (#25613) - review proxy geoip patch (#29734) - review on further log sanitization (#30125) and recommendations for deployment - prototyping with AMP cache Help with: cecylia (cohosh): last updated 2019-04-11 Last week: - investigated obfs4 blocking (#29279) - Looked at data from VPS in China and NA probe site - modified phw's tcpdump scripts and published results - snowflake - merged and deployed #21304 and #25688 - more discussion about #29863 - closed #21305 and started looking at #25429 instead - revised #29734 for geoip data on proxies - implemented #30125 - community stuff - discussed with phw my thoughts on the PT integration pipeline Next week: - investigate obfs4 blocking (#29279) - keep checking current tests - expand tests for bridge enumeration problem? - snowflake - make some progress on websocket protocol - take a look at windows reproducible build problem (#25483) - work on client connectivity issues (#25429) Help with: - review of #30125 - ahf: are you still working on snowflake? i'd like to move forward with #29736 (and #29207), since it's blocking work on #29260 and #21315 - phw: I think it would be cool to expand the study for #29279 (see https://trac.torproject.org/projects/tor/ticket/29279#comment:16 ). I'm happy to do the leg work with designing and running the study, though you're probably in the best position to handle (2) at the moment. It's probably worth our time at this point to design it carefully. Also, do we want to have actual people doing probes instead of just our VPS probe site? catalyst: week of 4/4 (planned): - focus on sponsor31 stuff (like control.c refactor) that might be blocking nickm; please let me know if i should reprioritize - work on #29276 (bridgedb release) if there's time week of 4/4 (actual): - mostly sponsor31 stuff like control.c refactor week of 4/11 (planned): - more sponsor31 work; maybe also #29976 as prep work for more bootstrap reporting improvements

1 0

march 2019 report for the sysadmin team
by Antoine Beaupré 11 Apr '19

11 Apr '19

Hello, Here are the minute from our last meeting, which we have just decided might double as a report for the larger project as well. I hope that's still useful! Agenda: * What has everyone been up to * What we're up to in April * Other discussions * Next meeting What has everyone been up to ============================ anarcat ------- 1. lots of onboarding work, mostly complete 2. learned a lot of stuff 3. prometheus research and deployment as munin replacement, mostly complete 4. started work on puppet code cleanup for public release lots more smaller things: 5. deployed caching on vineale to fix load issues 6. silenced lots of cron job and nagios warnings, uninstalled logwatch 7. puppet run monitoring, batch job configurations with cumin 8. moly drive replacement help 9. attended infracon 2019 meeting in barcelona (see report on ML) hiro ---- 1. website redesign and deploy 2. gettor refactoring and test 3. on vacation for about 1 week 4. IFF last week 5. many small maintenance things ln5 --- 1. nextcloud evaulation setup [wrapping up the setup] 2. gitlab vm [complete] 3. trying to move "put donated hw in use" forward [stalled] 4. onboarding [mostly done i think] weasel ------ 1. brulloi decommissionning [continued] 2. worked on getting encrypted VMs at hetzner 3. first buster install for Mandos, made a buster dist on db.tpo, cleaned up the makefile 4. ... which required rotating our CAs 5. security updates 6. everyday fixes What we're up to in April ========================= anarcat ------- 1. finishing the munin replacement with grafana, need to write some dashboards and deploy some exporters (trac #30028). not doing Nagios replacement in short term. 2. puppet code refactoring for public release (trac #29387) 3. hardware / cost inventory (trac #29816) hiro ---- 1. community.tpo launch 2. followup on tpo launch 3. replace gettor with the refactored version 4. usual small things: blog/git... ln5 --- 1. nextcloud evaluation on Riseup server 2. whatever people need help with? weasel ------ 1. buster upgrades 2. re-encrypt hetzner VMs 3. finish brulloi decommissionning, canceled for april 25th 4. mandos monitoring 5. move spreadsheets from Google to Nextcloud Other discussion topics ======================= Nextcloud status ---------------- We are using Riseup's Nextcloud as a test instance for replacing Google internally. Someone raised the question fo backups and availability: it was recognized that it's possible Riseup might be less reliable than Google, but that wasn't seen as a big limitation. The biggest concern is whether we can meaningfully backup the stuff that is hosted there, especially with regards to how we could migrate that data away in our own instance eventually. For now we'll treat this as being equivalent to Google in that we're tangled into the service and it will be hard to migrate away but the problem is limited in scope because we are testing the service only with some parts of the team for now. Weasel will migrate our Google spreadsheets to the Nextcloud for now and we'll think more about where to go next. Gitlab status ------------- Migration has been on and off, sometimes blocked on TPA giving access (sudo, LDAP) although most of those seem to be resolved. Expecting service team to issue tickets if new blockers come up. Not migrating TPA there yet, concerns about fancy reports missing from new site. Prometheus third-party monitoring --------------------------------- Two tickets about monitoring external resources with Prometheus (#29863 and #30006). Objections raised to monitoring third party stuff with the core instance so it was suggested to setup a separate instance for monitoring infrastructure outside of TPO. Concerns also expressed about extra noise on Trac about that instance, no good solution for Trac generated noise yet, there are hopes that GitLab might eventually solve that because it's easier to create Gitlab projects than Trac components. Next meeting ============ May 6, 2019, 1400UTC Meeting concluded within the planned hour. Notes for next meeting: 1. first item on agenda should be the roll call 2. think more about the possible discussion topics to bring up (prometheus one could have been planned in advance)

1 0

March 2019 report for the UX team
by Antonela Debiasi 11 Apr '19

11 Apr '19

Hello Tor, During March we launched the new torproject.org landing pages, using responsive web design to enhance the end-users experience. We included 7(seven) languages, and more locales are coming. As we shared back in Rome, this release is just one small part of the big website overhaul project. We released support.torproject.org back in February, and we will continue with community.torproject.org next month, and dev.torproject.org in the following quarter. https://www.torproject.org/ Tor Browser 8.5 is about to reach stable. We worked on both desktop and android alpha releases. Security Settings, Network Settings, Onboarding, and the new Icon are going live. https://trac.torproject.org/27484 https://trac.torproject.org/28329 https://trac.torproject.org/28622 https://trac.torproject.org/28628 https://trac.torproject.org/29768 Thanks, dunqan for working on the onboarding update for this release: https://trac.torproject.org/projects/tor/ticket/29768#comment:16 Thanks, wayward for working on the new Security Settings documentation for users: https://lektor-staging.torproject.org/tor-browser-manual/staging/security-s… Caroline is debriefing the user research we ran in India and Indonesia during Q1. We will share the key findings with the lists shortly. Elio has been working on finalizing OONI Explorer landing pages for the beta launch. You can sneak peek them here: https://www.figma.com/file/OElUj1XR5SmbXUpWVzl8iton/Explorer-Landing-Page?n… In order to have a better understanding of the project teams, pili ran a team vision exercise. You can see the outcomes and also the entire meeting log here. Thanks, pili. https://lists.torproject.org/pipermail/ux/2019-March/000444.html The Cyborgrrrls Encuentro Tecnofeminista happened in Mexico last month, and I gave a Tor 101 talk and we discussed how technology could allow us to shape our identities online. https://hysteria.mx/cyborgrrrls-encuentro-tecnofeminista-en-la-cdmx/ o/ A -- Antonela Debiasi UX Team Lead @antonela E2330A6D1EB5A0C8 https://torproject.org <https://keybase.io/antonela#show-public>

2 1

Tor Browser team meeting notes, 8 April
by Georg Koppen 08 Apr '19

08 Apr '19

Hi everyone! Our weekly meeting just finished. The log can be found at http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-04-08-17.31.l… and the entries from our pad are in full copy below: Discussion: -8.5a11? (GeKo: we aim for this week) -next meeting? (GeKo: next week won't work well for a bunch of us and the Monday thereafter is public holiday in some countries, so we aim for 4/23 same time, same place) - #29837 Include Tor Browser data from Google Play (GeKo: We'll think about that after we are done with TB 8.5) tjr (may miss) - Did a bunch of letterboxing work, and think I have an idea of what sets of window sizes we should pursue. - Will present it at the monthly meeting tomorrow, but have written up my notes and they are in that minutes doc - Sent an email link to it last week; ask me on irc (or gk, or Richard) for it. GeKo: Last week: - worked on localization tickets for mobile: #30016 and #30069 - tried to come up with a good theory about why our previous attempts on addressing the accessibility bug on Windows (#27503) failed - reviews: #22538 (acat's first bug!1!), #29768 (started reviewing #29328; sysrqb: if you have any ideas about my last comment, please add them) - wrote smaller patches: README update for x86 android target (#29980), no need for libgtk2.0 headers for WebRTC build (#30038) - i dug down the media container rabbit hole for #29859 and am sufficiently sure our workaround does not make matters worse - looked over tjr's proposals and added them to the tor-browser-spec repo - followed up on the potential proxy bypass outlined in #29916 but did not get a reply yet - sponsor27 prep - begin of the month team admin updates - review help with my tickets (thanks mcs and brade for already picking up some tickets) (GeKo: That got sorted out, boklm is picking up #30016 and sysrqb #28622, #29843, #29859, and that's it for now) This week: - finish #30069 and more work on removing no longer necessary Orfox patches - more tbb-8.5(-must) work and help where needed - hopefully substantial reviews for #28329 and #27609 (and friends) so that we can start building 8.5a11 - release prep and building 8.5a11 sisbell: Last week: - Investigated tor loading issue with latest version of loader from tor-android-binary. On some devices tor isn’t being found (OS5/note3, OS7/motog6). Working on Samsung s10 and emulator. - Opened and fixed 6 new issues on TOPL project. Mostly dealt with making TOPL more configurable (needed to customize tor installation) - Significantly improved startup time of Tor/TOPL by reimplementing startup. - tor-android-service: Created custom installer based on what I learned in investigating loading issues. By following library naming conventions, we can force installing of tor/PT libraries. - worked on integrating changes into tor-browser-build. Cleaned up build by using ndk filters in gradle, rather than adding/removing libraries with zip utility. This Week: - Get latest code building/working in Firefox project. - Check in code that is in sync from March 16th. Then update to latest tor-browser-build master. boklm: Last week: - Some reviews (#29980, #29966, #30038) - Made patch for #30039 (Add the target_append and target_prepend input_files options in rbm) - Started a patch for #29981 (Add option to build without using containers), and tried to get matching android builds with and without containers. It seems possible if we solve the stalling jarsigner issue. - Went to IFF This week: - Finish fixing #27137 and disable all currently failing tests - Make some patch for #26907 (Guard against failures during MAR file generation) - Work on #30089 (Use apksigner instead of jarsigner) and #29981 (Add option to build without using containers) - Help building 8.5a11 - Review #30016 (Include onboarding/start-up translations in localized builds) sysrqb: Last week: Worked on crash-fix for Kitkat (#29906) Worked on crash-fix when selecting the bootstrap settings button (#29982) Worked more on TBA bootstrap UI (#28329) - Waiting on update from animation designer Worked on fastlane integration (#26844) Responded to comments on F-Droid package submission (#27539) This week: More of the above release prep(?) Review TOPL+orbotservice branches Review #28622, #29843, #29859 (maybe #30069) mcs and brade: Last week: - Made progress on #29768 (Introduce new features to users in Tor Browser). - Worked on travel plans for the Stockholm meeting. This week: - Monitor #29768 (Introduce new features to users in Tor Browser). - Help with code reviews for tbb-8.5-must tickets. - #29045 (ask tor to leave dormant mode) - Start on #30000 (Integrating client-side authorization to onion services v3) - Tor employee/team feedback process. - We will be out of the office April 17-22 (taking some time off around Easter). pili: Last week: - At IFF - S27 ticket organisation This week: - Start putting together Google Season of Docs application - S27 Planning meeting - S27 Preliminary roadmap - Tor Browser release meeting this week pospeselr: Last week: - #27503 (windows screen reader investigation) - Nextcloud prep - travel planning This week: - #27503 acat: Last week: - Setting up stuff, paperwork, travel planning - #22538 This week: - #24622 antonela: Last week: - IFF - Reviewed #29768 This week: - Firefox Monthly meeting - I'll demo the new security settings, pospeselr could you catch any technical question could raise there? (GeKo: We'll have this covered either pospeselr or I, no worries :) ) - OTF Onions, setting up ux work - #28329 Georg

1 0

Network team meeting notes, 8 April 2019
by Nick Mathewson 08 Apr '19

08 Apr '19

Here are our logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-08-17.00.html Below are our notes: = Network team meeting pad! = This week's team meeting is at Monday 8 April at 1700 UTC on #tor-meeting on OFTC. Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. April schedule: * Tuesday 2 April at 2300 UTC * Monday 8 April at 1700 UTC * Monday 15 April at 1700 UTC * Tuesday 23 April at 1700 UTC (Monday 22 April is the Easter Monday public holiday) * Monday 29 April at 1700 UTC * teor will probably be on leave at the end of April May schedule: * Tuesday 7 May at 2300 UTC <-- teor may not be in this meeting. let's check with them if it makes sense to have it on Tuesday (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 5 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002244.html 11 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002252.html 18 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002263.html 25 Mar: https://lists.torproject.org/pipermail/tor-project/2019-April/002280.html == Stuff to do every week = * How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… * Let's check the 0.4.0 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… <-- filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the needs-review tickets, by reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&reviewer… Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… Any blocker from last week? == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. ------------------------------- ---- 8th April 2019 ------------------------------- == Announcements == - The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0. - US DST began a few weeks ago; let's be careful with schedules Then we need to prioritize 0.4.0 fixes and reviews in March and April, because stable is due on 15 April. - Anti-censorship team is up: Gaba moved s19 stuff into anti-censorship team own roadmap. That teams meets every Thursday. - Onion Services proposal tickets will go into roadmap possible this week (right now they are in the board in its own column). == Discussion == - Should we remove dgoulet from the April rotations? Yes == Recommended links == == Updates == NOTE NEW FORMAT! Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: Last Week of 04/01 (actual): - process mails - tor scaling follow up - s27 roadmapping (onion services) - compile overall understand on plans/brainstorming/future-roadmap for the team (for grant strategy meeting next week) - capacity and cloning asn - send own travel expenses request for july meeting - move s19 tickets out of network team roadmap - talked with people about the bug This Week of 03/08 (planned): - capacity for s27 and timeline on the project - move s27 tickets into roadmap - grant strategy with grants team includes priorities for funding for network team teor: (offline except for the first meeting each month) Week of 1 Apr (planned): High-Priority: - Do wiki trac query status pages for each network team role - Backport merge fixes needed for CI with Chutney/Tor to Tor 0.2.9 - Do mainline merges and backport merges - 040 bugfix reviews - Hack out quick fixes to #29500 and #29437 Roadmap: - CI with Chutney/Tor: #29729 - Review nickm's parts of the CI with Chutney/Tor tickets: #29280 - Other roadmap reviews Other: - Assigned reviews - Do remaining reviews from last week - Add a travis test for stem (it's a copy of the chutney test, but using the stem command) Week of 1 Apr (actual): High-Priority: - Backport merge fixes needed for CI with Chutney/Tor to Tor 0.2.9 - Do mainline merges and backport merges - Did a CI failures status page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… Roadmap: - CI with Chutney/Tor: #29729 and children - Other roadmap reviews Other: - Assigned reviews Week of 8 Apr (planned): High-Priority: - Do mainline merges and backport merges Roadmap: - CI with Chutney/Tor: #29729 and children - Other roadmap reviews Other: - Assigned reviews Notes: I won't be doing reviews or merges until Wednesday or Thursday, so I can get some roadmap coding done +1 Help with: Nick: Week of 1 April (planned): - Try to fix remaining 040-must issue: - Reopened Can't parse networkstatus consensus time (#28614) - 040 release? - Lots of review and merge - Control.c refactoring: try to better unify command-parsing logic - Prepare for presentation at Tufts on Saturday - Write a couple of users for publish/subscribe logic - Time permitting, adl/rup revisions Week of 1 April (actual): - Worked on and came to resolution or diagnostics for 040-must issues: - Reopened Can't parse networkstatus consensus time (#28614) - 29437 -- test-stem timeout. (This was HARD) - Lots of review and merge - control.c refactoring: unified command-parsing logic. perhaps eventually useful for config and state and parsecommon too? - Presented on Tufts about a student paper; helped clarify thoughts - PETS review Week of 8 April (planned): - PETS discussion - Finish control.c command-parsing refactoring - Finalize draft abbrevs list. - More review and merge - 040 release - Write a couple of users for publish/subscribe logic. - CI failure tickets: #29645 test.exe hangs on Appveyor CI #29922 util/time test failure on Jenkins - I would like to to take time off between 17 and 19 April. 22 April (monday) is a state holiday for me. Is that okay with everybody? +1000 dgoulet (missing meeting): - AFK. Mike: Week of 4/1 (planned) - Scalability planning & discussion - Plan lots of travel - Finalize plan for keeping circuits open (#28780) - #29034 patch - Catch up on code reviews Week of 4/1 (actual): - Lots of Tor scalability discussion & thought - Continued testing vanguard fixes - #29500 and #29900 rabbithole and discussion - DMV bureaucracy+life issues Week of 4/8 (planned): - Scalability planning & discussion - Plan lots of travel - Vanguards release - Finalize plan for keeping circuits open (#28780) - #29034 patch - Catch up on code reviews catalyst: week of 04/01 (2019-W14) (planned): - bug triage rotation - reviews - clean up pubsub rework of bootstrap reporting - look into control.c protocol and events refactoring - travel planning/req week of 04/01 (2019-W14) (actual): - bug triage - reviews - submitted travel request - preliminary control.c protocol formatting splitting (#30007) - a little more bootpubsub work week of 04/08 (2019-W15) (planned): - reviews - finish up control.c protocol splitting (#30007) - get bootpubsub ready to review (#29976) asn: Week of 04/03 (planned): - Continue work on #28634. Still some rough edges to iron out, so that we reach something mergeable. In particular, I need to finish the bandwidth overhead analysis. - Start working on April roadmap items. Is it S31 or S27? Week of 04/03 (actual): - Did some more of #28634. Finished the bandwidth overhead analysis and did a bit more testing. Ticket is still in needs_review. - Started work on #29209 s31 deliverable. We decided with Nick we are first gonna try to hide crypt_path_t. It's hard work to hide any parts of that structure but I started with crypt_path_t->crypto. I think I will have something reviewable in a day or two. - Did some digging in the hackerone tickets with the help of Nick. Waiting for OTF email to proceed. - Did reviews and merges. Week of 04/08 (planned): - Will focus on the #29209 s31 deliverable this week. I hope to have it done by the end of the week, so that I can focus on s27 for the rest of the month. ahf (offline): Week of 4/3 (planned) Anti-censorship team: - Intro meeting for phw with cohosh and gaba. - Get #29206 and #29207 design finished. Already six points above target for those. - Implement #29736 in Broker and (Go) Proxy code. Network team: - Solve 040-must ticket: #29930 Week of 4/3 (actually) Anti-censorship team: - Continued work on #29736. Network team: - Small reviews. - Reproduced #29930 and think we know *why* it is happening. Misc: - Ready for our Sweden trip: travel approval and booked transport. - Configured a relay with some patches from asn to test. - 1:1 with Gaba: Now that phw have started I will return to network-team full-time 1st of May. - Some Harvest issue that got solved by gaba and sue. Week of 4/8 (planned) Anti-censorship team: - Continue with #29736. Network team: - Solve 040-must #29930 (figure out why the file is still open). Misc: - Figure out PETS logistics. - I will probably be away some of Wednesday.

1 0

Tor Browser Release Meeting: Wednesday 10th April @ 1800UTC
by Pili Guerra 08 Apr '19

08 Apr '19

Hi everyone, Here’s the usual reminder of our fortnightly Tor Browser release meeting and the details: Wednesday 10th April @ 1800UTC at #tor-meeting. Please note the updated UTC time now that Europe has changed to summer time. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

S27: Onion Services project - Meeting notes
by Pili Guerra 05 Apr '19

05 Apr '19

Hi everyone, We had a meeting this week to start mapping out our work for the S27 (Onion Services) project. Here's a recap and the outcomes and action items from our conversation. Network team - Will start working on Objective 2, Activity 2: Notify users about typo errors when entering .onion addresses (https://trac.torproject.org/projects/tor/ticket/30022) to solve any potential browser team dependencies in this area. - asn to contact Bill (EFF) and Jenn (Securedrop) to start coordinating work on Objective 2, Activity 5: POC for Human-memorable addresses for .onion services (https://trac.torproject.org/projects/tor/ticket/30029) and start planning future collaboration/work in this area - Next priority after this will be Objective 2, Activity 4: Better client-side errors (https://trac.torproject.org/projects/tor/ticket/30025) Browser Team - Will start working on Objective 2, Activity 1: Integrating client-side authorization to onion services v3 (https://trac.torproject.org/projects/tor/ticket/30000) as soon as the work on TBB 8.5 blockers is completed - We will also need to contact CF and/or FB regarding their use of alt-svc to check whether there are any bugs that need fixing to provide an optimal experience. Feel free to update any incorrect details and/or continue this conversation here. You can find the full conversation logs here: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-02-15.01.log… Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 1

March 2019 report and April 2019 plans for the metrics team
by Karsten Loesing 05 Apr '19

05 Apr '19

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in March 2019 as well as a few expected highlights for the current month, April 2019. On behalf of the Tor metrics team, Karsten March 2019: Attempted to upgrade TorDNSEL [1] from GHC 7.6 to 8.0 in order to migrate this service from Debian Jessie to Stretch. This attempt is currently stalled due to difficulties with replacing the deprecated and removed Data.HashTable with the hashtables package. If you're a Haskell developer willing to help us with this, please let us know! [1] https://gitweb.torproject.org/tordnsel.git/ Published a technical report on Tor Metrics Data Collection, Aggregation, and Presentation [2] which concludes our work for Sponsor 13 [3]. [2] https://research.torproject.org/techreports/metrics-evaluation-2019-03-25.p… [3] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor13 Discussed an extended data format for exit lists [4]. [4] https://trac.torproject.org/projects/tor/ticket/29624 Deployed changes to the daily updater for Tor Metrics visualizations which run as a Java-only process now rather than separate Java/Python/R processes executed by Ant [5]. [5] https://trac.torproject.org/projects/tor/ticket/29166 Presented Tor Metrics at the Scottish Networking Event [6]. [6] http://scone.cs.st-andrews.ac.uk/wiki/ Attended IETF 104 [7] and presented an Internet Draft on Guidelines for Performing Safe Measurement on the Internet [8]. [7] https://www.ietf.org/how/meetings/104/ [8] https://datatracker.ietf.org/doc/draft-learmonth-pearg-safe-internet-measur… April 2019: Either upgrade TorDNSEL enough to run on Debian Stretch, or write a replacement in Python. If both plans fail, possible alternatives range from accepting ownership of the Stretch VM to accepting that Tor's exit list scanner gets shut down without replacement. Continue analysis and visualization of worst-case performance and failure cases as measured by OnionPerf [9, 10, 11, 12, 13]. [9] https://bugs.torproject.org/29743 [10] https://bugs.torproject.org/29744 [11] https://bugs.torproject.org/29772 [12] https://bugs.torproject.org/29773 [13] https://bugs.torproject.org/29787 Next metrics team meeting times (with short-term changes announced on the metrics-team@ mailing list): * Thursday, 11th April 2019 15:00 UTC * Thursday, 18th April 2019 15:00 UTC * Thursday, 25th April 2019 15:00 UTC

1 0

Notes from April 4 2019 Vegas team meeting
by Karsten Loesing 05 Apr '19

05 Apr '19

Notes for April 4 2019 meeting: Gaba: 1) network team: 1.1) Updated roadmaps with s27 (onion services) and s19 stuff. And reorganize some people's allocation of time. 2) anti-censorship team: 2.1) Onboarding for Philip this week with Alex and Cecylia 2.2) New roadmap for anti-censorship team. 3) metrics: 3.1) Sent last report for s13 (data collection improvements) to OTF 4) ooni: 4.1) Almost the whole team is at IFF. 5) other: 5.1) Follow on scalability drafts from Mike. [GeKo: Where are those drafts? Is it possible to have a look at them? Gaba: Mike will send them to the mailing list soon GeKo: Ah, okay. Looking much forward to that, thanks.] 5.2) Sent request for approval and booked flight to STO. Mike: 1) Working on scalability strategy mail for tor-scaling 2) Working on vanguards bugs 3) Still dealing with misc bureaucratic issues due to stolen wallet Sarah: 1) Had technical difficulties with Monero wallet that are now resolved and have raised ~$4K from that cryptocurrency so far. 2) Prepping for grants meeting next Monday to plot out next few months and combine work into bigger projects. 3) Sending our first Sponsors Newsletter to grant officers so that they can better understand the bigger picture. 4) Al submitted a proposal to the Indela Fund for LFI. 5) Various administrative tasks to complete state registrations. Georg: 1) Busy with 8.5 stabilization Erin: 1) Started this week: phw and new browser dev, acat 2) Moving forward with OONI dev recruiting next week (after IFF) 3) General HR stuff Nick: 1) Got to finish reviews, and get ready for a Tufts "Student Symposium in Cybersecurity Policy" tomorrow and maybe staying for Saturday. 2) network team is quite overloaded with 040, CI, tech debt, code review, and funded stuff. Please don't divert network team personnel without careful consideration. When one team member is diverted, their distraction increases the workload and pressure on everybody else. Alison: 1) Super busy with LFI 2) Most of the team is at IFF 3) Thinking about new funding ideas for LFP 4) Gave some talks last week -- Western Colorado University and Temple Law 5) Prepping for RightsCon 6) Have not had any time to work on feedback yet but hoping to get to it soon Steph: 1) We were accepted as a vendor at def con. Coordinating us having a badge with the help of Anto, ahf, and a volunteer we met last year 2) Preparing for onion services campaign 3) Coordinating talk for swiss unis 4) Reviewed copy for new tb features Pili: 1) At IFF 2) Spoke to EFF, Guardian Project and Tails about Google Season of Docs and we'll move forward with a joint submission 3) S27 bug triage and initial roadmapping 4) Booked dev meeting travel 5) Website triage 6) Getting lots of nice feedback and comments from people at IFF isabela: 1) Had the board meeting last friday 2) reviewed sponsor8 final report (submitted) 3) reviewed Indela proposal (submitted) 4) reviewing another general grant proposal and final report for metrics 5) met w/ sue and jon to sync on dev meeting prep work Karsten: 1) Miscellaneous tiny things, including planning travels, writing feedback, commenting on various tickets, responding to volunteers, and so on. Sue: 1) Short Period 990 sent to Board for Review 2) Sida Attestation Audit Report sent to Board for Review 3) Uploaded Audit report to Federal Clearning House 4) General Accounting processes (invoicing, disbursements, reconciliations)

1 0