- tor-project - lists.torproject.org

May 2018 report for the Tor Browser team
by Georg Koppen 07 Jun '18

07 Jun '18

Hi! We had two Tor Browser releases this month, Tor Browser 7.5.4[1] and 8.0a7[2] picking up Firefox 52.8.0esr which contained a couple of security bug fixes. Apart from that we were able to fully concentrate on the Tor Browser transition to Firefox 60 ESR and on our Tor Browser for Android work. Since May 30 we have Linux nightly builds available which are based on Firefox 60 ESR[3] and we meanwhile finished the transition for macOS as well[4]. That does not only include updating the toolchains to new Firefox requirements but getting our own extensions, Torbutton[5] and Tor Launcher[6], to work the new browser version, too. We worked as well on the network code and new feature audit to make sure we don't miss criticial changes for Tor Browser and patch them if necessary. On the mobile side we were fighting with an unexpected crash bug due to a Firefox patch closing a serious vulnerability.[7] We hope to have this problem resolved soon. Moreover, we made progress on having a first branch based on Firefox 61 ready[8], which will be the base for our first Tor Browser for Android alpha release. The full list of tickets closed by the Tor Browser team in May is accessible using the `TorBrowserTeam201805` keyword in our bug tracker.[9] For June we need to get outstanding build issues for the new Tor Browser for Windows resolved.[10] In parallel work to stabilize the code to be ready for the first alpha based on Firefox 60 ESR is under way, adapted to the new Firefox Photon user interface. If we get all the remaining pieces done in time the first ESR 60-based alpha will be out at the end of this month. For mobile we should have first test builds ready this months and close remaining proxy bypass bugs, if there are any. Additionally, we are working together with the UX team to get the UI adapted to match what we'll ship for desktop. All tickets on our radar for this month can be seen with the `TorBrowserTeam201806` keyword in our bug tracker.[11] Georg [1] https://blog.torproject.org/tor-browser-754-released [2] https://blog.torproject.org/tor-browser-80a7-released [3] https://lists.torproject.org/pipermail/tbb-dev/2018-May/000849.html [4] https://trac.torproject.org/projects/tor/ticket/24632 [5] https://trac.torproject.org/projects/tor/ticket/26100 [6] https://trac.torproject.org/projects/tor/ticket/25750 [7] https://trac.torproject.org/projects/tor/ticket/26320 [8] https://trac.torproject.org/projects/tor/ticket/26233 [9] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [10] https://trac.torproject.org/projects/tor/ticket/26203 [11] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

One job opening and two new hires!
by Erin Wyatt 05 Jun '18

05 Jun '18

Hello, everyone! Here’s a quick hiring update: 1. We’ve (finally) found our Android OS developer, who will be starting later this month!! 2. We’re closing in on finding our amazing magical person for the User Research Coordinator position and will hopefully be making an offer in the next couple weeks! 3. Still accepting applications for the Localization Project Manager, a part-time position. (https://www.torproject.org/about/jobs-localization-projectmanager.html.en) 4. New opening for a Fundraising Director! This one we really need your help with — please apply, forward, share, tweet, whatever! This is such an important job and we’d really like to find someone totally awesome for it, so please help us spread the word. (https://www.torproject.org/about/jobs-fundraising-director.html.en) (PDF attached and plain text pasted below.) Hope you’re all having a great week! :) Cheers, Erin Wyatt HR Manager ewyatt(a)torproject.org GPG Fingerprint: 35E7 2A9F 6655 45F9 2CB6 6624 BA0C 9400 F80F 91CE Internet Freedom Nonprofit Seeks Experienced Fundraising Director June 5, 2018 The Tor Project, Inc., a 501(c)(3) nonprofit organization that provides technical infrastructure for privacy protection over the internet, is seeking a dynamic, creative, and organized Fundraising Director to help us grow and expand our funding base. The Fundraising Director will be responsible for planning, directing and coordinating all fundraising activities, with an emphasis on diversifying our funding sources. The ideal candidate will have at least five years of leadership experience working in the fundraising department of nonprofit organization. This person must be able to straddle the worlds of technology and fundraising. The Tor Project is funded in part by government research and development contracts, and in part by individual, foundation and corporate donations. The ability to talk about the Tor Project's work to all different types of current and potential donors is essential. This senior level position will report directly to the Executive Director and will be part of the organization's leadership team. The Fundraising Director will set and guide the strategy for all of our fundraising, including increasing contributions from government, foundation, corporate, and individual donors. This is a new, hands-on position for a highly skilled fundraising professional. Responsibilities: • • Work with Tor Project program staff to understand and communicate effectively about the range of our projects and accomplishments. • • Grow a major gifts program, including identification, cultivation, and solicitation of major donors. • • Oversee the flow of our donation system, from initial ask to thank you. • • Oversee grant seeking, including research, proposal writing, and reporting requirements. • • Interact with our current government and foundation program officers, making sure they are receiving necessary reports and keeping them apprised of our work. • • Oversee our annual crowdsourced funding campaign. • • Supervise and collaborate with our grant writer. • • Write and edit grant proposals, grant reports, year-end report, conference one-pagers and other fundraising-specific writing. • • Plan fundraising events, as appropriate. • • Determine appropriate Tor Project booth presence at conferences and events. • • Ensure that the time of the Executive Director is used efficiently for fundraising. Qualifications: • • Demonstrated track record of success in raising major gifts and writing complex proposals for various audiences, including foundations. • • Knowledge and experience in fundraising techniques, particularly major gift fundraising. Must be comfortable making pitches and personally asking people for money. • • Excellent verbal, written, and editing skills, including the ability to produce high quality work quickly and under deadline pressure. • • Ability to develop fundraising budgets and prepare financial reports. • • Comfortable with highly technical topics and ability to explain them clearly and accurately to non-technical audiences. Must embrace the mission of the Tor Project. • • Strong generalist understanding of the basic mechanics of how the internet works, as well as issues related to privacy, security, censorship, and surveillance. • • Excellent computer skills, including familiarity with donation tracking systems. (We use the open source CiviCRM.) • • Experience with, or willingness to learn how to use, communications and collaboration technologies such as PGP, IRC, Jitsi, Signal, WordPress, and etherpads. • • Hard working and highly organized with superior attention to detail. • • Willingness to take responsibility and initiative. • • Highly collaborative, preferably with experience working with and as part of remote teams in different time zones. • • Prior experience working on U.S. government grants and contracts is a plus. • • Willingness to travel to international meetings at least twice a year. • • The successful candidate should be eager to be an inspiring mentor and colleague to the board and staff of the Tor Project. The Tor Project's workforce is smart and committed. Experience working with open source communities and/or a dedication to Internet freedom are added pluses. The Tor Project currently has a paid and contract staff of around 35 developers and operational support staff, plus many thousands of volunteers who contribute to our work. The ideal candidate will be energetic, unflappable and flexible, and will thrive in a highly-technical collaborative environment. This is a full-time, hands-on position, which can be done remotely or in our office in Seattle, WA. Flexible salary, depending on experience. The Tor Project has a competitive benefits package, including a generous PTO policy; 14 paid holidays per year (including the week between Christmas and New Year's, when the office is closed); health, vision, dental, disability, and life insurance paid in full for employee; flexible work schedule; and occasional travel opportunities. To apply, send a cover letter and your resume to hr at torproject dot org with the subject "Fundraising Director." Tell us why you think you're the right person for this job, and please include links to writing samples. No phone calls please! The Tor Project, Inc., is an equal opportunity, affirmative action employer.

1 0

OONI Monthly Report: May 2018
by Maria Xynou 05 Jun '18

05 Jun '18

Hello Tor world, In May 2018, the OONI team established a new partnership, created a fully working prototype of an OONI Probe Windows app, continued to make progress on revamping the OONI Probe mobile apps, and published interviews with community members. Further information is provided in the following report. # Established new partnership We are excited to have formally established a new partnership with Nigeria's Paradigm Initiative! As part of our new partnership, we aim to collaborate on the study of internet censorship in Nigeria through the collection and analysis of OONI Probe network measurements. Social media announcement: https://twitter.com/OpenObservatory/status/993395765665062912 # Created a prototype of an OONI Probe Windows app We reached a fully working prototype of an OONI Probe Windows app! This involved mostly fixing various issues that were Windows-specific and developing workarounds. Below is a partial list of the issues we resolved and worked on: * https://github.com/ooni/probe-cli/commit/a0be45e32313cf0423b3b49ce6b38acecc… * https://github.com/ooni/probe-cli/commit/d15fddc538e3020d758cbfe4fb68e18d91… * https://github.com/ooni/probe-cli/commit/c97217c49e1bfc1500e526bff892388d0e… * https://github.com/ooni/probe-desktop/commit/b5754c9a1405355a5b7d0604c10d88… * https://github.com/ooni/probe-desktop/commit/686591c694102c678edafb73d52033… Moreover, we improved how exceptions are reported back to us by integrating sentry.io into the desktop app. We will likely add support for doing the same in the CLI tool as well. See: https://github.com/ooni/probe-cli/issues/12 # Revamping the OONI Probe mobile apps The iOS version of the revamped OONI Probe mobile app is almost ready! We completed the details screens and OONI Run, and we can start a testing and tweaking phase. The current stable version has been updated to 1.3.2 with the update on measurement-kit, geoip and test lists: * https://github.com/TheTorProject/ooniprobe-ios/pull/178 * https://github.com/TheTorProject/ooniprobe-android/pull/148 We also started refactoring the Android code and researching the required libraries. See: https://github.com/TheTorProject/ooniprobe-android/pull/149/commits # Press coverage OONI received the following press coverage in May 2018: 1. CBC News wrote a story about OONI, discussing the use of OONI Probe and OONI data by researchers and advocates around the world. This article, titled "When governments censor websites and block messaging apps like Telegram, here's where to turn for proof", is available here: http://www.cbc.ca/news/technology/ooni-tor-information-controls-measurement… 2. The Malay Mail reported on the use of OONI data by Malaysian digital rights organization, Sinar Project, in monitoring censorship events during the country's elections and detecting the blocking of an election result site. This news article is available here: https://www.malaymail.com/s/1631677/watchdog-tm-maxis-censored-live-result-… # Community use of OONI data 1. Malaysia's Sinar Project published a report based on OONI data, revealing the blocking of an independent election results website during the country's elections: https://sinarproject.org/en/updates/internet-censorship-monitoring-14th-mal… 2. Kenya's Strathmore University CIPIT published a research report examining intentional internet dusruptions in Africa over the last 5 years. This report cites OONI data: https://blog.cipit.org/wp-content/uploads/2018/05/Report_Intentional-Intern… 3. The "Ranking Transparency of Mobile Service Providers in Russia" report used OONI Probe and cites OONI data: https://roskomsvoboda.org/media/2018/05/RDR-report-EN-1-1.pdf 4. The Berkman Centre published an interview with Sinar Project (our Malaysian partner), which discusses their use of OONI Probe and OONI data as part of their work: https://medium.com/berkman-klein-center/open-without-freedom-8faf1df6e45b 5. OONI is cited in the Global Network Initiative's research report "Disconnected: A human rights-based approach to network disruptions": https://globalnetworkinitiative.org/wp-content/uploads/2018/05/Disconnected… # Community activities ## Publication of community interviews We have started publishing interviews with OONI community members to share their work with the world. In May 2018, we published interviews with the following OONI community members: 1. Moses Karanja: https://ooni.torproject.org/post/ooni-community-interviews-moses-karanja/ 2. Julie Owono: https://ooni.torproject.org/post/ooni-community-interviews-julie-owono/ Over the next months, we'll be filming and publishing more community interviews, which will be made available on our YouTube channel: https://www.youtube.com/channel/UCQhDgj9wBf4_w5bWFvLlq-w ## RightsCon 2018 We joined the internet freedom community at RightsCon (https://www.rightscon.org/) hosted in Toronto by Access Now between 16th-18th May 2018. At RightsCon, we presented OONI and participated in the following sessions: 1. Enforcing Net Neutrality with Evidence Based Policy Making: https://rightscon2018.sched.com/event/EHoY/enforcing-net-neutrality-with-ev… 2. Shedding Light on Internet Blackouts: https://rightscon2018.sched.com/event/EHmS/shedding-light-on-internet-black… 3. Defending Minority Voices on a Censored Internet: https://rightscon2018.sched.com/event/EHmO/defending-minority-voices-on-a-c… 4. When Repressive Authorities #KeepItOn: https://rightscon2018.sched.com/event/EHlH/when-repressive-authorities-keep… We published a blog post to encourage participation at our RightsCon sessions: https://ooni.torproject.org/post/ooni-rightscon-2018/ ## OONI swag By donating to The Tor Project, community members can now get OONI t-shirts and OONI stickers. See: https://donate.torproject.org/pdr ## Updated test lists The following test lists were updated in May based on URLs provided by community members: * KZ: https://github.com/citizenlab/test-lists/pull/348 * PK: https://github.com/citizenlab/test-lists/pull/346 * AO: https://github.com/citizenlab/test-lists/pull/345 * Global: https://github.com/citizenlab/test-lists/pull/347 * IR: https://github.com/citizenlab/test-lists/pull/343 * UG: https://github.com/citizenlab/test-lists/pull/342 # Userbase In May 2018, OONI Probe was run 246,655 times from 4,739 different vantage points in 209 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research 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

Reviving The Discussion: Crowdsourcing some guidelines for what it means to make a web site "Tor-friendly"
by Kevin Gallagher 04 Jun '18

04 Jun '18

Hello everyone, Recently in a Tor UX meeting I brought up the idea of creating a Tor-Friendliness scanner, or a program that evaluates and ranks the "Tor-friendliness" of a web site and provides recommendations to improve. This idea seemed pretty well received by those attending the meeting, so I'd like to get stated on creating this. However, in order to do this I would need to precisely define "Tor-friendliness." That's when this discussion (https://lists.torproject.org/pipermail/tor-project/2018-January/001606.html) was brought to my attention. It seems conversation about this has died down. I would like to revive this conversation and work towards creating an understanding of the definition of being "Tor-friendly." Currently I am reading the Tor Browser Design Document to understand the Tor Browser more fully, and to understand how it works to thwart tracking and fingerprinting, etc. If there are other approaches I should consider to help me understand what "Tor-friendliness" is, please let me know! Otherwise, I would love to hear about what people think constitutes "Tor-friendliness" so I can build a tool that tests for these things. Thanks, Kevin Gallagher -- Kevin Gallagher Ph.D. Candidate Center For Cybersecurity NYU Tandon School of Engineering Key Fingerprint: D02B 25CB 0F7D E276 06C3 BF08 53E4 C50F 8247 4861

5 5

Notes from the Tor Browser team meeting, 4 June 2018
by Georg Koppen 04 Jun '18

04 Jun '18

Hi! We just finished our weekly Tor Browser meeting. The chat log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-06-04-18.00.log… The notes from our pad are: Monday, June 4, 2018 Discussion: sysrqb: Do we want to use the 'status:' updates during the week like the network team? [GeKo: It seems we like this idea. Need to check with the network team to not mess with their status updates] sysrqb: General question: is there an update/timeline on the new tp.o website? [GeKo: not sure actually] igt0: Last Week: - Updated #1459420 patch (HLS Player doesn't use the centralized Proxy Selector) - Still struggling with the Orfox crash, I also contacted Till from Mozilla (sysrqb: could you give a hand? yes) - Delivered my talk in the JSConfEU about fingerprinting techniques and mitigations. [GeKo: Are there slides/a recording available somewhere?] This Week: - More Orfox debugging - tweak Tor Button to make it work on mobile and initial mobile UI preparation (we need to think about what we can reuse) mcs and brade: Last week: - Reviewed and tested rebased external helper app patch (part of #25543). - Fixed #26235 (Help menu does not open in Tor Browser nightlies based on ESR60). - Started working on #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). This week: - File a Bugzilla bug for #25909 (disable updater telemetry) - Continue with #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). GeKo: Last week: - continued MAR signing key testing - finished macOS patches for new toolchain (including all the other components, not only firefox), nightlies should be available rather soon - made progress on the network review - reviews (#25859, #25650, #26204, #26235) - sent out 1:1 feedback scheduling mails This week: - finish MAR signing testing and come up with a plan for the changes we need for the next update and how we address them (#26050) - network review - more code reviews - help with the windows changes for esr60 - begin of the month admin stuff, ticket prioritization for next alpha - I'll be afk on 6/6 sukhe: Last Week: - Worked on #26204, #25837, #26073, #26216 (in progress), #26205 (in progress). Looked at Windows builds of Firefox 60ESR - Rust build question: what's the purpose of prev_version? Is there a reason we are using the source tar and not the git? I am asking because panic-abort.patch fails to apply for the Windows 32bit build. I am building on top of master with https://github.com/azadi/tor-browser-build-1/tree/bug-26204 and https://gitweb.torproject.org/user/gk/tor-browser-build.git/commit/?h=bug_2… merged [boklm: prev_version is the binary version we use for bootstrapping the build. panic-abort.patch was made on rust 1.25.0 and it seems it will need to be rebased on version 1.26.1.] This week: - Resume #26126, #26205, #26203 (Windows builds) tjr - Ethan, Tim and Gary are back! Had their first couple days. Will sync up with them this week. (Arthur says: yay!) - Expect a Tor/Mozilla sync meeting to get scheduled after all-hands, probably late day Berlin time / early morning USA time - MinGW Work - x64 Sandbox work: https://bugzilla.mozilla.org/show_bug.cgi?id=1461421 - x64 Sandbox with jemalloc: https://bugzilla.mozilla.org/show_bug.cgi?id=1466192 - Jacek will start on mingw-clang sometime soonish in https://bugzilla.mozilla.org/show_bug.cgi?id=mingw-clang and children boklm: Last week: - reviewed #26204, #26249, #9711, #25832, #25894, #25554, #25548, #26195, #26003 - updated #25860 (Clean up OpenSSL's configure options for Windows) This week: - finish reviewing #24632 (Update macOS toolchain for ESR 60) - update HEASLR patch (#12968) and try to inspect the binary to check if we are good - start looking at #26050 and #26234 (update "watershed" for ESR60-based Tor Browser) - fill upstream binutils ticket for #26148 - continue work on some ansible roles for testsuite VMs setup (#26149) pospeselr: Last week: - run without /proc patch uplift updates - seems like #23247 test failures were some intermittent issue with the ESR60 tryserver, rebased agains latest and test failures went away - localization approach of pulling strings from tor-button strings list won't work as is (due to string formatting specifiers) - problem is modifying that first line which either shows: - the various HTTPS and encryption properties (uses string formatters) OR - scary connection not encrypted message (hard coded string) - for onion https connections we would need to throw away the HTTPS info altogether and only display a constant 'onion encryption' message for the 1st line - if anyone has thoughts on this I'm all ears - started work on #26039 (<profiledir>/preferences/extension-overrides.js will not be loaded in ESR 60) - took off Friday (and Monday was Holiday) This week: - finish up #26039 patch sysrqb: - Last week: Monday was US holiday Continued work on TBA patches Looked at Orfox bug Began dogfooding nightly - This week: Rebasing and testting TBA patches on top of Arthur's Tor Browser patches (#26233) Looking at Orfox bug some more arthuredelstein: - Last week: Finished a branch for #26233 (Rebase to Firefox 61) Started work on #14952 (HTTP2 audit and patch) - This week: Try to get a patch for review for #14952 Work on #25555 (optimistic socks) and #26128 (noscript/security slider, possibly in collaboration with sukhe) Georg

1 0

Notes from May 31 2018 Vegas team meeting
by Karsten Loesing 04 Jun '18

04 Jun '18

Notes for May 31 2018 meeting: Georg: 1) First Tor Browser nightlies based on Firefox 60 ESR are out; we work on getting macOS and Windows builds in shape as soon as possible 2) Where are we with the meek/moat/domain fronting situation? Did Amazon or anywhere else signal they seriously want to help us? 3) Mike: What's the state of Goolgle ReCAPTCHA blocking Tor users outright? Are there new results from the measurement side (IIRC I just saw one/two mails weeks ago)V Alison: 1) Returned from Uganda. Antonela and I will be writing up and sharing our report soon. 2) While in Uganda we encountered a bug in Facebook that prevents connections over Tor, even with the onion service. 3) Library Freedom Institute starts next week! You can follow along with our curriculum and see what resources we produce here: https://github.com/alisonLFP/libraryfreedominstitute 4) Next Saturday I'm speaking at the French librarians' conference in La Rochelle, France 5) LFP is signing the contract this week to coordinate the Glass Room Experience in the US 6) Doing lots of Mexico City planning including working on the open days. Meeting with Gus later to talk about hosting a few sessions for new people, including Tor trainings/installation in both English and Spanish, and some other things that can help get people involved. Steph: 1) Newsletter going out today 2) Published a post with Ed at PI 3) Who can help with frontdesk? 4) Answered questions for a journalist Karsten: 1) Finished open reviews and wrapped up tasks worked on by iwakeh. The metrics team will be 1 person only in June before growing back to 2 in July with irl. 2) Put out five releases to switch from Gson to Jackson as JSON library, also as an exercise to hand over CollecTor/Onionoo operation from iwakeh to irl.

1 0

Notes from the Tor Browser team meeting, 29 May 2018
by Georg Koppen 30 May '18

30 May '18

Hi! We had our last weekly meeting in May yesterday due to a US holiday on Monday and here come the usual notes. The chat log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-05-29-18.00.log… The notes from the pad are: Tuesday, May 29, 2018 Discussion: -nightly releases, preparations for the alpha mcs and brade: Last week: - Reviewed #25750 (update Tor Launcher for ESR 60). - Reviewed #23247 (Communicating security expectations for .onion). - Tested the new circuit display on macOS. - Took a lot of time off for family events. This week: - For a couple more days, we still have limited availability for Tor work. - Begin #22074 (Review Firefox Developer Docs and Undocumented bugs since FF52esr). sysrqb: Last week: - Finished TorLauncher updates for 60ESR (#27570) - Tested which unit tests fail/break with TBA patches (#25741) - Started rebasing tor-browser patches (using Arthur's branch, #25543) onto FF61 (#26233) This week: - Continue rebasing tor-browser patches onto FF61 (#26233) - Help igt0 with troubleshooting orfox igt0: Last Week: - Helped out Arthur to wrap up the 26100; - Kept pocking Gecko trying to figure out why the latest ESR release is crashing(I also asked for help from the JSAPI team https://bugzilla.mozilla.org/show_bug.cgi?id=1463741) This Week - Still need to figure out why Orfox is crashing - Look again in Tor Button for Mobile (What it needs to be done in the esr60) - Finish my JSConf slides and present it. boklm: Last week: - made patches for: - #22242 (Selfrando embeds the RUNPATH in Linux binaries) - #26165 (make it possible to use gcc:var/setup without hardening wrapper) - #25860 (Clean up OpenSSL's configure options for Windows) - #25859 (Clean up zlib's build script) - #12968 (Specify HEASLR (High Entropy Address Space Layout Randomization) in MinGW-w64) - updated patch for #25862 (move mingw helper scripts to firefox) - updated and rebased patch for #16472 (binutils update) - looked at the list of things to do for #26050 (achieve update "watershed" for ESR60-based Tor Browser) This week: - file upstream binutils ticket for #26148 - review some tickets (#25832, #25894, #25975, #9711) - continue work on some ansible roles for testsuite VMs setup (#26149) tjr - We know where the (one?) crash in x64 sandbox is and are working on a fix - Scheduled some all hands meetings, scheduling more this week. - Working on getting Jacek as a contractor for mingw-clang GeKo: Last Week: - reviews, reviews, reviews - debugged various issues with our proposed patch for nightly linux builds based on esr60 (#26073) - wrote a fix for about:tor not shown in upcoming nightlies (#26129) - helped antonela with builds for user testing (arthur asks: what were results? did circuit display ever work?) [GeKo: not sure about the results but we fixed the issue with the circuit display and .onion icons not showing up) - worked on setting up new signing (sub) keys (MAR and Tor Browser) - debugged issues with our switch for macOS to the new toolchain; the good news is I get Tor Browser built (wrote patch for #9711 and started with #26195) - went over the patches we want to have on ESR60 for the mingw-w64 build: tjr: are there patches left we want to uplift? [GeKo: currently not but we want to have backport at least one patch to get the browser compiled for mingw-w64: https://bugzilla.mozilla.org/show_bug.cgi?id=1448748; we'll probably want to pick https://bugzilla.mozilla.org/show_bug.cgi?id=1411401 and https://bugzilla.mozilla.org/show_bug.cgi?id=1389967 as well, once they are ready] This Week: - finish MAR signing key testing - finish macOS switch to new toolchain (including all the other components, not only firefox) - make progress on the network review pospeselr: Last Week: - finished up #23247 patch (for tor-browser and ESR60), though when applied against ESR60 tryserver tests start failing left and right - investigated said failures, but haven't fixed yet This Week: [GeKo: + start to work on #26039] - fix #23247 test failures - resolve localization issue - taking Friday off, flying to Kansas for wife's bike race arthuredelstein: Last Week: With igt0, finished up revisions for https://trac.torproject.org/projects/tor/ticket/26100 Finished up revisions for https://trac.torproject.org/25543 (update tor-browser.git for esr60) Posted my WIP patches for feeback on https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 This week: Work on more ff60-esr tickets: (#26128, #14952, #25555) Rebase branches for mozilla-beta (#26233) (sysrqb: great, thanks!) sukhe: Last Week: - Worked on #26073. I think it's done but I will wait for it to be merged. - Meeting with Hooman: #25483 This Week: - Will work on #26216 and #26203 - If there is a higher priority ticket for the nightly, please let me know. [GeKo: no, #26203 is the highest prio for now] Georg

1 0

[TSoP2018] Bandwidth scanner status - status report #1
by juga 30 May '18

30 May '18

Hi, Since SoP started, these has been the tasks i have worked on: Bandwidth List format specification: -------------------------------------- - Version 1.1.0 was merged [1] - Replace timestamp by the the latest scanner result time [2] - Started to work on adding KeyValues counting errors in Bandwidth Lines [3] little-t-tor -------------- - Stop logging stack contents when reading a zero-length bandwidth file [4] - Fix Tor to accept node_id at the end of a bandwidth file line [5] - Stop warning when Bandwidth files contain additional header lines [6] - Create unit test for the additional header lines and for whole Bandwidth files [7] Simple Bandwidth Scanner (sbws): --------------------------------- - Discussion about the order of hops when measuring relays [8] - Make sbws a proper Python package by including all files required in source and binary distributions [9] Generation of Bandwidth List files: - Started to work on adding failure types and number to the Relays' Bandwidth Lines [10] - Replace timestamp by the the latest scanner result time [11] - Add additional headers [12] - Include software and sofware_version headers [13] Best, juga. [1] https://trac.torproject.org/projects/tor/ticket/25869 [2] https://trac.torproject.org/projects/tor/ticket/26155 [3] https://trac.torproject.org/projects/tor/ticket/26200 [4] https://trac.torproject.org/projects/tor/ticket/26007 [5] https://trac.torproject.org/projects/tor/ticket/26004 [6] https://trac.torproject.org/projects/tor/ticket/25960 [7] https://trac.torproject.org/projects/tor/ticket/25947 [8] https://github.com/pastly/simple-bw-scanner/issues/167 [9] https://github.com/pastly/simple-bw-scanner/pull/163 [10] https://github.com/pastly/simple-bw-scanner/issues/160 [11] https://github.com/pastly/simple-bw-scanner/issues/169 [12] https://github.com/pastly/simple-bw-scanner/pull/130, https://github.com/pastly/simple-bw-scanner/issues/119 [13] https://github.com/pastly/simple-bw-scanner/issues/128

1 0

Fwd: [TSoP2018] Ahmia status update #1
by Stelios Barberakis 29 May '18

29 May '18

Hello all, This is an update report for ahmia project, as part of the Tor Summer of Privacy 2018. The first two weeks I have been working on updating and slightly improving the codebase of *ahmia-site, ahmia-index, ahmia-crawler* subprojects. More specifically: * Updating python packages and adding python3 support (default version from now on), to have a clean building process. * Prettifying the code towards pep8 compliance * Fixing some minor issues, like unresolved references, substitude deprecated methods, etc * Separating code from configuration by introducing environment variables approach through python-decouple. The already pushed commits can be found at the corresponding github repositories [1] <https://github.com/ahmia/ahmia-site/commits/tsop18>, [2 <https://github.com/ahmia/ahmia-crawler/commits/tsop18>], [3 <https://github.com/ahmia/ahmia-index/commits/tsop18>]. Best Regards, Stelios -- PGP key: http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xBF6EA91B7CBE3998

1 0

[TSoP] stem.client - status report #1
by Dave Rolek 28 May '18

28 May '18

Hi everyone! This is my first status report for the stem.client TSoP project [1]. # Updates A lot of these first two weeks has been improving development processes, workflows, and coordination. A new Trac keyword "dev" now exists for stem tickets related to developers/development. [2][3] I'll be adding more and addressing some of these soon. I continued some work on the stem.control caching behavior, to wrap up #25821 [4] and tie out a remnant event into a new ticket, #26129 [5]. I've been planning out some of the architecture/design of stem.client [6], as well as reviewing existing code [7]. For the former, I'm especially considering how to make stem.client most useful within the Tor and Python ecosystems. I've looked at the "sans-io" style in hyper-h2 that meejah mentioned [8][9][10][11], along with similar resources [12][13][14]. I've also been looking at a few of the modules in the Python stdlib and projects in the ecosystem, to try to understand their potential integration points. # What's next For both architecture and code review, I have a bit more work to do. I'll confer further with Damian for these. Architecture discussion will be started on a private pad and then opened up to the larger community. Afterwards, I'll be moving onto these cells: * CREATE * CREATED * CREATE2 * CREATED2 * PADDING_NEGOTIATE And then I'll be working on CERTS, AUTH_CHALLENGE, NETINFO cells and the "v3 handshake". # Other Tor things I'd like to point out some other Tor things I'm doing, too, that aren't under the scope of stem :). I've had some mild involvement in the University of Michigan getting their exit node [15] up and running again. And Cryptoparty Ann Arbor will be having an event on Sat., June 9th, at the public library. [16] # Closing As with before, I've been active and reachable over IRC, where my nick is dmr. I'm still attending the network-team meetings, and since I've been asking some clarifications on the tor-spec [17], I'll probably be more chatty in those soon, too! Please don't hesitate to reach out to me via IRC or email. Thanks, Dave [1] https://lists.torproject.org/pipermail/tor-dev/2018-April/013090.html [2] https://trac.torproject.org/projects/tor/query?keywords=~dev&component=Core… [3] https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs?action=diff&con… [4] https://trac.torproject.org/projects/tor/ticket/25821 [5] https://trac.torproject.org/projects/tor/ticket/26129 [6] https://trac.torproject.org/projects/tor/ticket/26226 [7] https://trac.torproject.org/projects/tor/ticket/26227 [8] https://lists.torproject.org/pipermail/tor-dev/2018-February/012906.html [9] https://lists.torproject.org/pipermail/tor-dev/2018-February/012908.html [10] https://lists.torproject.org/pipermail/tor-dev/2018-April/013100.html [11] https://python-hyper.org/h2/en/stable/ [12] https://sans-io.readthedocs.io/how-to-sans-io.html [13] https://www.youtube.com/watch?v=7cC3_jGwl_U [14] https://github.com/python-hyper/h11 [15] https://metrics.torproject.org/rs.html#details/5AFAC3D00E97D6733112CC9CA2A7… [16] https://aadl.org/node/372209 [17] https://trac.torproject.org/projects/tor/ticket/26228

1 0