- tor-project - lists.torproject.org

Notes from June 6 2019 Vegas team meeting
by Karsten Loesing 07 Jun '19

07 Jun '19

Notes for June 6 2019 meeting: Gaba: 1) Untagging remaining tickets from sponsor 19, looking for s19 tickets for new sponsors (phw and network team working on it) and updating roadmaps. The same with sponsor V. 2) Added sponsor 28 and 30 to trac. Going through checklist of new grants. 3) OONI meeting to update roadmap. 4) Creating the agenda for Tor meeting. This year we only have 3 days and we need to go through a process of selection of which sessions we want to have. Add the sessions you are all thinking are important to have in the face to face meeting. Thoughts on how to select/prioritize sessions? https://pad.riseup.net/p/_kDAK09C16xL2lBRQ7sJ 5) [INFRA INVENTORY] Sysadmin Team is asking for people at the Tor project to fill information about resources they are using right now. Please ask your team to add the resources they are using: https://nc.riseup.net/s/QEM4MNBA8MmWW4x - purpose (e.g. service running) - location (e.g. hetzner, amazon, etc) - age/lifecycle (e.g. 2008, ephemeral containers, etc) - memory (e.g. 24GB RAM) - disk (e.g. 2TB SSD or HDD) - cores (12 CPU) - cost (100$USD/mth) 6) helping with grant application 7) meeting with simple secure about new metrics data portal 8) meeting to talk about scalability projects for funding 9) looking at capacity starting in july for sponsor work Pili: 1) Helping Season of Docs candidates with their proposals 2) Polishing up Community Portal before sharing for feedback 3) Looking at different Open Source initiatives to attract volunteers and/or committers. 4) Helping with Tor meeting agenda 5) Updated New Grants Checklist and added template for project kick off meetings 6) UX Ticket triage 7) S27 meeting 8) Tor Browser Release meeting Nick: 1) another alpha release came out 2) another stable soon, after alpha has seen more testing Mike: 1) Tor-scaling making progress towards Mozilla all-hands 2) Helping with 0.4.1 fixes Karsten: 1) Updated circuit round-trip latencies graph to include worst-case latency: https://metrics.torproject.org/onionperf-latencies.html 2) Added throughput graph including worst-case throughput: https://metrics.torproject.org/onionperf-throughput.html 3) Merged OnionPerf branch to include more detailed error codes in .tpf files for later analysis and/or visualization. Antonela: 1) did frontend work for the community portal 2) working with OONI - OONI Explorer issues review, prioritization toward stable - reviewing tickets that require UX efforts for this month 3) supported the Pride Month initiative by the comms team 4) sent RSVP to OTF invite for the Taiwan summit 5) working on TBA - reviewing #24920 and #30540 6) working on S27 - will meet syverson_ next week to discuss/learn about his ideas for O2A3 7) working on Defenders of Privacy campaign for the fundraising team 8) made assets for the Bug Smash Fund campaign for the fundraising team Erin: 1) General HR stuff Anarcat: 1) hardware survey in progress 2) pushed back on request to open SMTP authentication with request for concrete bug reports of delivery failures 3) usual sysadmin stuff

1 0

Damian's Status Report - May 2019
by Damian Johnson 07 Jun '19

07 Jun '19

Hi all! Here's my status report for the last few months... https://blog.atagar.com/may2019/

1 0

Anti-censorship meeting notes, 6 June 2019
by Philipp Winter 06 Jun '19

06 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-06-17.06.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 6th 17:00 UTC Weekly meetings every Thursday 17: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. (There is a bug in wekan, what we use for the board, that make it hard to load. You have to click in 'all boards' and then in the board to get it to load) Roadmap by topic: https://storm.torproject.org/shared/KXkqlNP8ouNks_ey5khZKUSbNj9ZoidXmEp80OD… Gettor Roadmap: https://dip.torproject.org/anti-censorship/gettor/boards <-- We are experimenting with gitlab for gettor and hiro is working on the board there. Each ticket is linked back to trac for now to keep historical context --> 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. --------------------------- ---- 6th June 2019 ---- --------------------------- == Announcements == * [INFRA INVENTORY] Sysadmin Team is asking for people at the Tor * project to fill information about resources they are using right * now. https://nc.riseup.net/s/QEM4MNBA8MmWW4x * purpose (e.g. service running) * location (e.g. hetzner, amazon, etc) * age/lifecycle (e.g. 2008, ephemeral containers, etc) * memory (e.g. 24GB RAM) * disk (e.g. 2TB SSD or HDD) * cores (12 CPU) * cost (100$USD/mth) * [EMAIL] If you have problems with email @torproject.org please * comment on this ticket: https://bugs.torproject.org/30608 == Discussion == * Creating the agenda for Tor meeting. This year we only have 3 days * and we need to go through a process of selection of which sessions * we want to have. Which sessions you are all thinking are important * to have in the face to face meeting? * https://pad.riseup.net/p/_kDAK09C16xL2lBRQ7sJ * Roadmap: are people ok with what is in the 'in progress' and * 'review columns'? Are people ok with stuff in the backlog until * our roadmap building session in July? Some tickets from s19 moved * into s28 by phw. We continue working on them and adjust on the way * until July meeting. == 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. hiro: This week (2019-05-16): - Revised gettor code with phw - Merge new code - Deploy gettor - See who has access to gettor repository in torgit - Sync torgit repository with dip - Port tickets from roadmap to dip Next week: - Add more tests to gettor - Work on twitter distribution channel Past week: - Rebase gettor PR with phw - Started testing framework phw: This week (2019-05-30): - Filed #30777 for a "set up new bridges" campaign - Started reviewing #30731 - Improved obfs4 bridge setup guide - Published monthly anti-censorship report - Deployed bridges.torproject.org/scan/ - Deployed #28655 - Reviewed Sponsor 19 report - Filed #30706 for BridgeDB housekeeping - Wrote script that tests obfs4 port of our bridges. Emailed some ops whose obfs4 port was unreachable. Next week: Help with: Gaba: Last week: * looked at s28 info * closed up s19 * updated roadmap with s28/s30 and removed s19 This week (05/30): * follow on s28 and s30 ahf (will be AFK due to Ascension Day here in DK) Last week: - Uploaded rebased patches for #29736, #29207, and #29260 at https://github.com/ahf/snowflake/tree/features/websocket_r5 - Been playing around with a method that I think will allow us to load shared libraries of PT's for Tor (on Linux only for now). - Hacking on #28930 - Got OK from dcf on #28849! Thanks! Next step is to talk to the PT adapter person. This week: - Hacking on #28930 - Prepare presentation for some conference next week in Switzerland. - Away Thursday/Friday for "Ascension Day". kat5: Last week (May 20): - Added more content from tickets - Added Tails content This week (May 27): - Marked finished sections complete - Final edits - Hand off for submission to DARPA - NEEDS HELP: - Sign-off from phw dcf: 2019-06-06 Last week: - made graphs of pre-sanitization broker logs (#30731) - deleted unsanitized broker logs (#30693) Next week: - look at WebExtension changes in https://bugs.torproject.org/23888#comment:24 - publish post-sanitization broker logs (#30731) - add resources I manage to the infrastructure survey Help with: cecylia (cohosh): last updated 2019-06-06 Last week: - snowflake - worked on a sequencing layer for snowflake (#25429, #29206) - sunk some time into the windows build (#25483) Next week: - continue reliability layer for snowflake (#25429, #29206) - re-evaluate broker stats and implement missing pieces (#21315) - continue hacking on windows build (#25483) - update default STUN configuration (#26348) - clean up and increase test coverage for snowflake (#29259) Help with: - incremental review of #29206 catalyst: week of 05/30 (planned): - open new tickets for improving bootstrap reporting - #30639 looks like it might be good to work on next? (raises some questions about how we tell Tor Launcher that bootstrapping has failed) week of 05/30 (actual): - bureaucracy - mostly network team reviews - finally updated our meeting time on the shared Tor calendar week of 06/06 (planned): - unparent open children of #28018 and tag them usefully, so we can close #28018 arlolra: 2019-06-06 Last week: - nothing This week: - get back to the snowflake webextension Help with: - nothing

1 0

OONI Monthly Report: May 2019
by Maria Xynou 06 Jun '19

06 Jun '19

Hello, Below is OONI's monthly report for May 2019. ## Beta release of revamped OONI Explorer Over the last year (thanks to Mozilla Open Source Support), we have been working on revamping OONI Explorer entirely. The code for the next generation OONI Explorer is available here: https://github.com/ooni/explorer This has involved re-writing all of the OONI Explorer codebase in react.js (using next.js), re-designing the platform entirely to improve its UX, creating a more powerful search tool (which required a series of improvements to the OONI data processing pipeline), and adding a number of new features (based on community requests). In January 2019, we conducted a usability study with several experienced OONI Explorer users to collect their feedback in the more initial stages of design and development. We released a beta of the revamped OONI Explorer in April 2019. The beta of the revamped OONI Explorer is available here: https://explorer-beta.ooni.io/ In May 2019, we engaged our partners and community members with beta testing and spent the month addressing bugs and making improvements in preparation for the upcoming stable release. If you notice any bugs or issues, please file Github tickets or send an email to bugs(a)openobservatory.org. ## Beta release of OONI Probe Command Line Interface (CLI) and Desktop App We released the first beta of the OONI Probe desktop app for Windows and macOS: https://github.com/ooni/probe-desktop/releases/tag/v3.0.0-beta.3 We also released a new beta of the OONI Probe CLI: https://github.com/ooni/probe-cli/releases/tag/v3.0.0-beta.3 If you notice any bugs or issues, please file Github tickets or send an email to bugs+desktop(a)openobservatory.org. ## New measurement engine in Go Measurement Kit (https://github.com/measurement-kit) is our measurement library that powers the OONI Probe (mobile and desktop) apps. In May 2019, we started writing a new measurement engine in Go to better support the integration of new nettests (such as the new OONI Probe test for Psiphon) and to generally improve its agility. The code for this engine is available here: https://github.com/ooni/probe-engine As of 31st May 2019, this new engine contains code to communicate with OONI servers and two nettests implemented in Go: ndt7 and Psiphon (discussed below). This new engine also includes code for exporting Measurement Kit network tests to Go code. ## ndt7 test ndt7 is a next generation speed test that will replace the NDT test currently included in the OONI Probe mobile app. In May 2019, we finished writing the ndt7 client (see https://github.com/m-lab/ndt7-client-go/pull/4) and integrating it into ooni/probe-engine. ## Psiphon test The ooni/probe-engine uses the Psiphon client library to implement a new nettest which checks whether Psiphon is able to create a tunnel and whether this tunnel could be used to fetch web resources over the internet. See: https://github.com/ooni/probe-engine/tree/master/experiment/psiphon ## OONI Probe mobile app In preparation for the 2.1.0 release, we made a series of improvements to the OONI Probe mobile apps. On Android: https://github.com/ooni/probe-android/pull/226 https://github.com/ooni/probe-android/pull/227 https://github.com/ooni/probe-android/pull/228 https://github.com/ooni/probe-android/pull/230 On iOS: https://github.com/ooni/probe-ios/pull/276 https://github.com/ooni/probe-ios/pull/277 https://github.com/ooni/probe-ios/pull/278 https://github.com/ooni/probe-ios/pull/279 https://github.com/ooni/probe-ios/pull/280 https://github.com/ooni/probe-ios/pull/281 ## Report on blocking of Wikipedia in China In collaboration with Taiwan's Open Culture Foundation (OCF) and China's iYouPort, we published a report on the blocking of all Wikipedia language editions in China: https://ooni.torproject.org/post/2019-china-wikipedia-blocking/ Thanks to our local collaborators, we were also able to publish a Chinese version of the report on our site: https://ooni.torproject.org/post/2019-china-wikipedia-blocking.zh/ The report was also published by iYouPort: https://www.iyouport.org/2019-china-wikipedia-blocking/ The report received press coverage from the following: * BBC: https://www.bbc.com/news/technology-48269608 * TIME: http://time.com/5589439/china-wikipedia-online-censorship/ * The Washington Post: https://www.washingtonpost.com/business/2019/05/15/china-bans-wikipedia-all… * CNET: https://www.cnet.com/news/the-great-firewall-of-china-blocks-off-wikipedia/ * National Post: https://nationalpost.com/news/world/china-bans-wikipedia-before-30th-annive… * NewTalk Taiwan: https://newtalk.tw/news/view/2019-05-15/246945 * Liberty Times Net: https://ec.ltn.com.tw/article/breakingnews/2791325 * Solidot podcast (Chinese website): https://www.solidot.org/story?sid=60516 * Alternatywa: https://alternatywa.net.pl/chiny-zaczely-blokowac-wikipedie-w-kazdym-jezyku/ * La Revue Internationale: https://www.revue-internationale.com/2019/05/wikipedia-censure-en-chine/ OONI's Arturo discussed the blocking of Wikipedia in China (and Turkey) with ABC Radio Australia: https://www.abc.net.au/radio/programs/pm/wikipedia-takes-turkey-to-european… The Top10VPN site also published an article covering our research: https://www.top10vpn.com/news/censorship/all-language-editions-of-wikipedia… ## Report on internet censorship in Nigeria In collaboration with our Nigerian partners, Paradigm Initiative, we co-published a research report measuring network interference during Nigeria's 2019 general elections. Our joint research report is available via the following sites: * OONI: https://ooni.io/post/2019-nigeria-internet-censorship/ (includes full OONI analysis) * Paradigm Initiative: https://paradigmhq.org/download/the-2019-nigerian-elections-through-the-len… (includes full PDF - but with summary of OONI analysis) ### Blocking of social media in Indonesia During post-election protests, access to social media was reportedly blocked in Indonesia. We coordinated with local community members on OONI Probe tests and confirmed the blocking of WhatsApp, Facebook Messenger, and Telegram by means of DNS on some ISPs. We also found that it was possible to circumvent the blocks by enabling encrypted DNS. We generated a chart based on our data analysis, which we shared with the community: https://twitter.com/OpenObservatory/status/1131207330366992384 We also shared our analysis used to produce the chart: https://gist.github.com/hellais/0166d1059d4055057b25b2f6ceddda76 ## Community use of OONI data ### Report on blocking of thousands of websites in Egypt AFTE, our Egyptian partners, published a research report on the collateral blocking of thousands of websites in Egypt: https://afteegypt.org/en/digital_freedoms-2/publications_digital_freedoms-d… The use of OONI Probe and OONI data supported this research. ### Report comparing internet censorship in Russia and Crimea during election period OTF Information Controls Fellows Ksenia Ermoshina and Igor Valentovitch carried out research examining internet censorship in Russia and Crimea through the use of OONI Probe and OONI data. Their research report, "Measuring Internet Censorship in Disputed Areas: An examination of online media filtering in Russia and Crimea during the 2018 Russian presidential elections", is published on the OTF website: https://www.opentech.fund/news/exploring-online-media-filtering-during-2018… ## Community activities ### Media for Democracy Forum OONI's Arturo traveled to Washington, DC, to participate at the Media for Democracy Forum (organized by USAGM) on 7th May 2019. Arturo presented OONI and discussed media censorship on the panel "New and Emerging Threats to Media Freedom: What's Next?". Information about the event is available here: https://www.usagm.gov/2019/05/07/media-for-democracy-forum/ ### Global Media Forum OONI's Arturo and Maria traveled to Bonn, Germany, to participate at the Global Media Forum (organized by Deutsche Welle) on 27th & 28th May 2019. Information about the event is available here: https://dw-global-media-forum.com/ ### Community meeting We held the monthly OONI community meeting on our Slack channel (https://slack.openobservatory.org/) on Friday, 31st May 2019. As part of the meeting, we discussed issues related to failed measurements and (accessing and sharing relevant) logs, as well as strategies and next steps in better supporting OONI Probe users who run into networking issues. We also shared updates with regards to OONI's new system for sharing the OONI metadb with third parties, recent research reports, and upcoming sessions at RightsCon. ## Userbase In May 2019, OONI Probe was run 355,293 times from 5,159 different vantage points in 215 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ 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

Tor Browser Release Meeting today: Wednesday 5th June @ 18UTC
by Pili Guerra 05 Jun '19

05 Jun '19

Hi everyone, This is your reminder for the Tor Browser Release meeting happening today @18UTC on #tor-meeting. See you there! 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 - Next meeting Tuesday 21st May @ 1500UTC
by Pili Guerra 04 Jun '19

04 Jun '19

Hi everyone, Just a reminder that we’ll be meeting this week to discuss progress on the Onion Services project. Please join us this Tuesday 21st May @ 1500UTC on #tor-meeting if you’d like to participate. 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

Anti-censorship team monthly report: May 2019
by Philipp Winter 03 Jun '19

03 Jun '19

BridgeDB ======== * We submitted our "gather BridgeDB usage statistics" proposal to the Tor research safety board. You can find the proposal it here: <https://lists.torproject.org/pipermail/anti-censorship-team/2019-April/0000…> We are still waiting to hear back from the board. * We filed <https://bugs.torproject.org/30441> to understand why BridgeDB is handing out so many offline bridges. It looks like this problem is a combination of several smaller problems. We wrote a tool that scans the obfs4 port of all bridges that our bridge authority knows about, and started contacting the operators of bridges whose obfs4 port was unreachable. Have a look at the ticket for details. GetTor ====== * We deployed the refactored GetTor codebase: <https://bugs.torproject.org/28152> Pluggable transports ==================== * We built a service that allows bridge operators to scan the obfs4 port of their bridge. The service is now deployed and available at <https://bridges.torproject.org/scan/>. Give it a try and tell us what we can do better! - The ticket is available here: <https://bugs.torproject.org/30472> - The code is available here: <https://github.com/NullHypothesis/obfs4PortScan> - This effort is part of improving the UX of setting up an obfs4 bridge: <https://trac.torproject.org/projects/tor/ticket/30471>. * We revised our obfs4 setup instructions: <https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4…> - This effort is part of improving the UX of setting up an obfs4 bridge: <https://trac.torproject.org/projects/tor/ticket/30471>. * We assessed the HTTPS Proxy pluggable transport; i.e., understood its advantages, disadvantages, and what it would take to deploy it. Our assessment is available at <https://trac.torproject.org/projects/tor/ticket/29278#comment:6>. Censorship analysis =================== * We are in touch with a research group that is studying the GFW's active probing system. We noticed that the GFW does not probe recent Tor versions. One explanation is that the cipher list in Tor's TLS client hello (this is what the GFW uses to identify Tor) changed. - See <https://bugs.torproject.org/30500> for the ticket. * We recently saw a drastic increase of Tor users from Iran. We don't yet understand the reason for this. - See <https://bugs.torproject.org/projects/30636> for details. Snowflake ========= * We made progress with snowflake's WebExtension. - See <https://bugs.torproject.org/23888> for details. * We started working on detailed measurements of the snowflake blocking in China. We saw Google's STUN servers starting to be blocked in China, as well as blocking stop for individual proxies. - See <https://bugs.torproject.org/30368> for the ticket. * Fixed several bugs in the client and snowflake proxy-go instances. * Starting locally collecting geo-IP metrics on snowflake proxies. * Fought a broker outage and implemented a fall-back mechanism for using snowflake certificates - See <https://bugs.torproject.org/30512> and <https://bugs.torproject.org/30509>. Miscellaneous ============= * We finished a technical report as deliverable for Sponsor 19. The report provides a comprehensive overview of the state of Tor's anti-censorship efforts and we will soon publish it in a blog post. * We attended the kick-off meeting for Sponsor 28. As part of this project we will keep improving snowflake, improve and evaluate the obfs4 protocol, and extend our pluggable transport specification. - See the following page for Sponsor 28-related work: <https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28>

1 1

Tor Browser team meeting notes 3 June 2019
by Georg Koppen 03 Jun '19

03 Jun '19

Hi! Our weekly meeting just ended (I am sure it was the shortest meeting ever :) ). The IRC log can be found at: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-03-17.31.l… and below are the items from our pad mcs and brade: Last week: - Helped with code reviews. - Commented in #30639 (Tor tries to connect over IPv6 in IPv4 networks) - Investigated the update portion of #30565 (corrupted Linux 64bit browser). - Thought about the updater-related work for #30429 (ESR 68 Rebase — updater patches). - Worked on #30000 (Integrating client-side authorization to onion services v3). - Continued to work on the Onion Services client auth prompt (#30237). - Provided some info for the May Sponsor 27 report (Onion Services). This week: - More work on the Onion Services client auth prompt (#30237). - Maybe: #29197 (remove use of overlays from Tor Launcher) - Maybe: #30429 (ESR 68 Rebase — updater patches). GeKo: Last week: - shorter week due to public holiday on Thursday - release prep and release building + signing for 8.5.1 - HackerOne bug triage - lots of toolchain work with patches for Linux toolchain (#30736, #30490, #30701, #30734); more work ins needed as at least Stylo build is breaking for unknown reasons (see: https://trac.torproject.org/projects/tor/ticket/30321#comment:1) - work on aarch64 build (#28119), need to revise the patch - backport of Mozilla bug 1552993 - wrote patches for ro locale (#30469) - reverted fix for #29641 - reviews (#30635, #30480, #30549) - going over more reports about 8.5 bugs/missing features This week: - another shorter week due to public holiday on Thursday - 9.0a2 prep and build and signing (hopefully) - more HackerOne work - toolchain improvements - rebase and #10760 reviews - finish fix for #28119 tjr - Not much. Was out 3 days recently. - Organized Letterboxing bugs: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1407366&hide_resolve… - There is a letterboxing bypass (1556016) that I don't *think* is exploitable in the default configuration, mostly due to luck - The mingwclang x86 malloc/free mismatch had some work done by glandium. I need to test if it fixed it https://bugzilla.mozilla.org/show_bug.cgi?id=1547519 - Organized RDD tasks - https://bugzilla.mozilla.org/show_bug.cgi?id=1553720 - Landed a patch disabling RDD and AV1 due to undiagnosed failures. This will have to be fixed by ESR 76 but hopefully much sooner. acat: Last week: - Some reviews. - Fix torbutton duplicate locales in 10760. - Ported onboarding for ESR68 (28822) This week: - Remaining work on 30429 (Rebase Tor Browser patches for Firefox ESR 68) - Finish! 30304 - Browser locale can be obtained via DTD strings sysrqb: Last week: Synchronized built-in bridges on Android with desktop (#30635) Investigated and created a patch for opening a URL from another app with tor browser when it wasn't previously running (#30573) Created a patch for implementing private tabs-only mode on Android (#24920) Began rebasing Android patches on 68esr This week: Release Continue rebasing for 68esr Fastlane (#26844) F-Droid (#27539) boklm: Last week: - was afk Thursday and Friday - helped build new release - reviewed #30492 and #28119 - worked on #28672 (Android reproducible build of Snowflake), trying to get go-webrtc to build This week: - help with publishing 8.5.1 - try to finish #28672 (Android reproducible build of Snowflake) - look at remaining failing testsuite tests - update patch for #30549 (Add script to remove expired sub-keys from a keyring file) after review - some reviews antonela Last week: - worked on onion auth #30237 - worked on tb8.5 bugs #30631, #30560 This week: - TBA user research going on in Uganda and Kenya Georg

1 0

Network team meeting notes, 3 June 2019
by Nick Mathewson 03 Jun '19

03 Jun '19

Hi! You can find the logs from our weekly meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-03-17.00.html Here are the contents of the meeting pad: ================= = Network team meeting pad! = This week's team meeting is at Monday 3 June at 1700 UTC (last Monday was a US public holiday) on #tor-meeting on OFTC. June schedule: * Monday 3 June at 1700 UTC (The 28 May meeting was at the patch party time) * Monday 10 June at 1700 UTC * Monday 17 June at 1700 UTC * Monday 24 June at 1700 UTC 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. (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.) 6 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002316.html 13 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002325.html 20 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002335.html 28 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002338.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.1 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… Click on 'all boards' and then the network team one. 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 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… . * See discussion notes below. 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. When you are overloaded, it is ok to say "no" to things. And it is ok to reschedule things. ------------------------------- ---- 03 June 2019 ------------------------------- == Announcements == == Discussion == Rotation updates: (CI/coverity nickm->teor; bug triage dgoulet->mikeperry) coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) jenkins (seems ok) Travis Stem failure is happening very frequently. Test_rebind failure less so. teor says: I need CI to be stable so I can do backports and CI changes. test-stem is failing (#29437), can we allow_failures for that job? test_rebind is failing (#28229), should we remove it, or put it in a separate job and allow_failures? Proposed solution: allow_failures for test-stem. Disable test_rebind on OSX only Add a section to our CI status page for disabled CI Add a section to doc/HACKING/ReleasingTor.md reminding releasers to manually check the status of whatever the disabled CI would have checked. CI person should periodically look at these jobs. Appveyor Bug triage Should we deploy sbws to half the bandwidth authorities? Should we raise AuthDirMaxServersPerAddr to 4? https://lists.torproject.org/pipermail/tor-dev/2019-June/013859.html https://lists.torproject.org/pipermail/tor-dev/2019-June/013852.html == 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 (actual): . followed on documents for new sponsor (28) . monthly report for sponsor 27 (onion services) This week (planned): . check sponsor V work until now . stockholm meeting planning . closing sponsor 19 Help with: teor: (offline at the usual meeting time) Week of 28 May (planned): - Urgent: - Keep on working on Tor / Stem CI - Fallback directory mirror list rebuild - 041-must Week of 28 May (actual): Urgent: - Kept on working on Tor / Stem CI - Fallback directory mirror list rebuild - made some progress - sbws diagnostics - 1:1 and workload planning and things Important: - relay operator queries Other: - Fixed a confusing address parsing bug with a nice refactor (#30721, can be Sponsor 31) Deferred: - #16564 (reject bridge descriptors on non-bridge authorities) Week of 3 June (planned): Urgent: - Kept on working on Tor / Stem CI ??? - Fallback directory mirror list rebuild - HR stuff Important: - chutney merge backlog (blocked on stable Tor CI) - merge add chutney to tor's CI (blocked on stable Tor CI) - backport backlog (blocked on stable Tor CI) Deferred: - #16564 (reject bridge descriptors on non-bridge authorities), needs complex unit tests Week of 3 June (actual): Urgent: - HR stuff Important: - sbws triage: - it is probably safe to deploy sbws to one more authority (we now have 2, we can have 3) - identified 3 blockers for deploying sbws to more than 3 authorities Nick: Week of 28 May (planned): - More for on PT transition bugs (29875, 24367). Fix? - More for on 041-must/should items - Chutney CI work with teor, tbd - Try to figure out stem CI issue with teor, tbd - Followup on issues from retrospective Week of 28 May (actual): - PT transition bugs (29875 and 24367) -- diagnosed and developed a fix. [This took a while to figure out, since there were at least two bugs at work here. First, we didn't treat bridge changes as meaning that we might not be able to build circuits. Second, we didn't ignore guard entries based on _former_ bridges when counting how many guards we had.] - Staring and poking at stem+CI issues, but didn't get too far. - Numerous bugfixes/investigations: - 29670 -- Could not create SOCKS args string - 30686 -- Better warnings when minherit/madvise fails - 30674 -- Find out why ubsan/asan CI didn't catch #30629 - 30629 -- We seem to be reading some freed events on exit - 30614 -- Use MAP_INHERIT_NONE/ZERO if available instead of crashing on assertion failure - 22619 -- SessionGroup = Reading config failed - Lots of reviews, some with tweaked branches. Lots of merges Week of 3 June (planned): - Release 0.4.1.2-alpha - Possibly, release 0.4.0.6 - Open tickets from team retrospective - Try to finish 041-should items - Try to solve CI failures. Mike: Week of 5/28 (planned): - Laptop issues - Scalability meeting - Peer feedback - Register for PETS - Circpad relay-side warn log bug (https://trac.torproject.org/projects/tor/ticket/30649) - Maybe circpad documentation? Week of 5/28 (actual): - Laptop issues - Scalability meeting and followup - Some work on circpad relay-side warn log bug (https://trac.torproject.org/projects/tor/ticket/30649) Week of 6/02 (planned): - More scalability followup (KIST+EWMA -> wiki; metrics updates; Mozilla all hands meeting planning) - Peer feedback - Register for PETs - #30649 - Circpad documentation? catalyst: week of 05/27 (2019-W22) (planned): - reviews - revise #29976 - other bootstrap work? week of 05/27 (2019-W22) (actual): - holiday 05/27 - medical 05/29 - reviews - revised #29976 (now merge_ready) - looked at #30639 some week of 06/03 (2019-W23) (planned): - reviews - rearange bootstrap tickets more logically - teor's on CI rotation but i can try to help with CI stuff, especially our persistent spurious failures asn: [Will be on dinner during meeting. Might be able to get in in the end.] Week of 05/27 (planned): - Finish reviews. - Finish backlog. - Move on with s27 o2a1. Hopefully get it close to review. Week of 05/27 (actual): - Posted a #30381 branch for review. It was imperative to get this done quickly so that we do not block the TB team. Also had to revise the proposal. - Revised #28634 proposal based on ML feedback. - Did reviews/merges but still got more to do. - Brainstormed HS DoS solutions with dgoulet and posted on mailing list: https://lists.torproject.org/pipermail/tor-dev/2019-June/013862.html - Helped with S27 monthly report. - Some travel planning for allhands. Week of 06/03 (actual): - Finalize s27 o2a1. - Help organize our AllHands experience. - Fix #30578 circpadding bug (041-must). - Do more work on HS DoS. - Some more travel prep for allhands. ahf Week of 29/5 (planned): Network team: - Continue with S19 tasks. - Begin review process of #29736 patches with cohosh while I finish the last bits. Misc: - Need to prepare a presentation for an event in Switzerland next week that Steph asked if I was up for. Going to be away some of the 5th of June while traveling for this event and the presentation is the 6th. - End of month tasks. - Away on Friday due to the "Ascension Day" (all the Danish holidays will be over soon!). Week of 29/5 (actually): Network team: - In S19 land: rebased and cleaned up patches for Snowflake tickets #29736, #29207, and #29260. - Progress on #28930. - Hacked a bit on the shared library PT idea during Ascension Day. Misc: - Began working on a non-XML-RPC based Trac Client to create tickets with. - Worked on presentation for the Switzerland event. - Out for the Ascension Day holiday. Week of 3/6 (planned): Network team: - Hack on #28930. - Talk with traffic-obfuscation list people about #28849 - Talk to Cecylia and dcf about patches for #29736 and friends. Misc: - End of month tasks. - At a conference Wednesday and Thursday in Switzerland doing a presentation on Tor. juga(offline): Week of 05/20 (planned) - Add Tor version to the bandwidth file (#30196) Week of 05/20 (actual) Week of 06/03 (plan) - Continue with #30406: Refactor header constants in sbws to use Stem's one dgoulet: Week of 05/28 (actual): - Implemented #15516. See tor-dev@ discussion https://lists.torproject.org/pipermail/tor-dev/2019-May/013837.html - Implemented #30382 (SOCKS5 extended errors, unofficial-prop304). Need unit tests. Under review by asn. - New version of #29034. - Got #30365 merged (prop289 proposal closed and merged into tor-spec.txt). - Discussion with arma and asn on HS DoS defenses. - Implemented #30687 (generic token bucket). Needed for #15516. - Merges and reviews. - Spent a bit of time on figuring out #30638 without success. - Tor-scaling meeting. Week of 06/03 (planned): - Finalizing s27 tickets (#15516, #30382). - Continuing to understand #30368. - Get prop#304 merged into tor-spec.txt

1 0

minutes from the tor sysadmin meeting
by Antoine Beaupré 03 Jun '19

03 Jun '19

These are the minutes from the TPA meeting held today. # Roll call: who's there and emergencies No emergencies, anarcat, hiro, ln5 and weasel present, qbi joined halfway through the meeting. # What has everyone been up to ## anarcat * screwed up and exposed Apache's /server-status to the public, details in [#30419][]. would be better to have that on a separate port altogether, but that was audited on all servers and should be fixed for now. [#30419]: https://trac.torproject.org/projects/tor/ticket/30419 * moved into a new office which meant dealing with local hardware issues like a monitors and laptops and so on (see a [review of the Purism Librem 13v4][] and the [politics of the company][]) [politics of the company]: https://anarc.at/blog/2019-05-13-free-speech/ [review of the Purism Librem 13v4]: https://anarc.at/hardware/laptop/purism-librem13v4/ * did some research on docker container security and "docker content trust" which we can think of "Secure APT" for containers. the TL;DR: is that it's really complicated, hard to use, and the tradeoffs are not so great * did a bunch of vegas meetings * brought up the idea of establishing a TPI-wide infrastructure budget there as well, so i'll be collecting resource expenses from other teams during the week to try and prepare something for those sessions * rang the bell on archive.tpo overflowing in [#29697][] but it seems i'll be the one coordinating the archival work [#29697]: https://bugs.torproject.org/29697 * pushed more on the hiera migration, now about 80% done, depending on how you count (init.pp or local.yaml) 13/57 or 6/50 roles left * tried to get hiro more familiar with puppet as part of the hiera migration * [deployed][] and [documented][] a better way to deploy user services for the bridgesdb people using `systemd --user` and `loginctl --enable-linger` instead of starting from `cron` [documented]: https://help.torproject.org/tsa/doc/services/ [deployed]: https://trac.torproject.org/projects/tor/ticket/30472#comment:12 * usual tickets triage, support and security upgrades ## hiro * been helping a bit anarcat with Puppet to understand it better * setup <https://community.torproject.org> from Puppet using that knowledge and weasel's help * busy with the usual website tasks, new website version going live today (!) * researched builds on Jenkins, particularly improved scripts and jobs for Hugo and onionperf documentation * deployed new version of gettor in production * putting together website docs on dip * setup synchronization of TBB packages to with GitlabCI downloading from www.torproject.org/dist/ and pushing to the gitlab and github repositories ## weasel * usual helping out * day-to-day stuff like security things * can't really go forward with any of the upgrades/migrations/testing without new hw. ## ln5 * on vacation half of may * decided, with Sue and Isa, to end the contract early which should free up resources for our projects ## qbi * mostly trac tickets (remove attachments, adding people, etc.) * list maintainership - one new list was created # What we're up to next ## anarcat * expense survey across the teams to do a project-wide infrastructure budget/planning and long term plan * finish the hiera migration * need to get more familiar with backups, test restore of different components to see how they behave, to not have to relearn how to use bacula in an emergency * talk with Software Heritage, OSL, and IA to see if they can help us with archive.tpo, as i don't see us getting short-term "throw hardware at the problem" fix for this ## weasel * somewhat busy again in June, at least a week away with limited access * work on Ganeti/KVM clustering when we get the money ## ln5 * Stockholm meeting prepatations * Tor project development, unrelated to TPA ## hiro * planning to get more involved with puppet * more gettor tasks to finish and websites as usual * finish the websites documentation in time for mandatory Lektor training at the dev-meeting so that it's easy enough for people to send PR via their preferred git provider, which includes for example people responsible for the newsletter as lektor also have a Mac app! ## qbi * react on new tickets or try to close some older tickets * happy to do bite-sized tasks (<30min) # Cymru followup? Point skipped, no new movement. # New mail service requests We discussed the [request to run an outbound mailserver][] for TPO users. Some people have trouble getting their email accepted at third party servers (in particular google) using their @torproject.org email address. However, specific problems have not been adequately documented yet. [request to run an outbound mailserver]: https://bugs.torproject.org/30608 While some people felt the request was reasonable, there were concerns that providing a new email service will introduce a new set of (hidden and not-so-hidden) issues, for instance possible abuse when people lose their password. Some also expressed the principle that e-mail is built with federation in mind, so we should not have to run a mail-server as people should be able to just use their own (provider's) mailserver to send mail, even if Google, Microsoft, and those who nowadays try to own the e-mail market, would like to disagree. Even if users don't have a reasonable outgoing mailserver to use, maybe it need not be TPA who provide this service. It was proposed that the service would be better handled by some trustworthy 3rd party, and TPO users may, but need not, use it. We all agree that people need their emails to work. For now, we should try to properly document concrete failures. Anarcat will gently push back on the ticket to request more concrete examples One way to frame this is whether TPI wants to provide email services or not, and if so, if that should be done internally or not. Anarcat will bring this up at the next Vegas meeting. # Stockholm meeting planning By july, anarcat should have produced an overview of our project-wide expenses to get a global view of our infrastructure needs. The idea would then be to do some real-time, in-person planning during the Tor meeting in July and make some longer-term plans. Questions like email hosting, GitLab vs Trac, Nextcloud, how many servers we want or need, etc. It was proposed we do like in Brussels, where we had a full day focused on the TPA team. We still have to figure out if we have the space for that, which anarcat will followup on. There's a possibility of hosting at Sunet's offices, but the 10 minutes walk would make this a little impractical. It's likely we'll be able to find space, fortunately, and we'll try to figure this out this week. # Other discussions No other discussion was brought up. # Next meeting Next meeting will be held on monday july 1st, same hour (1400UTC, 1000 east coast, 1600 europe). Meeting agrees minutes will be sent without approval from now on. -- Antoine Beaupré torproject.org system administration

1 0