May 2020 - tor-project - lists.torproject.org

NYC HOPE to nine days
by George 19 May '20

19 May '20

FYI: > > > Greetings, > > While we all want things to go back to normal, the science just doesn't > make that possible. July and August may still seem far away, but there > simply is no way the COVID-19 crisis will be over by then, even in the > best-case scenario. We had planned on waiting until June to make a final > decision, but it's become clear that planning an in-person conference > simply wouldn't be the responsible thing to do. Nothing matters more than > the health and safety of our attendees. Yes, this will be a financial > kick in the teeth for us. But it's one we'll willingly take as the mere > possibility of putting any of you at risk is unconscionable. > > We want to be clear on one important point. Apart from the obvious > disappointment of not being able to host this historic event at a new > venue we were so looking forward to, we want everyone to come out of this > not feeling dissatisfaction beyond that. More on that later. > > This is what we're now looking at: > > We are NOT canceling HOPE. Instead, we are changing what this year's HOPE > will be. > > HOPE 2020 will now be a NINE DAY EVENT, beginning on Saturday, July 25th > and running until Sunday, August 2nd, 2020. Why did we add an entire week? > Because we want some good to come out of this and we believe our community > is in a position to do just that. We all know what we WON'T have without a > physical conference, but let's now focus on what we CAN have with some > imagination and collaboration. That's what the hacker community is all about. > > We intend to have around the same number of talks as we normally do, but > spread out over a much longer period and available for viewing on a high > capacity stream. Those of you who bought tickets will have exclusive access > to the presenters so you can ask questions, participate in workshops, and > interact with other conference attendees. In addition, you will also > receive a conference t-shirt and badge that won't ever be made available to > anyone else. > > We plan on having NINE keynote speakers, again with exclusive Q&A access > for our attendees. > > Participation in HOPE will no longer be bound by visas and worries of arrest > by certain controversial types. So expect a dynamic and varied cast of > characters. It wouldn't be HOPE without that, but now we can REALLY remove > some barriers. > > In addition to ongoing talks and panels, we'll also have workshops for the > duration of the nine day event. Expect everything from lockpicking to > soldering instruction to our infamous ham radio exams. > > For the overnight hours, we're planning on having concerts, DJs, and other > fun stuff. HOPE will remain a 24 hour event, but for nine days! > > All of this has been - and will continue to be - a daunting task. The > COVID-19 pandemic has affected all of us in varying ways. The continued > survival of 2600 was quickly put into doubt as our distributors stopped > paying us, bookstores with our issues in them shut down, and new issues > were left in loading zones. We've lost more than half a year's income at > last count and have had to stop getting paid in order to continue to > survive. Making this year's HOPE a success is really the only way we can > come through this. > > As mentioned above, we don't want anyone to feel extra unhappy because of > this. If you want a refund, we will give you one. But with all of the > losses we've already suffered, we won't be able to continue existing if we > have to issue very many of those. That's why we're hoping we can put > together the best event possible and make this the highlight of our summer > despite all that's happened. > > We are in the process of accepting talk and workshop proposals that have > already been submitted. We will be providing technical support so that > presenters will be able to participate smoothly in a virtual environment. > We are now opening up the submission process to include many more > participants from all around the globe, something we never really had the > ability to do before. We hope to have talks, workshops, and musical > presentations from a truly international community, no longer bound by a > physical presence. > > While we have a dedicated team of volunteers already working on making this > happen, we can definitely use many more, especially as the event draws > closer and becomes bigger. Email volunteers(a)hope.net and let us know how > you think you can help. We're looking for people with experience setting up > and producing live online broadcasts. We are also looking for emcees, > moderators for online forums, and people to fulfill other behind-the-scenes > roles. > > If we get through all of this, we fully intend to hold a physical HOPE in > 2021 (the first odd-year HOPE since 1997). This will also enable us to > continue publishing once bookstores start opening again. All of this depends > on our hacker spirit getting us through the toughest times we ever could > have imagined. And if you share our enthusiasm over what this new incarnation > of HOPE will mean, this summer will indeed be one to look forward to. > > Stay safe. > > The HOPE Staff > _______________________________________________ > hope-announce mailing list -- hope-announce(a)lists.2600.com > To unsubscribe send an email to hope-announce-leave(a)lists.2600.com >

1 0

May 18th Meeting Notes for SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements
by Gaba 18 May '20

18 May '20

Hi! We are meeting every Monday at 18UTC via voice in a BBB room to coordinate the work related to Sponsor 58, where we are completing the migration of Tor Browser for Android from Fennec to Fenix. You can read more about it at Parent ticket: https://trac.torproject.org/projects/tor/ticket/33664 Wiki page: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 If you want to participate in this meetings please send us a message about how to join. The pad we are using is: https://pad.riseup.net/p/_kbebKhZvNcUuqxQL5NV And here are the pad's notes: NEXT MEETING: MAY 25TH AT 18UTC IN BBB Reminder: please own a ticket when you start working on it. Agenda Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… (any block from last week review, reviews not assigned yet) -> #27105 and #30832 not ready yet but geko will start reviewing it. -> #33932 and #34013 will be taken by ahf. Look at what people need help with. Status updates: GeKo: Last week: - finished all of the toolchain migration for projects already in tor-browser-build and addressed first review comments) (#34187, #33626, #33973, #33564, #33561, #33563, #33558, #33559) - made progress on review of acat's rebase work (#33533) - looked a bit over dependencies we want to keep/rip out (#33939) This week: - wire up geckoview into fenix - update android-components build patch and wire custom one into fenix as well - finish review of acat's rebase work (#33533) Blocked on decision for #33939 acat: Last week: - #30832: Fix tor-browser tbb-tests - Tested fix for https://github.com/EFForg/https-everywhere/issues/19102 - Revised and landed dns leak uplift followup https://bugzilla.mozilla.org/show_bug.cgi?id=1636411 - #34196: Update site info URL with the onion name - Reviews: Bug 34206: Tor Launcher button labels are missing (Firefox 76) Bug 34209: about:tor and about:tbupdate fail to load in debug build of Tor Browser Bug 34164: Tor Launcher hangs with 33533+5 branch Not blocked This week: - Fix intermittent test failure for https://bugzilla.mozilla.org/show_bug.cgi?id=1636411. - Try to run some tor-browser tests in try. - #30832 followup (tbb-testsuite). Alex: Week of 11/05 actually: - DNS proposal and changes being discussed on tor-dev(a)lists.torproject.org. - Sent revised patches for TROVE-2020-001 with Taylor's suggestions included. - Got OnionBrowser to build and reproduced the iOS Tor 0.4.2+ issue. - Done with emails from April. - Review of various patches for tor.git. - Managed to reproducibly compile GeKo's geckoview patches on two devices. - Code review of GeKo's geckoview patches to Tor Browser (#33626, #33973, #33113). Not blocked on anything. Week of 18/05 planned: - Write documentation for `Onion-Location:` for nginx. - Continue to work with the browser folks. - Hopefully nail down the iOS bug. - Thursday and/or Friday is a public holiday here in DK that I might make use of. Mike: Last week - 5/11: - Got TBB building in Ubuntu 'multipass' vms (https://multipass.run/) Is pretty straight-forward - Congestion control, FlashFlow proposal, TorFlow #33871 help, org discussion email - Got diffs of gecko-dev for proxy audit Blocking: - This week - 5/18: - gecko-dev proxy audit sysrqb: Last week - 11 May: Mostly reviewed patches and preparation for 9.5a13 Began #33939 This week: Finish #33939 Release prep for 9.5a13 and reviewing #31918 MAY 11TH Reminder: - please own a ticket when you start working on it. Agenda - Tickets for AHF - 33973 and 33626 - O2.2 with geko - Review ux-team tickets and set timelines -> #33658 is the first issue to solve in June https://trac.torproject.org/projects/tor/query?cc=~&keywords=~ux-team&spons… - Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… only #30832 needs a review - #33534 is still owned by pospeselr Status Updates: Name: What did you do last week? Anything anybody is block on? What is the plan for this week? Alex: Last week: - Got Fenix compiled on desktop and laptop with Android dev environment. - Moved the build to remote build host. - Started looking at the TB tickets we apply on top of Firefox. - Not blocked on anything, but I am interested in which tickets we should allocate to me. This week: - Look into the build-system patches from GeKo. Test and review. sysrqb: Last week: Tor Browser releases (Some) S58 ticket triage Make progress on setting up replacement Nightly build machine Blocked: No. This week: #33939 - Decide which components of Fenix to rip out, disable, or use Catch up on status of tickets GeKo: Last week: - worked on lots of toolchain tickets and put a bunch of them into review (#33557, #33561, #33626, #33760, #33833, #33973, #34011, #34012, #34013, #34014, testing currently #33801 and figuring out issues in #33563) - I started to look at writing the script for toolchain changes (#34108) - I started to look into #33939 to unblock me but I can't make a decision here alone - I looked into glueing mozilla-beta into fenix/android-components - I looked into fallout from rebasing to mozilla-beta (#34145) and worked around it - review of acat's rebased patches (#33533) Blocked: - Still on a decision for #33939 This week: - finishing #33801 and #33563 - trying to finish review of acat's rebased patches (#33533) - glueing the different components together - setting up missing projects in tor-browser-build (likely android-components) at least acat: Last week: #31918: Rebase and squash mobile and desktop patches #33533: Rebase Tor Browser patches to 77 beta #34125: Fix torbutton proxy api due to change in Firefox 77. #33962: Uplift patch for 5741 (dns leak protection) Started working on #27105: Fix Tor Browser testsuite Blocked: Not blocked, but not sure whether working on #27105 (Fix Tor Browser testsuite) is the right priority, or I should switch to something else. Next week: #27105: Fix Tor Browser testsuite -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network meeting notes, 18 May 2020
by Gaba 18 May '20

18 May '20

Hi! Network Meetings are happening every Monday at 17UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 18th: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-18-17.00.html Pad for 2020: https://pad.riseup.net/p/tor-netteam-2020.1-keep And here is the pad notes for today: == Network meeting pad! == Next team meeting is at Monday 25 May 1700 UTC on #tor-meeting on OFTC. May Schedule: * Monday 11 May 17:00 UTC * Monday 18 May 17:00 UTC * Monday 25 May 17:00 UTC Welcome to our meeting! We meet each month at: Mondays at 1700 UTC 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 tor-project mailing list archive for older notes.) 23 March: https://lists.torproject.org/pipermail/tor-project/2020-April/002804.html 1 April - 4 May: we skipped meetings while transitioning TPI == Stuff to do every week == Let's check and update our roadmap: What's done, and what's coming up? Any change? All the trac tickets for the roadmap are in the team's page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam S27 - Asn & Dgoulet - ends at the end of May S28 & S30 - Continue after October - Ahf S55 - Nickm S69 - Nickm - ends at the end of May Non sponsor stuff DoS defenses = Dgoulet + Asn Library Size reduction = Ahf + Dgoulet sbws = Ahf + Juga 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… Go over our 0.4.3 status page at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… . (If maint-0.4.3 were released as stable tomorrow, what would we regret?) == 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. * Check other's people call for help in their entries. Volunteers need help. Please help them when you are around. Maybe we should have times of day when different people are responders, and expectations of who helps. ------------------------------- ---- 18 May 2020 ------------------------------- == Announcements [please date] == == Discussion [please date] == [18 May] pastly asks: Current plan is that FlashFlow will consist of a program that controls tor clients via the Control Port. Like Simple Bandwidth Scanner and Torflow. Would writing this code in Rust make it non-transitionable? Does the network team know enough Rust? The other idea is Python 3. Is that way better? [resolution: rust isn't a blocker. maybe using stem would be a compelling reason to use python though. the best choice would be to do whatever you think can deliver the better code: "maintainable well-factored rust is much better than undocumented spaghetti python, and vice versa :)" [18 May] nickm asks: anybody able to help with 0.4.4 triage? We need to identify what we're doing between now and the freeze on 15 June. === Active Proposed Policies === * Pull Request Guidelines (stalled) === Design proposals under discussion === 315: require more fields in directory documents (?? [5/18]) 316: flashflow (asn and nickm are reviewing, should schedule discussion with pastly. [5/18]) 317: dns (under discussion on ML [5/18]) 318: limit protovers (nick needs to reply on ML [5/18]) 319: wide everything (nick needs to reply on ML [5/18]) 320: tap out again (nick needs to reply on ML [5/18]) protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18]) == Recommended links == == Updates == 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! Nick: Week of 11 May (planned): - Re-review PETS artifacts - Final S55 handover: - Make sure I can repro and experiment with Teor's work on ipv6 probing - 33898 (real_addr) - - merge and review - answer a ton of pending email. - catch up with proposal review - Finalize a bunch of walking onions sub-proposals - get an official location/repo for walking onions proposal. - identify most critical missing pieces of w.o. proposal, and pick them up. Can anybody pick up: - 33850 (log fd issue) Week of 11 May (actual): - merge and review - lots of pending email catch-up - walking onions sub-proposals - walking onions: more family analysis - lots of reading up on S55 stuff - network team idea for next steps - Release 0.4.3.5 as stable! - (much persnoal disorganizatioon) * * this was originally a typo, but I think it gives a fair picture of my mental state (same space here..) Week of 18 May (planned): - 0.4.4 triage - walking onions: try to finish. - s55: review and merge, identify steps to make wip-stuff mergeable. - review and merge in general - keep an eye on blog comments - Reply to prop316 - reply to email about protovers ahf: Week of 4/5 (actual) - Review of some GCC warnings. - Wrapping my head around Browser build-system and Mozilla Fenix. - Mac upgrade to help TGP and to debug iOS/Mac issues. - Got through the emails that was skipped in April. Week of 11/05 planned: - Continue to work with the browser team. - Wrap my head around DNS patches. - Execute next steps on TROVE-2020-001. Week of 11/05 actually: - DNS proposal and changes being discussed on tor-dev(a)lists.torproject.org. - Sent revised patches for TROVE-2020-001 with Taylor's suggestions included. - Got OnionBrowser to build and reproduced the iOS Tor 0.4.2+ issue. - Done with emails from April. - Review of various patches for tor.git. - Managed to reproducibly compile GeKo's geckoview patches on two devices. - Code review of GeKo's geckoview patches to Tor Browser (#33626, #33973, #33113). Week of 18/05 planned: - Write documentation for `Onion-Location:` for nginx. - Continue to work with the browser folks. - Hopefully nail down the iOS bug. - Thursday and/or Friday is a public holiday here in DK that I might make use of. (please take it) asn: Week of 11/05 (planned): - Work on PoW funding proposal - Email backlog Week of 04/05 (actual): - PoW proposal done. - Start reviewing flashflow proposal. - More onion services stuff - Did OTF learning lab meeting - Did HTTPS-E meeting. Week of 18/05 (planned): - Still more reviewing flashflow. - Still more emails. - Still more reviews. - Still more PoW. jnewsome: Week of May 4 (actual): - Some LD_PRELOAD behavior investigation to guide shadow-Phantom design decisions - Added more tests covering next-to-be-implemented shadow-Phantom syscalls - Mentored/reviewed a volunteer PR - Kickoff OnionPerf meeting Week of May 11 (planned): - Start digging into OnionPerf - Start familiarizing myself with Shadow *usage* for Tor simulations - tor-project@ Shadow update email Week of May 11 (actual): - Worked on improving Shadow logging framework - Helped volunteer get their PR to improve tests into mergeable shape and merged - Started poking at OnionPerf Week of May 18 (planned): - tor-project@ shadow update email - finish logging improvement PR - More digging into OnionPerf. #33974: update to tgen 1.0 \o/ pastly: Week of 18 May (planned): - Finish bones of external FlashFlow repo (python?) to control tor clients that perform FF measurements - Finish bones of little-t tor changes s.t. measurement can be performed - Discuss FlashFlow with network team devs as they have questions -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Metrics meeting notes, 14 May 2020
by Gaba 14 May '20

14 May '20

Hi! Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 14th: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-14-15.01.html And here is the pad notes: ----------------------------------------------------- Agenda Thursday, May 14th, 15 UTC ----------------------------------------------------- Stop generating .tpf files (#34141) Add CSV file export of graphed data (#33258) Record download times of smaller file sizes from partial completion times (#26673) Reminder: We are tracking Onionperf work at https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59 cheers, gaba -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Anti-censorship meeting notes, 14 May 2020
by Philipp Winter 14 May '20

14 May '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-14-16.00.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 14th 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #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 == * Our anti-censorship roadmap: https://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * Next planning session: last week of April * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep ------------------------- --- May 14th 2020 -- ------------------------- == Announcements == * Set up monit instance on phw's personal VPS. It's now sending outage alerts to anti-censorship-alerts(a)lists.tp.o * Monitoring targets available at: https://gitlab.torproject.org/torproject/anti-censorship/monit-configuration * We recently got a batch of censorship measurements from our friends at ICLab. Anyone interested in analysing it? Phw tool a brief look and has some Python code to get started. == Discussion == * Roger's mail about the overlap between BridgeDB and GetTor and how maybe they should merge https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000097… * Run a call for testing for Snowflake * before or after the stable release? before: we want to ramp up users so we know we can handle a stable release * use cases? * we want to involve/share with orgas in global south. There is not strict censorship in Colombia nor Chile, but snowflake can help users who don't want to disclose the fact that they are using Tor to their ISP. So may work. * Do we want users to do specific tasks like visiting a website or watching a video? Do we want users to use snowflake for a period of time and report back with feedback? What is more useful? * Are we looking for breakage? are we looking for perceived performance? * lists? * tor-qa * tor-ux * tor-project but with **bolds** on advertising that is an alpha version * S30 UX work this week == Actions == * == Interesting links == * https://github.com/greatfire/envoy * The GreatFire folks developed a library that helps make Android apps resistant to censorship. * From what I understand from looking at the sample patches, it provides easy-to-use hooks to do domain fronting and HTTP proxying, generalizing their project FreeBrowser. == Reading group == * We will discuss "Salmon: Robust Proxy Distribution for Censorship Circumvention" on May 14 * https://censorbib.nymity.ch/#Douglas2016a * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? Roger's notes for Salmon design questions: https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000100… == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-05-14): * Set up monit on my VPS and configured it to send outage alerts to our list. * https://gitlab.torproject.org/torproject/anti-censorship/monit-configuration * Tests everything except BridgeDB's and GetTor's autoresponders. * Some interaction with OONI to move forward with BridgeDB feedback loop. * Syncing MetaDB is too involved; will download raw measurements from S3. * Reviewed onionperf Python 3 port. * Sponsor 30 roadmap maintenance. * Reviewed #33835. * Filed #34154 to extend BridgeDB's BlockedBridges SQLite table. * Attended DARPA PI meeting (RACE) remotely. * Deployed #33945 test branch on BridgeDB. No sirens so far. * Quite a bit of progress with wolpertinger. * API end point live at https://bridges.torproject.org/wolpertinger/fetch * Summarised future plans with BridgeDB and posted them to anti-censorship team list. * Updated our docker bridge setup guide after a user in #tor pointed out an issue. Next week: * Help with: * Let me know your smart thoughts on BridgeDB's future: * https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000096… * #34212 Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective cecylia (cohosh): last updated 2020-05-14 Last week: - GSoC things - work on broker documentation (#34198), snowbox, snowflake READMEs - read dcf's plans for multiplexing (#25723) - started on using STUN servers for NAT type discovery (#34129) - writing up a funding proposal for GetTor - so many sponsor 28 meetings (all day Monday, Tuesday, part of Wednesday) - created ticket to make new snowflake repo for Hashik's GSoC work (#34222) This week: - Continue work on STUN servers (#34129 and #25591) - More work on reviving the twitter responder in GetTor (#33036, #27330) - look at old GetTor mirrors (#33893) - investigate #33669 - Follow up on discussions of debian obfs4proxy package - translations? Needs help with: - review of GetTor twitter fixes (#27330) - creation of snowflake repo (#34222) from git-admin juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-05-07 Last week: - webext repo versioning / publishing #34140, #34126, #34132, #34127 Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-05-14 Last week: - reviewed fix for Chrome proxy hang (#31278) Next week: - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: agix:2020-05-14 Last week: - Started work on #27984 Next week: - Submit a fix for #27984 Help with: - Review of #31528 catalyst: 2020-04-16 last week: - more work on #5304 (PT outbound bind address) - started looking at #29128 (assemble bridge line) this week: - more background research and work on s28/s30 tickets thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with:

1 0

Tails report for April 2020
by sajolida 12 May '20

12 May '20

Releases ======== * Tails 4.5 was released on April 7: https://tails.boum.org/news/version_4.5 * Tails 4.6 was released on May 5: https://tails.boum.org/news/version_4.6 * Tails 4.7 is scheduled for June 2. The following changes were introduced in Tails 4.5: - Tails now starts on computers with Secure Boot enabled. - Update *Tor Browser* to 9.0.9. This update fixes several vulnerabilities in *Firefox*, including some critical ones. Documentation and website ========================= Installation instructions ------------------------- - Updated our installation instructions to the support of Secure Boot: * On PC: https://tails.boum.org/install/win/usb#start-tails * On Mac: https://tails.boum.org/install/mac/usb#start-tails * When adding boot options: https://tails.boum.org/doc/advanced_topics/boot_options - Added a link to try downloading from another mirror in case the download fails. (#15754) Click on Download USB image and the link below it changes. https://tails.boum.org/install/download - Fixed a buggy content reuse on the cloning instructions for PC and Mac. (#17502) https://tails.boum.org/install/clone https://tails.boum.org/install/mac/clone - Added shortcuts to download for DVDs and virtual machines from install. (#17609) https://tails.boum.org/install/dvd-download https://tails.boum.org/install/vm-download - Added a **Skip download** link on the download only pages. (#17549) https://tails.boum.org/install/download Terminology ----------- - Implemented the terminology *Persistent Storage* consistently in all our documentation. (#8948) https://tails.boum.org/contribute/how/documentation/style_guide#persistent-… https://tails.boum.org/doc/first_steps/persistence - Renamed *Tails Greeter* into *Welcome Screen*. (#15122) https://tails.boum.org/doc/first_steps/welcome_screen Known issues ------------ - Documented that importing OpenPGP public keys using the *Passwords and Keys* utility is broken since Tails 4.0 (October 2019). (#17183) https://tails.boum.org/doc/encryption_and_privacy/gpgapplet/#import - Documented that opening *VeraCrypt* volumes fails if the passphrase is more than 64 characters long. (#17474) https://tails.boum.org/doc/encryption_and_privacy/veracrypt#parameters - Removed warnings about *Electrum* not working in Tails (#17581) User experience =============== - Andrés Fernández Cordón finished the illustrations for the new Home and About pages. https://anhdr.es/ https://tails.boum.org/about/staging/home https://tails.boum.org/about/staging/about sajolida finished writing and testing the written content and most of the responsive web design. - Changed our sidebar to a top bar. (#15112) It has a better contrast for accessibility, prevents right-rail blindess, and is more visible on mobile. Funding ======= - Sent 2 grant applications: * To the OTF Core Infrastructure Fund to improve the user experience of connecting to Tor and using Tails to circumvent censorship. https://tails.boum.org/blueprint/network_connection * To Reset.tech to integrate mobile messaging applications (Signal, Telegram, Wire, Matrix, etc.). - Redesigned our **Donate** button to fit in the top bar, even on mobile. - Added ourselves to a list of non-profits who accept lumens: https://lumenthropy.com/nonprofit-list/ Translations ============ ## All the website - fr: 85% (5541) strings translated, 7% strings fuzzy - es: 49% (3172) strings translated, 7% strings fuzzy - de: 32% (2087) strings translated, 13% strings fuzzy - it: 29% (1878) strings translated, 9% strings fuzzy - fa: 23% (1551) strings translated, 13% strings fuzzy - pt: 22% (1479) strings translated, 9% strings fuzzy ## Core pages of the website - fr: 85% (1577) strings translated, 10% strings fuzzy - es: 83% (1538) strings translated, 10% strings fuzzy - it: 55% (1023) strings translated, 21% strings fuzzy - de: 55% (1012) strings translated, 22% strings fuzzy - pt: 41% (772) strings translated, 17% strings fuzzy - fa: 28% (524) strings translated, 19% strings fuzzy ## Core pages of the website for languages not activated on the website yet - zh_TW: 28% (427) strings translated, 12% strings fuzzy - zh: 14% (225) strings translated, 6% strings fuzzy - ru: 10% (160) strings translated, 5% strings fuzzy - pl: 8% (133) strings translated, 4% strings fuzzy - tr: 8% (133) strings translated, 4% strings fuzzy - ar: 7% (119) strings translated, 5% strings fuzzy - ca: 7% (115) strings translated, 5% strings fuzzy - id: 5% (91) strings translated, 2% strings fuzzy - sr_Latn: 4% (62) strings translated, 1% strings fuzzy Metrics ======= * Tails has been started more than 936 560 times this month. This makes 31 219 boots a day on average. That's 8.7% more than in March and the biggest increase in usage since 2015. It's most likely due to the COVID-19 quarantine and people staying at home but it might also be a good sign from the support of Secure Boot and an easier adoption by new users. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0

New Contributor
by Mruga Shah 11 May '20

11 May '20

Hi All, I am a Computer Science student at Drexel University and have taken up a class that teaches us about Open Source software world. As a part of that class, we have to contribute to an open source project and I was really interested in working with your project team. I am writing this email to get myself introduced to the team and get in touch so as to get an idea of how I can contribute to the project. Thank you, With Regards Mruga Shah

2 1

minutes from the sysadmin meeting
by Antoine Beaupré 11 May '20

11 May '20

# Roll call: who's there and emergencies anarcat and hiro, tons of emergencies: * trac spam (#34175) * ganeti crash (#34185) # Part-time work schedule We're splitting the week in two, so far anarcat takes the beginning and hiro the end, for now. This might vary from one week to the next. The handover, or "change of guard" happens during our weekly mumble meeting, which has been moved to 1400UTC, on Wednesdays. # Roadmap review We reviewed the sysadmin roadmap at: <https://trac.torproject.org/projects/tor/wiki/org/teams/SysadminTeam> Since we're in reduced capacity, the following things were removed from the roadmap: * website migration to lektor (#33115) -- should be handled by the "web team" * solr search (#33106) -- same, although it does need support from the sysadmin team, we don't have enough cycles for this * puppetize nagios (#32901) -- part of the installer automation, not enough time * automate installs (#31239) -- same, but moved to october so we can check in progress then The ganeti cluster work got delayed one month, but we have our spare month to cover for that. We'll let anarcat do the install of fsn-node-06 to get that back on track, but hiro will learn how to setup a new node with (hopefully) fsn-node-07 next. The listera retirement (#33276), moly migration (#29974) and cymru hardware setup (#29397) are similarly postponed, but hopefully to june (although this will likely carry over to october, if ever). # Next meeting Change of guard on 1400UTC wednesday May 20th, no minutes. Formal meetings are switched to the first *wednesday* of the month, at 1400. So the next formal meeting will be on Wenesday June 3rd at 1400UTC. # Metrics of the month * hosts in Puppet: 74, LDAP: 78, Prometheus exporters: 120 * number of apache servers monitored: 30, hits per second: 164 * number of nginx servers: 2, hits per second: 2, hit ratio: 0.88 * number of self-hosted nameservers: 6, mail servers: 10 * pending upgrades: 0, reboots: 33 * average load: 0.55, memory available: 358.27 GiB/949.25 GiB, running processes: 383 * bytes sent: 210.09 MB/s, received: 121.47 MB/s * planned buster upgrades completion date: 2020-08-01 Upgrade prediction graph still lives at https://help.torproject.org/tsa/howto/upgrades/ Now also available as the main Grafana dashboard. Head to <https://grafana.torproject.org/>, change the time period to 30 days, and wait a while for results to render. -- Antoine Beaupré torproject.org system administration

1 0

OONI Monthly Report: April 2020
by Maria Xynou 11 May '20

11 May '20

Hello, Throughout April 2020, the OONI team worked on the following sprints: * Horseshoe Crab Sprint (30th March 2020 - 12th April 2020) * Blue Bottles Sprint (13th April 2020 - 26th April 2020) * Beluga Sprint (27th April 2020 - 3rd May 2020) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Details and highlights are available in this report. ## Public launch of new OONI Probe desktop app We launched a new OONI Probe desktop app for Windows and macOS! You can download and install the new app here: https://ooni.org/install/desktop To announce the launch of the new OONI Probe desktop app and share relevant highlights, we published a blog post: https://ooni.org/post/2020-ooni-probe-desktop-app/ ### Localization Thanks to support from the Localization Lab community, the new OONI Probe desktop app was translated to 14 languages: Chinese, Arabic, Farsi, Russian, Thai, Turkish, Spanish, French, Portuguese, Italian, Greek, Slovak, Catalan, and German. We launched the desktop app with 12 of these languages, excluding Arabic and Farsi, which we will be included in future releases once we have added RTL support. ### Press coverage The launch of the new OONI Probe desktop app received press coverage from Deutsche Welle (DW), who published an article about it: https://www.dw.com/en/ooni-an-app-for-detecting-internet-censorship/a-53224… The DW article was also published in the following languages: * German: https://www.dw.com/de/ooni-eine-app-um-internetzensur-aufzusp%C3%BCren/a-53… * Chinese: https://www.dw.com/zh/ooni%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F-%E8%AE%A9%E4… * Farsi: https://www.dw.com/fa-af/ooni-%D8%A7%D9%BE%D9%84%DB%8C%DA%A9%DB%8C%D8%B4%D9… * Spanish: https://www.dw.com/es/ooni-la-aplicaci%C3%B3n-para-detectar-la-censura-en-i… ## Adding support in OONI Probe for availability testing of the circumvention tools Tor, obfs4proxy, and Psiphon We released OONI Probe Desktop 3.0.0 (the new OONI Probe desktop app for Windows and macOS) which includes support for running the new Tor and the Psiphon circumvention tool tests. Tor test: https://ooni.org/post/2020-ooni-probe-desktop-app/#tor Psiphon test: https://ooni.org/post/2020-ooni-probe-desktop-app/#psiphon ## Analyzing collected censorship circumvention tool test results and integrating them into OONI Explorer and the OONI API Following the release of the new OONI Probe desktop app (which includes the new Tor and Psiphon tests), we started to collect, analyze, and publish OONI Probe measurements from the testing of Tor and Psiphon around the world. These measurements -- which are also available via the OONI API (https://api.ooni.io/) -- can easily be searched and accessed through OONI Explorer: * Tor measurements: https://explorer.ooni.org/search?until=2020-05-12&test_name=tor * Psiphon measurements: https://explorer.ooni.org/search?until=2020-05-12&test_name=psiphon Measurements collected from around the world are published on OONI Explorer in near real-time. ## Improving censorship circumvention tool methodologies to include metrics that are also related to the performance of the tool To improve our methodologies for measuring censorship circumvention tools, we aim to measure the performance of those tools as well. To this end, we: * Added support for running the NDT speed test over Psiphon: https://github.com/ooni/probe-engine/issues/506 * Switched to using the golang implementation of DASH, which will allow us to run this performance test over the Psiphon network: https://github.com/ooni/probe-engine/issues/501 * Made progress in refactoring netx to enable which more performance testing in the testing clients: https://github.com/ooni/probe-engine/issues/543 ## Developing OONI Probe orchestration logic that is specific to circumvention tool testing As part of our work on developing OONI Probe orchestration logic that is specific to circumvention tool testing, we discussed with Tor’s anti-censorship team how we would integrate bridge testing into OONI probe services. See: https://github.com/ooni/backend/issues/396 ## OONI Probe mobile app Some of the main new changes that the next releases of the OONI Probe mobile app will feature include: * New/improved design for the Dashboard * “Run” button (in the Dashboard) to run all OONI Probe tests at once * Grouping the middlebox tests inside the Performance card * Adding a new Circumvention card to release the new Tor & Psiphon tests In preparation for the next releases, we worked on the following tickets: * Implement new dashboard layout: https://github.com/ooni/probe/issues/1094 * Run All Tests button: https://github.com/ooni/probe/issues/826 * Implement Run All Tests button: https://github.com/ooni/probe/issues/1093 * Group the middlebox tests with the performance test group: https://github.com/ooni/probe/issues/835 * Remove notification settings screens: https://github.com/ooni/probe/issues/1090 * Verify network information settings: https://github.com/ooni/probe/issues/1112 * Remove country code in the opt out settings of the app: https://github.com/ooni/probe/issues/1105 * New navbar appearance on iOS: https://github.com/ooni/probe/issues/1108 * Create experimental flavour for the Android app: https://github.com/ooni/probe/issues/1080 * Remove/update obsolete NDT fields: https://github.com/ooni/probe/issues/1107 We also created a beta branch with support for automatic daily testing: https://github.com/ooni/probe/issues/1059 ## Push notifications As part of our ongoing efforts to add support for sending out push notifications, we deployed a production countly instance on Digital Ocean: https://github.com/ooni/backend/issues/379 We also made a developer build of the OONI Probe mobile app which uses countly to receive push notification and try it out: https://github.com/ooni/probe/issues/1101 We also did some testing of the countly backend to ensure that it is not a critical path and that downtime of the service will not affect our mobile app user: https://github.com/ooni/backend/issues/393 Then we updated the developer OONI Probe mobile app build to also support for receiving OONI Run links via push notification: https://github.com/ooni/probe/issues/874 ## Making the OONI Probe apps rely entirely on the OONI Probe golang engine We continued to make progress on making the OONI Probe mobile and desktop apps rely entirely on the golang based probe-engine. To this end, we completed the work in the following tickets: https://github.com/ooni/probe-engine/issues/125 https://github.com/ooni/probe-engine/issues/349 https://github.com/ooni/probe-engine/issues/352 https://github.com/ooni/probe-engine/issues/376 https://github.com/ooni/probe-engine/issues/396 https://github.com/ooni/probe-engine/issues/453 https://github.com/ooni/probe-engine/issues/482 https://github.com/ooni/probe-engine/issues/489 https://github.com/ooni/probe-engine/issues/501 https://github.com/ooni/probe-engine/issues/504 https://github.com/ooni/probe-engine/issues/538 https://github.com/ooni/probe-engine/issues/543 https://github.com/ooni/probe/issues/1017 https://github.com/ooni/probe/issues/1036 https://github.com/ooni/probe/issues/1040 As part of the process of switching entirely to the new golang probe-engine, Measurement Kit (https://github.com/measurement-kit/measurement-kit) has now been deprecated. Since several third-party projects rely on Measurement Kit, we published an upgrade path for all the use cases that we know of. This documentation is available here: https://github.com/measurement-kit/measurement-kit/blob/master/README.md As part of the process of deprecating Measurement Kit, we also worked on the activities in the following tickets: https://github.com/measurement-kit/measurement-kit/issues/1921 https://github.com/measurement-kit/measurement-kit/issues/1913 ## Expanding OONI Probe measurement methodologies As part of our ongoing efforts to expand our measurement methodologies, we: * Integrated the Go implementation of the DASH test into probe-engine: https://github.com/ooni/probe-engine/issues/501 (and implemented ConnectTime in the DASH test: https://github.com/ooni/probe-engine/issues/281) * Made improvements in the specification of the data format to allow for incrementally updating the data format without introducing breaking changes: https://github.com/ooni/probe-engine/issues/423 * Refactored and carried out research related to netx: https://github.com/ooni/probe-engine/issues/543 (i.e. netx is code used by probe-engine as a low level library to collect network, DNS, and HTTP events that occur during OONI measurements) * Analyzed measurements and performed quality assurance for our SNI blocking experiment: https://github.com/ooni/probe-engine/issues/547 & https://github.com/ooni/probe-engine/issues/299 ### Measuring SNI based filtering in Iran To check whether our new SNI blocking experiment (https://github.com/ooni/spec/blob/adf9537c43ef848b96792f8dea99fbd7f93fe608/…) works as expected, we tested it in Iran (where this censorship technique is known to be deployed) with the help of local community members. Following our experiments in Iran, we concluded that the new OONI SNI blocking experiment works as expected. To document and share our experiments and findings, we published the report “Measuring SNI based blocking in Iran”, which is available here: https://ooni.org/post/2020-iran-sni-blocking/ ## Prototype of system for probe URL selection To improve URL testing, we created a prototype system for probe URL selection which is now being deployed in production. Below we share details. ### Policy for URL prioritization We started off by writing and publishing a document that describes the new smart URL list system, why it’s needed, which problems it aims to address, how community members can contribute to URL priorities, and how we plan to roll this system out. This document is available here: https://ooni.org/post/ooni-smart-url-list-system/ We also published a policy that determines the criteria for URL prioritization: https://ooni.org/post/policy-url-prioritization/ooni-policy-url-prioritizat… ### Adding weights to Citizen Lab categories Creating a smart URL list system requires adding weights to the Citizen Lab category codes (based on which tested URLs are categorized), to ensure that certain categories of URLs receive more testing over others (depending on the criteria outlined in the aforementioned policy for URL prioritization). Our first steps therefore involved adding weights to the Citizen Lab category codes: https://github.com/ooni/ooni.org/issues/431 We will likely revise these weights as the system is rolled out and we receive community feedback. ### Prototype system The prototype is available through this ticket: https://github.com/ooni/backend/issues/361 The prototype system for URL prioritization is implemented in the backend through the following pull request: https://github.com/ooni/pipeline/pull/312 ## Analyzing data to extract website metrics We completed, deployed, and merged a series of improvements to our fast-path data processing pipeline: https://github.com/ooni/backend/issues/233 To add data export capabilities for website-related metrics, we implemented an API call to extract metrics from the counters table (in JSON and CSV): https://github.com/ooni/backend/issues/321 ## OONI Explorer Once the smart URL list system has been rolled out, we aim to add support to OONI Explorer (or, potentially, another web platform) for user accounts that (among other things) would enable users to run database-heavy queries for website-centric measurements. To this end, we did some research to understand, in practice, how these accounts could work across the various OONI products. See: https://github.com/ooni/backend/issues/391 and https://github.com/ooni/ooni.org/issues/434. During the April 2020 OONI Community Meeting, we did a poll to collect feedback and understand if OONI users would have issues with certain authentication methods, if OONI accounts were created. Our idea is to have an account that has interoperability across OONI Probe, OONI Explorer, and OONI Run to support seamless integration between the platforms. ## OONI backend To improve our backend services, we: * Implemented rate limiting on exposed services: https://github.com/ooni/backend/issues/260 * Completed our work around investigating API slowness and DB issues: https://github.com/ooni/backend/issues/381 * Improved DB query monitoring: https://github.com/ooni/backend/issues/382 * Decreased DB query load (throttling, caching, blocking bots): https://github.com/ooni/backend/issues/383 * Implemented throttling of the API based on IP address: https://github.com/ooni/backend/issues/394 * Investigated missing Psiphon measurements in the fast-path pipeline: https://github.com/ooni/backend/issues/296 * Ensured that the API gives priority to fast-path table data: https://github.com/ooni/backend/issues/283 * Investigated API query slowdown: https://github.com/ooni/backend/issues/401 * Added rate limiting to the API: https://github.com/ooni/backend/issues/405 * Added support for parallelising can processing in the fast-path pipeline: https://github.com/ooni/backend/issues/392 ## Improving OONI server infrastructure As part of our ongoing efforts to improve our server infrastructure, we: * Deployed workarounds for slow networking between servers: https://github.com/ooni/backend/issues/384 * Ensured that the new OONI Explorer redirects to HTTPS by default: https://github.com/ooni/backend/issues/252 * Made improvements to the fast-path pipeline: https://github.com/ooni/backend/issues/233 * Installed a clickhouse test instance on EC2: https://github.com/ooni/backend/issues/388 * Tested and benchmarked Greenhost object storage: https://github.com/ooni/backend/issues/247 * Dropped UI components from OONI API that are duplicated in OONI Explorer: https://github.com/ooni/backend/issues/139 ## Improving the quality of OONI software As part of our ongoing efforts to improve the quality of OONI software, we: * Refactored and did research around netx: https://github.com/ooni/probe-engine/issues/509 * Sanitized the netx error strings: https://github.com/ooni/probe-engine/issues/546 * Discussed the react-native integration plan: https://github.com/ooni/probe/issues/1058 ## OONI Run usability study To enable community members to more effectively use OONI Run (https://run.ooni.io/) we aim to research its limitations and collect structured community feedback through an OONI Run usability study. In April 2020, we created a user research plan and decided to collect feedback through a combination of a survey and a series of interviews with community members. Throughout the month, we created and circulated the survey, and we carried out interviews. ### Survey We created a survey with the goal of collecting more quantitative information on community needs, challenges, and feedback for the improvement of OONI Run. This survey is primarily meant to be completed by OONI Run users, as we include detailed questions that require experience with the OONI Run platform. The survey is available here: https://ooni.typeform.com/to/r9c5ee Throughout April 2020, we circulated the survey on social media and on multiple mailing lists, as well as with our network of partners. We aim to analyze the data collected through the survey in mid-May 2020. ### Interviews Through interviews with community members, we aim to collect more in-depth qualitative information to better understand their needs, challenges, and feedback for the improvement of OONI Run. The interviews also provide us an opportunity to observe how community members interact with the OONI Run platform. The interviews involve three user personas: * Measurement campaign coordinators: Experienced OONI Probe users who use OONI Run to generate links and coordinate censorship measurement campaigns * Measurement campaign volunteers: OONI Probe users who receive OONI Run links to perform testing and participate in censorship measurement campaigns * Internet freedom community members: People who care about internet censorship, but who haven’t necessarily used OONI Run before As each of these personas have different experiences with OONI tools, we drafted separate interview questions for each persona. During the last week of April 2020, we interviewed 7 community members. We plan to continue and complete the interviews by mid-May 2020. ### Blog post To promote the survey and encourage more community members to participate in the interviews, we wrote and published a blog post that shares the survey and information about the interviews. This blog post is available here: https://ooni.org/post/2020-ooni-run-survey-and-interviews/ ## OONI website Leading up to the public launch of the OONI Probe desktop app, we made a series of improvements to the OONI website. These include new Install pages (https://ooni.org/install/) for our mobile (https://ooni.org/install/mobile) and desktop clients (https://ooni.org/install/desktop) The new Install pages have a new layout, design, and copy. We also edited the copy for most of the other pages on the OONI website to ensure that the information we provide is up to date and relevant. As part of these copy edits, we updated the risks documentation (https://ooni.org/about/risks/) we updated the test descriptions (https://ooni.org/nettest/) and we improved the layout and copy of the landing page (https://ooni.org/) We also wrote and published OONI’s mission statement: https://ooni.org/about/ ## Updated OONI Data Policy We published an updated version of the OONI Data Policy: https://ooni.org/about/data-policy The new version of the OONI Data Policy shares the principles that govern our data practices, and we explain what data we collect, process, store, and publish when you use OONI Probe. We explain how you can opt out of the various forms of data collection and publication. We also share which analytics we use for the OONI website, OONI Explorer, and the OONI desktop app, and we explain how you can opt out of analytics all-together. ## Test list updates Throughout April 2020, we: * Updated the Global test list: https://github.com/citizenlab/test-lists/pull/600 * Updated multiple test lists with COVID-19 related sites shared by the Citizen Lab: https://github.com/citizenlab/test-lists/pull/601 ## Data analysis In April 2020, we analyzed OONI measurements for the following: * OTF Information Controls Fellow: https://github.com/ooni/ooni.org/issues/453 (analysis of OONI measurements collected from Myanmar) * Community members in Myanmar: https://github.com/ooni/ooni.org/issues/471 (longer-term analysis of OONI measurements collected from Myanmar) * Community members in Guinea: https://github.com/ooni/ooni.org/issues/488 (to examine the blocking of social media during Guinea’s March 2020 elections) * Website monitoring project: https://github.com/ooni/ooni.org/issues/454 ## GitHub sponsorship Our application to receive donations through our GitHub repositories was accepted! OONI now has a GitHub sponsors profile: https://github.com/sponsors/ooni We are therefore in the position to receive recurring donations. ## Community use of OONI data ### Blocking of sites hosting COVID-19 related information in Venezuela Through the use of OONI Probe and OONI data, VEsinFiltro reported new censorship cases in Venezuela involving the blocking of sites hosting COVID-19 related information. Many of these cases were shared on Twitter: https://twitter.com/vesinfiltro/status/1250579061937770496, https://twitter.com/vesinfiltro/status/1250571183579373568, https://twitter.com/vesinfiltro/status/1253423468273471490, https://twitter.com/vesinfiltro/status/1253122594976468993. VEsinFiltro also published a report (which links to OONI measurements) on the blocking of and the phishing attempts against the Heroes of Health platform (created by the management of Juan Guiado): https://vesinfiltro.com/noticias/2020-04-26-phishing_heroes_salud ### Blocking of websites in Egypt Masaar published a report on the blocking of websites in Egypt over the last months (“Internet Censorship in Time of Social Distancing”), through the use of OONI Probe and OONI data. Their report is available here: https://masaar.net/en/internet-censorship-in-time-of-social-distancing/ ## Community activities ### OONI Community Meeting On 28th April 2020, we facilitated the monthly OONI Community Meeting on our Slack channel (https://slack.ooni.org/) during which we discussed the following topics: 1. Updates from the OONI team. 2. Adding user accounts to OONI Explorer. 3. Monitoring potential censorship events during the upcoming elections in West Africa. 4. Challenging the blocking of social media during Guinea’s March 2020 elections in a strategic litigation case with OONI data. 5. Women on Web blocked in Spain: Technical analysis. 6. Reducing the latency of publication of measurements from custom URL tests and experimental tests. 7. SNI-based blocking. ### IFF Glitter Meetup On 30th April 2020, we were invited to attend the IFF Glitter Meetup as featured guests to discuss the OONI Probe desktop app launch. The notes from what was discussed are available here: https://internetfreedomfestival.org/wiki/index.php/April_30_2020_GM#Convers… ### Coordination of COVID-19 site testing in Mexico Our Mexican partners, R3D, published a blog post where they encourage OONI Probe testing of COVID-19 related websites. Their post is available here: https://r3d.mx/2020/03/27/ayudanos-a-descubrir-bloqueos-de-informacion-sobr… ## Userbase In April 2020, 7,175,892 OONI Probe measurements were collected from 6,124 networks in 214 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on “monthly coverage worldwide”): https://explorer.ooni.org/ ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

TBB 9.5 stable release meeting on Tuesday May 12th at 15UTC
by Gaba 08 May '20

08 May '20

Hi! On Tuesday May 12th at 15 UTC we are meeting in #tor-meeting to talk about the Tor Browser 9.5 stable release. Pad with discussion items are here: https://pad.riseup.net/p/tor-browser-release-meeting-keep cheers, gaba -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0