- tor-project - lists.torproject.org

hackweek in Brussels - notes
by Gaba 11 Feb '19

11 Feb '19

Hi! We had a great hackweek in Brussels with the metrics, network and sysadmin teams. On Monday we set shared agreements [0] for the week and went through the agenda. We did the network team retrospective [1] and discussed how a lack of team diversity affects the quality of our work. One of the point that came out of there is a discussion on hiring process. At the beginning of the week we drafted the network team roadmap[3] and finish it [4] on Friday. The metrics team worked on its roadmap [2] and sysadmin team went over services[19]. Sessions we had: . Discussion on modularization[5] for the refactoring work we will be doing during 2019. . Where do we want to be in 2 years? [6] . ahf presented snowflake [7] and lead the discussion with cohosh [8] . Helping users that are not us [9] . Mike Perry presented the work he has been doing with asn on website traffic fingerprinting defense [10] . Teor presented the work on privcount and the challenges that we are having [11] . Discussion on code review [12] . Chutney for the next 6 months [13] . Juga presented what they are working on bandwidth scanner and open questions [14] . A discussion on the maintaner role [15] and on release planning [16] . Metrics team discussed the work on extending OnionPerf to work with Pluggable Transports [17] . Last but not least an evaluation of the hackweek [18] cheers, gaba [0] shared agreements https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [1] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [2] https://storm.torproject.org/shared/TsgBadLSfM8uh_aftPjxmR_rm0a8E-4UQ2HEa_l0DHv [3] https://people.torproject.org/~nickm/volatile/roadmapping_v1/ [4] https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… [5] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [6] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [7] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [8] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [9] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [10] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [11] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [12] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [13] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [14] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [15] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [16] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [17] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Brussels/Not… [18] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetw… [19] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdmi…

1 0

January 2019 report for the UX team
by Antonela Debiasi 11 Feb '19

11 Feb '19

Hello Tor, During January the UX team have been collaborating with the Community Team on creating our new outreach material. Our ongoing work with Personas allowed us to create content focused on each different use case and user goal. We are going to have it localized and ready for download and print for organizations and partners who want to use them with their local communities. You can sneak peek them now: https://share.riseup.net/#8aTI-VwMHFbZaud4xkE_pA TBA is going to reach stable probably in March, and we worked closely with the mobile team to provide an intuitive and smooth experience for users connecting to Tor. The work is currently in development, and you can follow our design discussions here: https://trac.torproject.org/projects/tor/ticket/28329 Are you a Tor Browser Alpha kind of person? If yes, you already saw our new Tor Browser icon in action. If not, you can experience it by downloading our Alpha here (you can give us feedback also!) Thanks pospeselr for this shiny implementation! https://www.torproject.org/projects/torbrowser.html.en#downloads-alpha Pilar started a kanban board to track our open projects. You can lurk them here: https://storm.torproject.org/shared/4LLhH5s-55_Vj0uO9W8t6LD9_WqmuS9bjTB3AE3… During our global-south travel in Colombia last year, we met Bea. She is an activist and a Tor and Tails heavy user. We put her in contact with our friends at Tails and Sajolida interviewed her. They made it public this month, and you can read it: https://tails.boum.org/blueprint/interviews/#Bea We are still working with OONI on Explorer revamp. January was the time for the Country pages redesign. Our goals with this redesign are: giving an understanding to a visitor about how comprehensive and reliable the data OONI has on that country, present high-level findings, provide insights that act as an entry point to the search pages and cross-reference link to OONI research reports for that country. Maria coordinated usability research for our first wireframe iteration with partners, and it gave us light on how researchers are using Explorer nowadays and what they expect for the next iteration. That allowed us to work in a new round of high definition mockups focusing on how we are displaying data and how we are enabling the interface for researchers to compare across data sets. Take a look at this hottie that Elio is working on: https://www.figma.com/file/Z6PtVLW7YkqcTRIRsO2Qzg/Explorer-Country-Pages?no… The new Tor Project website is about to see the light, and we are polishing details in staging to make it possible: https://lektor-staging.torproject.org/tpo/staging/ Caroline Sinders is joining us this quarter as our User Research Coordinator. We put together the plans for our user Research for this Q119. We want to collect feedback on our new Onboarding and also on our new Security Settings. You can read them here: https://storm.torproject.org/shared/MUHbKrR0C1xakVNSQ0nRu9mwAdjAz5tSVhoOtZk… Gaba and Pilar collected priorities and needs for each team at the project. The UX Team ones for this 2019 are listed here: https://storm.torproject.org/grain/LjABMdzjECRMGoYeMgSjsf/ Hiro and I proposed a new feature for OnionShare that allows users to publish ephemeral .onion sites by merely dragging and dropping a folder inside OnionShare. This month, we got micahflee blessing, and it is scheduled for the next 2.1 release. You can read more here: https://github.com/micahflee/onionshare/issues/791 Are you a person interested on end-users? If you arrived to the end of this email, probably yes. Remember that our weekly meetings happen every Tuesday at 1400 UTC in #tor-meeting on OFTC. https://trac.torproject.org/projects/tor/wiki/org/teams/UxTeam See you online! A

1 0

Notes from February 7 2019 Vegas team meeting
by Karsten Loesing 08 Feb '19

08 Feb '19

Notes for February 7 2019 meeting: Arturo: 1) Moving forward with OONI Explorer design work 2) Resolving some incident which results in some measurements not being available in OONI Explorer and in the API Georg: 1) Moving forward with our mobile and toolchain work 2) Tor (Browser) hiring Pili: 1) GSoC Application for Tor submitted 2) Reviewed VPN with Tor doc 3) Organising Team Vision brainstorming sessions. Alison: 1) Working on training materials for the community portal. Also still finishing the outreach materials. 2) LFI recruitment 3) Three months checkins with all members of the first LFI cohort 4) Working on LF website redesign 5) Working on LFI curriculum 6) Colin held a relay operator meetup at FOSDEM 7) Kat is working on the next sponsor 19 report 8) Maggie wrote the first draft of the Tor vs VPN doc. I still need to review it! 9) Gus and emma held an AMA with Localization Lab. 10) Next community team meeting will be a brainstorming session about where we want to go in the next few years. Nick: 1) Recovering from Brussels meeting. 2) trying to wrap stuff up for 0.4.0. Make sure we know if there is a bug that you think is an 0.4.0 blocker or a must-backport blocker.V We don't need to have a discussion about this at this meeting, but please make sure that it is tagged with tbb-wants or tbb-needs, or the appropriate version of that for your project or team. 3) 0.4.1 opens for merges at the end of next week. 4) We're changing how we merge stuff in Tor: we plan to require that for each merge, the author, the reviewer, and the merger be three separate people. 5) Put out proposal 300: it's a start of a plan for scaling tor. 6) Due to brussels meeting recovery and upcoming leave, expect network team to be at low capacity for a while. Make sure we know about what you need us to know. Mike: 1) Recovering from brussels 2) Tagged a new vanguard release. Waiting on debian packages to appear in testing, then will do a blog post about using vanguards with onion services and Tor Browser. Sarah: 1) Donation page redesign and adding pages for monthly giving, major donors, and cryptocurrency. 2) Finalized Kraken account that will allow us to accept additional types of cryptocurrencies. Setting up wallets with the most requested. Engaging with folks who can cross promote to their followers when we launch. 3) Contacted all monthly donors to send 2018 donation statement. 4) Working with Jon to sort out some data-entry details. 5) Al submitted two proposals to NLnet and an OTF proposal as well as a narrative rewrite for the OTF onion services proposal. 6) Helped with the new Sponsors page. Steph: 1) inquiries. 2) working on the comms strategy 3) will be chatting with Mozilla about the internet health report. 4) finished new tor stories survey, will start sharing soon 5) reviewing website content Karsten: 1) Had a very useful team meeting together with the network team and sysadmin team in Brussels. 2) Made a new 6-month roadmap from February to July that will soon show up as Storm Kanban thing. 3) Started analyzing parts of the OnionPerf data that didn't make it to the Tor Metrics website so far. 4) Wrote down initial guidelines for adding new data to Tor Metrics (#29315). isabela: 1) working on budget estimations for dev meeting 2) Working w/ Sue on follow ups w/ sida 3) catching up on backlog of to do items from before Brussels 4) catching up w/ backlog of to do items from Brussels 5) planning a trip to Seattle office in March (probably week of March 11) 6) sent dev meeting change update to tor-project/internal antonela: 1) did a talk in FOSDEM last week, went great, we have designers interested in our work and I should back to them. 2) working on usability research documents for India and Thailand travels. 3) pushing all that is needed to have tpo.org and landings ready for release. You can sneak peek here https://lektor-staging.torproject.org/tpo/staging/. 4) working on donate.tpo wireframes to discuss this week meeting. 5) working on introducing a Call for Design structure where we can enable new UXD collabs to work on projects without funding. 6) working with OONI on Explorer redesign, we did usability research, we did a retrospective after that, and we are working on high definition mockups now. 7) preparing a call with Simply Secure next week to talk about Persona and a new possible OTF project, the new metrics portal. gaba: 1) recovering from hackweek 2) still in brussels doing tails stuff 3) digitalizing stuff from hackweek ewyatt: 1) General hr stuff

1 0

Anti-Censorship Team Meeting Notes, 7 Feb 2019
by Alexander Færøy 07 Feb '19

07 Feb '19

Hello. The weekly anti-censorship team meeting just finished. The IRC log of the meeting can be found at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-02-07-19.58.txt We had two discussion topics for the meeting this week: - The Brussels meeting. We walked over what we discussed and worked on in Brussels that was related to the anti-censorship team. - The Snowflake workflow: We discussed how we should onboard more people to get involved with the Snowflake codebase. For now we'll ramp up the new people on the anti-censorship team and try to help each other with doing code reviews, but we continue with Trac + git.torproject.org. Later on we can look into experimenting with more "modern" workflows such as Gitlab if that becomes available. The status updates from this week: Gaba: Last week: - hackweek in Brussels This week (02/07): - digitalize roadmap from hackweek - get up all the stuff from snowflake, bridgedb and pluggable transports into its own roadmaps. dgoulet: This week: - Going over BridgeDB infrastructure with sysrqb. - Got commit access to bridgedb.git and ssh access to the machine where it is running. - Documenting everything in the process! ahf: Last week: - Tor meeting in Brussels + attended FOSDEM. - Onboarding of cohosh - Roadmapping with cohosh, arma, and gaba. Lots of tickets was created. Sorry for the confusion if some of the tickets have slightly vague descriptions. This week: - Relax a bit after our meeting. - Follow up on everything from the meeting: look at roadmapped tickets, etc. - Continue with architecture document. - Figure out where we should begin with Snowflake: code reviews, repositories, etc. - Do the goptlibext library after discussing with dcf on #28940 kat5: Working on: - report 2 - going over new tickets (since Brussels) to figure out what to integrate into report 2 Help with: - private bridge guide for NGOs (hold off until we figure out a strategy for making set-up easy) - not sure where this is nor what should heppen next anto (offline): Working on: - Planning a Call for Design for Gettor, once we have the PRD doc ready - https://docs.google.com/document/d/18R_tUnqfFkn7d93w0pEbBOLxB62KAWHbUGd5MPK… pili (offline): working on: - gettor - agreed on next steps to deploy refactored code with ilv and hiro - still need to define project scope with gaba, antonela and hiro help with: - Browser team can't commit anyone to work on snowflake web extension - can we not just: a) wait for integration into cupcake (see https://github.com/glamrock/cupcake/issues/24) - we can help them with this also b) wait for anti-censorship developer - we need to also think about who is going to maintain this webextension dcf: 2019-02-07 Last week: - added proxy support and more tests to meek with uTLS, now a merge candidate (#29077) - meek and snowflake sysadmin (#29171, #29172, gave cohosh access to broker and bridge hosts) - checked the meek fingerprint in Tor Browser 8 (#26241) - upgraded Go in tor-browser-build (#29167) - housekeeping in tor-browser-build (#29349) - started working on a WebExtension port of meek-http-helper, for compatibility with the next ESR and for experimentation with ESNI (#29347) This week: - get review on meek with uTLS, maybe merge? - open a discussion about meek/meek_lite with uTLS in Tor Browser to replace the headless Firefox - meek-http-helper WebExtension Help with: - review on https://bugs.torproject.org/29308 - disable old Snowflake proxy-go instances - review on https://bugs.torproject.org/29077#comment:20 - meek-client with uTLS Samdney: Working on: - Will also have a look at the WebExtension ticket #23888 :) - Looking for something where they can help!!! - If you have anything in the direction of "research" or "investigation" in something, then I'm your guy! :) (- I'm working on a research project about censor <-> classical attacker in game theory. That's maybe later, when I have results :), interesting for UX/dev stuff.) _hc/eighthave: uniqx and I have been working on ways to integrate PTs into apps easily. we have a working client/server automation setup based in Python. We also were trying to do a more generic proxy, https://lists.torproject.org/pipermail/tor-dev/2019-January/013637.html n8fr8 is working on getting obfs4 into our Android Pluggable Transports library. he's having trouble getting it to connect to our server automation In Feb, I'll be working on figuring out a good URL scheme for bridge configuraton - #15035 OTF accepted our Concept Note with Stephen Farrell for working on ESNI and ensuring circumvention is included. We are submitting the proposal now, chances look good! cecylia (cohosh): Last week: - network team meeting in Brussels - started getting onboarded to new anti-censorship team - looked a bit into what we need before we talk to NGOs about reachability of obfs4 bridges This week: - Come up with a definite plan for obfs4 reachability tests - Continue getting up to speed on snowflake - Start on Snowflake tasks Help with: - Decisions on workflow for various projects (Snowflake, and BridgeDB) - Will probably reach out for questions about current infrastructure catalyst: week of 2019-01-28 (2019-W05) (actual): - Brussels meeting week of 2019-02-04 (2019-W06) (planned): - recovery from travel - maybe look at #28925 some more Cheers, Alex. -- Alexander Færøy

1 0

January 2019 report for the Tor Browser team
by Georg Koppen 07 Feb '19

07 Feb '19

Hi everyone! 2019 started with two releases for the Tor Browser team, Tor Browser 8.0.5[1] and 8.5a7[2]. Both contain security fixes to Firefox and ship updated Tor versions (0.3.5.7 and 0.4.0.1-alpha, respectively). The alpha release, moreover, contains our new logo for the alpha channel (thanks to Antonela and Richard for driving this!) and a number of fixes to crashes noticed in previous releases.[3][4][5] Apart from working on those releases we moved forward with our work on the next Tor Browser for Android milestone, TBA-a3. All tickets tracked for this task can be found under the `TBA-a3` keyword.[6] For the desktop side we made further progress in our security settings redesign[7] and started to move to a new toolchain for Windows, which is now clang-based[8]. The full list of tickets closed by the Tor Browser team in January is accessible using the `TorBrowserTeam201901` keyword in our bug tracker.[9] In February we plan to release another alpha containing in partiulcar the latest improvements for mobile users and to start addressing the remaining blockers for a Tor Browser 8.5 stable release. We'll work further on our toolchain improvements (the mingw-w64/clang-based toolchain and building 32bit Linux bundles on 64bit machines[10]) and on our Tor Launcher and Torbutton integration into the browser code itself.[11][12] All tickets on our radar for this month can be seen with the `TorBrowserTeam201902` keyword in our bug tracker.[13] Georg [1] https://blog.torproject.org/new-release-tor-browser-805 [2] https://blog.torproject.org/new-release-tor-browser-85a7 [3] https://trac.torproject.org/projects/tor/ticket/28705 [4] https://trac.torproject.org/projects/tor/ticket/27531 [5] https://trac.torproject.org/projects/tor/ticket/28874 [6] https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~TBA… [7] https://trac.torproject.org/projects/tor/ticket/25658 [8] https://trac.torproject.org/projects/tor/ticket/28716 [9] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [10] https://trac.torproject.org/projects/tor/ticket/26323 [11] https://trac.torproject.org/projects/tor/ticket/28044 [12] https://trac.torproject.org/projects/tor/ticket/10760 [13] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

Board Meeting Minutes from December 10, 2018
by biella 06 Feb '19

06 Feb '19

Hi all, Please find our meetings from our Dec 10 2018 meeting here Regards, Gabriella https://gitweb.torproject.org/company/policies.git/commit/?id=83aa99915cd5a… Tor Project Board Meeting Minutes for December 10, 2018 Phone/video meeting called to order at 16:00 UTC Present: Isabela Bagueros, Shari Steele, Matt Blaze, Ramy Raoof, Cindy Cohn, Biella Coleman, Julius Mittenzwei, Roger Dingledine, Megan Price, Nighat D – Approval of October 1, 2018 minutes. Biella made the motion to approve, Ramy seconded, all voted in favor. RESOLVED: board approved minutes from October 1, 2018. 2. Board Discussed and Passed Two Resolutions around Bank and Stock Accounts – Motion one: The board of directors of the Tor Project, Inc., hereby authorizes Sue Abt, Erin Wyatt and Cindy Cohn to be added as a signatory on the organization's Bank of America checking account #XXXXX.Cindy moved the motion, Julius second, all voted in favor. – Motion two: The board of directors of the Tor Project, Inc., hereby authorizes Sue Abt to be added as signatory on the organization's Merrill Lynch stock account.Cindy moved the motion, Matt seconded the motion, all voted in favor. RESOLVED: Sue Abt, Erin Wyatt and Cindy Cohn added as signatories on the organization's Bank of America checking account and Sue Abt added as signatory on the organization's Merrill Lynch stock account. 3. Finances – Isabela went over grants, budget, and pending grants. – Discussion about changes aroundgrant writing and hiring priorities. Nick left 12:32 4. New board members – After Cindy’s initial discussion Shari, Ramy, and Biella volunteered to reach out to prospective candidate Meeting Adjourned at 18 UTC

2 1

Tor Browser team meeting notes, 4 Feb 2019
by Georg Koppen 04 Feb '19

04 Feb '19

Hello! Our first weekly meeting in February 2019 just finished. The IRC log, as usual, can be found at: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-02-04-18.29.l… The notes from the pad are: Monday February 4, 2019 tjr - I am working this week, on: https://bugzilla.mozilla.org/show_bug.cgi?id=1407366 letterboxing prototype replying to geko's reply to my emails would like to work on the accessibility issue; but I think jacek is better suited. i asked if it was on his radar (GeKo: thanks, and yeah, Jacek helping would be very neat here) review gk's mingw-clang work yah know - emails and stuff - Not planning to work on this week: https://bugzilla.mozilla.org/show_bug.cgi?id=1471698 Work around binutils corrupting mingw clang binaries. https://bugzilla.mozilla.org/show_bug.cgi?id=1524742 What is Tor's thought on this? (GeKo: not high prio but it would be neat to get this fixed) mcs and brade: Last week: - Shared draft proposal for #28044 (Integrate Tor Launcher into tor-browser): https://lists.torproject.org/pipermail/tbb-dev/2019-January/000951.html - Created a patch for #29180 (MAR download stalls when about dialog is opened). - Revised patch for #28885 (notify users that update is downloading). - Started to look at the Firefox updater security audit report. This week: - #29328 (account for tor 0.4.0.x's revised bootstrap status reporting). - #29045 (ask tor to leave dormant mode). - Spend more time looking at the Firefox updater security audit report. - Respond to feedback on #28044 proposal (Integrate Tor Launcher into tor-browser). pili: Last week: - GSoC - S8 (TBA) Q4 report submitted This week: - Tor Browser Release meeting - Tor Browser Vision meeting sysrqb: Last week: - 80% complete with patch for #28329 (Bootstrapping UI) (GeKo: Yay, for getting this ready, it's a ton of work!) - Began looking at TOPL patches - Chatted with Anto about bootstrapping UI This week: - Finally, really, actually finish #28329 - Finish TOPL patch review - Integrate #28329 with TOPL (if any changes are needed) - Move onto next TBA-a3 ticket boklm: Last week: - published the releases - made patch for #29193 (obfs4 needs golang.org/x/net/http2) - made patch for #29235 (Build of https-everywhere fails because python3.6 is not available in buster anymore) - read the proposal for #28044 (Integrate Tor Launcher into tor-browser) This week: - try to get working patch for #26323 (Build 32bit Linux bundles on 64bit systems) - continue work on testsuite - some reviews - make patch for #29183 (We are using linux i686 langpacks in the linux x86_64 builds) igt0: Last week: - UI for #25764 is done, the integration side is a bit messy. - Review and tested more stuff This week: - Fix rough edges of my patch to the #25764 GeKo: Last week: - did a lot of work regarding the mingw-w64/clang toolchain: wrote patches for #28716, #29307, #29319; helped upstreaming an lld patch (https://bugs.llvm.org/show_bug.cgi?id=40582) and opened tickets for the remaining items to work on; posted bundles on #28238 to test the result - work on Torbutton integration into Tor Browser (#10760) - started to look into NSIS reproducibility issue (#29185) - reduced my email backlog - helped with the releases and dealt with blog comments - looked over the Tor Launcher proposal This week: - more work on #29185 and #10760 - looking into open issues for the mingw-w64 toolchain (SSP support, reproducibility) - begin of the month team admin stuff pospeselr: Last week: - various code reviews - #25658 (securiyt settings) UI work This week: - #25658, make all the new XUL actually do something besides look pretty - antonela: would you like a preview build of what we have so far? sisbell: Last week: - 29080/27609: TOPL - fixed more issues In TOPL based on feedback/testing - pull request being reviewed. Added content providers to tor-android-service. Started fixes based on orbot patches (in tor-browser-build). This Week: - 29312 - TBB for TOPL - 29313 - TBB for tor-android-service - Finish adding patches for tor-android-service - Will be taking PTO Friday (and possibly following Monday) Georg

1 0

Tor Browser Release Meeting: Wednesday 6th February @1900UTC
by Pili Guerra 04 Feb '19

04 Feb '19

Hi everyone, It's time for our next Browser Release meeting: Wednesday 6th February @1900UTC over at #tor-meeting We’re now looking ahead at our next Tor Browser Alpha release at the end of February as well as the security and stable releases in March. We’ll be taking requests, so please come along if you have anything you’d like to discuss. We look forward to seeing you there :) Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

announcing the next Tor Meeting location....
by Alison Macrina 04 Feb '19

04 Feb '19

We're excited to meet and hack with the Tor community in Athens, Greece in May 2019! The meeting planners are working on finalizing the precise dates and people for the invite-only portion of the meeting, but the open days will be held 18-19 May. Mark your calendars! Alison -- Alison Macrina Community Team Lead The Tor Project

3 3

Two new open jobs at Tor Project!
by Erin Wyatt 31 Jan '19

31 Jan '19

Hey everyone! We have two new open positions. Please help us spread the word! + Browser Developer https://www.torproject.org/about/jobs-browserdeveloper.html.en + Backend Engineer for OONI https://www.torproject.org/about/jobs-backenddeveloper.html.en Both job descriptions are attached in PDF and plain text format, and both are pasted below. Please share, forward, tweet, etc! Thank you! Have a great weekend. Cheers, Erin Wyatt Director of People and Office Operations ewyatt(a)torproject.org PGP: 35E7 2A9F 6655 45F9 2CB6 6624 BA0C 9400 F80F 91CE ———————————>8———————————>8———————————>8 Internet Freedom Nonprofit Seeks Backend Engineer for OONI The Tor Project, Inc. is looking for a dedicated backend engineer to work on OONI (https://ooni.torproject.org/) OONI is the Open Observatory of Network Interference: a free and open source software, global observation network for detecting censorship, surveillance, and traffic manipulation on the internet. You will be working to improve OONI’s data processing pipeline and other backend components responsible for recording measurements collected from our growing global user network. You will also be tasked with improving our network measurement methodologies and data analysis heuristics to increase the accuracy of our experiments. This is a full-time 12-month contract position, starting ASAP (no later than mid-May 2019); contract may be extended. The OONI team is based in Europe. However, this position may be performed remotely. Here are some of our code repositories: https://github.com/ooni/api https://github.com/ooni/pipeline https://github.com/ooni/orchestra https://github.com/ooni/collector https://github.com/ooni/sysadmin Required skills and qualifications: - Extensive experience in python or golang. - Comfortable working remotely. - Self-directed, self-disciplined, but good at working and communicating with a team. - Have experience and be comfortable with others reviewing your code and design; have experience and be comfortable reviewing others’ code. - Experience documenting and designing protocols. - Be comfortable with transparency! Preferred qualifications: - Experience designing, implementing, and maintaining scalable complex network applications. - Working experience with data processing pipelines. - Possess the confidence to refactor code and write unit-tests. - Familiarity with the challenges of developing and scaling data processing pipelines. - Familiarity with the network measurement field. - Experience with open-source software development, including working with distributed teams across different time-zones containing employees and volunteers of differing skill levels. - Basic familiarity with distributed version control systems. - Contributed significant chunks of code to multiple open-source projects in the past. - Be passionate about internet freedom and interested in contributing to it in a concrete way! Other notes: Academic degrees are great but not required if you have the right experience. You should be very good at working remotely at communicating with the team on a daily basis via Slack, IRC, instant messaging, email, and issue trackers. Salary negotiable. How to apply: Please email a *PDF* of your resume/CV, and a cover letter explaining how your qualifications and experience meet the requirements of this job description. Please include the reasons why you want to work on OONI. Please also include link to one or several code samples (of which you are authorized to share), and also your GitHub or GitLab profile, and three professional references. Email should be sent to jobs at openobservatory dot org with "OONI Backend Engineer" in the subject line. About the project: The Open Observatory of Network Interference (OONI) is a free software project under the Tor Project. OONI collects and processes network measurements with the aim of detecting network interferences, such as censorship, surveillance, and traffic manipulation. Since late 2012, OONI has collected millions of measurements across more than 90 countries around the world. The Tor Project, Inc., is a 501(c)(3) non-profit organization that provides the technical infrastructure for privacy protection over the Internet. With paid staff and contractors of around 30 technologists and operational support people, plus many volunteers all over the world who contribute to our work, the Tor Project is funded in part by government grants and contracts, as well as by individual, foundation, and corporate donations. We only write free and open source software, and we don't believe in software patents. The Tor Project, Inc., is an equal opportunity, affirmative action employer. ———————————>8———————————>8———————————>8 The Tor Project is looking for a Browser Developer (C++ and Javascript) As a browser developer, your job would be to work closely with other members of the Tor Browser development team on C++ patches to our Firefox-based browser, writing new APIs, altering functionality for privacy and security, and making improvements to our collection of Firefox add-ons (JavaScript code). Being a Tor Browser developer includes triaging, diagnosing, and fixing bugs; looking for and resolving web privacy issues; responding on short notice to urgent security issues; and working collaboratively with coworkers and volunteers to implement new features and web behavior changes. We also need help making our code more maintainable, testable, and mergeable by upstream. The person in this position will also review other people's code, designs, and academic research papers to make suggestions for improvement. This is a full-time position. Required Qualifications: - Experience in C++ (and ideally, JavaScript). Five years of C++ experience is probably necessary for the level of expertise we want, though some of these years can be replaced with other Object Oriented Programming and/or C experience. If you meet this level of experience with C++/OOP, JavaScript can be learned on the job. - Possess a solid understanding of issues surrounding secure C++ programming and reference counted memory (at least to the level of avoiding issues). - Be comfortable diving into new, unfamiliar codebases, looking for ways to alter and augment their functionality in specific, goal-oriented ways. - Be familiar with web technologies and how the web works, especially the same-origin model and web tracking. - Willingness and ability to justify and document technical decisions for a public, world-wide technical audience. - Be comfortable working remotely with a geographically distributed team. - Experience interacting with users and other developers online, including experience being confronted with differing ideas and opinions (not always in a nice manner), while maintaining a high level of professionalism. - Comfort with transparency: as a non-profit organization who develops open source software, almost everything we do is public, including your name (or at least your business name) and possibly salary information. Preferred qualifications: - Familiarity and/or experience with writing add-ons and/or patches for Mozilla Firefox or other web browsers. - Familiarity with compiling software for the Android platform. - Familiarity with browser fingerprinting defenses - Familiarity with Firefox's internal architecture, including its use of multiple processes and sandboxing. - Be intensely creative yet also ruthlessly pragmatic in your thinking. - Possess knowledge/familiarity of probability, statistics, and information theory. - Know enough about networking to be able to visualize what HTTP 1.1 looks like on the wire while encapsulated within Tor's network protocol. - Experience working with distributed (remote) teams across different time-zones with people of differing skill levels over multiple mediums, including email, instant messaging, and IRC. - Open-source experience: contributed significant chunks of code to multiple open-source projects in the past. - Familiarity with distributed version control systems, including Git. - Familiarity with rust - Genuinely be excited about Tor and its values! - Willingness and ability to travel internationally to twice-yearly team meetings (strongly preferred). For a more detailed understanding of the full breadth and depth of the work you'd be doing, have a look at The Design and Implementation of the Tor Browser, especially The Design Requirements section at https://www.torproject.org/projects/torbrowser/design/#DesignRequirements. Academic degrees are great, but not required if you have the right experience! The team coordinates via IRC, email, and bug trackers. This position may be performed remotely, but we would be happy to provide a desk at our office in Seattle, Washington. Salary negotiable. We have a competitive benefits package, including a generous PTO policy; 14 paid holidays per year (US; including the week between Christmas and New Year's, when the office is closed); health, vision, dental, disability, and life insurance; flexible work schedule; and occasional travel opportunities. To apply: Please email a *PDF* of your resume/CV, and a cover letter explaining how your qualifications and experience meet the requirements of this job description. Please include the reasons why you want to work at Tor Project, and include links to code samples, if possible. Email should be sent to job-browser at torproject.org with "Browser Developer" in the subject line. Link to at least one of your code samples (ideally, more than one and all of which we will presume you are authorized to disclose). No phone calls, please! About the Organization: The Tor Project, Inc., is a 501(c)(3) non-profit organization that provides the technical infrastructure for privacy protection over the Internet. With paid staff and contractors of around 30 technologists and operational support people, plus many volunteers all over the world who contribute to our work, the Tor Project is funded in part by government grants and contracts, as well as by individual, foundation, and corporate donations. We only write free and open source software, and we don't believe in software patents. The Tor Project, Inc., is an equal opportunity, affirmative action employer.

1 0