- tor-project - lists.torproject.org

Notes from Vegas Meeting OCTOBER 10 2019
by Erin Wyatt 12 Oct '19

12 Oct '19

Vegas Team Meeting Notes OCTOBER 10 2019 ++ OLD BUSINESS + From Oct 3: "What is our policy on people printing Tor swag for themselves" -> isabela will write a policy w/ Jon + From Oct 3: Are we still paying $800/mo for the blog hosting? -> today we have a meeting regarding blog; we haven't yet paid $800/month + From Oct 3: MOSS future? Answer: it is being tracked by the money-machine-meetings + From Sept 26: Gitlab CE EE progress -- we will go with CE and take back this discussion on EE once we migrate. + From Sept 26: Plans for Mozilla All Hands, FOSDEM, ShmooCon -- and also CCC -> isabela and sue need to balance the budget to see how spending is going before deciding on spending more -> FOSDEM is being organized by Pili, For moz allhands we sent 'who should go' from last week to Arthur. + From Sep 12: Revamp our "matching speakers to invites" process - we have a list of people that could give talks and a list of events that would be good to go to. --------------->8 --------------->8 --------------->8 ++ NEW BUSINESS + Do we need more git service admins? See e.g. #31583 and #31486 and other tickets that are going months without attention. - Discussion: We don’t have that many unresolved tickets, but we also don’t know who is supposed to be doing them. No volunteers, so the issue remains unresolved. + Considering a change to the hardware FAQ to clarify what we want if we *do* accept donations - Discussion: We want to be more specific about what kind of hardware donations are helpful and what our policy will be in order to accept them; the FAQ on the website will be updated soon. --------------->8 --------------->8 --------------->8 ++ GENERAL NOTES + Roger: 1) We moved forward with dropping the obsolete relays from the network. I contacted many of them beforehand, and the next phase is that they notice and reach out to us and we help them upgrade and get back into the network. 2) I'm coordinating a Tor outreach talk in Taipei on Oct 31 with our friends there (pre OTF summit). 3) I'm working with Rob to shepherd a website fingerprinting paper that will hopefully get into the next Usenix Security conference. 4) I will soon plan to get back up to speed on our RACE work, to help Rob present at the PI meeting in early November. 5) Also on my todo list: NSF annual report x2; follow up to person doing security comic to help them fix their 'dark web' portrayal; coordinate upcoming Phoenix meeting and DC talk; investigate Mozilla's VPN experiment plan; answer anarcat's questions about our remaining uses of svn. 6) Do we need more git service admins? See e.g. #31583 and #31486 and other tickets that are going months without attention. + Gus: 1) Working with Outreachy applicants. If you see someone lost on IRC, point to them this wiki page: https://trac.torproject.org/projects/tor/wiki/Outreachy#Projects 2) Sponsor9 phase3: partners are submitting Partnership agreement signed, so far 3 organizations. 3) Following up with drupal freelancer + Antonela: 1) TB9 release: new identity, network settings, dark theme support, onboarding update. 2) EOY: working with Alon on the art, 3) S30: trying to coordinate a meeting with the involved people in Taipei 4) S27: working on TB error pages for onions 5) S9: Coordinating user research with communities with nah 6) meetings, meetings, meetings everywhere + Steph: 1) Corresponding with Outreachy folks 2) Inquiries 3) Signed a letter with 100+ orgs urging FB to continue encryption plans 4) Published and shared EOL relay post 5) Community portal review 6) Went through another edit of our fundraising deck 7) Edited copy for new TB onboarding 8) EOY campaign prep + Sarah: 1) EOY campaign prep 2) Sourcing new foundation prospects 3) Updating roadmap with foundation/grant deadlines 4) OTF proposal 6) First round of Brave Rewards transferred to us - almost $300 + Gaba: 1) S30: follow up from meeting this week 2) Meetings (sponsors, mozilla, proposals, weekly team meetings) 3) Gitlab migration 4) Small tasks, keeping up with trac. 5) Getting back the sponsor V report this week. + Anarcat 1) joined a call with giant rabbit about finances, security and cost, hiro also talked with them about upgrading their CiviCRM, some downtimes to be announced soon-ish 2) testing backup server restore procedures by replacing the backup server 3) monthly sysadmin meeting, notes in https://help.torproject.org/tsa/meeting/2019-10-07/ talked about onboarding and overlap between Puppet and Ansible, in particular 4) tracking major upgrades progress (fancy graphs!), visible at https://help.torproject.org/tsa/howto/upgrades/ - current est: june 2020 5) completed the "ops report card" in https://bugs.torproject.org/30881 - scored 44%, not bad for such an exhaustive questionnaire. 6) jabber service shutdown and LDAP sudo password transitions next week 7) puppet sprint last friday: working with real humans in the same room, whoohoo 8) considering a change to the hardware FAQ to clarify what we want if we *do* accept donations + Alex: 1) Work on 0.4.2 tasks. Hope to get back to S29 next week. 2) Continuing with the Gitlab migration work together with a lot of people from different teams. 3) Planning my Zurich trip for the end of the month to give a talk on Tor. + Georg 1) ESR 68 transition for Tor Browser (we are close) 2) OTF proposal work + Matt 1) What Georg said + isabela: 1) Wrote report to MDF regarding the fundraising training they have sponsored for us 2) Finalizing metrics for donors folder 3) Reviewing OTF full proposal + Nick: 1) Super busy in the network team! Another alpha came out on Monday. Expecting that 0.4.2.x series will go on schedule. 2) Team is discussing changes to our review/merge policies; ask if you're curious. Hoping to land them in October. + Mike: 1) Wrapping up Firefox ESR network code review + Pili: 1) Helping set up gitlab accounts for Outreachy people and trying to be generally helpful. 2) Submitted FOSDEM20 Stand request. Deadline is not until Nov 1 and accepted stands will be announced Nov 11. 3) Planning to submit FOSDEM20 main track talk today 4) S27 "extraordinary" meeting 5) OTF Browser proposal + Philipp: 1) Released BridgeDB v0.8.3 after merging several patches 2) Wrapped up our bridge campaign. 96 new bridges and a volunteer supplied us with several fast, private bridges 3) Wrote up anti-censorship research ideas, to be published on research.tp.o 4) Improvements of flow obfuscator for obfs4 5) Worked on localising snowflake website 6) More work on snowflake's broker/proxy protocol and tests + Erin: 1) Mostly AFK Tuesday through Thursday this week 2) General HR stuff

1 0

Anti-censorship meeting notes, 10 Oct 2019
by Philipp Winter 10 Oct '19

10 Oct '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-10-16.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday October 10th 17:00 UTC Weekly meetings, every Thursday at 17:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == * Our anti-censorship roadmap: https://dip.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/torproject/anti-censorship/gettor/boards * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Projects from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 --------------------------- --- 10th October 2019 --- --------------------------- == Announcements == * A volunteer set up 20 fast and private obfs4 bridges. We will hand them out to NGOs, for distribution among their users. * Let's continue last week's discussion on website mirrors in <https://bugs.torproject.org/31990>. * Our "set up new bridges" campaign is over. See #30777 for a summary. == Discussion == * Frontdesk - users from censored countries are asking private bridges. How do we handle it to them? - gus * Website: Isa asked if we could add gettor link if someone search Tor Project in Google. - gus == Actions == * == Interesting links == * == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. Hiro: Gettor moved off moly and to new VM. https://trac.torproject.org/projects/tor/ticket/31785 - Gettor only uses debian packages included in puppet and doesn't use virtualenv - Gettor is deployed via ansible - Gettor website is maintained via Lektor and deployed via Jenkins Nagios checks are working Started review and string translation: https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… Restore Twitter responder: https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… - https://dip.torproject.org/hiro/gettor/merge_requests/3/diffs Fixed metadata of files on archive.org Next Week: - Work on gettor specs - More with review of strings and website content and translation hiro: (2019-09-09)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) - gettor was down due to a VM reboot. Phw added a systemd script to reboot the service. - add archive.org - add gdrive - edit ansible scripts - edit scripts to upload files to various distribution endpoints Next week - reach out to irl about sending gettor stats to metrics - include reviews from code and website changes - review specs: are specs up-to-date? should we change something in the specs? - review docs: write documentation for web site and ansible playbooks. Help with: - probably more reviews. hiro: (2019-09-02)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) - Coded ansible recipes for gettor so that the service can be easily maintained by more people: https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… - Fixing some issues about git history taking too much space quota on gitlab and github Next week - use archive.org as new distribution endpoint: upload files to archive.org - reach out to irl about sending gettor stats to metrics - review specs: are specs up-to-date? should we change something in the specs? - review docs: write documentation for web site and ansible playbooks. Help with: - waiting to be told that's fine to upload files to archive.org? Can we start? - review new website. New website should be reviewed. https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… phw: This week (2019-10-03): * Wrote up anti-censorship research ideas and created patch for research.tp.o (#32007). * Created ticket to continue our discussion on mirrors (#31990). * Merged BridgeDB spec (#31780), translation request (#31903), and updated BridgeDB's requirements (#29484). * Released BridgeDB v0.8.3. * Attended Sponsor30 meeting. * Re-deployed meek-server on polyanthum (#31890). * Wrapped up our bridge setup campaign (#30777). * Tried to get a better grasp of how BridgeDB/babel/Transifex interact. * More polishing of obfs4 flow obfuscator prototype. * Reading up on the state of CAPTCHAs and if there's any hope (there isn't). * Sat in on RACE meeting to understand progress on obfs4 evaluation. Next week: * Wrapping up flow obfuscator prototype * Merge BridgeDB's language switcher Help with: * Gaba: (updated October 10th) Last week (): * sponsor 30 meeting This week (planned): * ahf Last week: - Worked on #28930 This week: - Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info. - Continued to work on a tool to convert Trac tickets into Gitlab tickets. cecylia (cohosh): last updated 2019-10-10 Last week: - make a patch for the proxy---broker communication (#29207) - implemented localization of snowflake website (#31384) - finished reviewing and merged linting fixes (#31794) - merged snowflake pion branch to master (#28942) - added an automatic packaging script for the webext (#31253) - worked on refactoring tests for #29259 - created ticket for tbb update to go1.13 This week: - more and better tests for #29206 (also related to #29259) - snowflake dogfood and think about how to address bad snowflake health - refactor proxy-pair state machine (#31310) - work on #29207 and #29206 - update webextension version and deploy new versions of snowflake broker and proxies (#31889) - more clearing out backlog - grant writing Help with: - review of #29207 and #29206 (dcf) - review of #31384 (phw or arlo) - review of #31253 (phw or arlo) catalyst: week of 09/19 (planned): - reviews - sponsor31 planning - coding style discussion - comment on draft network team review guidelines - #30984 week of 09/19 (actual): - reviews - sponsor31 planning - talking with people about proposed network team review processes week of 09/26 (planned): - reviews - sponsor31 doc coordination - checking in on Season of Docs work - #30984 arlolra: 2019-09-26 Last week: - mia Next week: - add a build step / documentation for code reuse in cupcake - pick up another ticket (looking at #31497, #31685, #31537, #31765, #31028, #31310) Help with: - review of #31391 dcf: 2019-10-10 Last week: - reviewed pion webrtc branch (#28942) - prototyping KCP and QUIC in obfs4proxy - made a post about recent Shadowsocks blocking https://github.com/net4people/bbs/issues/16 Next week: - prototyping KCP and QUIC in obfs4proxy - review #29206 (sequencing protocol for Snowflake) - review #29207 (broker protocol for Snowflake) - redeploy meek-server instances (#31890) - archive test pion builds from #28942 - migrate Snowflake broker to a datacenter with IPv6 (#29258) Help with: - need meek-azure to redeploy meek-server for #31890 - need to redeploy Snowflake broker and bridge for #31889

1 0

Network Team Meeting Notes, 7 October 2019
by Alexander Færøy 09 Oct '19

09 Oct '19

Hello, Here is a short summary of the network team meeting from Monday: 1) We started out by looking at the 0.4.2 status page on Trac to see how we are doing there. Some tickets were pushed to 0.4.3. We use the keyword `042-deferred` for tickets pushed to 0.4.3 in Trac. 2) We went over our kanban board to see if it is up-to-date. A lot of people are back to working on sponsored items as well as 0.4.2 items. 3) We went over the reviewer assignments by David and George. Everyone should have gotten around 1.2 reviews each this week. #31943 got priority as it is part of our GSoD project. 4) Alex asked for people to comment on a pad such that we can begin doing monthly network team reporting to tor-project(a)lists.torproject.org 5) A question was asked on how to handle the S27 ticket #14389 for 0.4.3 inclusion and the answer was that it was going to be discussed at the S27 meeting Tuesday this week. 6) No new policies to discuss this week. The other policies continues to be discussed on the internal network team mailing list. 7) Nobody had anything additional to discuss. --- end of summary --- You can read today's network team meeting log at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-07-16.59.html Below are the contents of our meeting pad: gaba: (updated on september 30th) Last week (actual): . s30 . s31 . 1:1:1s . get up to date with trac tickets This week (planned): . s30 coordination with all teams involved . roadmap update (bring october tickets) Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 23 September (planned): Take Time for: - gitlab signup / config - team policies: - faster reviews - commit bit and roles? - finish add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - split off bugs I found while writing the control trace code Roadmap: - Sponsor 31 outstanding bugs / tasks - Sponsor 31 possible coding tasks for me - follow up email Other: - finish off bug smash logging bugs Week of 23 September (actual): Take Time for: - gitlab signup / config - team policies: - faster reviews - commit bit and roles - kept working on add tor controller trace logging to diagnose stem hangs (#30901) - split off bugs I found while writing the control trace code - did some preparation work Roadmap: - Sponsor 27 - Add IPv6 HSv3 chutney tests to CI - Sponsor 31 reviews - Sponsor 31 modularisation: disable relay mode when compiling - Initial design and strategy to move forward - Preparation work - speed up CI Other: - Finish off bug smash logging bugs - Quick bug fixes x3 Week of 30 September (planned): Take Time for: - team policy discussions - meetings x3 Roadmap: - add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - Sponsor 31 modularisation: disable relay mode when compiling - First cut: disable DirCache, DirPort, ORPort, and sets --disable-module-dirauth - If I stall on coding, finish sponsor 31 documentation that's assigned to me Other: - Reviews and revisions - Check CI & backports Week of 30 September (actual): Urgent: - Take Time for: - team policy discussions - meetings x3 Roadmap: - Sponsor 31 config refactor - control trace logging #30901 - preparation work - fix conflicting bugs - started work - Sponsor 31 modularisation: disable relay mode when compiling #31851 - Initial design and strategy to move forward - Preparation work - speed up CI Other: - Revisions - Check CI & backports - Quick bug fixes x2 - tor-relays moderation Nick: Week of 30 September (planned): - One more PETS review. - Work on 042-must/should items - Start on another alpha, if all the -must items are done? - Kick off a C style poll - More review and feedback on pending refactoring - Review and merge stuff - Finish circuit-padding editing Week of 30 September (actual): - More editing on circuitpadding docs - another PETS review - Resolve a coverity issue (31948) - Mock DNS resolution to avoid slowdown in addr/parse (31841) - Review and merge - Work on draft C style poll more - Prepare an 0.4.2.2-alpha release - 042-must items: - 31796 practracker warning (investigated, no fix needed) - 31611 investigate causes of 31495. - 31634 investigate module topology vs initialization order - 31898 crash on shutdown with tor-api - Retrospective - Proposal for revised merge policy Week of 7 October (planned): - Actual 0.4.2.2-alpha release - Start a maint-042 branch, open master as 043 - remaining 042-must/should issues - keep an eye on blog comments - Review and merge - tor-guts documentation work - Work on a blog post about an upcoming paper. - Back to 29211 (config refactoring)? Mike: Week of 10/02 (planned): - Finish Firefox networking review - Check in with Tobias re circpad perf issues and simulator plan - Perhaps update circpad doc with perf notes Week of 10/02 (actual): - Firefox networking review ~80% done? - Minor circpad dev doc updates - Assited w/ our Mozilla all hands session proposals Week of 10/07 (planned): - Finish Firefox networking review - Do some of Firefox Feature Review - Check in with Tobias re circpad perf issues and simulator plan - Blog post writing? Need help with/at risk of dropping this month: <-- do you still need help with this? - Not doing any code reviews this month, unless on circpad patches. Got enough for Tor Browser - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) - Relay community drive/mgmt (and related LTS herding) catalyst: week of 09/30 (2019-W40) (planned): - reviews - #30984 - review policy proposals week of 09/30 (2019-W40) (actual): - reviews - more feedback about C style - many meetings week of 10/07 (2019-W41) (planned): - reviews - look at policy proposals some more - be available for GSOD help as needed asn: Week of 02/10 (planned): - Bring OB hsv3 descriptor encoding closer to completion. - Attend s27 meeting about error passing over SOCKS vs HTTP vs control port - Handle remaining 042 bugfixes. Week of 02/10 (actual): - Working on hsv3 descriptor encoding (#31823) - Can now do blinding #31777 (also ported the tor ed25519 to python3 on the way #31912) - Can now do descriptor layer encryption - Can do the superencrypted layer - Stem hsv3 descriptor decoding is merged upstream (#31369)! - Reviewing and testing - Did 042 tickets assigned to me. Also reviews and merges. Week of 07/10 (planned): - Bring the hsv3 descriptor encoding branch to some browseable state so that I can show atagar before I leave for vacations on Friday. - Attend the s27 meeting about error passing which did not happen last week. - Check updates on #19251 - Finalize anything else remaining before I sign off for two weeks on Friday. ahf: Week of 30. September (planned): - Finish 0.4.2 tickets - Get back to S29 tickets - Work on migration scripts for Gitlab transition. - Take the good parts of our PR policy discussion and turn into a policy. - Network team retrospective. Week of 30. September (actually): - Quite a few meetings. - Did network team retrospective. - Continued work on Gitlab transition with anarcat's ticket migration idea. - Hacked on #31810 and #31091 (042-must) - Looked into 2 GB log issue on Windows (#31036) - Community Council meeting. Week of 7. October (planned): - S30 meeting. - Plan Zurich trip. - Get #31810 and #31091 merged. - Finish #31036 - Do full migration of Trac tickets to Gitlab as an experiment. - S31 meeting. - PR policy. dgoulet: Week of 02/10 (planned): - Go through my 042 tickets. - Assess s27 situation and timeline and prioritize work that need to happen soon. - Attend s27 meeting about the SOCKS error situation. - Bad relay world. Week of 02/10 (actual): - Network Team retrospective. - Went through some 042 tickets. Most were in needs_revision. - s27 work was bit on hold due to 042 ticket work and other work. - Spent time working the details and logistics for the removal of all EOL relays in the network (including blog post, and a whole LOT of emails). Week of 07/10 (planned): - Finish this EOL removal scheduled on Tuesday. - Revise my 4 remaining tickets in 042. - Merges/Reviews. - s27 meeting on October 8th about prop304 mostly. swati (offline): Week of 02/10: - Registered and created an account for myself on trac. - Created a ticket https://trac.torproject.org/projects/tor/ticket/31943 for reviewing changes in the tor Manual. - Forked the tor repository and cloned the copy of the repository to my local filesystem - Pushed changes to the local repository and created a pull request. - The pull request is https://github.com/torproject/tor/pull/1391. - Can someone assign reviewers for this pull request? I don't seem to have write access for this repository. [dgoulet: for #31943, we did this morning :)] All the best, Alex. -- Alexander Færøy

1 0

September 2019 report for the UX team
by Antonela Debiasi 09 Oct '19

09 Oct '19

Hi Tor, S9 - Tor Browser ================ During September, we worked on having Tor Browser 9 improvements ready for handing off to developers. Those were: - New identity Historically, the New Identity feature has been placed under the Tor Button doorhanger menu. Since the Tor Button is going to be removed from the toolbar, we needed a new icon to expose this critical feature to users. We talked with users[0], explored some ideas[1], and defined the icon which is going to reach stable[2]. [0] https://trac.torproject.org/projects/tor/ticket/28800#comment:8 [1] https://trac.torproject.org/projects/tor/ticket/27511#comment:17 [2] https://trac.torproject.org/projects/tor/attachment/ticket/27511/27511-1.png - Network Settings We moved Net Settings to the familiar place for end-users to find Settings: about: preferences. Since TB9, we'll have a new settings section called Tor Network so users can configure bridges and local settings following the default pattern. It is a first step in improving the path of connecting to Tor for users with circumvention needs. https://trac.torproject.org/projects/tor/ticket/31286 - TB9 Onboarding Duncan designed the best way to expose the above critical changes to users. https://trac.torproject.org/projects/tor/ticket/31768 Last but not least, Orfox sunsetted. We joined the Guardian Project folks on designing, localizing, and deploying the latest Orfox release, which offered a path for users to download Tor Browser for Android. https://trac.torproject.org/projects/tor/ticket/27399 https://trac.torproject.org/projects/tor/ticket/29955 S9 - User Research ================== Nah, Isabela, and I met at the NYU's Tor offices to document the work we have been doing and for creating user research guides for community researchers. When it is ready, this content will be available in community.torproject.org. https://dip.torproject.org/torproject/ux/research/tree/master/community Nah worked on moving the content from the UX team wiki to the User Research portal. This section will host documentation about our processes, our current user research activities, and user research reporting. https://lektor-staging.torproject.org/community/develop/user-research/ Also, we compiled a list of the frequency asked questions from our 2018/2019 groups. We are working on having them merged into the community portal. https://dip.torproject.org/torproject/web/community/issues?label_name%5B%5D… S9 - tpo.org ============ We joined the community team's Docshackaton. A lot of new and old friends jumped to help us with tpo.org, support.tpo.org, manual.tpo.org, and community.tpo.org. We took this time to work in layout and frontend related issues. Some highlights: - The shared Donate button at our headers is now pointing to the localized donate.torproject.org https://dip.torproject.org/web/tpo/issues/14 - The support portal has a lot of new content, but the layout didn't contemplate a massive list of items. We iterated it, and now each section has just its list of actual questions making it easier for loading and readability. https://dip.torproject.org/web/support/issues/32 L10N ==== emmapeel wrote a blogpost to honor translators in their day. Thanks l10n community for working with us on delivering Tor Browser in 28 languages! https://blog.torproject.org/honoring-translators In the commitment to keeping a healthy and engaged community of translators, emmapeel started a round of love spreading with translators and sent them Tor t-shirts and stickers, worked on having better internal l10n documentation and thought about successful ways of sharing best practices between translators. https://trac.torproject.org/projects/tor/wiki/doc/translation OONI Explorer ============= Finally, OONI Explorer got released! We collaborated with OONI on this significant redesign, supported this huge overhaul since the beginning, through the development process, and during the launch. Congrats OONI for this release! https://explorer.ooni.torproject.org/ We also gave design support for OONI Probe related issues: https://github.com/ooni/probe/issues/870 https://github.com/ooni/probe/issues/826 https://github.com/ooni/probe/issues/881 Fundraising =========== We worked in a joint proposal with Guardian Project and Tails folks to continue our work on running community training and user research during 2020/2021 Alon and I are working on the end of the year campaign. Fundraising wants to go with a cyberpunk/90's internet theme this year. We couldn't be more excited! Stay Tuned! Open Team ========= The UX Team roadmap kanban breaths here: https://dip.torproject.org/groups/torproject/ux/-/boards If you missed those, September weekly meetings notes are here: https://lists.torproject.org/pipermail/ux/2019-September/000463.html https://lists.torproject.org/pipermail/ux/2019-September/000462.html https://lists.torproject.org/pipermail/ux/2019-September/000461.html Peace and love, A -- Antonela Debiasi UX Team Lead @antonela E2330A6D1EB5A0C8 https://torproject.org

1 0

Community Team report for September 2019
by gus 08 Oct '19

08 Oct '19

Hi, Here's Community Team report for September 2019. Documentation ============= In the first week of September, Community Team hosted DoscHackathon, our first documentation hackathon <https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH…> During the week, we had 70 registrations, 8 contributors, and over 70 pull requests to Support Portal, Tor Browser Manual, Tor Project main website and other web repositories. It was a lot of work, and we still have some open issues tagged as DocsHackathon. The participants received different Tor prizes according to their contribution. Many thanks to all who collaborated in some way: reviewing the pull requests, opening new issues, writing new content, fixing css, doing screenshots and many other things! <3 We also worked in the content migration from old FAQ to Support Portal - <https://dip.torproject.org/torproject/web/support/issues/43> These are the new sections on Support Portal: - About Tor: <https://support.torproject.org/about/> - Get in touch: <https://support.torproject.org/get-in-touch/> - Debian repository instructions: <https://support.torproject.org/apt/> And more content migrated to: - Relay operators: <https://support.torproject.org/operators/> - Tor Browser: <https://support.torproject.org/tbb/> Sponsor9 work ============= Since July, Community Team has been working on Sponsor9 phase 3, which consist of our partners from the Global South to organize Tor trainings with the mentorship and online help from Community and UX teams. In September, we reached out more than 15 partners from different countries inviting them to join us this new phase. As this partnership process is new to the Community team, we're slowly bringing the partners on board. User support ============ Frontdesk: since BridgeDB fixed ticket #28533 <https://bugs.torproject.org/28533>, Frontdesk queue slowed down and we don't receive more blank bogus email. Outreachy: We submmitted a proposal "Help Tor Project support our users" to Outreachy <https://trac.torproject.org/projects/tor/wiki/Outreachy#HelpTorProjectsuppo…>. Applicants will make contributions from October 1 to November 5. And the intern will work with us from December 2019 to March 2020. Outreach ======== - At the beginning of this month, we reached out some non-profits to spread and share bridges campaign: <https://blog.torproject.org/run-tor-bridges-defend-open-internet> - Pili did a talk during APIdays.io (Barcelona): <https://blog.torproject.org/events/apidaysio-barcelona> - Kushal gave a workshop on digital security + Tor workshop in Goa <https://www.debutsav.in/> - nvjacobo and marco19_ did a presentation about Tor in Cumbre de Contribuidores de Open Source Software, Guadalajara, MX <https://ccoss.org/> - Cybelle had a talk during ABCDev, in Sao Paulo, Brazil. - In September, Narrira and other volunteers organized a Tor training with human rights defenders in Rio de Janeiro. - Pili, Brabo and others have started to organize FOSDEM activities: <https://trac.torproject.org/projects/tor/wiki/org/meetings/2020Brussels> - Global South IRC meeting happened last September 27th - <https://lists.torproject.org/pipermail/global-south/2019-September/000260.h…> Next Global South meeting scheduled for Wednesday, Oct 30, 1600 UTC, #tor-south - We published a blog post about the digital security training and UX feedback cycle that the Community and UX teams have been working over the last two years. <https://blog.torproject.org/reaching-people-where-they-are> - Many members of our community joined the Global Climate Strike. And as part of this, we also added Global Climate strike bannerto the main website: <https://blog.torproject.org/join-global-climate-strike-20-27-september> Meta ==== Meeting notes * Community Team meeting notes 02 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team meeting notes 09 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team Meeting notes 16 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team meeting notes 23 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team meeting notes 30 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00…

1 0

Tails report for September 2019
by sajolida 08 Oct '19

08 Oct '19

Releases ======== * Tails 3.16 was released on September 4 (major release). https://tails.boum.org/news/version_3.16/ * Tails 4.0 is scheduled for October 22. These are some of the changes that were introduced in Tails 3.16: * Removed pre-generated Pidgin accounts * Removed LibreOffice Math * Upgraded Tor Browser to 8.5.5 Code ==== * We started to integrate _Tor Browser_ 9.0 (#16356). * We started working on the upgrade to _Thunderbird_ 68 (#16771). * We did lots of work to improve the reliability of our test suite. * We did some initial research and tests on using _Portals_ to improve the UX of saving downloaded files from _Tor Browser_ (#10422 #15678). * We did some initial research on redesigning, in a Wayland-compatible way, our current sudo-based privilege separation model (#12213 and subtasks). * We improved the UX of the _Greeter_ and fixed a few of its most annoying bugs (#16095 and the tickets it blocks). This work will hopefully land in time for Tails 4.0 :) Documentation and website ========================= - We rewrote completely the instructions to backup the persistent volume: https://tails.boum.org/doc/first_steps/persistence/copy/ - We documented how to do right-click on Mac. (#15718) - We proposed to use Trimage to compress better the images on our website. (#17099) - We agreed on having a "People" page. (#17046) User experience =============== - We published a job offer on illustrations on what is Tails and how it works: https://tails.boum.org/jobs/illustrations_how_tails_work/ - We did some stats on how good people upgrade their Tails, with data from April 2019. (#17069#note-4) - 16.6% of boots (3800/day) had no direct automatic upgrade path to the latest version because they were more than 3 months old. - 3.8% of boots (860/day) were stuck before 3.6, which had broken all automatic upgrades. The impact of breaking all automatic upgrades in 3.6 was still huge even 1 year later. Hot topics on our help desk =========================== * Unfortunately we had some problems with our WhisperBack system, and because of that, some users were prevented from contacting us. We are looking into how to prevent so much downtime the next time. (#17110) * Tails can't establish a connection with obfs4 bridges and a hardware clock too far away from UTC is still ongoing. (#15548) * Graphics cards still give problems to some users. (#16447) Infrastructure ============== * We upgraded our very old Jenkins to the current LTS version (#10068). This in turn allowed us to implement a bunch of improvements and bugfixes that had been blocked by this postponed upgrade. * We kept working on making our web translation ready for prime-time. We're almost there! https://translate.tails.boum.org/ Funding ======= - We submitted a joint grant proposal with Tor and the Guardian Project to the DRL Internet Freedom program. - We added Monero and Zcash as cryptocurrencies in which you can donate to Tails: https://tails.boum.org/donate#cryptos - We received a $1 000 donation from TOP10VPN. - We prepared most of the content for our upcoming donation campaign: banner, blog posts, email, tweets, etc. (#16096) Outreach ======== Past events ----------- * sajolida attended the 1st Café Internet on September 19 in Mexico City: https://internetfreedomfestival.org/wiki/index.php/Ciudad_de_Mexico Upcoming events --------------- * intrigeri will facilitate a "Discover Tails and translate it into your own language" session at the Mozilla Festival on October 26-27 in London (UK): https://www.mozillafestival.org/ Translations ============ ## All the website - fr: 90% (5148) strings translated - es: 54% (3095) strings translated - de: 38% (2189) strings translated - it: 33% (1887) strings translated - fa: 30% (1721) strings translated - pt: 24% (1383) strings translated Total original words: 59107 ## Core pages of the website - fr: 94% (1669) strings translated - es: 88% (1572) strings translated - de: 66% (1178) strings translated - it: 62% (1114) strings translated - pt: 45% (801) strings translated - fa: 34% (606) strings translated Total original words: 16513 Metrics ======= * Tails has been started more than 746 622 times this month. This makes 24 887 boots a day on average. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0

September 2019 report for the Tor Browser Team
by Pili Guerra 08 Oct '19

08 Oct '19

Hi everyone! During September, the team has been busy at work on the ESR68 Transition as we work towards our first 9.0 stable release later on in October. During this period we have made three releases: Tor Browser 8.5.5[1], 9.0a6[2], and 8.5.6[3]. The first release incorporated a number of important security updates[4] to Firefox and was expected to be the last release in the 8.5 series. However, due to an issue with the aarch64 version on Android which was causing a crash on every launch[5] we had to release 8.5.6 for Android only the following week. As for the 9.0 series, we shipped our first alpha release based on Firefox 68 ESR at the start of the month. September also marked the sunsetting of Orfox[6] with a final update[7] pointing users to download Tor Browser for Android as the definite way to take advantage of the full protections Tor Browser offers, on Android. Other than that, we are finally done adapting our Linux and Windows toolchains for Firefox 68 ESR. We have also made some strides in getting our bundles to build reproducibly and hope to work on Android build reproducibility during October. Another important piece of work during September involved making Tor Browser on macOS compatible with Apple's notarization process[8] and we have started rolling out these changes with the alpha series at the beginning of October. The full list of tickets closed by the Tor Browser team in September is accessible using the `TorBrowserTeam201909`[9] keyword in our bug tracker. During October we are working hard towards our first 9.0 stable release based on Firefox 68 ESR as well as continuing work on the updater for Tor Browser nightly desktop builds. We also hope to ship a few more locales[10], Thai, Lithuanian, and Malay, in our alpha series. Finally, once the first stable 9.0 release is out, we will start picking up sponsor work again, finishing off the work that was started before the Firefox 68 ESR transition period to integrate client-side authorization to onion services v3 in Tor Browser[ 11]. All tickets on our radar for October can be seen with the `TorBrowserTeam201910` keyword in our bug tracker.[12] Thanks for reading! Pili [1] https://blog.torproject.org/new-release-tor-browser-855 [2] https://blog.torproject.org/new-release-tor-browser-90a6 [3] https://blog.torproject.org/new-release-tor-browser-856 [4] https://www.mozilla.org/en-US/security/advisories/mfsa2019-27/ [5] https://trac.torproject.org/projects/tor/ticket/31140 [6] https://blog.torproject.org/orfox-paved-way-tor-browser-android [7] https://trac.torproject.org/projects/tor/ticket/29955 [8] https://trac.torproject.org/projects/tor/ticket/30126 [9] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [10] https://trac.torproject.org/projects/tor/ticket/29935 [11] https://trac.torproject.org/projects/tor/ticket/30000 [12] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… — 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

minutes from the sysadmin meeting
by Antoine Beaupré 07 Oct '19

07 Oct '19

Hello! Here are the minutes from this month's sysadmin meeting. # Roll call: who's there and emergencies anarcat, hiro, ln5, qbi and weasel are here. # What has everyone been up to ## anarcat * announced LDAP sudo transition plan ([#6367][]) * finished first phase of the hiera transition ([#30020][]) * deployed trocla in test ([#30009][]) * coordinate textile shutdown ([#31686][]) * announced jabber service shutdown ([#31700][]) * closed snowflake -> TPA transition ticket for now, external monitoring is sufficient ([#31232][]) * improvements on grafana dashboards * gitlab, nextcloud transitions coordination and oversight * ooni.tpo to ooni.io transition coordination ([#31718][]) * bugtracking on networking issues ([#31610][], [#31805][], [#31916][]) * regular janitorial work (security upgrades, reboots, crashes, disk space management, etc) * started needrestart deployment to reduce that work ([#31957][]) * completed the "reports card" questionaire ([#30881][]) * continued work on the upstream prometheus module * tested puppetboard as a Puppet Dashboard ([#31969][]) [#6367]: https://bugs.torproject.org/6367 [#30009]: https://bugs.torproject.org/30009 [#30020]: https://bugs.torproject.org/30020 [#31232]: https://bugs.torproject.org/31232 [#31686]: https://bugs.torproject.org/31686 [#31700]: https://bugs.torproject.org/31700 [#31718]: https://bugs.torproject.org/31718 [#31610]: https://bugs.torproject.org/31610 [#31805]: https://bugs.torproject.org/31805 [#31916]: https://bugs.torproject.org/31916 [#31969]: https://bugs.torproject.org/31969 ## weasel * Started with new onionoo hosts. Currently there's just one backend on fsn, irl is doing the service part (cf. #31659) * puppet cleanup: nameserver/hoster info * new static master on fsn * staticsync and bacula puppet cleanups/major-rework/syncs with debian * new fsn web frontends. only one is currently rotated * retire togashii, started retiring saxatile * moved windows VM away from textile * random updates/reboots/fixes * upgraded polyanthum to Debian 10 ## Hiro * Setup dip so that it can be easily rebased with debian upstream * Migrated gettor from getulum to gettor-01 * Random upgrades and reboots * Moving all my services to ansible or packages (no ad - hoc configuration): - Gettor can be deployed and updated via ansible - Survey should be deployed and updated via ansible - Gitlab (dip) is already on ansible - Schleuder should be maintained via packages * Nagios checks for gettor ## ln5 Didn't do much. :( ## qbi Didn't do volunteering due to private stuff # What we're up to next ## anarcat New: * LDAP sudo transition ([#6367][]) * jabber service shutdown ([#31700][]) * considering unattended-upgrades or at least automated needrestart deployment ([#31957][]) * followup on the various ops report card things ([#30881][]) * maybe deploy puppetboard as a Puppet Dashboard ([#31969][]), possibly moving puppetdb to a separate machine * nbg1/prometheus stability issues, ipsec seems to be the problem ([#31916][]) Continuing/stalled: * director replacement ([#31786][]) * taking a break on hiera refactoring ([#30020][]) * send root@ emails to RT ([#31242][]) * followup with email services improvements ([#30608][]) * continue prometheus module merges * followup on SVN decomissionning ([#17202][]) [#17202]: https://bugs.torproject.org/17202 [#30608]: https://bugs.torproject.org/30608 [#30881]: https://bugs.torproject.org/30881 [#31242]: https://bugs.torproject.org/31242 [#31232]: https://bugs.torproject.org/31232 [#31786]: https://bugs.torproject.org/31786 ## weasel * more VMs should move to gnt-fsn * more VMs should be upgraded * maybe get some of the pg config fu from dsa-puppet since the 3rd party pg module sucks ## Hiro * Nagios checks for bridgedb * decommissioning getulum * ansible recipe to manage survey.tp.o * dev portal coding in lektor * finishing moving gettor to gettor-01 includes gettor-web via lektor * do usual updates and rebots ## ln5 Nextcloud migration. # Other discussions ## configuration management systems We discussed the question of the "double tools problem" that seems to be coming up with the configuration management system: most systems are managed with Puppet, but some services are deployed with Puppet. It was argued it might be preferable to use Puppet everywhere to ease onboarding, since it would be one less tool to learn. But that might require giving people root, or managing services ourselves, which is currently out of the question. So it was agreed it's better to have services managed with ansible than not managed at all... # Next meeting We're changing the time because 1400UTC would be too early for anarcat because of daylight savings. We're pushing to 1500UTC, which is 1600CET and 1000EST. # Metrics of the month Access and transfer rates are an average over the last 15 days. * hosts in Puppet: 79, LDAP: 82, Prometheus exporters: 106 * number of apache servers monitored: 26, hits per second: 177 * number of self-hosted nameservers: 4, mail servers: 10 * pending upgrades: 0, reboots: 0 * average load: 0.51, memory available: 318.82 GiB/871.81 GiB, running processes: 379 * bytes sent: 134.28 MB/s, received: 94.38 MB/s Now also available as the main Grafana dashboard. Head to <https://grafana.torproject.org/>, change the time period to 7 days, and wait a while for results to render. Note that the retention period of the Prometheus server has been reduced from 30 to 15 days to address stability issues with the server (ticket #31916), so far without luck. -- Antoine Beaupré torproject.org system administration

1 0

Tor Browser Release Meeting this week: Wednesday 9th October @ 18UTC
by Pili Guerra 07 Oct '19

07 Oct '19

Hi everyone, We’ll be having our usual Tor Browser Release meeting this Wednesday 9th October @ 18UTC on #tor-meeting. We’ll be discussing the upcoming 9.0 stable release and this will be the very last chance to request any small additions. 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

S27 Meeting: Tuesday 8th October @ 16UTC
by Pili Guerra 07 Oct '19

07 Oct '19

Hi everyone, We’ll be having an un-scheduled meeting to discuss S27 and in particular Objective 2, Activity 1: Integrating client-side authorization to onion services v3[1]. The main agenda topic will be how to resolve incompatibilities between Tor Proposal 309: Optimistic SOCKS[2] and Tor Proposal 304: Extending SOCKS5 Onion Service Error Codes[3]. This meeting will take place 1hour later than usual at 1600UTC. Please join us if you think you have some input you can give to help us figure this one out. Thanks! Pili [1] https://trac.torproject.org/projects/tor/ticket/30000 <https://trac.torproject.org/projects/tor/ticket/30000> [2] https://gitweb.torproject.org/torspec.git/tree/proposals/309-optimistic-soc… <https://gitweb.torproject.org/torspec.git/tree/proposals/309-optimistic-soc…> [3] https://gitweb.torproject.org/torspec.git/tree/proposals/304-socks5-extendi… <https://gitweb.torproject.org/torspec.git/tree/proposals/304-socks5-extendi…> — 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