June 2019 - tor-project - lists.torproject.org

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

10 Jun '19

Hello! Our weekly Tor Browser meeting just ended. The IRC log can be found at http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-10-17.31.l… and the contents from our pad are: Discussion: - Reminder: The monthly Tor/Mozilla meeting is tomorrow at 8 AM Pacific Time / 11 AM Eastern Time mcs and brade: Last week: - Worked on #30000 (Integrating client-side authorization to onion services v3). - Continued to work on the Onion Services client auth prompt (#30237). - Helped with bug triage: - #30565 (Corrupted Linux 64bit browser). - #30718 (Tor is inconsistent on virtual disk drives) - #30732 ("Your Firefox is critically out of date" banner). - Thought about how to test the fix for #18101 on macOS (IP leak from Windows/macOS UI dialog with URI). This week: - Review for #18101 (IP leak from Windows/macOS UI dialog with URI). - at the same time, test Snowflake on macOS 10.9.x. - 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). sysrqb: Last week: Rebasing mobile/ commits onto FF68 branch Some BridgeDB reviews Updated only-private-tabs on Android (#24920) Filed "Begin bootstrapping immediately after success" (#30756) Stumbled over "search.disconnect.me don't work for a long time now" during rebase (#27437) Some alpha release prep This week: Understand why the new alpha release is rejected by Google Play and resolve it. (GeKo: We'll block the mobile part of the release but proceed with the other platforms) Alpha release More rebasing and begin testing FF68 branch Fastlane (#26844) F-Droid (#27539) Bug fixing boklm: Last week: - helped with publishing 8.5.1 - helped with building 9.0a2 - made patch for #30779 (OpenSSL 1.1.1c is not built reproducibly) - worked on #28672 (Android reproducible build of Snowflake): finally managed to build some snowflakeclient.aar file. I still need to clean-up patches, and find where the snowflakeclient.aar file should be put. This week: - help with publishing 9.0a2 - 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 acat: Last week: - Rebased onion security expectation patch to ESR68 (#30429). - Found out some things preventing tbb-tests/mochitests from being run in ESR68 branch. - Some torbutton refactor work. - Pushed patch to https://bugzilla.mozilla.org/show_bug.cgi?id=467035, but changes will be needed. - Built rebased ESR68 with GeKo's linux_esr68_v6 tor-browser-build branch. Next week: - More #30429 work (patches remaining, find out why themes extensions are not installed...) - Fix patch for 467035. - torbutton cleanup/refactor/integration work (#28745, #10760) pospeselr: Last week: - fixed macos icons for #30631 (blurry tor browser icons in macOS chrome) - finished rebasing widl changes into a digestable patch chain, submitted to wine-devel dev list for review - squashed widl changes into a patch for mingw and put up a patch for tor-browser-build - changes cause crash on 64-bit windows (both 64-bit tor browser and 32-bit tor browser runing WoW which is surprising) - got my functional ia2 test working on 64 bit windows - initial investigation here indicates likely another typeformat string issue (the generated code that's used to determine data marshalling logic at runtime) This week: - replicate my debug environment in 64-bit and fix this 64 bit issue - update tor-browser-build patch tjr (very little) - Planning for Whistler - Confirmed we still have an x86 crash in mingw-clang (Bug 1547519) after glandium's work. This is high-concern, going to follow up with him GeKo Last week - helped with releases - reviews (#30779, started with #27503, #30631, #24920) - looked at #10760 and started with reviews for for the rebase work - finally figured out why rust barfed during esr68 build (still need to update #30321 with that fun bug) - going over blog comments and filed tickets where needed - HackerOne bugs - started to plan work for June This week - finish review of #10760 and #30429 - figure out 32bit Linux build issues for esr68 branch (part of #30321) - help with releases where needed - Whistler prep - planning work for remaining June Georg

1 0

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

10 Jun '19

Hi! You can find our meeting logs at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-10-17.00.html Here are the contents of our meeting pad for this meeting: = Network team meeting pad! = This week's team meeting is at Monday 10 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 10 June at 1700 UTC * Monday 17 June at 1700 UTC * Monday 24 June at 1700 UTC July schedule: * Wednesday 3 or Thursday 4 July 2300 UTC ? * Monday 8 July at 1700 UTC * (In-person meeting 12-14 July) * Monday 22 July 1700 UTC * Monday 29 July 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.) 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 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.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… 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. ------------------------------- ---- 10 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. Please add your resources: 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) [INFRA] Do you have problems with email? Please report any problem (or not) that you may have here: https://trac.torproject.org/projects/tor/ticket/30608 (also https://help.torproject.org/tsa/doc/reporting-email-problems/) [PROCESS] Please comment on CI role's proposal from Teor: https://trac.torproject.org/projects/tor/ticket/30759 The master branch is now 0.4.2.x. 0.4.1.x development continues on maint-0.4.1 and release-0.4.1. 0.3.4.x is now end-of-life. == 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 Rotation updates: (CI/coverity teor->ahf; bug triage mikeperry->nickm) See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… . 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 wrote patches to: allow failures for stem, and disable test_rebind on Travis macOS using an env var Appveyor (seems ok) Bug triage Can we move the patch party and first team meeting of the month to Wednesday or Thursday 2300 UTC ? (ahf: +1 for Thursday, I already have the anti-censorship team meeting there, so I keep that night off in the calendar, also OK with Wednesday.) [catalyst: Wednesday 2300 UTC works better for me; i have a periodic conflict with Thursdays at 2300 UTC] teor would like to have their Wednesdays off (UTC+10). nickm has no objection to any particular 2300 UTC except Friday. * https://pad.riseup.net/p/54diULYSxeRrckkdKdOQ -- Nickm asks if we should send this to the relevant dirauth operators. It is a list of Tor versions that we should un-recommend. == 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): . check sponsor V work until now . stockholm meeting planning This week (planned): . more stockholm meeting planning . scalability meetings Help with: . moving sponsor 19 tickets (https://pad.riseup.net/p/x3G09tvOfODGflMcjW83 ) . please add sessions to the stockhom meeting pad this week as it may be harder to fit in things later teor: (offline at the usual meeting time) Week of 3 June (planned): Urgent: - 041-must - Quick CI fixes, disable failing tests and document them - code reviews - Help close Sponsor V - Help close Sponsor 19 - 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) Week of 3 June (actual): - It is flu season, looks like it got me, took some time off Urgent: - HR stuff - Decided to defer PrivCount until we have specific funding. (It was Sponsor V, but we ran out of time.) - Quick CI fixes, disable failing tests and document them - code reviews: chutney, docs, etc. - Help close Sponsor V - some progress on Fallback directory mirror list rebuild Important: - sbws triage: - it is probably safe to deploy sbws to one more authority (we now have 2, we can have 3) - identified 4 blockers for deploying sbws to more than 3 authorities - worked on deployment and comparison plan - reject bridge descriptors on authorities (#16564, Sponsor 30) - also did some refactoring to make practracker happy, but now the file is bigger - found and fixed #30782, to make authorities cache fetched outdated descriptors - did some backport triage - tor bootstrap sometimes hangs (#21969, #16844), it's complicated, looks like we need a proposal (#30817) - merged chutney merge_ready tickets - re-did chutney #30279 and #30820 because they didn't work Deferred: - stem CI logging fixes, because the control messages are not in the log (or stem hangs before logging them) Week of 10 June (planned): Urgent: - Fallback directory mirror list rebuild (#28793) - Get gus access to the fallback-scripts repository - Help close Sponsor 19? - code reviews - More HR stuff Important: - work out which roadmapped work to do next: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - off-by-default module practices (#29224) - remove unneeded dependencies for tor roles: client, relay, etc. (#29227) - merge add chutney to tor's CI (blocked on stable Tor CI) - backport backlog (blocked on stable Tor CI) - work on stem CI hangs? - revise reject bridge descriptors on authorities (#16564) - improve documentation for chutney warnings in make test-network-all (#30455) Low-Priority: - document disabled CI (#30745) - revise tor_addr_port_lookup() is overly permissive (#30721) Week of 10 June (actual): Urgent: - Important: - Low-Priority: - Nick: 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. Week of 3 June (actual): - Finished most 041-should items - Opened tickets and did followup from retrospective - Worked on analysis for walking onions paper - Released 0.4.1.2-alpha - Worked on handle refactoring (29218) - Other review and merges Week of 10 June (planned): - Open 0.4.2. - Deprecate 0.3.4. - More analysis for walking onions, time permitting - Review and merge - Revise chutney/CI improvements: - 29280 (Use Chutney in Tor's CI) - 29024 (chutney and PTs) - 30459 (Let chutney tell Tor whether a network is supported) - Finish handle refactoring and cleanup (29218) - Plan configuration refactoring - More modularization? Mike: Week of 6/03 (planned): - More scalability followup (KIST+EWMA+sbws -> wiki; metrics updates; Mozilla all hands meeting planning) - Peer feedback - Register for PETs - #30649 - Circpad documentation? Week of 6/03 (actual): - Laptop issues - More scalability followup (KIST+EWMA thread; funding meeting; metrics categories) - work on circpad relay-side warn log bug (https://trac.torproject.org/projects/tor/ticket/30649) - Work on #29034 (hs circuit re-purpose leaks) - Code reviews Week of 6/10 (planned): - Mozilla all hands planning/discussion - Scalability metrics review/page reorg - Peer feedback - Register for PETs - Circpad documentation? catalyst: 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 week of 06/03 (2019-W23) (actual): - reviews - medical and financial bureaucracy - tried and failed to find an easily configured SOCKS5 proxy daemon that requires auth (as part of a patch review) - rearranged bootstrap tickets more logically -- unparanted still-open children of #28018, etc. week of 06/10 (2019-W24) (planned): - reviews - some sponsor31 tickets asn: Week of 06/03 (planned): - 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. Week of 06/03 (actual): - Finally managed to get #30381 in needs_review. - Wrote some scaling emails. - Worked on #30578 (041-must). - Did some work on HS DoS: https://lists.torproject.org/pipermail/tor-dev/2019-June/013873.html - Cleaned most of my review backlog, but there is still more. - Merged prop304 to torpec. Week of 06/10 (planned): - #30381 is now in needs_revision. Need to do that. - More prepping for AllHands. Flying out on Sunday. - Try to do some work on s27 #26294 (intro point rotation dos) - Still got reviews hanging. In particular #30382. - I also got lots of hanging merges... Help needed: - teor, I still have troubles mapping all the pieces of #22029 in my brain. Perhaps at some point you can take over the review of that ticket, and I can take one big review from you? I don't see you having any big reviews this week, so perhaps we can wait until next week. ahf 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. Week of 3/6 (actually): Network team: - Hacked on #28930. Misc: - End of month tasks: Harvest, etc. - Did a talk about Tor at a conference. They seemed excited. Week of 10/6 (planned): Network team: - Finish #28930. - Talk with traffic-obfuscation list people about #28849 - Talk to Cecylia and DCF about patches for #29736 and friends. Misc: - Presentation Thursday evening at the local union about Tor. - CI/Coverity role. 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 06/03 (actual): - Call with asn on #15516 next steps. - Unit testing on #30382 - tor-scaling discussions. - Some urgent work on #30771 and #30775 041-alpha2 release blocker. - Review s27 tickets: #30381 - Started sketching some ideas for #30790 - Got my brain smashed by #30628 issue. Fortunately, fixed now! - Emailed a big HS operator for some introduction stats in order to learn more to make a better choice on #15516 parameters. - prop304 is in tor-spec.txt! :) - Some merges and reviews. Week of 06/10 (planned); - Continuing s27 work on the anti-DoS side. - Add consensus params for #15516 and hopefully propose baseline values. - Hope to get #30790 in a Draft state. - 042 window is opened so some merges need to happen in master.

1 0

May 2019 report for the UX team
by Antonela Debiasi 07 Jun '19

07 Jun '19

Hello Tor o/ #S27 During May, we continued working on S27. After the official kick-off last month, we've worked on the two new Tor Browser features we want to achieve for this sprint: onion-auth and onion prioritization. You can follow our work on the relevant tickets: https://trac.torproject.org/projects/tor/ticket/30024 https://trac.torproject.org/projects/tor/ticket/30237 #User Research dunqan has been working for a few months now to consolidate our first Tor users Persona tool. We are planning to have a session during the next dev meeting to introduce this tool to the teams and collect feedback for the next iteration. https://lists.torproject.org/pipermail/ux/2019-May/000449.html #Community Portal The community portal is taking shape. We are still writing and reviewing content, fixing UI bugs, and polish the mobile view. You can sneak peek our progress here https://community.torproject.org/ Clash gave us support on the various front last month. The most relevant was the help in updating our training material for the community portal. Thanks, Clash! #Tor Browser 8.5 The last week of May, Tor Browser 8.5 was released. It included the new UI for security settings, the new app icon, and four new locales: cs, el, hu, ka. This release also made available a stable version for Tor Browser in Android. There is a lot of work to do yet, but we are proud to offer this efficient way to connect to the Tor network for mobile Android users. https://blog.torproject.org/new-release-tor-browser-85 #OONI After the OONI Explorer Beta release, we have been working on prioritizing the features we want to get done for the stable version and supporting the design needs. Thanks, A

1 0

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