- tor-project - lists.torproject.org

Mirroring the #tor-meeting channel with the OONI slack
by Arturo Filastò 06 Jul '18

06 Jul '18

Hi list, I am wondering if it would be OK to mirror the #tor-meeting channel (which already mentioned in the topic that it’s publicly logged) with the OONI slack. This would allow people that are not too familiar with IRC and that are on the OONI slack (we currently have 200+ people in there) to participate in the meetings that happen in that channel and to easily access the backlog. Is this something that people would be OK with? Ideally I would like to have this setup before todays Network Traffic Obfuscation meeting happening in there. ~ Arturo

4 4

Notes from July 5 2018 Vegas team meeting
by Karsten Loesing 06 Jul '18

06 Jul '18

Notes for July 5 2018 meeting: Georg: 1) Do we want to be a verified Brave publisher (see: https://brave.com/publishers )? 2) I gave a Tor presentation for the Cliqz folks and we had a good meeting with them. I synced with Isa afterwards. 3) Nothing exploded in the first Tor Browser release based on Firefox 60 ESR. 4) Final preparations for the first Tor Browser for Android release started. We expect to get it our later this month Shari: 1) interviews for fundraising director 2) visiting with family this week, so lots of time away from computer 3) working on Sida report isabela: 1) working on sida phase2 plan 2) getting reports to sponsors out (13, 17 and 8) 3) we got nce for sponsor17 (new deadline oct 1st) and sponsor8 (new deadline dec 31) 4) reviewing PM's applications 5) started a process to better organize how Tor will use github.com 6) officially passed the hat of UX team lead to Antonela !! \o/ 7) finished updating and organizing a very long list of things that must be done this month, including presenting a full proposal for onion services work to otf and other grant proposals Steph: 1) lost most of tues to food poisoning. still not quite 100% yet 2) thanks to Tom, Arthur, Richard for helping with a Tor Browser post. Need to get back into editing and sharing w a couple more folks 3) preparing for presentation on Tor to 50 high school girls as part of Computer Science for Cyber Security (CS4CS) Summer Program for High School Women. Thanks to gman and Yin for getting this going, sysrqb who’ll be joining, and alison for helping with an activity 4) helped with OONI launch 5) AMA with Roger was accepted in the crypto village at Def Con - we are waiting to hear our time slot. 6) lots going on through mid august: cs4cs session, hope, lfi workshop, def con, website copy writing, plus routine comms Karsten: 1) Fully integrated Relay Search into Tor Metrics rather than including it as Git submodule. 2) Developed two new graphs based on existing OnionPerf data that show circuit build times and circuit latencies. Alison: 1) Mexico City meeting planning, especially open days scheduling - I want each team to give at least one talk on the open days. I will be reaching out about this soon! 2) HOPE organizing - btw, HOPE speakers get comped tickets. A few of us HOPE speakers bought tickets. Do we know anyone who might want to buy our tickets from us? 3) trying to see where I can help with Sponsor9 next steps 4) currently in LFI week 5, working on our in-person meetup next month 5) working on updating docs for Tor Browser 8 Mike: 1) Nothing for the group Nick: 1) Still keepin' on with the Network Team; not much is happening 2) Going to PETS at end of month 3) Other teams, including OONI and Mobile and etc: we need info on how the tor in-process integration support is working for you, so we can fix any problems and annoyances while we still have time and funding. [Arturo: Yes we have this on our todo list for this month (we were hoping to do it last month, but it fell through the cracks). Are we still in time if we give some feedback by then? It would also be useful to get pointers to some unittests or similar things that check if the expectations of the API are met (if such exist).][GeKo: The best is to ping sysrqb and/or igt0 for that. They have spent the most time on mobile stuff.] Arturo: 1) Published research report on internet censorship in Egypt with AFTE: https://ooni.torproject.org/post/egypt-internet-censorship/ (received a fair amount of press coverage in Egypt and Maria spoke about it in a talk show on the Al Araby TV channel!) 2) Published research report on Ethiopia with Access Now: https://ooni.torproject.org/post/ethiopia-unblocking/ 3) Coordination with locals in Uganda to test the blocking of social media platforms following the social media tax rollout 4) Working towards a beta release for OONI Probe 3.x: https://github.com/ooni/probe-cli/pull/13

1 0

June spreadsheet - Users queries, issues, demands and comments
by cy63113 05 Jul '18

05 Jul '18

Hi everyone I'm gathering issues, comments, demands, and suggestions from different sources like IRC channels, blog comments, Stack Exchange, Tor and Tails Reddit, RT, Facebook, and Twitter. You can see here the June spreadsheet link with issues, demands and comments of users: https://ethercalc.org/3nx3nx3injin And also a pad with only relay issues with regular updates: https://pad.riseup.net/p/faq_relays-keep As mentioned in Community Team meeting in July 2, people ask questions, search for answer, and give answers, not necessarely right, spreading loads of misinformation - deep web is the champion followed by the use o VPNs, in many differents channels. It is quite noticeable that people prefer ask and get answers from other users even if it takes long rather than looking for in Tor's official channels. I guess or people don't know exactly where to looking for or are lazy to search with so many information and documentation. In the last month, there were many complaints of the TBB 7.5.4, 7.5.5 and 7.5.6. TBB 8.0a9 such as "TOR unexpectedly exited" "It is not working" "Fail to connect" and so on. Windows 10 shows most installation and updating problems. Also, loads of grievances of Orbot crashing and having hard time to update Tails (any version). A constant query is "Can I run Tail on a VM?" and "Is safe/how to route something/everything over/ through Tor. Please feel free to reach me out if you have feedback, suggestions to improve or something else. Cheers, Cybelle

2 1

June Communications Report
by Stephanie A. Whited 05 Jul '18

05 Jul '18

Hello Tor, This season is busy! I spoke on a panel with Trevor Timm (FPF) and David Greene (EFF) about tech and free speech in June, and coming up, I’ll be at NYU Tandon, HOPE, and Def Con. There are many other events happening soon, too: https://blog.torproject.org/events/month Thanks to everyone for taking initiative to write and help with posts and letting me help get the word out about events and other happenings in our community. I celebrated 1 year with Tor in June! <3 We are going strong on social media, and I picked up our Instagram account (we had 2 posts there from before my time). I will see about keeping up at least 1 post a month. Digital details: Written or edited blog posts https://blog.torproject.org/new-release-tor-browser-80a9 https://blog.torproject.org/siti-networks-india-wants-me-pay-unblock-tor https://blog.torproject.org/rompiendo-barreras-de-censura-incluso-cuando-to… https://blog.torproject.org/workshop-explorar-o-tor-em-lisboa-portugal-meet… https://blog.torproject.org/meetup-tor-community-night-pets https://blog.torproject.org/dont-let-facebook-or-any-tracker-follow-you-web Twitter: https://twitter.com/torproject Avg 3 tweets/weekday New followers: 3,906 Top tweets: https://twitter.com/torproject/status/1011324419262812162 https://twitter.com/torproject/status/1007334390479941632 https://twitter.com/torproject/status/1010156373752107008 https://twitter.com/torproject/status/1012377280000258048 Mastodon: https://mastodon.social/@torproject At least 1 post/week July2: 2.23k new: 230 followers Instagram: https://www.instagram.com/torproject/ At least 1 post/month New followers: 41 Total: 172 followers LinkedIn: https://www.linkedin.com/company/tor-project/ At least 1 post/week New followers: 43 FB: https://www.facebookcorewwwi.onion/TorProject/ At least 1 post/weekday New followers: 163 Notable press: https://news.vice.com/en_us/article/59qvwz/venezuela-maduro-tor-network-cen… https://www.zdnet.com/article/venezuela-ramps-up-censorship-with-tor-ban/ https://www.cnet.com/news/brave-advances-browser-privacy-with-tor-powered-t… o/ -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Key ID: 39A876AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

Tor Browser team meeting notes, 3 July 2018
by Georg Koppen 05 Jul '18

05 Jul '18

Hi all! We had our weekly Tor Browser meeting on Tuesday, July 3. The IRC log can be found on http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-07-03-17.58.log… and here come the meeting notes, as usual: Tuesday July 3, 2018 Discussion: - What are people's plans for Mexico City? mcs is slightly concerned that not many Tor Browser team members are listed on the wiki page (it is optional to list your plans on that page though). - next meeting [GeKo: we'll meet on 7/16 again but feel free to coordinate an ad hoc meeting if needed] - sandboxing update and meeting scheduling pospeselr: Will be working roughly half-time for the week of July 16th - 20th, wife and I will be visiting Portland The week after, we're moving to a new apartment so who knows what my schedule will be like then Last Week: - fixup patch for #26039 (extension-overrides.js) - posted patch for #26456 (HTTP onion sites inheriting previous HTTPS page's cert) - posted patch for #26615 (backport patch #859782 to ESR60 TorBrowser) - investigated #26450 (first party isolation for ESR60 pdfjs) This Week: - more #26450 investigation - fingerprinting tickets - out Friday for awesome medical fun sukhe: Last Week: - #26216 (MAR generation broken); under review - #12968 (Specify HEASLR in MinGW-w64); working - #26484 (remove windows workaround for #26476); working - #26319 (don't package in mach package step); quick rebase This Week: - Complete #12968, #26484 - Partially online on Monday (national holiday) igt0: Last week: - Sent a patch to #26528 (App stores should not be allowed to use UpdateService) - Sent a patch to #26574 ( Save TBA updates in the internal android storage) This week: - Investigate (system) addons update process for mobile mcs and brade: Last week: - Helped with the Tor Browser 8.0a9 release (macOS code signing and updater testing). - Filed #26514 (intermittent updater failures on Win64 (Error 19)). - Code reviews. - More work on #26381 (about:tor page does not load on first start in localized Windows bundle) - Started to make Mexico City travel plans. This week / soon: - We will be afk Wednesday and Thursday for an Independence Day break. - Assist with #26506 (NoScript not working on TBB/ESR60 on Windows) - Look at #26477 (Meek is broken in ESR60-based Tor Browser) - Continue on #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr) GeKo: Last Week: - Helped with the 8.0a9 release and monitored potential fallout - Got back to look at where we are wrt mobile work - Prepared meeting with Cliqz folks and did a talk in Munich and coordinated with them - worked on #26475 (ESR60-based .dmg images are not built reproducibly with Stylo enabled using rustc > 1.25.0) - more network code audit This Week: - review catch-up - begin of the month admin stuff - more work on #26475 - I'll be on vacation from July 8-July 16 tjr (most likely missing meeting) - Most likely outcome of Jacek's work is a mingw-clang build in the esr60 tree with --disable-stylo - I should get the mingw jobs actually merged into the esr60 branch this month - Unsure if he will be able to work on --enable-stylo [GeKo: If not, ping me and I'll put it back on my plate] - Once --enable-stylo is working we can get mingw-clang into -central again - the mingw-clang sandbox also crashes for an unknown reason :( boklm: Last week: - helped with publishing 8.0a9 - started looking at #25485 (Browser/TorBrowser/Tor/libstdc++.so.6: version `CXXABI_1.3.11' not found) - made patches for: - #26410: Stop using old MAR format in the next esr60-based alpha - #26515: Update Tor Browser blog post URLs - #26623: Make fpcentral recognize esr60 Tor Browser This week: - investigate testsuite and fpcentral test failures with version 8.0a9 - fill upstream binutils ticket for #26148 - continue work on some ansible roles for testsuite VMs setup (#26149) - do #26569 (Redirect pre-8.0a9 alpha users to a separate update directory) sysrqb: Last week: - Sandboxing stuff - TBA testing + proxy-bypass - Orfox release This week - Sandboxing - https://lists.torproject.org/pipermail/tbb-dev/2018-July/000874.html - Next batch of TBA tickets Does anyone have a Win10 machine with golang installed and can run this test as an unprivileged user and tell me the result?: https://github.com/Microsoft/hcsshim/blob/master/test/hns_test.go arthuredelstein: Last week: - Worked on #26237 patch (Back and Forward button should be on the left side of the toolbar) - Wrote patch for #26519 (Avoid Firefox icons in ESR60) - Investigated #25620 (NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Br) - Opened #26579 (about:tor slow to low) - Worked on #25555 (optimistic socks) - Helped with Steph's blog post This week: - More 25555, 26237, 25620, HTTP2 stuff, blog post Georg

1 0

June 2018 report for the UX team
by Antonela Debiasi 05 Jul '18

05 Jul '18

Hello Tor! A lot of exciting things happened last month. We launched Tor Browser 8 Alpha! It includes a few of UX/UI improvements we have been working on this year, and I'd like to go a little bit deep here: (a) New Circuit Display https://trac.torproject.org/projects/tor/ticket/24309 Problem We found that users don't know if circuits work per tab or globally (Tor Browser has first party isolation by default). Also, many users expect the guard node to change when asking for a new circuit. Indeed, there is nothing on circuit display that tells the user the first node is a guard, what guards are, and how it works when Tor creates new circuits for the user. Hypothesis We are consistently moving site-specific settings into the URL bar. We thought that running the circuit display to the URL bar area will help users to relate the circuit and the domain. Improve the comprehension of how Tor has been building the circuit is also part of it project scope. Related with the guard node: if we highlight the Guard node label at the UI, users will be able to identify it easier and faster. Finally, the Community team is updating the Tor Browser Manual with more information about Guard nodes for users who want to [Learn More]. (b) .onion security indicators https://trac.torproject.org/projects/tor/ticket/23247 Problem Tor Browser doesn't communicate ideally to users that visit .onion sites. For example, users visiting .onion services under HTTP looks scary with lots of warnings. Also, we are missing the opportunity to educate users about .onion services. Hypothesis Adding an onion icon will help users to identify onion services. Moreover, keeping our security indicator icons close to default security indicators will help users to react accordingly to their past experiences. You can read more about this release here [0]. Please download it, try it and report us what do you think. Next steps include a new About:Tor Page[1], a Tor Browser onboarding[2] and a reviewed update Tor Browser flow[3]. Helen Nyinakiiza (nyinz) joined us as a User Research Coordinator last month. She is working on reporting the results of all the user testing sessions we ran in India, Spain, Uganda, and Colombia related with this release. Last month also, we had been in Colombia doing privacy and security training, spreading Tor tools and learning from our new and old users. During this period, we were able to conduct six digital security and privacy training and reach three cities in Colombia. Thanks Fundación Karisma, Congreso de los Pueblos, Hacklab Bogota, Colnodo and many others for receiving us! Our support portal got its soft launch[4]. Emmapeel joined us as a Localization Manager, and she will be helping us to sort all the localization efforts we need to release it in our Tier1 languages. If you find any bug or you want to report anything you can report those in various ways[5]. If you're going to help us with translations, then you're welcome here[6]. We have a lot of things on our plate. You are welcome to join us on Tuesdays at 1600 UTC in #tor-meeting if you want to get involved! On behalf of the Tor UX team, Antonela [0] https://blog.torproject.org/new-release-tor-browser-80a9 [1] https://trac.torproject.org/projects/tor/ticket/25695 [2] https://trac.torproject.org/projects/tor/ticket/24918 [3] https://trac.torproject.org/projects/tor/ticket/25694 [4] https://support.torproject.org [5] https://trac.torproject.org/projects/tor/wiki/doc/community/HowToReportBugF… [6] https://trac.torproject.org/projects/tor/wiki/doc/translation/Introduction#…

1 0

OONI Monthly Report: June 2018
by Maria Xynou 05 Jul '18

05 Jul '18

Hello Tor world, In June 2018, the OONI team established a new partnership with the Jordan Open Source Association and published two research reports. We also made progress on the new OONI Probe desktop and mobile apps, made improvements to the OONI API, and we came up with a new scheme for an OONI measurement ID. Further information is available below. # Established a new partnership We are excited to have established a new partnership with the Jordan Open Source Association! As part of our partnership, we aim to collaborate on the study of internet censorship in Jordan through the collection and analysis of OONI Probe network measurements. ## Recap of partnerships Overall, we have established new partnerships with the following 5 organizations over the last months: 1. Paradigm Initiative (Nigeria) 2. The Advocates for Human Rights and Democracy (South Sudan) 3. Karisma Foundation (Colombia) 4. Asociacion por los Derechos Civiles (Argentina) 5. Jordan Open Source Association (Jordan) # Report on internet censorship in Nigeria In collaboration with Paradigm Initiative, we published a research report examining internet censorship in Nigeria. The full report is available here: https://ooni.torproject.org/documents/nigeria-report.pdf The OONI network measurement findings are summarized here: https://ooni.torproject.org/post/nigeria-internet-censorship/ A summary of the report is also available: https://ooni.torproject.org/documents/nigeria-report-summary.pdf # Report on the unblocking of websites in Ethiopia In collaboration with Access Now, we published a research report examining whether and to what extent websites have been unblocked in Ethiopia, following the government's announcement on the unblocking of 264 websites. Our research report is available here: https://ooni.torproject.org/post/ethiopia-unblocking/ ## Recap of reports Over the last months, we have published reports covering censorship events in the following 5 countries: 1. Pakistan: https://ooni.torproject.org/post/how-pakistan-blocked-social-media/ 2. Iran: https://ooni.torproject.org/post/2018-iran-protests/ (Part 1) & https://ooni.torproject.org/post/2018-iran-protests-pt2/ (Part 2) 3. Sierra Leone: https://ooni.torproject.org/post/sierra-leone-network-disruptions-2018-elec… 4. Nigeria: https://ooni.torproject.org/post/nigeria-internet-censorship/ 5. Ethiopia: https://ooni.torproject.org/post/ethiopia-unblocking/ # OONI Probe Desktop We made a fair amount of progress on the OONI Probe desktop apps, mostly on the command line interface (CLI) front. See: https://github.com/ooni/probe-cli/pull/13 # OONI Measurement ID We came up with a strategy for adding a unique ID to past OONI Probe measurements and how to integrate this into our collector for future measurements. Up until now OONI measurements were identified by a report_id (which can be shared by a set of measurements in the same report file) and the input. With the newly proposed scheme, it will be possible to share a single identifier to identify a specific measurement. You can read more about this here: https://github.com/ooni/pipeline/blob/master/docs/ooni-uuid.md # OONI API We made some bug fixes to the OONI API and made a new release for it. See: https://github.com/ooni/api/pull/54 & https://github.com/ooni/api/blob/master/ChangeLog.md#ooni-measurements-104-… # Revamping the OONI Probe mobile apps We internally released the revamped OONI Probe Android app with the first three screens (Dashboard, Test Overview, Test running). See: https://github.com/lorenzoPrimi/ooniprobe-android/pull/2 https://github.com/lorenzoPrimi/ooniprobe-android/pull/1 https://github.com/lorenzoPrimi/ooniprobe-android/commits/release/2.0.0 # Community use of OONI data ## Blocking of political party site in Pakistan In the run up to Pakistan's elections, the site of the Awami Workers Party got blocked on 3rd June 2018. Through the use of OONI Probe and OONI data, Pakistan's Media Matters for Democracy reported on the blocking (and unblocking) of the site: http://digitalrightsmonitor.pk/generalelections2018-amidst-shrinking-online… ## Blocking of media websites in Venezuela Two media websites (lapatilla.com and el-nacional.com) were blocked in Venezuela this month. Our Venezuelan partner, IPYS Venezuela, reported on the blocking of these media sites based on OONI data: https://ipysvenezuela.org/alerta/nueva-forma-de-censura-en-internet-aparece… # Community activities ## ENOG 15 / RIPE NCC Regional Meeting OONI's Leonid attended the ENOG 15 / RIPE NCC Regional Meeting in Moscow, Russia, between 4th-5th June 2018 (https://www.enog.org/enog-15/) ## Citizen Lab Summer Institute (CLSI) 2018 We attended the Citizen Lab Summer Institute (CLSI) in Toronto, Canada, between 13th-15th June 2018 (https://citizenlab.ca/summerinstitute/2018.html) As part of our participation at the CLSI, we facilitated the following sessions: 1. Making OONI's censorship data more actionable (https://docs.google.com/document/d/e/2PACX-1vRhl3ErFOG5gRNdzVydrGIkpsIJ_C-p…) 2. Measurements from embedded devices (https://docs.google.com/document/d/e/2PACX-1vRhl3ErFOG5gRNdzVydrGIkpsIJ_C-p…) We also interviewed five community members and plan to publish their interviews within the next months (as part of the "OONI Community Interviews" series). ## Community meeting We held a community meeting on Slack (https://slack.openobservatory.org/) on Monday, 25th June 2018. As part of our June community meeting, we discussed the following: 1. Sub-categories and tags for test lists 2. OONI Probe Debian packaging 3. Challenges in sharing OONI Run links: Creating OONI-maintained URL shorteners? ## Updated test lists Based on URLs provided by community members, we updated the following test lists: 1. Cuba: https://github.com/citizenlab/test-lists/pull/357 2. Global: https://github.com/citizenlab/test-lists/pull/353 3. US: https://github.com/citizenlab/test-lists/pull/352 4. Egypt, Tunisia, Jordan, Saudi Arabia: https://github.com/citizenlab/test-lists/pull/358 5. Azerbaijan: https://github.com/citizenlab/test-lists/pull/361 # Userbase In June 2018, OONI Probe was run 240,541 times from 4,627 different vantage points in 214 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

Proposal for the people page: Pronouns
by Tom Ritter 04 Jul '18

04 Jul '18

There's a lot of us and many folks (or maybe just me) haven't met most people or are otherwise unsure about pronouns. Put them on the people page? Good idea? Bad idea? Too public? https://imgur.com/a/u6pIZnJ The crappy HTML I wrote to do this is to float left and float right the field. <td> <a id="tjr"></a> <div class="photo"><img src="../images/people/tjr.png" alt="tjr" width="128" height="150"></div> <div class="icon"><a href="https://twitter.com/tomrittervg"><img src="../images/twitter-small.png" alt="twitter" width="20" height="20"></a></div> <div class="icon"><a href="https://db.torproject.org/fetchkey.cgi?fingerprint=8ACD146EA94CEB12E4EA6915…"><img src="../images/pgp-key.png" alt="pgp key" width="20" height="20"></a></div> <div class="name"><a href="#tjr">Tom Ritter</a></div> <div class="field" style="float:left"><b>IRC:</b> tjr</div> <div class="field" style="float:right">he/him</div> <div class="description">Maintains <a href="https://consensus-health.torproject.org/">Consensus Health </a>, runs one of the bandwidth authorities, and contributes to Tor Browser.</div> </td> -tom

16 30

[Announcement] Antonela is our new UX team lead \o/
by isabela 04 Jul '18

04 Jul '18

Hello Tor! With me transitioning to ED some reorg will have to happen to accommodate tasks I was leading into other hands You might have already seen the 2 PMs job posts we have online: https://www.torproject.org/about/jobs.html.en Besides PMing things at Tor I was also leading the UX team. Back in May I asked Antonela if she would step up and take the leadership of the team. Antonela is amazing as you all know already she strongly shares the vision for the UX team that I have and has demonstrated amazing skills at actually executing it, not only on the design part of it (which she has being great at facilitating the collaboration of all stakeholders in the process) but at organizing projects related to the UX team vision, like leading the selection of illustrators and their projects or putting together user testing processes. I am very happy to say that Antonela said yes to my question and since then has already taken the leadership hat but we haven't yet announced it to the community so I am doing it now. If you wondering what are the other people in the UX team she will be leading, they are Helen (our User Research Coordinator), Emma (our Localization Project Coordinator), Alon (our illustrator) and will also help organize projects that Hiro (our Services Admin) is helping us with. I asked Antonela if she would share some words on her new role: --- start of Anto words --- I'm grateful for this opportunity. Finally, I found IT people who have the same concerns I have! We want informed and educated users. We want users who have the power to decide. We want to make technology that makes people free. The main UX team aim is to collect all those voices around the world, understand and empathize with them and make a technology that all can use. I hope we can continue working as a bridge, with all the teams around The Project, improving our technology for people without compromise their safety and privacy. --- end of Anto words --- So! Here is the official announcement \o/ join me on congratulating Antonela on this new role and supporting her too! #GoAnto! cheers, isabela

1 0

Network team meeting notes, 2 July 2018
by Nick Mathewson 03 Jul '18

03 Jul '18

Logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-07-02-16.58.html Pad contents below: ==== = Network team meeting pad, 2 July 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 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 == 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 == * Tor 0.3.1 has reached end-of-life. * 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 == Any volunteers for handling backports to stable? teor asks: what's the timeframe? Can people help out for particular releases? End of life for 0.3.2 is October, and 0.3.3 is February. (I don't know if that will work so well unless we coordinate. It would be messy if something were backported to e.g. 0.2.9 but not 0.3.2. -NM) Any volunteers for leading 0.3.5 triage process? teor asks: 0.3.5's feature freeze is September 15, so do we need triage done in July or August? (IMO now -NM. Working on with ahf.) Do we need a volunteer to focus on the remaining bugs in 0.3.4? (isis will make sure every must bug has a person who remembers they're working on it.) Where is the work-in-progress guide for big patches in Tor? Is this based on the Seattle notes or is there more info there? [komlo] [catalyst will send komlo a link. We're keeping this unpublished until we like it more, since it has potential to read as obnoxious if we get it wrong.] == Updates == Nick: * Last week: * Get 26479 and 26480 (appveyor failures) fixed so I can release 0.3.4.3-alpha. * Release 0.3.4.3-alpha. * Prepare for an 0.3.3.6 release * Continue refacatoring src/common * Make the dependencies in src/libs acyclic. * This week: * Plan an order of operations for splitting src/or. * Open tickets about remaining cases of #25386 (sanitizers, rustdoc). * Document src/lib. * Make requested post-merge cleanup changes in src/lib structure. * Release 0.3.3.8 * Finish PETS reviews teor (offline): last week: - Reviewed juga's patch to put bandwidth file headers in votes (#3723) - Other small bwauth suggestions and feedback - Helped answer some fallback questions - We have 30 new fallbacks, we need another 40 fallbacks for censored clients to bootstrap (Maybe it will take a few more weeks to get there.) https://trac.torproject.org/projects/tor/ticket/24805#comment:33 - Two successful experimental PrivCount data collections - And the research is done! this week: - Review PrivCount in Tor blinding and secret sharing branch - Implement PrivCount in Tor noise - Work on a per-relay / per-consensus / per-counter noise spec for PrivCount in Tor - Reduce my review and revision backlogs ahf Last week: Sponsor 8: - Better process handling for #25502 update: started to write the Windows related code, but ran into #26594 as a blocker. Spend some time trying to figure out what the issue was. Misc: - Reviewed #24104, #26594, first look at #24546. - Continued study of Chrome's Windows sandbox implementation. This week: Sponsor 8: - Finish Windows specific parts of #25502 (reading of output from subprocesses). - Memory profile work with Nick and David(?) Misc: - Look at the remaining Coverity issues from week 25 (bug #26521). - Rotation role: Bug triage. - Figure out Mexico logistics: We have no meetings before the team day? No meetings after the schedule on trac? (This is correct -NM.) - Hope to be able to lift Chrome's Windows sandbox out as a small C++ library to play around with. - I'm away most of Wednesday (US time). - Do phase 1 triage with Nick: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TicketT… haxxpop: Last week: - Revise the PR according to dgoulet's comments This week: - Continue revising the PR komlo (offline): - Last week: - Prepare for some public talks (not much hands-on tor work) - This week: - Follow up and test out #24249 with https://github.com/eqrion/cbindgen. Overall, I think we definitely want to compile Rust->C types, as opposed to using bindgen as we would still need manual translation for libc types. More analysis on the ticket if anyone is interested. Mike: Last week: - Feeling a bit paralyzed by choosing which semi-urgent thing to prioritize (Sponsor2 work, Sponsor2 report, PETS Research Blog posts, vanguards experiments, vanguard packaging, vanguards blogposts, figuring out how the hell to pay PETS attendance, accumulated bureacracy since vacation). Treaded a bit of water trying to figure out which thing to do. This week: - Hopefully now have a plan: - Backburner Vanguard performance experiment and just choose consservative 2-3-8 params - Write a vanguards release blogpost draft, circulate to asn - Write PETS research blogpost draft, circulate to ??? - Ignore the bureacracy because fuck it. asn: Last week: - Finalized #25552. Been testing it for the past weeks and it's working great! Ensured that it addresses the issues onionshare has been seeing as well as #26549. - Reviewed #26479, #26480, #26425. - Discussed onion name systems with Mike and others. Now that v3s are getting more and more deployed, it's important to start fixing this big UX barrier. This week: - More reviews. - Catching up with leftover 035 deliverables. catalyst: last week (2018-W26): - CI rotation -- included some Jenkins issues like #26503 - reviewed some cross-compilation tickets (#25895, #25977) - made some progress on the big patches doc - helped with a few minor glitches from the refactoring commits (thanks for working on the refactor, Nick!) this week (2018-W27): - Coverity rotation - code review - more work on big patches doc - follow up on some Rust-related tickets as needed - dealing more with flaky internet access - July 4 off because holiday isis: last week: - took tuesday through thursday off to attend zcon0 - reviewed #25386 #24249 this week: - back to the create cell work - catching up on backlog - 1:1:1 meeting on tuesday at 10am PST - july 4 off

1 0