tor-project February 2018

tor-project@lists.torproject.org

14 participants
26 discussions

community team January update!
by Alison Macrina 14 Feb '18

14 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Tor folks, check it out: January 2018 Community Team report Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Cu rrentTeamDiscussions Support and translation ================================================================== Colin worked on fixes for some webml issues with Transifex and the old website, and continued on translation work for the new support portal. We added even more content to the soon-to-be-live support portal. Our Outreachy intern Pari released the January user issues doc: https://storm.torproject.org/shared/XuN4uMdY0Y6vm6G1vOZs0bx9mmRtq-MpSgKo a6WSKLJ Colin has also been working with Localization Lab and the Tor Browser team to get more languages added to the browser. Relay operator love ================================================================== We continued work on the Tor Relay Guide (#24497 and here https://trac.torproject.org/projects/tor/wiki/TorRelayGuide). We're still working on letters of interest to funders who might want to help us support growing the network of relays. Tor talks ================================================================== Sukhbir gave a Tor talk at the Alternative Law Forum in Bangalore, India . Sukhbir gave a Tor talk at the Toronto Public Library in Toronto, Canada . Alison gave a Library Freedom Project talk at the University of Washington in Seattle, USA. Alison gave a Library Freedom Project talk at Georgetown University in Washington DC, USA. A bunch of us worked on plans for the NYC Tor Meetup that will happen on February 15. Library Freedom Institute ================================================================== LFI application recruitment continued through January. We also worked on drafting the schedule and recruiting guest lecturers. Tor Meeting ================================================================== We finalized the location for the end of 2018 Tor Meeting -- Brazil! We analyzed survey feedback from Montreal to make improvements for the upcoming Rome meeting, and we did some other prep work for Rome. Community governance ================================================================== Discussion of the code of conduct text continues on tor-internal@! ================================================================== - -- Alison Macrina Community Team Lead The Tor Project -----BEGIN PGP SIGNATURE----- iQJKBAEBCAA0FiEE+/Dn2xQzAY7lLQ3an8NAicvoPKMFAlqEmdcWHGFsaXNvbkB0 b3Jwcm9qZWN0Lm9yZwAKCRCfw0CJy+g8ozEtD/4qZQYsWAMewqZO1P1QPOgx7g3A PjB6HXCndFoL/5zm/qLJhq25aiSgHjcOgjp5Fg++6Jb1fE5lAG+f4F75NqWX2k2Y OEY2765r8unxcVwWJg0WnsmcgIgIxOvy5ScFV2ywXnqRuePYUzhjcbboIvx/Ee9B wsZB7LvWz7Z343P88RqCzLWY018zYw3kvCtKoOXSgJH2P49sgYWTiUfrH5uPvi04 Hf8Cemd4andqdjdlHTcZDnYPRSqp5Zm4JJotB07vK2wdWIKHaapEtNB2T8wRGwPm /njLxTUIluJQ31Zm2yLPL3smfgTH/Hjf7MGPPsyLNnehK5bVy53LKQHkDwPHfKFd ekYL3GwAPrLM48XRLfrphHKv1xlnjlv1CSxIjOt0MZAFD4Q/B90iw5U+W3FLWIMQ xsMRJip0f4wNbzHr2eeSIlmtfgFD4JN7/uQhoxTdHYYxTzVtrPcHiQK8k4XiRc7X CJfXUKg1IsLe9/7h5zFEMUCJB5CjBveVA59usUt5uQ9kq0PKc4KRqQpIOW7S9Cc9 4NSartZwzVo9vELSTYAKOGAIc9Rk1cqitTTEkR/5Pb2JILhUpkll91yjlkm3G/28 9NUQXqoLDehC7sViv00qOgbjL/LAGTDdZ6x+MIgf0WmgSVR5khKi+axTrdJ+oISX kIO5kcPYh2g3NvSfqQ== =G5YX -----END PGP SIGNATURE-----

1 0

UX Team January 2018 report
by isabela 13 Feb '18

13 Feb '18

The UX team is cooking with gas in 2018!! We did a lot of work this January, and are preparing to share a lot with the community during the Rome Meeting. Keep an eye on the meeting schedule to know when and what o/ We will also be at IFF doing user testing on March 6 (at the tabling thing they will have) from 2-4pm. Here is some really cool stuff we did in January: User Testing in India ===================== - Helped organize Tor Meetup Mumbai 18 - together with Sukhbir and Tor community folks. https://blog.torproject.org/secure-communication-gaining-momentum-india - At the Mumbai Meetup we did somem user testing of .onion services and Tor Launcher Tests methodology and scripts can be found here: https://docs.google.com/document/d/1KdnEsAlXdkQT4EBsRUAEgzqz5lkdmjNBUB29YfE… - We now have our own survey tool which was deployed and tested at meetup in Mumbai This tool will be very useful to collect user feedback. https://survey.torproject.org (also exist as a .onion service!) Website ======= Styleguide - Our styleguide is done! https://styleguide.torproject.org - We also added icons we created for metrics team to it - see ticket #24664 for more info. - Next is to tell the world it exist! Support Portal - Desktop UX/UI is done. Waiting for translations. - Support mockups for Mobile are on development -> https://marvelapp.com/3i2hggg/screen/37876933 - Support portal coding 90% completed. Fixing usability issues and bugs Comms Portal - We start to design our community.torproject.org portal, you can find links to our mocks at the ticket #24133 Collaboration with other teams ============================== Tor Browser - #24918 was updated with some suggestions on how to present the new location of Circuit Display on Tor Browser desktop. https://trac.torproject.org/projects/tor/ticket/24918#comment:3 (this work is still in progress and we are doing another round in Feb) - We worked with the Tor Browser team on the UI for Moat on Tor Launcher, more at #24696 - Tor Browser 7.5 was released!!!! https://blog.torproject.org/tor-browser-75-released Major UI updates on this release, check out the blog post with gifs (if you haven't seem it in your browser yet!! and you should update it then :P) Metrics - Worked with irl on icons for metrics team to use to communicate what the data is about, This is now deployed. https://trac.torproject.org/projects/tor/ticket/24717 Comms team - Created some covers for Comms <3 https://blog.torproject.org/news-orgs-activists-onionize-your-sites-against… https://www.dropbox.com/s/izj7tho5c0i1az0/relays-guide.png?dl=0 https://www.dropbox.com/s/z4vio4xmb9n6oil/volunteer-spotlight-2%3A1.png?dl=0 Gracias y hasta la proxima o/ cheers, UX Team

1 0

Network team meeting notes, 12 Feb 2018
by Nick Mathewson 12 Feb '18

12 Feb '18

Hi! You can find logs from our IRC meeting today at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-12-17.58.html The contents of our pad are below: ======== Network team meeting pad, 12 Feb 2018 These days I use her real name But I don't dare to mention it. She hides from cameras. And now I've gone and put her in a poem. -- Wendy Cope, "Omo" Welcome to our meeting! Mondays at 1800 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Meeting notes from previous weeks: * https://lists.torproject.org/pipermail/tor-project/2018-January/001644.html * https://lists.torproject.org/pipermail/tor-project/2018-January/001647.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001654.html Old Announcements: * 0.3.3.x is in feature-freeze. No new features (except for #24902, which has permission.). * No 0.3.4.x patches will be merged till the window opens on Feb 15. * Please, work on bugfixes! It would be great to have this release release on time. (Planned date is 15 April) * There are tons of tiny 0.3.3.x tickets. Maybe if you can do one of them in <X minutes for some small X, you should just do it? * May hackfest has been approved by Shari. dgoulet, teor, and isabela are organising it off-list. See the network-team list for updates. Announcements: * 0.3.3.2-alpha came out Saturday. * Review-group-32 is open! There are 17 tickets for us to review. https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * Meeting today (2100 UTC) to discuss UTF-8 proposal * No GSoC for Tor :'( [this time] * We moved the hackfest 2 days later (Wednesday 30th - Sunday 3rd) to avoid clashing with Memorial Day Discussion: - any questions about areas of work for our roadmap planning - please review and give feedback / trying to close this by friday feb 16. (Let's review it again!) https://pad.riseup.net/p/LMxcQxvWOvzz-setofareas - 0.3.3 wrapup - 0.3.4 opening ====== Nick: * Last week: * Alpha release of 0.3.3.2-alpha. * Started taking a class about Coq [isis: COOL] * Tons of release-engineering, ticket triage, etc. * Tried to work on numerous small bugs * This week: * Many meetings. * Lunch with Isabela on Friday * Try to get all important stuff backported to stable releases * TROVE-2018-001 * Work on sleep/wakup auditing. [ ahf: I'm doing some experiments with Shadow on this right now - maybe we should talk about joining forces here? ][yes,let's talk for a couple minutes right after this? -nm][ ahf: WFM ] * Open 0.3.4 merge window? [asn: sounds good] [dgoulet: +1, on schedule :)] * Try to finish identifying all must-fix issues for 0.3.3. Please help. [dgoulet: Do you prefer a keyword or we tell you which one we think are must fix or ... ?] [asn: we are also done with review-group-31] dgoulet: * Last week: - Did some roadmap brainstorming with isa/asn - Hackfest in Seattle logistics. - DoS mitigation released (woot!). Final work needed for that was in #25193 along with work nick did in #25183. - Triage and commented on 033 tickets. - Some patches for other 033 tickets can't recall them all (see timeline). - Perf analysis of 033 busy relays. #25152 is a ticket resulting in that investigation. I think 033 is in good shape in terms of CPU cycles. The DoS mitigation doesn't seem to be affecting performance much. Timeline: https://trac.torproject.org/projects/tor/timeline?from=Feb+12%2C+2018&daysb… * This week: - Work on 033 tickets. - I have big patches for 034 in the scheduler so I'm aiming to get them in needs_review very close to when the merge window opens in 3 days. - <whatever comes up this week> isabela: - last week: - sent sponsor8 Q4 report finally o/ - sent a proposal for roadmap(s) planning to the list, please see discussion point above regarding the areas of work exercise/list creation - this week: - finalize areas of work w/ team - notify network testers - start preparing for next phase of roadmap(s) planning - lunch w/ nick on friday ahf Last week: Sponsor 8: - Did some data collection for Isa for the Q4 2017 reporting. - Wrote a log collection script for MainLoopStats log messages (from #24605). - Got Shadow to run with 0.3.2 with the patch from #24605. Misc: - Did some bug triaging for 0.3.3 bugs, moved bugs ahead, closed some duplicates. - Reviewed: #24909, #25162. - Landed fix for: #25120. - Added two possible solutions to #22926 - one was rejected, the second one might be better. - Weekend project: Wrapped my head around Tor's PT implementation and wrote a Quic PT -- was a fun exercise. Next step is to get the source IP change (roaming) feature to play nicely. This week: Sponsor 8: - Go over S8 roadmap tasks. - Wrap my head around using Shadow for all experiments where it is suitable for reproducible results. - Continue memory optimization work. isis: last week: - added extra logging temporarily to the bridgedb server on polyanthum to attempt to debug the remainder of #24432 - fixed a rust memleak #25127 and then never-going-to-happen-but-if-it-did rust FFI panic!() UB - we should maybe be compiling our rust code with `-C panic=abort` to avoid unwinding across FFI? not sure - tried to make utilities for working with static strings across the FFI boundary #25185 - transfered moat google appengine account to TPO ownership - continued a bit of work on organising how the large create cell code should be implemented #24986 - led a proposal meeting for consensus hash chaining prop#239 - began scheduling proposal meetings for prop#267 prop#245 and prop#242 - reviewed the openssl 1.1.1 patches #24978 this week: - more of #24986 - moat debugging / probably writing SQL statements by hand to transfer the "unassigned" bridges to be assigned to moat - going through the appengine instance to try to document how to set one up :/ - more proposal meeting scheduling - prop#285 "make directory documents be utf-8" meeting today at 13:00 PST (starts three hours after this meeting starts) teor: * Last week: - Implemented and tested more Experimental PrivCount onion service stats - Merged the DDoS fixes into Experimental PrivCount, they work well so fat (so fattt!) lol - May hackfest planning - Ticket triage - Proposal meetings - More planning for floating point tests in Rust and C, no code yet [isis: lmk if i can help with anything!] * This week: - Final Experimental PrivCount features - Eventually make a trac user page that lists the tickets I'm working on in priority order - I should get time to review or revise more tickets next week asn: Last week: - Helped isa with roadmapping. - Worked some more on removing guardfraction from the codebase. And prepared some branches: #24456 - Triaged 033 tickets on prop224, tor-hs and tor-guard keywords. Moved some of them on 034, others need further work. - Did some more digging on a skeleton prop#279 implementation. This week: - More work on roadmapping. - Help out with 033 releases and do reviews/bugfixes as needed. - Figure out rome flightplan. catalyst: Last week (2018-W06): - travel arrangements for Rome meeting - Rust protover leak fix review (#25127) yay, master builds on Travis again! - read some more about Rust FFI to help with #25127 - some s8 bookkeeping for isabela - reviewed #25120 (log getrandom failure more quietly) - responding to CoC and SoV feedback - still slowly recovering from this cold This week (2018-W07): - Travis is currently broken on 0.3.2 due to check-changes https://api.travis-ci.org/v3/job/340488056/log.txt - review more Rust cstr stuff - work on some 0.3.3 bugs - CoC and SoV feedback as needed Mike: Last week: - Booked tickets to rome! - Wrote patch for #24769 - Reviewed #22212 - Coordination with Matt Wright & co re adaptive padding in tor-core - Reorganzing and refactoring vanguards repo for easier packaging This week: - More vanguards repo work

1 0

Report on the FOSDEM relays meetup
by Nicolas Braud-Santoni 10 Feb '18

10 Feb '18

Hi, I facilitated the meetup at FOSDEM, last Sunday, and I wanted to report back on what happened, and what worked (or did not). We had around 20 people, with relatively little overlap with the 34C3 meetup (I could be wrong, though, as I'm bad at recognising faces). This seems quite good, esp. considering that the 34C3 meetup was a month before, and that the meetup wasn't announced especially early (we announced ~2 weeks in advance there would be one, but the time and precise location couldn't be fixed until Sat. morning) The room configuration wasn't exactly ideal (typical lecture room, not great if you want people to talk to one another). That's something we can probably improve next year, by organising the meetup at a side-event (say, on Friday early evening) at one of the local hackerspaces or somesuch; this way, we get a better location and we could communicate time & locations much more in advance. Communication-wise, I started publishing the events in blog.tpo (thanks hiro!), which seems to have helped some people; if we organise it as a side-event next year, we shoudl also get it on their website: https://fosdem.org/2018/fringe/ Content-wise, there were some pretty fruitful discussion, but we spent quite a bit of time on questions that recurr at other meetups too: - What's the most useful thing I can bring to the network? (TL;DR: Ideally, fast relays (if possible exits); if you can't contribute more than 1MB/s, make it a bridge) - Can I run my relay on a Raspberry Pi (or similar) ? - Why does my relay (or Internet connection) die once I have TLS connections established to most other relays? (This instance was likely caused by an ISP-provided router with bad TCP connection tracking.) - Why doesn't Tor support IPv6 yet? (Feel free to add more questions if I forgot some here) Those are all somewhat simple, and I think we would definitely benefit from having better, and more visible, FAQs for those. I will try to take the time and make/improve wiki pages for those, but I wouldn't mind some help from one of the website-makers to see how we can make it more visible. Getting people to ask a bunch of questions at the start, and broadly categorizing them, as suggested by Roger last meetup, seemed to work well: we managed to cover all topics people were interested in, and were only 20 minutes over time. However, I had people shortly introduce themselves before adding their question, and that might not be so good in retrospect, as the intros took a bunch of time, and might have been an obstacle to people suggesting more questions. If people are interested, I can start collating advise on how to facilitate tor-relays meetups in some wiki page, though I'm not sure yet how to convey that “nicoo's way of relays meetup” isn't meant to be authoritative or prescriptive at all (read: I have no clue what I'm doing, but hopefully it works not too bad.) Best, nicoo

1 0

January 2018 Report for the Tor Browser Team
by Georg Koppen 09 Feb '18

09 Feb '18

Hi all! This is the first report of our work we did in 2018. This month we released a new major Tor Browser stable, 7.5[1] and the first alpha in the 8.0 alpha series, 8.0a1[2]. We made major improvements into our 7.5 series regarding our bootstrap process which should make it much easier for users to customize their settings in case they need bridges to circumvent censorship. Additionally, we finally enabled content sandboxing for our Windows builds and fixed some annoying bugs sandboxing related bugs on Linux that prevented the "Print to File" option from working. Tor Browser 7.5 is the first release with a stable Tor of the 0.3.2.x series (0.3.2.9) which makes it possible to reach v3 .onion services with Tor Browser from now on. Apart from getting the new release out we worked in a number of non-release areas: we finally completed the deployment of our own Panopticlick-like fingerprinting measurement tool, FPCentral[3], and are currently investigating how to tie it closer to our regular quality assurance means. On the mobile side we further worked on integrating Orfox and the additional mobile patches into our tor-browser git repository[4] and started the Torbutton and TorLauncher port with proposals on how to do that.[5][6] Feedback and concerns are still very welcome! The full list of tickets closed by the Tor Browser team in January is accessible using the `TorBrowserTeam201801` keyword in our bug tracker.[7] In February we hope to have Moat ready to be deployed in an alpha release and plan to pick up the latest Tor 0.3.3.x-alpha for further testing. Moreover, we have UX work going on to redo our circuit display[8] and a proposal to redesign our security controls is currently under discussion.[9] Please join we'd love to hear your feedback and ideas! Additionally, the work on Tor Browser 8.0 has begun which means our annual patch rebase to a new Firefox ESR version is under way[10] and efforts to upstream as many of those patches to Mozilla have begun and will continue during February. All tickets on our radar for this month can be seen with the `TorBrowserTeam201802` keyword in our bug tracker.[11] Georg [1] https://blog.torproject.org/tor-browser-75-released [2] https://blog.torproject.org/tor-browser-80a1-released [3] https://fpcentral.tbb.torproject.org/ [4] https://bugs.torproject.org/19675 [5] https://lists.torproject.org/pipermail/tbb-dev/2018-January/000723.html [6] https://lists.torproject.org/pipermail/tbb-dev/2018-January/000735.html [7] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [8] https://trac.torproject.org/projects/tor/ticket/24309 [9] https://lists.torproject.org/pipermail/tbb-dev/2018-February/000756.html [10] https://lists.torproject.org/pipermail/tbb-dev/2018-January/000749.html [11] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

Notes from February 8 2018 Vegas team meeting
by Karsten Loesing 09 Feb '18

09 Feb '18

Notes for February 8 2018 meeting: Arturo: 1) Published a blog post on mining OONI data: https://ooni.torproject.org/post/mining-ooni-data/ 2) Correcting more assignments submitted from the participants of the upcoming OONI workshop we'll be doing in Uganda 3) Started trying out, as an alternative path for the upcoming OONI Probe desktop apps, using golang. See: https://github.com/openobservatory/gooni 4) Established new partnerships with IPYS Venezuela and with ADC Argentina Alison: 1) The relay guide is up on the blog and it looks amazing! https://blog.torproject.org/new-guide-running-tor-relay Tons of people worked on this, but nusenu in particular brought it over the finish line. 2) Library Freedom Institute applications are in for the first round. We got 70 applicants for 10 spots! We will announce our first cohort in March. 3) Recruiting many rad guest lecturers for LFI :D 4) It looks like the team meeting day schedule is complete? https://ethercalc.org/zil3cf5nm9ge 5) Sponsor9 job descriptions and workplan -- Isa, do you want to schedule some time to do this/talk about this? 6) Code of Conduct and Statement of Values discussions are still ongoing, so I'm going to keep them open as long as they need to be. 7) a bunch of us met yesterday to plan for HOPE. I'm waiting to hear back from the conference organizers about getting some space for us to do workshops and hang out. 8) Do or Die time for the support portal :) ....double checking the content and testing the heck out of the site 9) preparing to speak at Barnard and at the NYU Tor meetup this coming week 10) Rome Meeting Onion Report/State of the Onion plenary. Do we want to have stations for each team/project, or one big introductory talk where someone from each team talks about the work? Some ideas are in this pad: https://pad.riseup.net/p/Rome-SOTO-plenary Roger: 1) I have an updated plan for my eye that I'm trying out in Feb, in hopes of trying it out in March too. 2) I've been continuing to help with the network overload issues, and dabbling in some Tor tickets. We have some more fixes to do before an 0.3.3.2-alpha can come out, with the ddos defenses in it. 3) On my mind still: job descriptions for relay coordinator, and for Snowflake developer, and for circumvention team lead 4) The Penn circumvention project thing is still on track to happen "soon". 5) I'm off to NYC on Sunday for various Tor speaking things. 6) I'm working to find a way to get to Rome a few days early, to help Isa et al with pre-roadmapping. Georg: 1) Miscellaneous. Karsten: 1) Put out Onionoo 5.0-1.10.0 and .1 with long-expected graph fixes for Relay Search. 2) Started a discussion about publishing bridge contact information on tor-relays@. 3) Merged the CollecTor webstats module, but did not deploy it yet due to newly found memory issues with bulk imports of existing data on webstats.tp.o. Nick: 1) Working on releases. Release engineering has taken over my brain. 2) Continuing education: learning coq via mit subject 6.822. we should encourage others to do continuing education stuff somehow. Shari: 1) Getting ready for board meeting next week. 2) Lots of Rome meeting planning. 3) Editing a number of things for Tommy. 4) Have to get a new budget to Sida. 5) Talking with Laura at DRL later today. 6) Trying to take vacation next week (other than board meeting). isabela: 1) uploading sponsor8 report during this meeting - and talking w/ laura on phone 2) sponsor4 extension was signed yesterday 3) prep work for Rome: - working on prep work for network team roadmap - getting sites mocks done to present in rome - want to propose something to yall - getting support ready to launch before rome - before rome will do a lot of work f2f w ux team in valencia - who can put me in touch w DDG? Steph: 1) Have been sick this week, coming back to life 2) Relay guide post published, in promotion now. Love the image Antonela made for it and am using a slight variation for some social media backgrounds 3) Have a nice volunteer spotlight coming up that Tommy and I worked on 4) Had a check-in with Moz/Tor folks Mike: 1) Dev stuff: Working on making Vanguards script more pythonic and packagable. 2) Research coordination: Coordinating work on Sponsor2 with Matt Wright and co. 3) Getting back on top of our TorBirdy/Thunderbird work so it doesn't fall into total limbo as we wait 100 years for OTF.

1 0

Damian's Status Report - January 2018
by Damian Johnson 08 Feb '18

08 Feb '18

Hi all! Reached some neat milestones this month. Here's my status report... http://blog.atagar.com/january2018/ Cheers! -Damian

1 0

OONI Monthly Report: January 2018
by Maria Xynou 07 Feb '18

07 Feb '18

Hello, The OONI team started the year by monitoring censorship events in Iran and by reporting on them through the publication of a report. We established two new partnerships and we released a new version of the OONI Probe mobile apps, including tests that measure the blocking of WhatsApp, Facebook Messenger, and Telegram. We also made progress in developing the new OONI Probe desktop apps and revamping the OONI Probe mobile apps. # Report on censorship events in Iran Thanks to network measurements collected by OONI Probe users in Iran, we were able to examine the censorship events that were reported amidst major anti-government protests. We published a report based on our analysis: https://ooni.torproject.org/post/2018-iran-protests/ OONI data provides evidence of TCP & DNS blocking of Telegram, Instagram & Facebook Messenger in Iran. # Established new partnerships We are excited to have formally established two new partnerships! We now also have the opportunity to collaborate with: 1. Tuwindi Foundation (Mali) (Announcement: https://twitter.com/OpenObservatory/status/956167750874992645) <https://twitter.com/OpenObservatory/status/956167750874992645%29> 2. Instituto Prensa y Sociedad (IPYS) Venezuela (Announcement: https://twitter.com/OpenObservatory/status/958336497140281345) <https://twitter.com/OpenObservatory/status/958336497140281345%29> As part of our new partnerships, we aim to collaborate on the stable collection of network measurements from local vantage points, the creation and maintenance of censorship measurement resources (i.e. test lists), and on reporting on censorship events. Over the last few months, we have established new partnerships covering 5 countries: 1. Mali (Tuwindi Foundation) 2. Venezuela (IPYS Venezuela) 3. Egypt (AFTE) 4. Sierra Leone (CHRDI) 5. Zimbabwe (Digital Society of Zimbabwe) # IM tests for OONI Probe Mobile We released a new version of OONI Probe Mobile (1.3.0, https://github.com/TheTorProject/ooniprobe-android/releases/tag/v1.3.0%2B21 & https://github.com/TheTorProject/ooniprobe-ios/releases/tag/v1.3.0%2B38) <https://github.com/TheTorProject/ooniprobe-ios/releases/tag/v1.3.0%2B38%29> that adds support for running Instant Messagging (IM) tests. These tests measure the blocking of WhatsApp, Telegram and Facebook Messenger. Announcement: https://twitter.com/OpenObservatory/status/953316589494968320 # Revamping of OONI Probe Mobile We have made a significant amount of progress on revamping the OONI Probe mobile app in terms of iterating on design mockups and implementing some of them inside of a staging branch in ooniprobe-android and ooniprobe-ios. # OONI Probe Desktop App A lot of progress has been done on the OONI Probe Desktop app front in terms of trying out different paths of development and figuring out how to get the CLI tool to speak to the desktop app. We aim to build a Windows prototype of an app for Windows by the end of this month and as part of this try out two alternative approaches for making the desktop GUI communicate to the CLI (a node.js CLI tool vs a golang CLI tool). # Probe Orchestration Specification Audit An architectural overview of the unattended probe orchestration system was audited and reviewed by Cure53. Based on their input and suggestions we will be implementing the OONI Probe Orchestration system over the upcoming months. # Community activities We held a community meeting on 30th January 2018 on the #ooni channel on IRC and Slack (http://slack.openobservatory.org/) <http://slack.openobservatory.org/%29>. As part of the meeting, we discussed the following topics: 1. Accessing OONI data and using it on demand: ooni-sync and data visualization. 2. What features would you like us to be sure to include in the upcoming OONI Probe desktop apps? The log of the community meeting is available here: http://meetbot.debian.net/ooni/2018/ooni.2018-01-30-13.59.html ## Updated test lists Thanks to URLs provided by community members, we updated the following test lists: 1. Nigeria: https://github.com/citizenlab/test-lists/pull/282 2. Uganda: https://github.com/citizenlab/test-lists/pull/283 3. South Sudan: https://github.com/citizenlab/test-lists/pull/287 4. South Africa: https://github.com/citizenlab/test-lists/pull/288 5. Kenya: https://github.com/citizenlab/test-lists/pull/290 6. Zimbabwe: https://github.com/citizenlab/test-lists/pull/291 7. DRC: https://github.com/citizenlab/test-lists/pull/292 # Userbase In January 2018 OONI Probe was run 426k times from 5,656 different vantage points across 212 countries around the world. This information can also be found through our stats here: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research and Partnerships Coordinator 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

Meeting about Tor at HOPE XII
by Alison Macrina 07 Feb '18

07 Feb '18

Hi all, Are you planning to attend HOPE XII? Want to coordinate with other Tor people on talks, workshops, organizing a Tor meetup, or just hanging out? Let's meet about this on Wednesday, February 7, at 1600 UTC in #tor-meeting. See you then! -- Alison Macrina Community Team Lead The Tor Project

1 1

January 2018 report for the metrics team
by Karsten Loesing 07 Feb '18

07 Feb '18

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in January 2018. On behalf of the Tor metrics team, Karsten Gathered first content for specifications for statistical assessment of aggregate data, which is Sponsor 13 deliverable 2 [1]. [1] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor13 Updated format of the News page on Tor Metrics [2], and added support for displaying ongoing events. [2] https://metrics.torproject.org/news.html Made various improvements to Relay Search, including displaying IPv6 addresses alongside IPv4 addresses in the search results, displaying time zones for data publication times [3], aggregated search by version number [4], and added plotting individual relay counts to the map view [5]. [3] https://bugs.torproject.org/24788 [4] https://bugs.torproject.org/6855 [5] https://atlas.torproject.org/#map_relays Shut down the Compass service [6] after integrating its main functions into Relay Search [7]. [6] https://bugs.torproject.org/24445 [7] https://atlas.torproject.org/#aggregate

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project February 2018