- tor-project - lists.torproject.org

S27: Onion Services meeting this week: Tuesday 23rd July @ 15UTC
by Pili Guerra 23 Jul '19

23 Jul '19

Hi everyone, This is a reminder of the next Onion Services meeting happening this week on Tuesday 23rd July at 15UTC on #tor-meeting. We hope to 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 1

Network team meeting notes, 22 July 2019
by Nick Mathewson 22 Jul '19

22 Jul '19

Hi! The IRC logs from our weekly meeting are available at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-07-22-16.59.html Below are the contents of our pad. = Network team meeting pad! = This week's team meeting is at Monday 22 July at 1700 UTC on #tor-meeting on OFTC. We have changed the day from Tuesday to Wednesday. July schedule: * Wednesday 3 July 2300 UTC - Changed Day! * 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: Wednesday 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.) 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html 10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html 17 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002365.html 24 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002373.html 3 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002389.html 8 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002390.html In-person meetings: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… == Stuff to do every week = * 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. ------------------------------- ---- 22 July 2019 ------------------------------- == Announcements == reminder: catalyst will be AFK Jul 29 through Aug 18 nickm will be AFK August 12 through August 16 ahf will be AFK all of August for BornHack and CCC Camp, but will be on IRC every now and then == Discussion == Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity catalyst -> catalyst & teor coverity the defect browser was down last week; it seems to be back now (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) Looking at coverity -- it seems our builds may have been stuck. I've cancelled the stuck builds. Also, they say they are going to have a planned outage to upgrade their backend, starting today and lasting about 3-4 days. Friday would be a good day to have another look. -nm stuff got unstuck on 28 Jun or maybe earlier? -catalyst Correct; we've been getting updates since then. I opened tickets for the first day's updates; there are more I hope to get to soon. jenkins some intermittent failures that could be network-related Travis teor did some work on stem failures, we need to add a control message trace to tor to diagnose (#30901) waiting for catalyst's advice, because they are refactoring this code Appveyor Bug triage ahf -> asn Things are looking OK asfaik. catalyst asks if we want to re-evaluate https://trac.torproject.org/projects/tor/ticket/31081 or stay with "make the spec match the code" Please give feedback on proposal 306: IPv6 "Happy Eyeballs" for Tor clients https://lists.torproject.org/pipermail/tor-dev/2019-June/013907.html == 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! gaba: Last week (actual): This week (planned): . tor meetup Help with: teor: (offline at the usual meeting time) Week of 8 July (actual): Urgent: - Taking time off before long-haul travel and Stockholm meeting - Travel preparation - Ticket triage - Proposal responses Backlog: - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - disown or quick fix the rest of my tickets: - I should only be owner on tickets I will work on in the next month - fix sponsor on tickets? - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Nick: Week of 15 July (actual): - Attend PETS reception - Take it easy post-meeting - Travel home - More work on refactorings for 29211 (config.c redesign) - Several practracker improvements - Catch up on email and expenses Week of 22 July (planned): - Review and merge - Try to release 0.4.1.4-rc - Backports for 0.4.0.x? - More 29211 work (config.c): can I get all the backend code written? - Reply wrt proposal 295 - Reply wrt proposal 306 - More practracker fixes, time permitting Mike (afk: jetlagged and recovering from 12 days travel+work) catalyst: week of 07/08 (2019-W28) (planned): - travel prep - Stockholm meeting week of 07/08 (2019-W28) (actual): - travel prep - Stockholm meeting week of 07/15 (2019-W29) (actual): - travel - time off to recover from travel week of 07/22 (2019-W30) (planned): - Season of Docs selection due 07/23 - expense reports - follow up from Stockholm meeting - hand off some reviews to teor - working partial days this week asn: Week of 07/01 (actual): - Pushed #26294 branch to needs_review. - Some more thoughts on the DoS thread. - Some more thoughts on scaling thread. - Lots of hackerone activity/triaging/rewarding (#31022, #31001, plus one more not yet filed) - Finished review/merge backlog. Week of 07/08 (planned): - Triaged a few wtf-pad related tickets but need more work: #30649, #31098. - Tor meeting in Stockholm. - Allhands expenses ahf Last N-weeks: - Send vacation info to the network team ML. - Traveled to Stockholm, had a good time with you all. Week of 22/7: - Do reimbursement - Go over all notes from Stockholm that seems relevant to me. - Follow up on pre-Stockholm items: - Continue figuring out some info on a potential Danish funder. - Continue with #5304 and #28930 dgoulet: (offline) Week of 07/01 (actual): - s27 DoS work: #15516, #24963/#24964 - Tor-dev update on the DoS experimentation: https://lists.torproject.org/pipermail/tor-dev/2019-July/013923.html Week of 07/08 (planned): - Stocklholm. - Need to address urgently a series of pending bad-relays email.

1 0

June 2019 report for the Tor Browser team
by Georg Koppen 19 Jul '19

19 Jul '19

Hello! In June we released 5 Tor Browser releases: 8.5.1[1], 9.0a2[2], 8.5.2[3], 8.5.3[4], and 9.0a3[5]. The last three were due to two chemspill releases Mozilla managed to do while they had their All Hands meeting in Whistler (Canada) and a group of Tor people attended as well, to discuss both further uplift + fingerprinting work and performance + scalability improvements. Tor Browser 8.5.1 was the first bugfix release in the 8.5 series which fixed minor shortcomings in 8.5 and defended against the readPixel() fingerprining vector[6]. Tor Browser 9.0a2 contained all the fixes that went into 8.5.1 and additionally bumped several components in our bundle (Tor on desktop to 0.4.1.2-alpha, OpenSSL on desktop to 1.1.1c) and in our toolchain and compilation environments (GCC to 8.3.0 for Linux, Debian Stretch for macOS cross-compilation), in preparation for the upcoming 9.0 release. Non-release related work mostly comprised progress on our work on onion service authentication support. First testing bundles are available.[7] Moreover, we rebased most of our patches for ESR 68 and they got a first round of review[8], and our toolchains for Linux[9] and macOS[10] are mostly ready. We made considerable progress on integrating Snowflake for Android into our reproducible build system[11], although we are still a bit away from getting this shipped to users as some glue code is so far missing.[12] Another highlight that month was our fixed accessibility support for Windows users, which Richard achieved after weeks of hard work (thanks!). It is included in the first alpha for July, 9.0a4. The full list of tickets closed by the Tor Browser team in June is accessible using the `TorBrowserTeam201906` keyword in our bug tracker.[13] For July, we attended the Tor dev meeting in Stockholm to think about upcoming work in the next month but, above all, to better coordinate all the ESR transition work under way. The whole team is currently working to get first nightly builds out[14] which are based on Firefox 68 ESR, which essentially means toolchain updates and patch rebase and review. We hope we'll have the latter finished by end of July so that we can ship the first nightly builds based on Firefox 68 ESR in early August. As usual it will probbably be Linux bunldes first with the other platforms being added as soon as the toolchains are in reasonable shape. So, stay tuned! All tickets on our radar for this month can be seen with the `TorBrowserTeam201907` keyword in our bug tracker.[15] Georg [1] https://blog.torproject.org/new-release-tor-browser-851 [2] https://blog.torproject.org/new-release-tor-browser-90a2 [3] https://blog.torproject.org/new-release-tor-browser-852 [4] https://blog.torproject.org/new-release-tor-browser-853 [5] https://blog.torproject.org/new-release-tor-browser-90a3 [6] https://trac.torproject.org/projects/tor/ticket/30541 [7] https://trac.torproject.org/projects/tor/ticket/30237#comment:19 [8] https://trac.torproject.org/projects/tor/ticket/30429 [9] https://trac.torproject.org/projects/tor/ticket/30321 [10] https://trac.torproject.org/projects/tor/ticket/30323 [11] https://trac.torproject.org/projects/tor/ticket/28672 [12] https://trac.torproject.org/projects/tor/ticket/30318 [13] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [14] Nightly blockers are tagged with `tbb-9.0-must-nightly` in our bug tracker: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~tbb… [15] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

Anti-censorship meeting notes, 18 July 2019
by Philipp Winter 18 Jul '19

18 Jul '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-07-18-17.00.html And here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday July 18th 17:00 UTC Weekly meetings, every Thursday at 17: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://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Our roadmap consists of a subset of trac tickets. * Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team" * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 18th July 2019 ---- --------------------------- == Announcements == * Added Stockholm meeting notes to: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam#… == Discussion == * https://dip.torproject.org/anti-censorship/state-of-censorship/blob/master/… * Is this a good start? == Actions == * == Interesting links == * https://www.swadeshimedia.in/spring-epfl-lightnion/ == Updates == FORMAT! Name: This week: - What you worked on this 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: (gettor days are Thursday) This week: Next week: Past week: phw: This week (2019-07-18): * Working with obfs4 bridge operators who couldn't get their bridge to run. * Filed OONI ticket to have OONI measure reachability of STUN servers. * Started working on a repository that keeps track of what's necessary to connect to Tor in censoring countries. * https://trac.torproject.org/projects/tor/ticket/28531 * Filed a ticket to get a new default obfs4 bridge running. * https://trac.torproject.org/projects/tor/ticket/31164 * Filed a ticket to have www services of anti-censorship team monitored. * https://trac.torproject.org/projects/tor/ticket/31159 * Wrapped up creation of docker image. * https://trac.torproject.org/projects/tor/ticket/30708 * Filed ticket for an easy-to-use bridge setup meta package in Debian. * https://trac.torproject.org/projects/tor/ticket/31153 * Read Matic et al.'s NDSS'17 paper and sent summary to anti-censorship-team@. * https://lists.torproject.org/pipermail/anti-censorship-team/2019-July/00002… * Moved forward with understanding the "long tail" of network traffic (required for Sponsor 28). * Attended Tor dev meeting in Stockholm. * Sponsor 30 kick-off meeting. * Had a chat with Antonela about UX challenges wrt bridges. * Had a chat with Hiro about the future of GetTor. * Had a chat with Nathan and Benjamin about ORbot and OnionBrowser. * Had a chat with Tails folks about maintenance of obfs4proxy package. * Had a chat with David about PT v2.0 and snowflake. * Attended session on anti-censorship rapid response. * Attended session on how to attract more snowflakes. * Attended session about Tor's upcoming dev portal. * Roadmapping. Next week: Help with: Gaba: (updated ) Last week (): This week (): * ahf Last week: - Worked on #28930 This week: - Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info. - Continued to work on a tool to convert Trac tickets into Gitlab tickets. cecylia (cohosh): last updated 2019-07-18 (will try to attend but still at PETS) Last week: - Tor Meeting and PETS - deployed a proxy-go instance that uses pion/webrtc library (#28942) - updated snowflake bridge survival guide instructions for new proxy-go instances - starting sorting out webextension infinite loop bug (#31100) This week: - Still at PETS and then travelling/recovering from travel - finish up addressing issues with #31100 - more dogfood catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 week of 06/20 (actual): - mostly sponsor31 - helped ahf with some bootstrap stuff week of 06/27 (planned): - mostly sponsor31 arlolra: 2019-06-27 Last week: - a bit of snowflake webextension This week: - getting the webextension published (#30931) Next week: - review #30934 Help with: - fixing our websocket server implementation (#30998)

1 0

April Fundraising Report
by Sarah Stevenson 17 Jul '19

17 Jul '19

Hello - below is the Fundraising team’s April update. Let us know if you have any questions! ## Grants The biggest news in the world of grants is that our proposal to DRL for anti-censorship work was approved. Al also submitted a proposal to CS Fund/Warsh Mott Legacy, Rights, and Governance that was declined and a proposal to Wallace Global on which we are still awaiting a response. We are also waiting to hear a response back from the DIAL Open Source Center about funding for the ESR migration. In these monthly updates we will begin informing you about proposals we intend to submit in the next month in case anyone might have comments or concerns about the funders, or connections that might help our chances. As a reminder, our grant work flow can be found on the Fundraising Team Wiki[1]. We plan to submit proposals to Media Democracy Fund, who have been funding us for several years now, the Reva and David Logan Foundation, NLnet, and The Charles Léopold Mayer Foundation for the Progress of Humankind. We welcome any and all feedback sent to grants(a)torproject.org <mailto:grants@torproject.org>. We have been working to better communicate with our grant program officers and, to that end, we sent our first Sponsors Newsletter[2]. The intent is to demonstrate the full impact of our work to funders who may only be familiar with specific projects. We plan to send the next newsletter after the meeting in Stockholm. Additionally, Isa and Sarah met with Michael Brennan from the Ford Foundation and are planning a follow-up meeting in June with others from Ford. ## Small Foundations / Major Donors In an effort to get lapsed major donors and small foundations to donate again, we sent a solicitation letter via postal mail. We included a nice insert, created by Steph, featuring Tor stories that we plan to use for acknowledgements that need to be sent in the mail. We’ve seen a small response. We sent a version of the Sponsors Newsletter to current major donors to let them know how impactful their giving has been. ## Monthly Giving / Defenders of Privacy We launched a donation page dedicated to monthly giving[3]. This will allow us to promote the Defenders of Privacy program and try to convert one-time givers into monthly givers. We currently have 334 people in the group who generated $3,438 in income in April. We will send a three-part series of emails to one-time givers beginning in May and will offer a new sticker or patch (yet to be determined) in the second invite. I will keep you updated on the growth of this program. ## Website Since the new website was launched at the end of March, we have been tracking the number of unsolicited donations from the website. That number decreased about 30% with the new site design. Our theory was that the Donate button was less noticeable, so at the end of April, Antonela changed the design and added a yellow Donate button in the header and footer. Since that change was made, donations are now almost double what they were per day before the website redesign. ## Administrative We have been working with a company called Labyrinth on making sure we are registered to fundraise in each of the 50 US states. This is a requirement that can result in fines if you are not properly registered. The process is a bit arduous since each of the states has different requirements. Thankfully, the process is almost complete for this year. ~ Fundraising Team [1] https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view <https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view> [2] https://crm.torproject.org/civicrm/mailing/view?id=158 <https://crm.torproject.org/civicrm/mailing/view?id=158>[3] https://donate.torproject.org/monthly-giving <https://donate.torproject.org/monthly-giving>

1 2

Damian's Status Report - June 2019
by Damian Johnson 13 Jul '19

13 Jul '19

Hi all! Sadly not much worth noting on the tor front. I have a feature branch in the works [1] that should hopefully be ready to announce later this month. https://blog.atagar.com/june2019/ Cheers! -Damian [1] https://gitweb.torproject.org/user/atagar/stem.git/log/?h=collector

1 0

OONI Monthly Report: June 2019
by Maria Xynou 10 Jul '19

10 Jul '19

Hello, In June 2019, the OONI team published two research reports, released OONI Probe mobile 2.1.0, improved analysis capabilities through a series of improvements to the OONI data processing pipeline, and continued to make progress on the development of the OONI Probe desktop apps and probe-engine. We also continued to work towards the stable release of the revamped OONI Explorer. ## Report on Facebook live-streaming interference in Jordan In collaboration with our Jordanian partners, Jordan Open Source Association (JOSA), we co-published a research report which examines Facebook live-streaming interference during protests in Jordan between December 2018 to January 2019. Our joint research report is available via the following sites: OONI: https://ooni.io/post/jordan-measuring-facebook-interference/ JOSA: https://jordanopensource.org/technical-report/ Thanks to JOSA, we also published a PDF version of the report: https://ooni.io/documents/jordan-facebook-interference.pdf In this report we share our findings in detail, as these methodologies could potentially be useful in examining similar cases elsewhere in the world. ## Report on censorship events in Ethiopia We published a research report which shares network measurement data on recent censorship events in Ethiopia: https://ooni.io/post/ethiopia-whatsapp-telegram/ OONI measurements collected from Ethiopia show the blocking of WhatsApp and Telegram between 15th to 18th June 2019. Both WhatsApp’s registration service (v.whatsapp.net) and web interface (web.whatsapp.com) were blocked by means of SNI filtering, but the blocks were lifted by 10:10 UTC on 17th June 2019. Many Telegram endpoints were blocked between 15th to 18th June 2019, strongly suggesting that Telegram’s mobile app was blocked (though connections to some Telegram endpoints were successful). The IP blocking of Telegram’s mobile app appears to have resulted in the (likely unintentional) blocking of web.telegram.org as well. We also share IODA and Google traffic data on the internet blackouts that appear to have occurred between 11th to 14th June 2019. ## OONI data processing pipeline We made a series of improvements to OONI's data processing pipeline. These can be viewed through the following pull requests: * Added pipeline metrics: https://github.com/ooni/pipeline/pull/208 * Progress on adding an analysis tool: https://github.com/ooni/pipeline/pull/205 * Feed generator prototype: https://github.com/ooni/pipeline/pull/204 * Matched fingerprints by country and globally: https://github.com/ooni/pipeline/pull/207 * Automated code restyle: https://github.com/ooni/pipeline/pull/206 The above pipeline work aims to support exposing blocking events in RSS feed hosted on OONI Explorer. ## OONI Probe Mobile 2.1.0 release We released OONI Probe 2.1.0 on Android and iOS. Android: https://github.com/ooni/probe-android/releases/tag/v2.1.0 iOS: https://github.com/ooni/probe-ios/releases/tag/v2.1.0 The new release includes: * Setting for manual (re-)upload of measurements * Email support for bug reports * Improved view of test methodologies ## Progress on OONI Probe desktop apps We made progress on improving upon the UI of the OONI Probe desktop app. We refactored some of the screens to be more alligned with desktop UI patterns. See: https://github.com/ooni/probe-desktop/pull/32 We also upgraded the probe-desktop codebase to use the latest version of javascript dependencies and made some of the development patterns closer to those used in OONI Explorer to make it easier to do code-sharing between the two. ## Probe-engine in golang We are experimenting with an OONI engine in Go. The objective of this experiment is to understand whether this could allow us to obtain good quality measurements with less code to maintain. We're specifically looking into using the automatic generation of Go bindings for mobile to better integrate with the mobile apps. As part of these experiments we're testing a branch containing measurement and reliability improvements and we are evaluating the measurements it produces in several network contexts. See: https://github.com/ooni/probe-engine/pull/26 ## Measuring the blocking of WhatsApp and Facebook in Liberia Amid mass protests in Liberia over inflation and corruption, locals reported that they couldn't access social media. We coordinated local testing and analyzed OONI measurements, confirming the blocking of WhatsApp, Facebook Messenger, and facebook.com. Our analysis is available here: https://gist.github.com/hellais/43c2d17a426b41fa5e847df1e73e5972 We shared our findings with the KeepItOn mailing list and with the broader public: https://twitter.com/OpenObservatory/status/1136995395106758656 ## Community use of OONI data ### AccessCheck The Internet Monitor project of the Berkman Klein Centre for Internet and Society at Harvard University launched AccessCheck, a tool that allows people to check the accessibility of websites around the world: https://accesscheck.thenetmonitor.org/ AccessCheck is powered by OONI data (along with data collected by VPNs, VPSs, and ICLab): https://accesscheck.thenetmonitor.org/about ### IPYS Venezuela report on recent media censorship Our Venezuelan partners, IPYS Venezuela, published a research report documenting the blocking of media websites El Pitazo and Efecto Cocuyo through the use of OONI Probe and OONI data. Their report is available here: https://ipysvenezuela.org/alerta/nuevos-episodios-de-bloqueos-digitales-afe… ## Community activities ### RightsCon OONI's Arturo and Maria traveled to Tunisia to attend RightsCon (https://www.rightscon.org/) between 11th to 14th June 2019. At RightsCon, we: * Facilitated an OONI workshop (hosted by The IO Foundation), as part of the satellite events (Day 0 - 11th June 2019), https://www.rightscon.org/program/ * Hosted the OONI Partners Meetup (Day 1 - 12th June 2019): A private meeting with our partners * Spoke on the panel: "Measuring internet shutdowns" (Day 2 - 13th June 2019), https://rightscon2019.sched.com/event/Pvs2/measuring-internet-shutdowns * Spoke on the panel: "Methods: Measuring freedom of internet" (Day 2 - 13th June 2019), https://rightscon2019.sched.com/event/Pvea/methods-measuring-freedom-of-int… * Spoke on the panel: "Detecting, understanding, and countering censorship of Wikipedia" (Day 2 - 13th June 2019), https://rightscon2019.sched.com/event/Pvem/detecting-understanding-and-coun… * Facilitated the session: "Supporting the KeepItOn campaign with network measurement data" (Day 3 - 14th June 2019), https://rightscon2019.sched.com/event/PvrM/supporting-the-keepiton-campaign… ### Instagram We created an Instagram account for OONI: https://www.instagram.com/openobservatory/. Follow, like, and share! ## Userbase In June 2019, OONI Probe was run 352,807 times from 5,033 different vantage points in 209 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

Tor's Defenders of Privacy Program
by isabela 09 Jul '19

09 Jul '19

Hello Tor! Today we launched our Defenders of Privacy program, a monthly giving program designed to honor donors who make privacy a priority. We have so many people who support us with donations, and some folks has signed up to give a small amount every month. These steady contributions allow us to make long-term plans and to be agile with our development. Because this type of contribution is so important to us, and for privacy, we decided to honor these donors by giving them the ‘Defenders of Privacy’ title :) and we will also be sending them exclusive gifts to show our appreciation! We are looking forward to building a strong base of Defenders of Privacy to support Tor. Do you want to help us on this mission? Here is how you can do it: 1) Maybe you would like to become a Defender of Privacy yourself ;) here is the link for that: https://donate.torproject.org/monthly-giving; 2) You can invite a friend, a family member, or someone you know that cares about privacy to join our program; 3) And you can help us spread the word! Share the donate page link or our social media posts (https://twitter.com/torproject/status/1148581357502828545) We will be at some events this summer with some cool patches as well for folks who sign up as monthly donors. We will share more when we have the schedule defined. Cheers, isabela

1 0

May and June Communications Report
by Stephanie A. Whited 08 Jul '19

08 Jul '19

1 0

Tor Browser team meeting notes, 8 July
by Georg Koppen 08 Jul '19

08 Jul '19

Hi! Our weekly Tor Browser team meeting just finished. The IRC log can be found at: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-07-08-17.31.l… and the items from our pad below: Discussion: - dev meeting (from a tor browser team bird's eye view) GeKo: Last Week: - wrote patch for mk bundle inclusion (#30468) - wrote patch for default bridge removal on mobile (#31058) - wrote patch for enabling letterboxing by default in the alpha series (#31059) - reviewed a bunch of patches (#31055, #27503, #30577, #30573, #31079, #30549, #31086, #30429) - release preparation, building and signing - begin-of-the-month-team updates - start with dev meeting prep This week: - help more with getting releases out - dev meeting prep - finally finish #30429 review - finish begin-of-the-month-team updates sysrqb: Last Week: Mobile 68esr rebasing and testing (#31010) Reviewed patch for updating default bridges and deleting obfs3 from list (#31058) Wrote revised patch for #30573 (opening link for other app) for 9.0 Looked at F-Droid patch again This week: Release. Traveling, meeting prep, some touristy things More on #31010 F-Droid patch (#27539) tjr Sent some emails/comments on fingerprinting issues Disabled mingw builds because we were missing APIs, got them added and re-enabled it Disabled jemalloc due to the alloc/dealloc mismatch :( Making a minimal reproducer to ask Martin for help with a linker patch Learned we do not have anyone working on Uplift for the next... quarter? Unsure. :( mcs and brade: Last week: - Review for #30683 (Properties in dom/locales/$lang/chrome/ allow detecting user locale). - Review for #31059 (Enable Letterboxing by default). - Stockholm travel preparations. - Took a couple of days off for the U.S. Independence Day holiday. This week/upcoming: - Travel to Stockholm. - Respond to Antonela's comments in #30237 (Onion Services client auth prompt). - #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - #29197 (Remove use of overlays from Tor Launcher). - #30429 (ESR 68 Rebase — updater patches). boklm: Last week: - Helped with building new releases - Made patches for: - #31079: Update Mozilla gpg key - #31086: Add instructions for adding new locales to the download page, in the ReleaseProcess documentation - #30548: Clean up keyring files - Fixed issue with the patch for #30549 (Add script to remove expired sub-keys from a keyring file) - Fixed #31054 (Add android aarch64 nightly builds) - Checked archive.tpo rsync scripts after migration to a new machine (#29697) - Reviewed #30468 (Ship macedonian Tor Browser in alpha series) This week: - Help with publishing new releases - Travel to Stockholm - Update patch for #28672 (Android reproducible build of Snowflake) after review - Look at how we can build 32bit mar-tools: https://trac.torproject.org/projects/tor/ticket/30321#comment:10 - Look at remaining failing testsuite tests pili: Last week: - Fundraising banner wrangling - general roadmap and project gardening This week: - dev meeting prep - Season of docs candidate evaluation acat: Last week: - Finished iteration of #28745 (torbutton cleanup/refactor) -> probably more to be done but will wait for review - Reviews (#30800, #30849) - Investigated how to upstream patch for #26353, opened #31075 for that. - Investigated local network proxy bypass in ESR68 -> opened #31065. - Checked whether patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1396224 fixed #21830 - Copying large text from web console leaks to /tmp (nope) This week: - Ask bugzilla 1561636 for esr68 approval - Fix/upstream #21830 (with https://bugzilla.mozilla.org/show_bug.cgi?id=1396224 fixed it should be easy). - Finish revision of https://bugzilla.mozilla.org/show_bug.cgi?id=1561322 (l10n reviewer does not like the original patch...) - Fix #29563 (css line-height revisted [at least zoom and linux]) so that it can be upstreamed together with #23104 (bugzilla is shared). pospeselr: Last week: - submitted hopefully last widl revision to wine-devel This week: - travel prep, travel and Stockholm Next week(s): - on vacation and mostly AFK after Stockholm through the 28th of July sisbell: Last week: - Submit PR to TOPL for issues #130 - IPv6 config for socks port, #120 fix for KitKat, #121 SDK 28, #129 debug. Looks like TOPL is getting additional devs submitting patches last week so some good activity. Changes compatible with tor-android-service - Orbot PR merged into their master (I did fix to resolve merge conflict with most recent master) - #30199 finished responses -Ready for review: #31047, #31043 - Worked on solution so we don't have to add MAVEN_REPO patches in tor-browser-build This Week - get tor-browser-build working with latest TOPL changes. Get ready for review. - Update TOPL build to add deployment of artifacts to maven central Georg

1 0