- tor-project - lists.torproject.org

NYC meetup notes
by George 14 Dec '17

14 Dec '17

Posting to tor-project@ as recommended: Greetings all. Just a quick note on the NYC event focused on running relays. The goal isn't to build a labor-intensive meetup, but rather to have bi-monthly events which address different aspects of the project's work while simultaneously connecting with different audiences. The meeting was structured with a 20 min or so presentation, followed by over an hour of discussion. The vast majority of people in the room spoke. There was a short wrap-up at the end. At least half the attendees went to the bar afterwards for more discussion, which is a good barometer for the level of interest. The discussion covered a very vast array of topics, from recommended hardware and local ISPs, to how DNS works on the Tor network and consensus, and that great old topic about the life of a relay from birth. A core person from HOPE was there, and we informally got an ok for a free table. At least we're on the radar. There were 22 people in the room, which wasn't bad for the first meeting. The Tor blog post was great to have, as were the posts to relays@ and talk@, but we should figure out how to broaden the reach for the next one. I wasn't personally disappointed, but I assumed the attendance was going to be higher. If we can begin to loosely build networks in a number of locations, we are in a better position to engage the larger community. Local networks could allow the TPO to respond to different external events more effectively, such as a remote censorship crackdown. It could mean, in a place like NYC, having more hands on deck to manage a table at HOPE. It doesn't have to be just in places where there are core TPO people, once a general approach propagates, but people in places like SF, Seattle, Berlin, Amsterdam, Santiago or in university towns should definitely consider at least a one-off event, catered to educated guesses of what would be relevant. But to reemphasize, it's a lot of effort to maintain a full-blown user group with, say, monthly meeting, speakers, etc. We don't have to set the bar so high. Periodic events, without necessarily maintaining any strong continuity between them, is possible since there is such a large critical mass of vaguely Tor-engaged people. Responding to different censorship events, for instance, can be addressed more effectively with loose networks of familiar people. If the next event attracts a different audience, maybe focused on TB, or PTs, some development topic, or whatever, then great. Casting and recasting a net bringing in new people who maybe aren't interested in the last meeting starts to give more people better familiarity with TPO, and encourages them to increase their commitment. There are other side effects. The notions about Tor being some USG front, or whatever loopy ideas thrive the internet, weakens when people interact with others using or contributing to the TPO. Conspiracy theories die hard in the real world. I am apprehensive about proposing new mailing lists, as it can disperse audiences from talk@ and relays@, in our case. But there may come a time when a low-volume NYC list, for example, makes sense to address more local concerns, such as discussing ISPs, data centers, relay installfests, etc. At this point, I'd argue that keeping it in the current channels probably makes the most sense. Input from others onlist encouraged. This is a more general issue everyone can brain dump into. g -- 34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682

5 6

Network team weekly meeting notes, 11 Dec 2017
by Nick Mathewson 11 Dec '17

11 Dec '17

Hi! You can find the logs for our weekly network team meeting at http://meetbot.debian.net/tor-meeting/2017/tor-meeting.2017-12-11-18.00.html Our notes are below: ============ Network team meeting pad, 11 December 2017 “I did not mean to break that planet it was just in the way when I came into being and I fixed it and I said I was sorry and the planet said OK so since I’m supposed to learn from stuff like that I will tell you don’t break planets, especially the ones with living things on them, or at least fix them if you do break them. Also, don’t go in black holes, no matter how much they look like cute little Nahas. They are not cute! They are actually very bitey and kind of mean. Also just OK I do not want to talk about any of this anymore.” -- The Awakened Kingdom, N. K. Jemisin Welcome to our meeting! Every Monday at 1700 UTC 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 last week: * https://lists.torproject.org/pipermail/tor-project/2017-December/001582.html Old Announcements: - On the roadmap spreadsheet: Please take december/january tasks. (If somebody else has already taken something you want, please talk to them and/or add yourself too.) https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… - Soon it will be It is now time to triage 0.3.3.x tickets. Please make yourself the owner of tickets in that milestone that you will do. - The meeting time is now 1800 UTC. Announcements: - We are planning a single-day pre-planned highly-focused hackfest before the Rome Tor meeting - komlo: Should there be a Rust update/planning session? What should we prepare/do beforehand to help this be planned/highly-focused? - review-group-27 is open, there are 5 tickets left https://trac.torproject.org/projects/tor/query?status=needs_review&keywords… - Let's have some proposal discussions. Isis kicked off the process here: https://lists.torproject.org/pipermail/tor-dev/2017-December/012666.html - No regularly scheduled network-team meetings on 25 Dec through Jan 5. - The _free() patch got merged so I would like to bring this to everyone attention: doc/HACKING/CodingStandards.md -> Allocator conventions - Tor 0.3.2.7-rc (or alpha) comes out Thu or Fri Discussion: - Does anyone want to help refresh the fallback directory mirrors? It's pretty easy, and you get to thank a whole bunch of relay operators. https://lists.torproject.org/pipermail/tor-dev/2017-December/012674.html [Pastly is interested! So is hello71!] - teor: - Last week: - PrivCount release and deployment - Revise the client code for IPv6 in microdesc consensus (#23827) - Revise a fix for bridge descriptor caching and retries (#24392) - Review the metrics IPv6 relay graphs (#23761) - Asked for an equal-area projection for metrics maps (#24563) Anyone remember the scene from The West Wing? Well, I'm living it. https://en.wikipedia.org/wiki/Gall%E2%80%93Peters_projection#In_popular_cul… - Emailed Jon about a venue for the pre-Rome hackfest. Awaiting a response. - Various security stuff and code reviews and helping volunteers. - This week: - Fix a bug in PrivCount where I confused "first to close" and "first to open" - Admin for collecting research data - Book flights for Rome - Work on getting the test network running new IPv6 consensus code - Maybe start implementing onion service client counts for experimental PrivCount? - Maybe revise node_get_{prim,ipv6}_{or,dir}port() so the unit tests work again (#23975) asn: Last week: - Another week of mostly code reviewing: + Reviewed mike's #23101: "Predict and build specific HS purpose circuits (rather than GENERAL)". + Reviewed #23603, #23459, #23271. - Attended UX+onion meeting and did some relevant work: + Updated the Onion-Location HTTP proposal: https://lists.torproject.org/pipermail/tor-dev/2017-December/012660.html + Posted some analysis on #23247 on the padlock/onion states of onion+HTTPS. - Slowly started work on guard discovery again: https://lists.torproject.org/pipermail/tor-dev/2017-December/012657.html - Opened #24544 for some leftover prop224 spec issues pointed out in [tor-dev]. This week: - Continue review/testing of prop247/SponsorV tickets. - Continue guard discovery work. Get the simulator run again. - Continue Onion+UX work. Mike: Last week: - Finished up #23100 and #23114 for merged (Thanks asn and Nick!) - Did a bit more work on #13837 in response to asn and dgoulet's code review This week: - Fix a memory leak that turned up in #23114 in the unit tests.. - Work on #13837 and #23101 - Try to find time to help review code Nick: Last week: - Worked on future sandbox strategy - Finished reviews and merges for review-group-26. (Lots of code!) Opened rg27. - Finished rewrite of free() functions. #24337 - Worked on several 0.3.2.x fixes - Worked on privcount-in-rust proof-of-concept code - komlo: If you want extra eyes on this afterward, I can help review - Worked on migrating xmit-time on channels to do less 64-bit division. Needs more work; got a false start. This week: - Meeting about wide-create cells - Follow-up about utf8 proposal (deferred) - Follow-up about privcount proposal (deferred) - Follow-up about hibernation proposal (deferred) - Release 0.3.2.7-{alpha? rc?} - Review and merge, review and merge. - See how much progress I can make on #23847 (make tor in-processs restartable.) - List sponsor8 tickets for isabela (with ahf and catalyst) dgoulet: Last Week: - #23709 got merged so very happy about this. Will allow me to continue to tackle child tickets of #23993. - Worked on a patch for #24554 which makes specific scheduler data to be stored in a channel_t. Big side effect is removing memory allocation from the scheduler main loop. - Found the cause of #24346 which was all along #23603 that just got merged this morning \o/. - Discussion on the security list. I've started an initial patch proposed by teor, nothing working yet. I'll need to put more time on this. - Reviewed review-group-27 tickets. - All my 032 tickets have been finalized This Week: - Be available for the 032 milestone and hopefully an -rc release this week. Still some tickets in there that we might want to try to resolve or explicitly postpone before the stable release. - A wise move on my part would be to start seriously the IPv6 support for HSv3. I'll go over the opened ticket and sync up with teor. - Maybe some scheduler work if time permit it. #23993 is the parrent ticket and maybe fixing stuff in #24554 once I get a review. My next move is #23744 but that depends on #24554 to be merged. komlo (offline): - This week: - I will finish #23881, I didn't have the chance to work on it last week - Thinking over which Rust work should be done next (excluding build pipeline tasks) in order to have a stable development environment for Rust-by-default/Rust-only implementations (will send an email with this for feedback). pastly: did: acted as a wall for dgoulet to bounce ideas off of todo: review #24554 for dgoulet todo: contact teor about helping build fallback directory mirror list ahf Last week: Sponsor 8: - Added patches for Android logging (#24362) - Been working on comparing progress with the reporting simpleperf does with focus on the monotime_coarse_absolute_msec() patches by Nick (#24374). - Switched over to using the `tor-android` repo for building native targets for Orbot. Misc: - Fixed Coverity issue: #24543 - Reviewed #22703, #24427 - Bug triage rotation duty. This week: Sponsor 8: - Finish event loop metrics patches. (nickm: how are they now?) - Upstream patches to `tor-android` for slightly easier compilation and to include bench/tests on devices. (nickm asks: do you mean "from" tor-android?) - Do Q4 reporting to Isa. - Status meeting with Sponsor 8 people and Isa. catalyst: Last week (2017-W49): - looked into Tails time sync issues and how they might relate to our bootstrapping related clock skew problems - looked at #24337 (*_free() macros) - looking at delaying descriptor fetches when they'd be useless (#2878) - tagging more sponsor8 stuff This week (2017-W50): - #2878 - collecting info about misleading bootstrap phases that bootstrap can hang on - out 12/15 and 12/22 (also 12/25-1/1 like many people); will occasionally check email but probably not IRC - other sponsor8 bookkeeping Hello71: - meson? https://cgit.alxu.ca/tor.git/commit/?h=meson&id=a0a6f3c4d0a0fb5f4d5bf2a27bc…

1 0

Tor Browser team meeting notes, 11 Dec 2017
by Georg Koppen 11 Dec '17

11 Dec '17

Hi! We finally switched to the network-team meeting type where only the discussion is logged by meetbot and all the status updates are on the pad. For transparency and easier cross-team collaboration we'll send out weekly meeting notes including both the meetbot log and our status updates to the tor-project as well. The meeting transcript is available at: http://meetbot.debian.net/tor-meeting/2017/tor-meeting.2017-12-11-18.59.log… The notes are below: Tor Browser Meeting Notes Monday, December 11 Discussion: -release preparations for 7.5a10 sysrqb - Configured android build environment, updated Orfox build dependencies, added integrity checks of binaries downloaded by `mach bootstrap`, began rebasing Orfox's tor-browser 52.2.0 patches onto 52.5.2 boklm: (maybe offline during meeting) last week: - helped build/publish the new releases - fixed #24475 (Add support for Windows 64 to update-responses) - created ticket #24585 (Add fpcentral apache configuration on forrestii) - traveled to Austin for Mozilla All Hands planned for this week: - will be at Mozilla All Hands igt0: last week: - Configured android build env; - Updated the wiki explaining how to build Orfox and Orbot; - Added a build script to the tor-android project: https://github.com/n8fr8/tor-android/commit/1b1c0b9537d85c0bfb5e0e42cdf188f… - Sent a patch to https://trac.torproject.org/projects/tor/ticket/22084 (backported it from firefox) - Resent a patch to https://trac.torproject.org/projects/tor/ticket/23104 (it broke the content inside chrome) planned for this week: - https://trac.torproject.org/projects/tor/ticket/19675 mcs and brade: last week: - Helped with bug triage. - Worked on Moat integration for Tor Launcher (#23136) and made a lot of progress. - You can see some screenshots of the UI here: https://trac.torproject.org/projects/tor/ticket/23136#comment:25 planned for this week: - Help with code reviews. - More work on Moat integration and other aspects of the new Tor Launcher UI. - We hope to have this ready for code review soon. Loose ends: - improve error handling. - show a spinner or similar UI element while waiting for a reply from BridgeDB. - more testing. GeKo: last week - release work - work on Fastly related blog post (should go live rather soon) - spent hours[sic!] on https://trac.torproject.org/projects/tor/ticket/24421; I still don't understand what exactly is going on but I have a workaround - started to look into building our new Windows toolchain based on clang (https://trac.torproject.org/projects/tor/ticket/21777) this week: - more work on #24421 and #21777 - fixing https://trac.torproject.org/projects/tor/ticket/21847 - release preparations for the next alpha (planned to get released in about a week) - another round of privacy pass code review - further work on the design document update Georg (on behalf of the Tor Browser team)

1 0

Community Team monthly update, November 2017
by Alison Macrina 11 Dec '17

11 Dec '17

Hello Tor World, Here's an update from the Community Team for November! November 2017 Community Team report Meeting notes November 2017 ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Funding community team projects ================================================================== Tommy is conducting the initial research on funding for two of the community team's main work areas: Global South outreach (growing, strengthening, and supporting Tor in the region) and Tor relay operator support. Support portal ================================================================== The communications team is working with us to finalize the text for the support portal, while the UX team continues to work on design. We continued writing more content for the portal, including explanations for common log errors. Our Outreachy intern, Parinishtha, is also working on organizing user feedback to better assist with support. She's monitoring things like blog comments, IRC, and questions submitted to frontdesk@ and then cataloging user issues to share with developers and people working on the support portal. Next month, Pari will send the first update to tor-project(a)lists.torproject.org. Relay operators guide ================================================================== Last month, we were planning to write a blog post with the steps to running a relay simplified. After a lot of work on the post in November, we realized it would be better to merge it into #24497, and turn the content into information on an organized wiki: https://trac.torproject.org/projects/tor/wiki/OperatorsTips. It's still majorly a work in progress. We need to add to some of the sections, and then simplify the document so it's not just a confusing text block. We'll be working on that in December. And we still plan to write a blog post about it! Tor talks ================================================================== In November, Alison spoke about Tor at the Freedom of Research Conference in Paris. We also submitted proposals for Tor talks at LibrePlanet and RightsCon. Library Freedom Institute ================================================================== Alison worked on finalizing the website, contacting potential guest lecturers, and getting outreach information organized for next month's launch. Translation/Localization ================================================================== Phoul put the downloads page up on Transifex and then ran into some issues with webml that needed to be troubleshooted. He also worked on a script to allow us to push translations up to Transifex faster. Community documents ================================================================== We decided to put the code of conduct proposal period on hold until after the Mozilla All-Hands meeting in December; Mozilla has an amazing Diversity and Inclusion team and we want to talk to them about codes of conduct and incident response policies. ================================================================== -- Alison Macrina Community Team Lead The Tor Project

1 0

November 2017 report for the metrics team
by Karsten Loesing 08 Dec '17

08 Dec '17

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in November 2017. On behalf of the Tor metrics team, Karsten Rebranded Tor Atlas to Tor Metrics Relay Search [1] and made it visually part of Tor Metrics [2]. [1] https://atlas.torproject.org/ [2] https://lists.torproject.org/pipermail/tor-relays/2017-November/013547.html Added an aggregate search [3] function to Relay Search in preparation of shutting down Compass [4] by the end of the year and a world map visualization of aggregations by country [X]. [3] https://atlas.torproject.org/#aggregate [4] https://compass.torproject.org/ [X] https://atlas.torproject.org/#map Released two Onionoo versions that come with protocol updates: Onionoo 4.3-1.7.1 [5] adds a new "host_name" parameter to filter by host name and a new "unreachable_or_addresses" field with declared but unreachable OR addresses. Onionoo 4.4-1.8.0 [6] extends the "version" parameter to bridges, adds a "recommended_version" parameter for relays and bridges, adds a "version" field to relay and bridge details documents, and adds a "recommended_version" field to bridge details documents. [5] https://lists.torproject.org/pipermail/tor-dev/2017-November/012621.html [6] https://lists.torproject.org/pipermail/tor-dev/2017-November/012631.html Announced next major Onionoo protocol version 5.0 [7] to be deployed after December 17, 2017, which removes $ from fingerprints in "effective_family", "alleged_family", and "indirect_family" fields. [7] https://metrics.torproject.org/onionoo.html#versions_5_0 Published draft specification of Tor web server logs [8]. [8] https://metrics.torproject.org/web-server-logs.html Added related events from the metrics timeline entries underneath graphs [9]. (Many thanks to David Fifield and to Isabela and Antonella from the UX team for valuable feedback!) [9] https://metrics.torproject.org/userstats-relay-country.html Made sample graphs showing IPv6 support of relays and bridges [10] which are likely going to be added as regular graphs to Tor Metrics in December. (Thanks for teor for all the input there!) [10] https://trac.torproject.org/projects/tor/ticket/23761#comment:6 Published roadmap [11] for work planned between October 2017 and September 2018. [11] https://lists.torproject.org/pipermail/tor-dev/2017-November/012615.html Improved OnionPerf VM configuration management [12] by using SaltStack [13] for management and orchestration [2] to ensure that all OnionPerf instances run the same environment, that we can ensure updates to happen all at once, and to provision new instances more conveniently. [12] https://oniongit.eu/infra/onionperf-management [13] https://docs.saltstack.com/en/latest/ Changed the web application server used by ExoneraTor from Tomcat to embedded Jetty [14] to facilitate development and deployment. [14] https://trac.torproject.org/projects/tor/ticket/24174

1 0

Notes from December 7 2017 Vegas team meeting
by Karsten Loesing 08 Dec '17

08 Dec '17

Notes for December 7 2017 meeting: Nick: 1) Had productive conversation with Mozillans last week; I'm feeling generally positive about spec work. 2) Security releases uneventful; next planned Tor release is an another alpha, or maybe a release candidate, around 15 Dec-- then aiming for another release in early January. 3) I need to disseminate knowledge to people going to the mozilla all-hands, but I don't know what. Ask me stuff? Karsten: 1) Made good progress on IPv6 relay/bridge statistics. Currently under review. 2) Relay Search (formerly known as Atlas) now has a world map! Steph: 1) going over support portal copy with Tommy to be done by end of Dec 2) planning onion services campaigning with comms, asn, & dgoulet 3) editing next fundraising email with tommy / comms 4) newsletter went out yesterday with blogs from the last month, donate call to action, upcoming events 5) I’ll be at Mozilla all-hands next week - interested to learn more about how we work together, their comms and marketing, and how we can campaign together 6) I'll be at our Tor meetup tonight in NYC Mike: 1) Is ReCaptcha acting up? I have developed a habit of skipping cloudflare captcha sites, but some guy keeps highlighting me on IRC about some issue? [GeKo: Could be, there have been some folks quite vocal about it on trac as well in the last weeks] 2) What do we think about Privacy Pass? Is it too early to ask Google if they would look at it? [GeKo: I plan to have another look at it next week. Let me get back to you then?] Georg: 1) We worked on remaining Sponsor4 items (we are almost done here, two things left) 2) The security releases are about to get out Isabela: 1) spoke at a panel at MDF annual meeting 2) Decision was made last week on what Sukhbir will work on :) which will be mail bundle (focusing on showcasing the experience of using an email client on mobile that connects to tor and then to the email provider using .onion - the bundle will enable the client to connect to tor. The email provider for this prototype will be riseup (they are already using .onion)) 3) working in Seattle this week - meeting about grants for 2018 and organizing workplan for big UX contract 4) Reviewing sponsor8 work to see how we doing for Q4 before Q4 ends [nick maybe we could sync about this like we did with ahf and catalyst (or whoever is working on this stuff)] Brad: 1) Thank you for all of the feedback on the latest employee time allocation budgets. I have made updates based on issues/concerns noted and will be sending out the updated version momentarily. 2) Jon and I have implemented a new inventory system for managing all of the swag that is sent to donors/relay operators/other friends of Tor. With the new office and the system we put in place, Jon is getting shirts out at a very high rate (over 300 in one day!) 3) Sue and I have been reviewing current use of Harvest and will be coming up with a brief report on ways we can utilize the system more effectively. Expect to distribute first to vegas team later this month. Roger: 1) CCC plans and spaces 2) rome invites 3) i disappear tomorrow to begin my five-country travel adventure

1 0

OONI Monthly Report: November 2017
by Maria Xynou 07 Dec '17

07 Dec '17

Hello, The OONI team made steady progress in November 2017. We reported on recent censorship events in Pakistan, as well as on cases of DNS misconfiguration. We also updated various test lists in collaboration with community members, and we presented OONI at the Free Society Conference and Nordic Summit (FSCONS). We are currently working on improving the design and usability of our mobile apps, and we completed the first draft of the onboarding process for the OONI Probe Android app. We also made an alpha release of node.js bindings for measurement-kit, made progress on implementing dynamic serving of test lists via the orchestration backend, and we started writing an architecture and threat model document for probe orchestration. # Published research report on recent censorship events in Pakistan In collaboration with Bytes for All we published a research report examining recent censorship events in Pakistan. This report is available here: https://ooni.torproject.org/post/how-pakistan-blocked-social-media/ Through the analysis of OONI network measurements collected from Pakistan, we confirmed the blocking of 14 news websites and various social media sites and instant messaging apps during Islamist protests. Our report received the following press coverage: https://www.thenews.com.pk/print/250865-internet-body-issues-report-on-news… # Published research report on cases of DNS misconfiguration* * As part of our analysis of OONI measurements and investigation into DNS failures, we uncovered various cases of DNS misconfiguration. We reported these cases in the following post: https://ooni.torproject.org/post/not-quite-network-censorship/ # Progress on mobile app redesign We are currently working on improving the design and usability of our mobile apps. During November we completed the first draft of the re-designed onboarding process for the OONI Probe Android app, and we worked on the Interaction Design elements. # Updated test lists We collaborated with community members on updating various test lists. During November, we updated the following test lists: 1. Sierra Leone: https://github.com/citizenlab/test-lists/pull/262 2. Pakistan: https://github.com/citizenlab/test-lists/pull/259 3. Nigeria: https://github.com/citizenlab/test-lists/pull/255 & https://github.com/citizenlab/test-lists/pull/257 4. India: https://github.com/citizenlab/test-lists/pull/261 5. Algeria: https://github.com/citizenlab/test-lists/pull/249 # Architecture & Threat model for Probe Orchestration We started writing an architecture and threat model document for the Probe Orchestration system and we also started collaborating with Cure53 to get it audited by them. # OONI data publishing Amazon accepted us into their Open Data program (https://aws.amazon.com/government-education/open-data/) <https://aws.amazon.com/government-education/open-data/%29> and as a result all the public OONI data is available for free on s3. You can access all our public JSON reports inside of this s3 bucket: s3://ooni-data/autoclaved/jsonl/ Example: https://s3.amazonaws.com/ooni-data/autoclaved/jsonl/2017-11-06/20171031T181… (If you were previously using s3 hosted data, the bucket name changed from ooni-public to ooni-data) Moreover we also offer, for batch import, lz4 compressed daily dumps of all measurements. These are available here: s3://ooni-data/autoclaved/jsonl.tar.lz4/ Example: https://s3.amazonaws.com/ooni-data/autoclaved/jsonl.tar.lz4/2017-12-01/dash… To get a listing and metadata of all the files in a given bucket, you may look for the index.json.gz file Example: https://s3.amazonaws.com/ooni-data/autoclaved/jsonl.tar.lz4/2017-12-01/inde… If you are using the AWS Command Line Interface (https://docs.aws.amazon.com/cli/latest/reference/) <https://docs.aws.amazon.com/cli/latest/reference/%29> and have a AWS access key configured, be sure to pass in the --no-sign-request option. Example: $ aws s3 --no-sign-request ls s3://ooni-data/autoclaved/jsonl/2017-12-04/ We will be releasing a short blog post explaining how to use this data, once Amazon updates their Open Data page to list us as a project. # Test lists orchestration Progress was made on implementing dynamic serving of tests lists via the orchestration backend. See: https://github.com/TheTorProject/proteus/pull/29 # Node.js bindings for Measurement-kit We made an alpha release of node.js bindings for measurement-kit: https://github.com/measurement-kit/measurement-kit-node It's not yet ready for usage by the general public, but we have been using this as a foundation for the development of our new OONI Probe desktop apps. # Community activities We presented OONI at the Free Society Conference and Nordic Summit (FSCONS) in Norway on 4th November 2017. Information about our presentation is available here: https://frab.fscons.org/en/fscons17/public/events/309. We also attended the OTF Summit in Valencia, and hosted our monthly community meeting on 28th November 2017. As part of the community meeting, we discussed strategies for monitoring emergent censorship events and rapidly responding to them (in light of recent censorship events in Pakistan, for example). # Research citing OONI data During November OONI data was cited in the following research: * Citizen Lab Submission to the United Nations Special Rapporteur on violence against women, its causes and consequences: https://citizenlab.ca/wp-content/uploads/2017/11/Final-UNSRVAG-CitizenLab.p… * Internet Censorship Capabilities in Cyprus: An investigation of online gambling blocklisting: https://www.researchgate.net/publication/319482512_Internet_Censorship_Capa… # Userbase In November 2017 OONI Probe was run 184,800 times from 3,544 different vantage points across 202 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

Damian's Status Report - November 2017
by Damian Johnson 06 Dec '17

06 Dec '17

Hi all, here's what I've been up to this month... http://blog.atagar.com/november2017/ http://blog.atagar.com/interview-with-ben-collier/ Cheers! -Damian

1 0

November 2017 Report for the Tor Browser Team
by Georg Koppen 06 Dec '17

06 Dec '17

Hi everyone! November was an exciting month. The Tor Browser team made four releases: Tor Browser 7.0.9[1], 7.0.10[2], 7.5a7[3], and 7.5a8[4]. Tor Browser 7.0.9 and 7.5a7 fixed a critical vulnerability reported to us by Filippo Cavallarin potentially affecting Tor Browser users on macOS and Linux. Thanks again for notifying us and coordinating the disclosure! Tor Browser 7.0.10 and 7.5a8 picked up Firefox security fixes and new Tor versions. The alpha release was the first that contained 64bit Windows bundles[5] and an improved Tor Launcher user interface[6][7]. Besides release related work we tried to finish our remaining Sponsor4 items this month. We succeeded with the excecption of our custom Panopticlick deployment (FPCentral)[8][9] and our improvements for fetching and using non-default bridges (done via moat)[10]. Working on those two remaining deliverables will be top priority over the coming weeks. The full list of tickets closed by the Tor Browser team in November is accessible using the `TorBrowserTeam201711` keyword in our bug tracker.[11] Apart from finishing the two remaining Sponsor4 tasks we plan to prepare this month the remaining tickets for our next major stable release, Tor Browser 7.5, which is due January 23, 2018. And we hope we can spend some time on tackling remaining regressions from our 7.0 release. Finally, the mobile work will get up to speed which is internally tracked under Sponsor8. We'll start with merging the Orfox patches into our repository[12] and making first investigations about the state of the proxy safety on mobile[13]. All tickets on our radar for this month can be seen with the `TorBrowserTeam201712` keyword in our bug tracker.[14] For those interested in Tor Browser work planned in the longer term (which means the coming months) we've created a roadmap taking dependencies of other teams into account.[15] This should give everyone a fair understanding of where we are heading toward. Feedback is welcome! Georg [1] https://blog.torproject.org/tor-browser-709-released [2] https://blog.torproject.org/tor-browser-7010-released [3] https://blog.torproject.org/tor-browser-75a7-released [4] https://blog.torproject.org/tor-browser-75a8-released [5] https://trac.torproject.org/projects/tor/ticket/20636 [6] https://trac.torproject.org/projects/tor/ticket/23261 [7] https://trac.torproject.org/projects/tor/ticket/23262 [8] https://trac.torproject.org/projects/tor/ticket/6119 [9] https://trac.torproject.org/projects/tor/ticket/23738 [10] https://trac.torproject.org/projects/tor/ticket/23136 [11] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [12] https://trac.torproject.org/projects/tor/ticket/19675 [13] https://trac.torproject.org/projects/tor/ticket/21863 [14] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… [15] https://storm.torproject.org/shared/roevbMxlBi5rxSAh57iRjy8w1MB2HZArEmM2Jek…

1 0

UX team report for November 2017!
by isabela 06 Dec '17

06 Dec '17

Hello Tor! Here is some updates from the UX team for the month of November. First of all! We now have Antonela as part of our team working on Design o/ Hiro is also working with us on some projects like the website redesign. And I am now leading the UX team :) (besides project managing stuff as I always do). We reviewed and gave feedback to the Metrics team new 'timeline of events' project (which is pretty cool). Our feedback can be found as comments at the 24260 ticket. [1] We are also in touch with OONI to review their revamp of mobile experience. And we helped the Tor Browser team by doing QA on the Tor Launcher new UI project, you can see the bugs we found and other feedback under 24371. [2] Another big effort we worked on during November is the Website Redesign project! So, for those catching up just now with it, the website redesign [3] is a big project that aims to not only redesign 'torproject.org' but create 3 other portals to better organize the content that is now hosted at 'torproject.org'. Those other 3 portals are: community.torproject.org, dev.torproject.org and support.torproject.org Before November we had mocks for all of these sites done and their cotent organized as well. After montreal we decided to build the support site first, so we started to work on it. Each project follows the same list of steps to get it done: 0) content architecture - map current content related to the portal and organize it 1) whiteboard draw organization of the content into pages 2) wireframe these pages 3) create design for these pages [these include design reviews till we are happy with what we have] 4) start organizing content for the pages (with the design already done we will be working with that) 5) update high definition mockups with real content 6) guerrilla user testing #1 7) start coding the pages 8) once content is finished we upload them on transifex for translation to start 9) Once coding is done we can start QA by language (as translations gets complete) Right now we are working on 4 and 5 of those steps for support.tpo, but we have done 0-2 for all portals. If you would like to check out the design for support you can find it under the main ticket tracking all the work to build that site 24129. [4] Another work we are doing that is part of this big effort is the creation of 'styleguide(a)torproject.org'. If you were at the Seattle dev meeting (Q4 2016) you might remember that we were working on a design style guideline for Tor Project [5] What we did was to apply that to some components of 'bootstrap' and have a fork version of it where people can easily build sites using the css/templates from styleguide.torproject.org We are still working on that in December but should be done soon. This work will definetly speed up the process of building sites within the Tor Project ecosystem. But a site is not only done with 'frontend' or better saying html and css hehe We still had to decide what framework to use to build those. So that was another work we did in November, based on the requirements we had we decided to test a framework called Lektor 24275 [6], we also got stakeholders who will be editing the site to test it and everyone liked it. So this will be the framework we will use. If you have any questions about any of the projects the UX team is working please reach out to us! If you would like our help with any project you are working on, reach too! Our roadmap [7] is public and you can check what we have planed for December in there o/ Cheers, isabela [1] https://trac.torproject.org/projects/tor/ticket/24260 [2] https://trac.torproject.org/projects/tor/ticket/24371 [3] https://trac.torproject.org/projects/tor/ticket/21222 [4] https://trac.torproject.org/projects/tor/ticket/24129 [5] https://media.torproject.org/image/Tor%20Style%20Guide%20v1.3.pdf [6] https://trac.torproject.org/projects/tor/ticket/24275 [7] https://docs.google.com/spreadsheets/d/1ELMvnIksL-m_r0vJt_rwpIkcjyzZpCyYiQJ…

1 0