tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

integrating Tor in Mozilla and beyond
by Gaba 16 May '19

16 May '19

Hello! Mozilla just launched a call for proposals [0] for researchers to work on several areas. One of the areas is "RQ12 Privacy & Security for Firefox" and particular questions around Tor network performance and scalability. You can read about many of research ideas in the blogpost [1][2][3] we published last week. The deadline to apply for this grant is May 31st. We are receiving questions/comments/discussions at research(a)torproject.org It would be great if you all can share this call with researchers, students and community in general that may be interested in tackle this questions. Thanks!! cheers, gaba [0] https://mozilla-research.forms.fm/mozilla-research-grants-2019h1/forms/6510 [1] https://blog.torproject.org/mozilla-research-call-tune-tor-integration-and-… [2] https://twitter.com/torproject/status/1126117511966097414 [3] https://mastodon.social/@torproject/102072044469996039 ps. yes, the subject of this mail was "clickbait" :P -- Project Manager: Network, Anti-Censorship and Metrics teams and OONI support gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

OONI Monthly Report: April 2019
by Maria Xynou 16 May '19

16 May '19

Hello, The OONI team made steady progress in April 2019. ## Report on social media blocking and internet blackout in Benin In collaboration with CAIDA's IODA project, we co-published a research report that shares network measurement data on the blocking of social media (and the subsequent internet blackout) in Benin, amid the country's 2019 parliamentary elections. Our report is available here: https://ooni.io/post/2019-benin-social-media-blocking/ ## OONI Probe mobile app Throughout April 2019, we improved testing coverage (https://github.com/ooni/probe-ios/pull/263) and we did a lot of development work on the OONI Probe mobile apps (in preparation for the upcoming 2.1.0 release). We worked on adding support for re-uploading non-uploaded measurements manually. This will allow users to submit measurements at a later stage, even if they had disabled automatic upload or if the initial upload had failed. On Android: https://github.com/ooni/probe-android/pull/214 https://github.com/ooni/probe-android/pull/215 https://github.com/ooni/probe-android/pull/213 On iOS: https://github.com/ooni/probe-ios/pull/258 https://github.com/ooni/probe-ios/pull/265 https://github.com/ooni/probe-ios/pull/266 https://github.com/ooni/probe-ios/pull/267 https://github.com/ooni/probe-ios/pull/268 https://github.com/ooni/probe-ios/pull/269 ## OONI pipeline We worked quite extensively on the OONI data processing pipeline to make the annotation of confirmed and anomalous measurements more accurate, and to extract metadata from new tests. Our work on the pipeline can be viewed via the following pull requests: https://github.com/ooni/pipeline/pull/177 https://github.com/ooni/pipeline/pull/151 We also worked on improving the documentation of the OONI pipeline and explained how to reprocess measurements: https://github.com/ooni/pipeline/pull/183 ## System for sharing OONI metadb with third parties We set up a system for sharing OONI's metadata database with third parties: https://github.com/ooni/sysadmin/issues/272 This new system allows external people to set up their own instance (and to have an always in sync version) of the OONI measurement database that powers the OONI API and OONI Explorer. It includes all the features that are extracted as part of the OONI pipeline for all OONI measurements ever collected. We also wrote documentation which explains how you can set up your own copy of the OONI metadb: https://github.com/ooni/sysadmin/blob/metadb-share/docs/metadb-sharing.md. ## ndt7 We aim to replace the NDT speed test (currently included in the OONI Probe mobile app) with ndt7: a next generation speed test that will run very short network performance tests and provide users with greater quality information. To this end, we have been working on implementing the ndt7 server and ndt7 client for Measurement Kit: https://github.com/measurement-kit/engine/issues/4. We continued to make progress on this throughout April 2019. ## Updated test list Leading up to India's 2019 general elections, we updated the Indian test list to include more political party sites and election sites: https://github.com/citizenlab/test-lists/pull/455 We also embedded several OONI Run buttons on our site (https://ooni.io/get-involved/run/) to enable the testing of Indian political and media websites, as well as the testing of the whole Indian test list. ## Community activities ### Internet Freedom Festival (IFF) The OONI team attended the Internet Freedom Festival (IFF) in Valencia, Spain, between 1st to 5th April 2019. As part of our participation at the IFF, we: * Facilitated a session to collect OONI community feedback: https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/cus… * Hosted the OONI Partners Meetup: https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/cus… * Presented OONI at the IFF expo: https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/cus… * Presented OONI at the Tool Showcase: https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/cus… * Co-facilitated a session with our Venezuelan partners: https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/cus… ### Digital Rights & Inclusion Forum (DRIF) OONI's Maria traveled to Lagos, Nigeria, to participate at the Digital Rights & Inclusion Forum (DRIF) between 23rd to 25th April 2019. At DRIF, Maria facilitated the session "Uncovering censorship evidence", where she presented OONI and explained how digital rights communities in Africa can use OONI Probe and OONI data as part of their work. Information about the event is available here: https://drif.paradigmhq.org/ ### Community meeting We held the monthly OONI community meeting on our Slack channel (https://slack.openobservatory.org/) on 30th April 2019. As part of the meeting, we discussed: 1. Measuring HTTPS throttling in Iran 2. Starting to use a Go engine - would an OONI Probe app bigger than 50 MB be a big problem for users? 3. Sourcing more in-country collaborators for OONI Probe testing ## Userbase In April 2019, OONI Probe was run 319,720 times from 4,805 different vantage points in 212 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 Browser team meeting notes 13 May 2019
by Georg Koppen 15 May '19

15 May '19

Hi! We had the weekly Tor Browser meeting on Monday. Here come the link to our IRC meeting log: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-05-13-17.31.l… and the notes from our pad: Discussion: - Monthly Tor/Mozilla meeting is tomorrow morning - Did we get the donate button/assets for the next Browser release? (GeKo: no, however we have #30497 now) mcs and brade: Last week: - Discussed PT args encoding in #29627 (Moat: add support for obfsproxy's meek_lite). - Opened #30442 (PT spec: should 255 bytes be sent in the RFC 1929 UNAME field?) - Revised our patch for #28044 (Integrate Tor Launcher into tor-browser). - Worked on #30000 (Integrating client-side authorization to onion services v3). - Experimented some more with Arthur's old v2 auth patch from 14389#comment:15. - Discussed control port event vs. SOCKS or HTTP CONNECT error code on IRC, in #14389, and in child tickets. - Responded regarding time estimates / roadmap. - Commented in #10760 (Integrate TorButton to TorBrowser core). - Code reviews. - Booked flights for travel to the Stockholm meeting in July. This week: - #30000 (Integrating client-side authorization to onion services v3). - investigate possible use of new SOCKS5 error codes for integration with tor. - continue discussions with Network Team. - review UX proposal in #30237. - Submit peer and team lead feedback. - We will be out of the office Wednesday and Thursday (15 and 16 May). boklm: Last week: - fixed/disabled some testsuite tests - helped with published releases - fixed #30448 (Strip Browser/gtk2/libmozgtk.so) - reviewed #30377 (Remove selfrando from our build system) - started working on #28672 (Android reproducible build of Snowflake): - go is now building - currently trying to get webrtc building This week: - continue work on #28672 (Android reproducible build of Snowflake) - look at remaining failing testsuite tests - make a patch for #30480 (rbm should check that a signed tag object contains the expected tag name) - review #30319 (Drop FTE related bits in Tor Browser) - help with building new releases - will be afk on Wednesday - submit feedback sysrqb: Last week Finished creating Tor Browser APK Signing key (#26536) Finished code-review of "Tor Browser" renaming on Android (#30136) Finished code-review of torbutton localization on Android (#30069) Looked a little bit at control port issue on Android (#30284) Some BridgeDB things This week F-Droid deployment (#27539) Mozilla bugs (1480877, 1478438) Remaining tbb-8.5-must code reviews and debugging (as needed) Fastlane deployment (#26844) (maybe) Remove remaining Orfox patches (#30036) (maybe, at least before 68esr rebasing) Maybe begin creating final Orfox update (#29955) acat: Last week: Worked on torbutton integration with Tor browser for ESR68 (#10760) This week: Finish #10760 Finish patch for https://bugzilla.mozilla.org/show_bug.cgi?id=467035 If ESR68 beta branch is there, start working on rebasing patches. tjr - Letterboxing improvement: https://bugzilla.mozilla.org/show_bug.cgi?id=1546832 - Got findbar fixed in a local patch; still trying to get a response from people about devtools - Working on Mingw Build Stuff (free time only) - Fix binutils issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1471698 waiting on Jacek to r+ - x86 alloc/free mismatch: need to catch glandium and ask him about it - RDD process doesn't work with mingw-clang - need to write test program - Inching towards enabling some tests for the mingw-clang build on try GeKo: Last week - feedback mails - finished monthly admin work - clean-up (dropping fte (#30319) and selfrando (#30377)) - bump GCC to 8.3.0 for Linux builds (#25930) - work on letterboxing backport (#30372) - reviews ( This week: - release prep - reviews - will be at SIF on Thursday and part of Friday - feedback mails - more toolchain work: mingw-w64/clang for Firefox (#28238) pili: Last week - GSoD admin duties - Roadmapping This week - Looking into gitlab instance (dip.tpo.org) - dev meeting planning sisbell: Last Week: - #30324 - Update Android Toolchain for 68 ESR (completed this), will check in tomorrow after verifying it works with other projects. - Started reviews for tor-android-service issues: #30483 - JCenter Repo, #30489 - Remove unused resources from tor-android-service, #30484 - Upgrade Android Plugin, #30166 - custom bridges - Opened PR to cleanup resources in Orbot This Week: - Investigate KitKat Failures for starting tor (tor works with Orbot implementation) #30284 - Move delta in latest Orbot code to tor-android-service, open issues - #30460, #30461 Use new Android Toolchain pospeselr: Last week: - widl work - found yet more bugs, though it doesn't look like they are blockers for us - worked around more discovered complications, but a fix for the main issue should be reviewable today or tomorrow, with smaller fixes following for remaining issues - finally got Phabricator working for submitting mozilla patches, #1506693 in review again This week: - review emails antonela Last week: - Worked on #29955 - Orfox > TBA - Filed #30456 - Better bridges for TBA, could work for TB Desktop too This week: - #30024 - #30497 - `about:tor` Donate link Georg

1 0

Network team meeting, 13 May 2019
by Nick Mathewson 13 May '19

13 May '19

Hi! We just had a meeting. Logs are at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-05-13-17.00.html Meeting pad contents are below: = Network team meeting pad! = This week's team meeting is at Monday 13 May at 1700 UTC on #tor-meeting on OFTC. May schedule: * Monday 6 May at 1700 UTC * Monday 13 May at 1700 UTC * Monday 20 May at 1700 UTC * Monday 27 May at 1700 UTC June schedule: * Tuesday 4 June at 2300 UTC * Monday 10 June at 1700 UTC Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 25 Mar: https://lists.torproject.org/pipermail/tor-project/2019-April/002280.html 2 Apr: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-04-02-23.00.html (we forgot to post the notes) 8 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002289.html 15 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002296.html 23 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002308.html 29 Apr: https://lists.torproject.org/pipermail/tor-project/2019-April/002310.html 6 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002316.html == Stuff to do every week = * How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… * Let's check the 0.4.0 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… Click on 'all boards' and then the network team one. Filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… . * See discussion notes below. Any blocker from last week? == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. * Remember to fill in the doodle for monthly retrospective https://doodle.com/poll/8xhmkm3zqmzdg8pe ------------------------------- ---- 13th May 2019 ------------------------------- == Announcements == - The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0. We need to prioritize 0.4.0 fixes and reviews in April, because stable was due on 15 April. == Discussion == Rotation updates: Bug triage - ahf to asn The Bug Triage role description and queries is on the wiki at: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… I think I've left all our triage queries as empty as of Monday. CI - catalyst to dgoulet https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… Jenkins tor-ci-freebsd-amd64-0.2.9 seems to have been broken for a while, but maybe the FreeBSD builds don't automatically build anymore? Coverity - catalyst to dgoulet [In other news, coverity scan seems to have TLS issues that are keeping nick's automatic updates from working. If anybody can provide a correct incantation to "curl https://scan.coverity.com/ " in a way that works, that would rock. -nickm] new CID 1444999 https://trac.torproject.org/projects/tor/ticket/30467 -- fixed by dgoulet new CID 1444999 https://trac.torproject.org/projects/tor/ticket/30458 -- low priority? Tor meetup in July: do we need 1 room for the network team for 1 whole day? Retrospective, roadmap, any other session that may not be shared with the rest of Tor? How do we handle our freeze and freeze period? Nick has suggestions: Let's default to "if a feature isn't needs_review by Wednesday, it isn't going in", with sensible exceptions. If the initial review suggests that the branch is high-risk, we should maybe not merge it, depending on impact. Let's IMMEDIATELY look for MUST items in 041, and try to fix them. Nick will recreate Teor's "040-must" page for 041. We can open 042 early if people are all focusing on 041-must fixes. Please look for 041 problems to fix, or S19 things to do, instead of getting an early start on 042. By default we keep 042 closed for a month, but should look at it fresh each meeting. == Recommended links == "Select male faculty, they said, effectively ran the Institute and were showered with private donations, while women were forced to fire essential staff and were shut out from power." This article is an excellent analysis of the mechanics of power and discrimination: https://www.nytimes.com/2019/04/18/magazine/salk-institute-discrimination-s… On allyship in newsrooms but also in workplaces: https://source.opennews.org/articles/how-be-ally-newsroom/ In github but a bot for assigning reviews: https://github.com/lmarkus/ReviewBot == Updates == NOTE NEW FORMAT! Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: Last week (actual): looked at closed tickets during April. Still a lot of non sponsor work. incorporated net team sponsored projects into Tor planning This week (planned): check sponsor v and 2 work until now check s27 in the network team roadmap Help with: teor: (online for 23 April, then on leave until 21 May) * AFK Nick: Week of 6 May (planned): - Finish up ADL prototype - More refactoring - Work on PTs in chutney? - Lots of reviews and merges - Meetings most of the day on Tuesday - finish up relay-periodic events branch and get it merged, then fill in some gaps from it that would be well suited for pubsub. Week of 6 May (actual): - ADL prototype to mailing list, with comments on prop295. (https://lists.torproject.org/pipermail/tor-dev/2019-May/013804.html ) - Implemented code to make chutney handle bidi connections (#29263) and gracefully detect unsupported configurations (#30459) - Wrestled with confusing chutney travis failures for way too long on #29263. - Lots of reviews and merges and meetings Week of 13 May (planned): - Reviews and merge as top priority - Work on 29024 [PT support in chutney] for obfs4 at least - Freeze 0.4.1.x - Start on (and finish?) an alpha release - Privcount, time permitting - More work on 30414, time permitting, if review happens dgoulet: Week of 05/06 (actual): - Reviews and merges (See timeline). - Work on #26288 child tickets. - Resolve important issue found by armadev about prop289 code: #30428 - While working on the #15516 defenses, find out that #30440 is a big problem so we are falling back to a token bucket approach instead. - Found #30454 issue in the HS code and made a fix for it. - Opened #30466 which is related to #30440. - Did worked hard on implementing a unit test for #26288 but ultimately couldn't achieve it with our current code setup :S. Week of 05/13 (planned): - Rush anything needed for the freeze. In particular, some child tickets in #26288. - Work on the #15516 Plan B which is token bucket rate limit design. - Make progress in #30382 which changed to using SOCKS error. - REMINDER: Will be offline on Thu and Fri. Mike: Week of 5/6 (planned): - PETS stipend, registration, and hotel logistics - Get child tickets of https://trac.torproject.org/projects/tor/ticket/28634 merged or needs_review Week of 5/6 (actual): - PETS stipend - Got child tickets of https://trac.torproject.org/projects/tor/ticket/28634 merged or needs_review Week of 5/13 (planned): - Get child tickets of https://trac.torproject.org/projects/tor/ticket/28634 merged Need help with: - Discuss https://trac.torproject.org/projects/tor/ticket/28780 with Nick, asn some more catalyst: week of 05/06 (2019-W19) (planned): - reviews - CI + Coverity rotation - get #29976 ready for review - peer feedback (2) and team leader feedback - open more bootstrap reporting improvement tickets week of 05/06 (2019-W19) (actual): - more [redacted] - medical bureaucracy - CI + Coverity rotation -- a few new defects; see handoff section - reviews week of 05/13 (2019-W20) (planned): - reviews - #29976 - peer feedback (2) and team leader feedback asn: Week of 05/06 (planned): - Hopefully finalize open WTF-PAD tasks. - Work more on #30381. - Work more on #15516. - Reviews and merges. Week of 05/06 (actual): - Hopefully finalize open WTF-PAD tasks by the 15th. - Finalized #30381 spec work and started coding the control port parts. - Provided (almost) final revisions for the final WTF-PAD branch (#28634), and tested #28780 code. - Discused #14389 with mcs and David. We figured that reviving prop#229 is the way to go. - Discussed #15516 with David and made some plans for future DoS prevention. - Rebased #30236 to master because of some conflicts. - Reviews and merges. Week of 05/13 (planned): - Continue coding #30381 so that we unblock the TB team. - Keep on working on the DoS stuff by the side. - Got lots of reviews for this week. Got a few more last midweek, so I got stuff to do here. - Peer review everything ahf Week of 5/6 (planned): Network team: - Bug triage role. - Look at network team S19 tickets for May after the network team meeting. Anti-censorship team: - Cleaning up Snowflake patches for cohosh/dcf to review. Week of 5/6 (actually): Network team: - Meeting with Gaba and Catalyst about splitting up S19 network team tickets. - Got a lot of help from Nick with Dormant mode questions - Wrote pt-spec.txt patch proposal and initial patch for #28849 (dormant and PT integration) - Got help from Catalyst with understanding #28930 Anti-censorship Team: - Got help from dcf with #28849 spec changes. Misc: - Triage duty. - Submitted request for PETS stipend. Week of 13/5 (planned): Network team: - Finish #28849 when we (PT community and us) agrees on spec changes. - Begin #28930 code. - Rebase #29736 code on top of master and see what is missing. Misc: - Submit peer review to people's respective team leaders. juga(offline): Week of 05/06 (plan) - Add Tor version to the bandwidth file (#30196) - Most headers non-compliant with spec (#30373) Week of 05/13 (actual) - Revised Add HeaderLine to the bandwidth file specification (#30311) - Revised Refactor header constants in sbws to use Stem's one (#30406) - Added patch for Most headers non-compliant with spec (#30373) Week of 05/20 (actual) - Continue with #30311, #30406, #30373 as needed Help with: - Question: basted would start running sbws 1.0.1 (Tor 3.5.8) later this week if nobody sees a problem with it

1 0

Tails report for April 2019
by sajolida 13 May '19

13 May '19

Releases ======== * Tails 3.14 is scheduled for May 21. Code ==== - The Foundations Team met for a sprint focused on porting Tails to Debian 10 (Buster): https://lists.autistici.org/message/20190408.075929.1c2952c0.en.html https://lists.autistici.org/message/20190429.091241.82e34497.en.html - We finalized our criteria for including dictionaries, fonts and language packs, which will be reflected in Tails 3.14. - We prototyped a USB image with Secure Boot support and GRUB, in order to better understand what implementation difficulties we should expect. - We submitted to ikiwiki upstream a branch that makes it keep PO files up-to-date for a set of languages that are not ready to be enabled and visible on the live website yet. This will allow us to merge into our main Git repository changes made via our upcoming Weblate-based translation platform, which supports languages whose work-in-progress translation is not ready for prime-time yet. https://ikiwiki.info/todo/_Add_ikiwiki_PO-Plugin_to_ignore_languages/) - We uploaded to Debian a few fixes for regressions in the GNOME on- screen keyboard. https://tracker.debian.org/news/1038188/accepted-gnome-shell-3302-6-source-… Hot topics on our help desk =========================== 1. Some users reported loosing the access to their persistent volume https://redmine.tails.boum.org/code/issues/10976 2. A few reported the "USB stick becomes unbootable boot after first boot" issue https://redmine.tails.boum.org/code/issues/16389 3. Some issues caused by partially applied incremental upgrades https://redmine.tails.boum.org/code/issues/14754 Infrastructure ============== - The Foundations Team started experimenting with GitLab for merge requests. https://salsa.debian.org/tails-team/tails/merge_requests/?scope=all&utf8=%E…). - We started looking into how GitLab could work for our issues tracking and drafted a rough plan. https://tails.boum.org/blueprint/GitLab Funding ======= - We started working on a proposal for Mozilla Open Source Support Awards. https://www.mozilla.org/en-US/moss/ Outreach ======== Past events ----------- - sajolida, moire, and emmapeel were at the [Internet Freedom Festival on April 1-5 in Valencia, Spain. There, sajolida presented a workshop on "Creating usable tools from day one with paper prototyping" https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/cus…). - carlosm2 (@dospesosinc) held 2 workshops about Tails in Mexico: - On April 13 at the Colima Hacklab https://twitter.com/dospesosinc/status/1115675448753573888 - On April 25 at UNAM, Ciudad de Mexico https://flisol.acatlan.unam.mx/ - There was a Tails workshop on April 27 in Vienna as part of the Anarchist Black Cross festival https://abcfestvienna.noblogs.org/post/2019/04/11/tails-workshop-saturday-4… On-going discussions ==================== - We studied and narrowed down our options regarding the future of Electrum in Tails. It seems there will be a way forward, although it's unclear at this point how much effort it will require from us. https://lists.autistici.org/message/20190429.094536.22d3598f.en.html Metrics ======= * Tails has been started more than 733 234 times this month. This makes 24 441 boots a day on average. -- sajolida

1 0

Notes from May 9 2019 Vegas team meeting
by Karsten Loesing 13 May '19

13 May '19

Notes for May 9 2019 meeting: Arturo: 1) Wrapped up the MOSS related work for OONI Explorer and defining the roadmap for the public launch 2) Spoke about OONI in DC at an event by the USAGM: https://www.usagm.gov/2019/05/07/media-for-democracy-forum/ 3) Preparing OONI Probe mobile 2.1.0 release 4) Planning upcoming work on OONI Probe Desktop: https://github.com/orgs/ooni/projects/4 Gaba: 1) worked on blogpost for moz grant research 2) talked and started writing a proposal with ggus for APC (that it turns out we are not going to apply now) 3) time allocation for sponsors 4) finalize team planning document 5) attended part of csvconf yesterday 6) peer reviews Steph: 1) Press inquiries: Answered questions about the CIA’s onion service 2) Working with organizers and managing the eventbrite page and tix for the upcoming Tor talk/fundraiser connected to Ethereal Summit. Will help with Roger's slides 3) Published a post on the Mozilla Research Grant w help from Gaba 4) Getting ready to be ooo May 23-June 11 5) Will submit for Roger to do another ama at the crypto and privacy def con village 6) Planning for upcoming comms campaigns including t-shirt discounts, story pitches, next TB launch 7) Looking into a collab at upcoming Blockchain event Sarah: 1) Sponsors newsletter went out yesterday. 2) Monthly giving page should be live today and I'll start inviting past donors to convert to monthly giving. 3) Al submitted proposal to Craig Newmark Philanthropies for $50k of general operating support. 4) Submitted proposal to Deer Creek Foundation for $50k for general operating/comms funds. 5) Organizing vintage swag promotion for social media. 6) Creating appeal for newsletter subscribers who have not yet donated to get the sticker pack for a discounted $17. 7) Peer reviews. 8) Travel arrangements. Pili: 1) Finished off first draft of S9 Workplan 2) Mailing list moderation 3) Finally finished of S27 roadmap! 4) Working on other sponsors and work time allocation 5) Started setting up 1:1s with community team members 6) Helping with OTF Fellowship proposal 7) Replying to Google Season of Docs enquiries Georg: 1) Fun with Mozilla emergency releases 2) Tor Browser 8.5 gets delayed due to those releases (we plan to start building 8.5 next week) 3) Getting tickets sorted for May work 4) More HackerOne (Sue: could you please wire the 1.000 USD, thanks! - yes I did not do disbursements last week and it is included in this week's disbursements-SA) and other organizational tasks 5) feedback mails 6) Generally struggling to keep up with doing ALL the things Mike: 1) Wrapping up 0.4.1 things for sponsor2 Antonela: 1) made a meeting with OK Thanks. They are working on Onion Browser with Guardian Project. 2) shared the Mozilla Grant with academic researchers interested in usability. 3) working on OTF #30029, #30024. 4) coordinating User Research in Mexico with flexlibris, reviewing nah's reporting from Q2, Caroline's reporting from Q1, organizing next travels. 5) sent Personas to the UX list for feedback. 6) closed OONI Explorer for the sponsor, roadmapping OONI Explorer stable release. 7) writing peer-reviews. 8) worked on some fundraising needs. Sue: 1) general accounting procedures Erin: 1) general HR stuff 2) reminder: peer and team lead feedback is due next Friday, May 17 Nick: 1) all's well on network team 2) reminded team about booking travel. Do we have a list of people who are not yet booked?

1 0

Communications Report: April 2019
by Stephanie A. Whited 10 May '19

10 May '19

Hello Tor, Last month, we started preparing for a small fundraising event coming up next week in NYC: https://www.eventbrite.com/e/building-private-censorship-resistant-tech-a-c… We also continued making preparations for our DEF CON booth in August. I've also been helping coordinate a couple of other talks. We've been advocating for Ola's release. We were featured in Mozilla's Internet Health Report. We worked with the fundraising team on donor communications. April in links and stats: Blog posts https://blog.torproject.org/ecuador-free-ola-bini https://blog.torproject.org/google-season-docs-2019-help-tor-improve-our-do… https://blog.torproject.org/how-bandwidth-scanners-monitor-tor-network https://blog.torproject.org/collecting-aggregating-and-presenting-data-tor-… Twitter https://twitter.com/torproject New followers: 4,101 Top tweets: https://twitter.com/torproject/status/1117802702489235458 https://twitter.com/torproject/status/1113471748253659136 https://twitter.com/torproject/status/1116692285977182209 Mastodon https://mastodon.social/@torproject New followers: 300 Instagram https://instagram.com/torproject New followers: 286 LinkedIn https://www.linkedin.com/company/tor-project/ New followers: 171 Facebook https://www.facebookcorewwwi.onion/TorProject/ New followers: 607 Newsletter https://newsletter.torproject.org/archive/2019-04-30-advocating-for-anonymi… Notable press https://internethealthreport.org/2019/in-defense-of-anonymity/ o/ -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Fingerprint: E976 9771 7D46 2E63 9697 9F6D 6D6B 72C3 39A8 76AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

April 2019 report for the sysadmin team
by Antoine Beaupré 10 May '19

10 May '19

Hi, Here is our report for April 2019 in sysadmin land, enjoy! A. -- Drowning people Sometimes die Fighting their rescuers. - Octavia Butler

1 0

April 2019 report for the UX team
by Antonela Debiasi 10 May '19

10 May '19

Hey Tor, April found us spreading glitter at the Internet Freedom Festival. We shared a lot of sessions with the Community Team, we spent valuable time with our founders and also we met with old and new friends. We ran some talks, table time and meetups, you see them here https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Valencia We provided our new outreach material in 3 different languages. Soon, it will be available for download at the new community portal, which is a work-in-progress: https://lektor-staging.torproject.org/community After torproject.org release, we worked on some short iterations of the download page, and we fixed some hot bugs. Also, we released it in two more languages: Icelandic and Georgian. The community team traveled to Colombia during April and Narirral (nah), a researcher from Brazil, joined ggus to run usability studies over Tor Browser desktop in Spanish with our community members. We released OONI Explorer Beta, and we are planning what we should prioritize for the stable version, in June. You can see our open tickets here https://github.com/ooni/explorer/issues?q=is%3Aopen+is%3Aissue+label%3AUX We kicked off our S27 work to make Onion services more accessible and usable. The network team is working on a feature that allows onion services admins to set up an authentication key for accessing the service. The end-user facing part for this feature is the client authorization. We are creating this user interface following Mozilla Photon design system. https://trac.torproject.org/projects/tor/ticket/30237 Thanks, A -- Antonela Debiasi UX Team Lead @antonela E2330A6D1EB5A0C8 https://torproject.org

1 0

April 2019 report for the Tor Browser team
by Georg Koppen 10 May '19

10 May '19

Hi everyone! Here comes the April report for the Tor Browser team (a bit late this time, but hey!). In that month we got Tor Browser 8.5a11[1] out which above all contains improvements for Tor Browser for Android stabilizing the alpha release and preparing for the first mobile stable one. Unfortunately we did not manage to get Tor Browser 8.5 out in April, thus this will happen in May. However, we made progress on a number of other fronts: We got up to speed on our Sponsor 27 tasks and started investigating different options for reporting onion service errors back from tor to the browser[2][3] and we started to work on Snowflake integration into the mobile Tor Browser[4]. Both sponsor work will keep parts of the team busy in May as well. Moreover, we started to plan our upcoming Firefox 68 ESR transition work. The full list of tickets closed by the Tor Browser team in April is accessible using the `TorBrowserTeam201904` keyword in our bug tracker.[5] In May we'll finally release Tor Browser 8.5. That will not only be the first stable release for Android users but will have restored full accessibility support for Windows users, too[6]. Moreover, we hope as well to finish our Snowflake integration on Android to have additional capacity to work on the first big tasks for the Firefox 68 ESR transition: toolchain updates for all supported platforms[7] and rebasing our patches and upstreaming them if possible[8]. All tickets on our radar for this month can be seen with the `TorBrowserTeam201905` keyword in our bug tracker.[9] Georg [1] https://blog.torproject.org/new-release-tor-browser-85a11 [2] https://trac.torproject.org/projects/tor/ticket/14389 [3] https://trac.torproject.org/projects/tor/ticket/30382 [4] https://trac.torproject.org/projects/tor/ticket/28672 [5] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [6] https://trac.torproject.org/projects/tor/ticket/27503 [7] See: https://trac.torproject.org/projects/tor/ticket/30320 and child tickets [8] https://trac.torproject.org/projects/tor/ticket/30429 [9] https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~Tor…

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project