tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

Tor Browser Release meeting this week
by Pili Guerra 23 Sep '19

23 Sep '19

Hi everyone, It’s been a while since we’ve had one of these, so please join us this Wednesday 25th September @ 18UTC on #tor-meeting. We’ll be getting into a regular fortnightly meeting schedule from this Wednesday (barring any special events.) See 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

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

19 Sep '19

Here are our meeting notes: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-19-17.01.html And here's our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday September 19th 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… --------------------------- --- 19th September 2019 --- --------------------------- == Announcements == * Bug Smash Fund campaign has been on since beginning of August. Update: https://blog.torproject.org/tors-bug-smash-fund-86k-raised . The idea is that this will be funding non-sponsor bugs. If you are working on ticket that is not sponsored please tag it with BugSmashFund keyword. * Remember to add 'actual points' to a ticket when you are closing it. * BridgeDB bot updated its HTTP header to evade our anti-bot mechanism * Still maintained, after all * ValdikSS created yet another forum for Internet censorship discussion: https://ntc.party * Transition to gitlab is slowly moving forward: * Notes from last meeting: https://lists.torproject.org/pipermail/tor-project/2019-September/002492.ht… * Planning document: https://nc.riseup.net/s/SnQy3yMJewRBwA7 == Discussion == * Tickets from July and August's roadmap: * July * 30830 did not started. Should we move it into roadmap for next months or back to icebox? * August https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… * move into september/october, back to icebox? * September: #26543 is a ticket that irl will work on. We are moving it to October. * I'm going to use the keyword 'anti-censorship-roadmap' for tickets that are getting out of the roadmap into icebox (they do not have a specific period for completion).(Gaba) == 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: (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-09-19): * Wrote draft of BridgeDB metrics specification (#31780) * Updated obfs4 docker container to use the new Debian buster (#31692) * Worked with new obfs4 bridge operators * A handful ran outdated Tor versions that didn't manage to publish their descriptor to Serge. Need to investigate. * 57 new bridges so far * Lots of work on updating BridgeDB's requirements.txt (#29484) * Some of BridgeDB's dependencies have vulnerabilities * Lots of progress, but still struggling with broken tests * Sent a bunch of private obfs4 bridges to NGO so it can distribute them among its users * Will be interesting to see their experience * I'm monitoring the availability of these bridges with monit * Merged scripts that rsync assignments.log files to CollecTor (#19332) * Merged pull request for community portal that fixes obfs4 setup instructions for OpenBSD * Reviewed and merged zoossh pull requests * Summarised work on obfs4 improvements (#30716) * Took a look at the BGram app and how it uses tor. Found a bridges.txt with now-offline obfs4 bridges * Sent an email to author, asking how they are using bridges in their app Next week: * Make progress with obfs4 improvements * Figure out how to reduce per-packet entropy Help with: * https://bugs.torproject.org/31780 (BridgeDB metrics spec) Gaba: (updated September 16th) Last week (): * checking roadmap * playing with gitlab - we are moving forward migration out of trac This week (planned): * sponsor 30 is finally officially starting 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-09-19 Last week (holiday on Monday): - review #19332, #31692, #31780 - wrapped up pion/webrtc changes and windows build (#28942 and #25483) - set up a snowflake bridge for testing #29206 - addressed comments on work done up until now on #29206 - did a speed test on pion snowflakes and found some concerning snowflake health indicators (#28942) - Created #31804 after discussion on IRC This week: - take a look at and respond to errors swallowed ticket (#31794) - make a patch for the proxy---broker communication (#29207) - wrap up pion/webrtc changes and windows build ( #28942 and #25483) - snowflake dogfood and think about how to address bad snowflake health - continue work on sequencing layer, hope to have it fully working this week (#29206) - clean up logs (#30830) - review #31780 Help with: - review of #28942 (GeKo is reviewing #25483) catalyst: week of 09/12 (planned): - reviews - sponsor31 reporting and planning - sponsor31 architecture documentation etc - gitlab migration planning - coding style discussion week of 09/12 (actual): - reviews - sponsor31 reporting and planning - gitlab migration planning week of 09/19 (planned): - reviews - sponsor31 planning - coding style discussion - comment on draft network team review guidelines - #30984 arlolra: 2019-09-19 Last week: - mia Next week: - add a build step / documentation for code reuse in cupcake - make an attempt at #31391 Help with: - dcf: 2019-09-19 Last week: - reviewed sequencing layer (#29206) - read a draft of TCP encapsulation guidelines ( https://github.com/net4people/bbs/issues/9#issuecomment-532218292 ) Next week: - catch up on pion updates and rbm build - archive test pion builds from #28942 - Turbo Tunnel prototyping Help with:

1 0

Metrics team meeting notes, 19 September 2019
by Gaba 19 Sep '19

19 Sep '19

Hi! Metrics team meet every Thursday at 15:00 UTC in #tor-meeting. You can read today's meeting logs in: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-19-15.00.html Below is a copy of the agenda from today: Agenda Thursday, September 19th, 15 UTC - Proposal status: continue on Monday. - Transition to gitlab is slowly moving forward: Notes from last meeting: https://lists.torproject.org/pipermail/tor-project/2019-September/002492.ht… Planning document: https://nc.riseup.net/s/SnQy3yMJewRBwA7 - Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap cheers, gaba -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

update on ticket system discussion
by Gaba 17 Sep '19

17 Sep '19

Hi! There has been some discussion in the 'corridors' of Tor and in the last meeting face to face during the session on 'internal tooling' and specifically about tickets system. I'm sending this mail to try to summarize what the discussion has been until now, make it transparent and try to get an agreement on how to move forward. Problem: - Trac software is not being mantained (from our perspective of users of Trac this is a bomb getting ready to explode) [0] Solution - Move out into a better (possible feature parity with what we use now AND integration between project management tool and tickets) and mantained ticketing system. Discussion until now - A few years ago there was a survey [1] on which features people would like to see in a new ticketing system. - There is a ticket [2] that has a discussion on features needed and a document [3] that brainstorm features between trac and gitlab. - The last meeting in Stockholm there has been several discussions on what is needed. [4] - In 2017 Hiro and the network team experimented with the oniongit.eu Gitlab instance. - In 2019, a test instance was setup, called "dip.torproject.org"[5], that a few projects are using right now to test its use. We are mostly considering Gitlab (until now) because: 1. We can host it ourselves and not have other company control the data. 2. It is open source [6]. 3. It is mantained [7]. 4. It supports the project management tool that we are interested in. Before moving forward we need: 1. Consensus or a clear compromise on what to move into. 2. A plan on how the migration to a new ticketing system will happen. I started drafting it here (thinking that Gitlab would be the new one) [8]. This plan is still a work in progress and we will continue doing it when we all agree on which system to move into. cheers, gaba [0] https://trac.edgewall.org/roadmap [1] https://docs.google.com/spreadsheets/d/1V4Faq2y9vv8XTp-OADl4YRMTiRB0G9DHvj2… [2] https://trac.torproject.org/projects/tor/ticket/30857 [3] https://nc.riseup.net/s/TYX37BDT4eQfTiW [4] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… [5] https://dip.torproject.org [6] https://gitlab.com/gitlab-org [7] https://gitlab.com/groups/gitlab-org/-/roadmap?layout=MONTHS [8] https://nc.riseup.net/s/SnQy3yMJewRBwA7 -- Project Manager: Network, Anti-Censorship and Metrics teams and OONI support gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

5 11

Network Team Meeting Notes, 16 September 2019
by Alexander Færøy 16 Sep '19

16 Sep '19

Hello, Here is a short summary of the network team meeting today: 1) We went over our Kanban board to ensure that it is up-to-date. 2) We went over the set of code reviews that needs to happen this week. A few tickets were moved around amongst the team members. 3) We looked at the list of tickets for the upcoming 0.4.2.x Tor release on Trac: - Some of the tickets got distributed out amongst the team members. - The team looked into whether some tickets should be upgraded from being `-should` (we hope to do them for this release) to `-must` (we must do these tickets for this release). 4) We discussed the "What does an ideal Pull Request on Github look like" proposal: - This topic was moved forward from the S31 sponsor meeting last week where only a subset of the network team members participated. Afterwards we had a short discussion round on the internal network team mailing list. The idea behind the proposal is for the team figures out what requirements we have for Pull Requests internally amongst the team members. The policy is only going to apply for team members in that we don't expect volunteers to follow the exact same requirements that we expect from each other. - The policy proposal that was sent to the network team mailing list contained the following list of expectations to a PR: - A correct `changes` file if appropriate. - CI that passes. - Test coverage that has not decreased. - Documentation for all functions. - Description of overall design changes (if any). - Needs to have a sensible "size": not too big to review in a reasonable amount of time and not too small so that it misses lots of context. Better to split things up into multiple PR's if things are getting too big. - The last item in the proposal was discussed briefly due to a concern on whether the policy is going to cause more work to happen for the entire team instead of reducing the amount of work: if we start doing earlier and smaller PRs for large feature branches, the reviewers/mergers might lose the bigger picture of the overall architectural changes to the codebase that will happen when the project is nearing its end (and all the PRs have been merged). Additionally, this could lead to the sum of work that has been spend over the duration of the project will be larger than if the developers deliver a large feature branch at the end of the project period where the feature branch, containing the feature and the refactoring needed to do the feature, is all contained within the same PR. We decided to continue the discussion for a bit longer on the internal network team mailing list before we bring this up for vote internally in the team. 5) We went over the "Needs help with" section of our meeting pad. --- end of summary --- You can read today's network team meeting log at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-16-16.59.html Below are the contents of our meeting pad: = Network team meeting pad! = This week's team meeting is at Monday 16 September 1700 UTC on #tor-meeting on OFTC. September-October schedule: * Monday 23 September 1700 UTC * Wednesday 2 October 2300 UTC * Monday 7 October 1700 UTC * Monday 14 October 1700 UTC * Monday 21 October 1700 UTC * Monday 28 October 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the tor-project mailing list archive for older notes.) 19 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002435.html 26 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002442.html 4 September: https://lists.torproject.org/pipermail/tor-project/2019-September/002465.ht… 9 September: https://lists.torproject.org/pipermail/tor-project/2019-September/002466.ht… == Stuff to do every week = * Coming up: the 0.4.2 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://dip.torproject.org/torproject/core/tor/boards * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. ------------------------------- ---- 16 September 2019 ------------------------------- == Announcements == On September Swati (technical writer) started working with us on rewriting the Tor manual page (part of Google Season of Docs). She is participating in the network team meetings. Her project: https://developers.google.com/season-of-docs/docs/participants/project-tor We are moving the kanban board from storm into https://dip.torproject.org/torproject/core/tor/boards . This will help lead a plan for migration into dip.torproject.org. People working on sponsor 31 will meet every fortnight, next meeting is Tuesday 24 September at 2300 UTC Remember that 0.4.2.x-alpha is now in feature freeze Bug Smash Fund campaign has been on since beginning of August. Update: https://blog.torproject.org/tors-bug-smash-fund-86k-raised . The idea is that this will be funding non-sponsor bugs. If you are working on ticket that is not sponsored please tag it with BugSmashFund keyword. Remember to look at transition to gitlab https://lists.torproject.org/pipermail/tor-project/2019-September/002458.ht… - meeting to discuss plan on September 17th, at 18UTC in #tor-meeting == Discussion == * Next steps for 0.4.2 triage. * What is -must or -should but doesn't have the labels? * What has the -must or -should labels, but doesn't need them? * Who will work on what? * "Pull request requirements before review": * next steps here? * Are we ready to try hiving this as a policy? == Recommended links == (copied from the anti-censorship pad) * https://google.github.io/eng-practices/review/reviewer/ * Google's guide on how to do code reviews. Worth a skim. * In general, reviewers should favor approving a CL once it is in a state where it definitely improves the overall code health of the system being worked on, even if the CL isn’t perfect. * "One business day is the maximum time it should take to respond to a code review request (i.e. first thing the next morning)" * However, never interrupt your focused work to do a code review. If people are interested, we could talk about trying a faster turnaround on code reviews at the monthly retrospective. == Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: (updated on september 4th) Last week (actual): . s31 report . scalability funding proposal . other small tasks This week (planned): . more scalability . trac migration moving forward Help with: teor: (online first week of the month, offline at the usual meeting time) Urgent: - Roadmap: - Sponsor 31 config.c refactor reviews - 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 Other: - team policies: commit bit and roles? Week of 9 September (actual): Urgent: - Roadmap: - Sponsor 31 config.c refactor and reviews (3? tickets) - review #31625 - sponsor 31 planning - sponsor 31 report review - revise sponsor 31 tickets after last week's reviews - Sponsor 31 C style planning Other: - review gitlab transition document - bug smash on logging bugs #31594 and children (maybe some of these are bugs on other sponsored work) - bug triage - emails - some quick tool fixes because they were annoying me: #31679, #31677 - revise bug smash fixes after last week's reviews - backport deciding - Climate Strike blog post / website help Week of 16 September (planned): Leave: - May need to take some leave for the climate strike on 20 September Urgent: - Take Time for: - gitlab signup / config - team policies: 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 possible coding tasks for me Other: Week of 16 September (actual): Urgent: - Take Time for: - Roadmap: - Sponsor 31 Other: Nick: Week of 9 September (planned): - Merge big pending patches. (Sorry asn & dgoulet! :/ ) - Respond to questions on S31 pad before tuesday - Another S31 meeting - Work on circuitpadding doc merge stuff. - Start a PETS review - Work on more 29211 followup issues - More 0.4.2 triage. Week of 9 September (actual): - Started PETS review, wrote first draft - Merged 30924 (onion service dos settings), but did not get to 26294 (changes in replay cache) - S31 meeting - Read through circuitpadding stuff, asked a question about next steps - More 29211 followups, including lots of tests - Worked on another mmap crash issue (31696) - Gitlab discussion - Tests for 31675 (microdesc refactoring) - 042 triage: labeled must/should. Week of 16 September (planned): - Release 0.4.1.6 - release 0.4.2.1-alpha - Start 0.4.2 stabilization process - Read proposal 308 (counter galois onion) - Discuss C style polling with Teor and Taylor - Finish PETS review - Work on circuitpadding doc stuff? - Pending reviews Mike: Week of 9/09 (planned): - Funding proposals - Medical and bureaucracy Week of 9/09 (actual): - Funding proposals - circpad doc discussions - Medical and bureaucracy - circpad ticket analysis and triage - LTS ops discussion on tor-relays Week of 9/16 (planned): - Funding proposals - Circpad doc tweaks and ticket #s -> git & trac - Patch for #31653 (0ms circuitpadding circuit failure bug) Need help with/at risk of dropping this month: - Not doing any code reviews this month, unless on circpad patches. Got enough for Tor Browser - Circpad doc followup/fold-in? (nickm is helping here, thx!) - Firefox ESR code review - (I am working on this, but unlikely to finish it this month at this rate of interruption+distraction) - Firefox new feature review - Funding proposal review, meetings, coordination, cross-checking estimations, strategy, etc. - 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/09 (2019-W37) (planned): - more sponsor31 reporting and check-in - reviews - look at gitlab migration plan doc - #30984 week of 09/09 (2019-W37) (actual): - more sponsor31 reporting and check-in - reviews week of 09/16 (2019-W38) (planned): - reviews - coordinate sponsor31 documentation work - respond to C style thread - respond to review guidelines thread - review gitlab migration plans - #30984 need help with: - please help take a look at some jenkins failures: * tor-ci-linux-0.2.9 (old-ish) https://jenkins.torproject.org/job/tor-ci-linux-0.2.9/292/console -- this looks like a travis failure. There's a java exception caused by a timeout, and no builders actually happen. +1 - teor * tor-ci-linux-0.4.1 (new-ish) https://jenkins.torproject.org/job/tor-ci-linux-0.4.1/ARCHITECTURE=amd64,SU… Buster amd64 is failing with what appears to be 08:50:53 08:50:53 FAIL: src/test/test_workqueue_efd.sh 08:50:53 ==================================== 08:50:53 08:50:53 Illegal instruction 08:50:53 FAIL src/test/test_workqueue_efd.sh (exit status: 132) I wonder if this is transient, or if it is a real problem? We didn't change this code any time recently. Transient, or an environment change? - teor transient -- fixed itself. CI failures page updated -catalyst * tor-ci-linux-master-clang (new-ish) https://jenkins.torproject.org/job/tor-ci-linux-master-clang/3640/ARCHITECT… This is only happening on i686 sid, and it is a compiler segfault. This makes me think it is a bug in the clang package in debian unstable. +1 - teor * tor-ci-mingwcross-* (old-ish) https://jenkins.torproject.org/job/tor-ci-mingwcross-master/2499/ARCHITECTU… This looks like a misconfiguration to me -- it seems to be complaining about not having found a zlib package maybe? Let's open a ticket, we can fix config issues - teor * tor-ci-windows-master (old?) https://jenkins.torproject.org/job/tor-ci-windows-master/78/console This looks like it could be a real bug: a unit test is failing. It's in "slow/process/callbacks" -- I believe ahf knows that code best. Let's open a ticket and give it to ahf? - teor asn: Week of 09/09 (planned): - More work on stem side of onionbalance (#31369 and #31648) Week of 09/09 (actual): - Tons of work on #31648. I have a rough Python implementation of hs_get_responsible_hsdirs(), and I'm making test vectors using the little-t-tor implementation so that I can cross-test them. - Some discussion about how to vendor onionbalance v3. Should it be the same project as the old onionbalance so that operators don't need to install/learn two software? I sent an email to Donncha about maintainership and waiting reply. - Wrote down Stockholm notes in #28005 after discussion with antonela. - A bit of 042 triaging. - Opened #31754. - Did reviews/merges. Week of 16/09 (planned): - Get close to finalizing #31648. This involves cross-testing the Python implementation of the HSv3 hashring with the little-t-tor one. - Maybe start working on HSv3 public key blinding using the hazmat crypto library in stem. ahf: Week of 9th of September (planned): - Solve my laptop situation. - Work on #5304 and #28930. - Work with Nick and Gaba on which tasks to takeover. Week of 9th of September (actually): - Solved laptop situation. - Lots of Gitlab migration discussions. Thanks to everyone helping out here! - Hacked on #5304 spec changes and trying to figure out how the code should work. - Began task takeover with Nick and Gaba: running some meetings, begin doing 1:1(:1). Week of 16th of September (planned): - Follow up on "Good PR" discussion on network-team@ and turn it into a proposal - Keep the discussions on GL migration active and hopefully continue to make progress. - Finish #5304 - Figure out my task plan for the rest of the year'ish for tickets. dgoulet: - on vacation Week of 02/09 (actual): - Most of my time has been on #30200 parent tasks working on building and running an onion service health tool (#28841). - From the above, several tickets have been opened, see the child tickets of #30200. - I've mostly worked on the service side health. I've moved now on writing the tool analysis part for the client side. - One ticket I opened which was needed for my development branch in #30200 that affects the wider tor (and found a bug): #31608. It is good that we are all awayre of this imo. Week of 09/09 (planned): - Continue making sure #31549 is on track and doesn't stall. - Help write blog post about the above ^ in order to be as loud as we can about this big change in the network. - Continue on #30200 to dig into client side behavior (s27 stuff). swati (Updated on September 16) What I did last week: - Spent time learning how to use Asciidoc. - Set up the Atom Editor by installing plugins to be used for editing/writing Asciidoc documents. - Sent my questions regarding cloning/forking and the process followed. Gaba and Taylor answered my queries. - Forked and cloned the repo: https://github.com/torproject/tor/ - Saved a local copy of Tor Manual (doc/tor.1.txt) on my machine. - Added a Table of Contents and regrouped topics to create a better flow and structure. What I plan to do this week: - Continue working on the tasks planned for month 1 (https://developers.google.com/season-of-docs/docs/participants/project-tor) - Create a pull request and request the network team to review the first set of changes. Help with: - Might have questions about the categorization of configuration options and might need info about config files. - Need to get an account to use Trac (https://trac.torproject.org/) for creating tickets for pull requests. (gaba looking at it) All the best, Alex. -- Alexander Færøy

1 0

S27: Onion Services meeting this week - Tuesday 17th September
by Pili Guerra 16 Sep '19

16 Sep '19

Hi everyone, A reminder that we’re having our Sponsor 27 meeting again this week to discuss progress and next steps. We’ll be meeting on Tuesday 17th September at 15UTC on #tor-meeting. See 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

Invitation to virtual learning session: Online Anonymity, privacy, the Tor Browser and more
by Allen Gunn 16 Sep '19

16 Sep '19

Hi Tor friends and future friends, I hope this finds you well. With apologies for vacation-induced late notice, we are hosting a free virtual learning session this Tuesday 17th on "Online Anonymity, privacy, the Tor Browser and more" Details are here: https://aspirationtech.org/blog/learningsessionsonanonymitydigitalidentity It's taking place at 2pm California US PT time. We would welcome anyone interested to join. Disclaimers, confessions and apologies below :^) Big big thanks to Alison and Gus for sharing their latest Tor slides with us, we'll be incorporating a number of those. And if anyone wants to see the "privacy/anonymity" material beforehand and share tough love to help us make it better, hit me up off-list and I'm happy to share the pad where we have drafted the slides. Few comments/respectful apologies: * Sorry it's not offered at a Europe-, Africa- or Asia-friendly time, this is primarily for our California US network, but I wanted to make sure you all know about it. We are happy to offer these at any time of day if there is interest. * Also sorry we are doing it on the corporate Zoom platform, we just have not found a free/open live video platform that meets our reliability needs. I welcome you to educate me off-list on platforms you think might be worth exploring. Too many jit.si servers have broken our hearts too many times, especially as participant counts grow. * That also means that we don't have an in-Tor-browser option, again happy to discuss how we might offer Tor-browser-friendly online learning moving forward. * BUT we'll be recording the session and making it available in some hopefully-friendly formats (.ogg I believe) once things are done. * AND for anyone with ability and willingness to dial a US toll-free number, there is that option for audio-only. BYOBP (Bring Your Own Burner Phone ;^) * Final apology with custom support offer! You don't have to use the annoying corporate registration system to join, just hit me up off list and I can share whatever details you need. OK, that's a lot of disclaimers, hope some of you can join, and I look forward to feedback from any who have time to offer the same before, during and after. peace, gunner -- Allen Gunn Executive Director, Aspiration www.aspirationtech.org Aspiration: "Better Tools for a Better World" Read our Manifesto: https://aspirationtech.org/publications/manifesto Twitter: www.twitter.com/aspirationtech

1 0

people page: mastondon?
by meejah 12 Sep '19

12 Sep '19

Hello, Would it be possible to include a mastodon link instead of (or alongside?) twitter on the "people" page? In case that's an "easy yes", I'm: https://mastodon.social/@meejah/ -- meejah

2 1

Anti-censorship meeting notes, 12 Sep 2019
by Philipp Winter 12 Sep '19

12 Sep '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-12-17.01.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday September 12th 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… --------------------------- --- 12th September 2019 --- --------------------------- == Announcements == * == Discussion == * Any services left that aren't monitored or restarted on crash/reboot? * Set up systemd user script for GetTor (based on <https://help.torproject.org/tsa/doc/services/>) == Actions == * == Interesting links == * https://google.github.io/eng-practices/review/reviewer/ * Google's guide on how to do code reviews. Worth a skim. My personal take-aways: * Make sure that patches improve the health of the existing code. They won't be perfect. * "One business day is the maximum time it should take to respond to a code review request (i.e. first thing the next morning)" * However, never interrupt your focused work to do a code review. == 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: (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-09-12): * Compiled set of private bridges (and distribution instructions) for NGO * Set up private monit instance to monitor these bridges from my laptop * https://mmonit.com/monit/ (the tool is really neat!) * Updated our obfs4 docker image to use Debian buster * Worked with new obfs4 bridge operators, many of which had troubles setting it up * Most had obsolete Tor versions; one from Ubuntu 12.04 (!) * RACECAR meeting about obfs4 improvements * Experimenting with libFTE to look like "a protocol with structure" * Many research questions remain * Experimenting with an "entropy reducer" that can survive high-entropy filters * More work remains to be done for flow obfuscator * Reviewed GetTor website changes * Wrote systemd user script to automatically resurrect GetTor when it crashes * Merged #28533 and released BridgeDB 0.8.1 (contains two usability fixes) * Reviewed revisions for #31407 * Decided to rsync BridgeDB metrics to CollecTor instead of exposing them over web server (#19332) Next week: * BridgeDB fixes * E.g., ridiculously outdated requirements.txt * Make progress with obfs4 improvements * Figure out how to reduce per-packet entropy Help with: * https://bugs.torproject.org/19332#comment:20 * https://bugs.torproject.org/31692 Gaba: (updated September 12th) Last week (): * grant writing 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-09-12 Last week (holiday on Monday): - reviews (gettor and bridgedb) - looked into #31425 a bit more - grant writing meeting - worked a bit on #29207 - upstream patch for pion/webrtc This week: - make a patch for the proxy---broker communication (#29207) - wrap up pion/webrtc changes and windows build ( #28942 and #25483) - snowflake dogfood - continue work on sequencing layer (#29206)? - revisit snowflake reachability scripts, check status of tests, and enhance (#30368) - review of gettor metrics work (https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor…) - review #19332 and #31692 Help with: - review of progress on sequencing layer (#29206) catalyst: week of 09/05 (actual): - reviews - sponsor31 reporting and planning week of 09/12 (planned): - reviews - sponsor31 reporting and planning - sponsor31 architecture documentation etc - gitlab migration planning - coding style discussion arlolra: 2019-08-29 Last week: - merged #30310 - helped with some review Next week: - add a build step / documentation for code reuse in cupcake - make an attempt at #31391 Help with: - dcf: 2019-09-12 Last week: - started review of sequencing layer (#29206) - raised the file descriptor limit in the broker (#31425) Next week: - review Snowflake sequencing layer (#29206) - archive test pion builds from #28942 - Turbo Tunnel prototyping Help with: - redeploy meek-azure bridge for Go net/http DoS vulnerability (#31455) - needs attention from inf0 at Team Cymru (dcf and phw have sent email)

1 0

Notes from Vegas team meeting September 5th
by Erin Wyatt 12 Sep '19

12 Sep '19

Notes for SEPTEMBER 5 2019: MAIN DISCUSSION ITEMS: + Nextcloud: who makes the decision on which route/option to go? Anarcat and his team? - Tor have its own NC instance, and to migrate to that one - Tor continues using the 'shared' NC one of riseup. - Riseup setup a NC instance only for Tor and maintain it - Riseup setup a NC instance only for Tor that is maintained by Tor sysadmin team Discussion: sysadmin team has a lot to maintain now, NC might be a stretch in the short term but makes sense in the long term; another option is to let rise maintain it, though it would be hard to extract our stuff in the future; we need a migration plan to move storm to rise up and also an exit strategy out of riseup in the future; anarcat will bring it up in next TPI meeting; + Gus and Pili would like to start sharing the Partnership agreement with partners/Sponsor 9. Discussion: We passed it along to Julius and Wendy for comments; Isa will pass it along to SIDA for review/comments. + We should confirm/clarify what counts as a trademark violation see: https://lists.torproject.org/pipermail/tor-project/2019-January/002186.html Discussion: People think the line is if someone is making money out of our trademark; Nick suggests we talk to lawyers about it so we don't lose our trademark; Isa suggests linux foundation, EFF, or OTF Legal Lab might be able to help w/ a lawyer for this; Isa will do a review of the issue and start drafting a letter for what we need. https://2019.www.torproject.org/docs/trademark-faq.html + Other Discussion: People asking about an org chart, and it turns out, Bekeela just made one! We'll find a place to post the anonymized one. --------------->8 INDIVIDUAL NOTES: Steph 1. Docshackathon and bridges promotion 2. Posts: Browser fingerprinting and Orfox sunsetting. Next: Onion Browser, Tor trainings 3. Coordinating Bitcoin Magazine podcast — After talking with Isa, they want to do a longer series on Tor with a few people. Another interview in the works. 4. Locking down on a several page fundraising deck for next week 5. Preparing for the EOY fundraising campaign, mapping out content and messaging 6. Pitched an exclusive story idea to a journalist 7. Items on deck: next demystifying dark web page edit, community portal review, relay campaign Gaba 1. Back from emergency surgery and recovering. 2. Nextcloud: not sure if we still need to have this discussion here or anarcat and team has all the info to move forward. 3. Scalability proposals moving forward. Georg 1. Work on Tor Browser releases (the alpha should be based on ESR 68 now) Nick 1. Transferred apple dev credential to Pili. Successfully? Let's see! Sarah 1. Attended cryptocurrency and nonprofit meetup at GivingBlock in DC. 2. EOY campaign coordination. 3. Major donor meetings and event coordination. 4. Updates to donate pages. Philipp 1. Worked with new bridge operators as part of our obfs4 bridge campaign. Fixed a bunch of issues in our docs. 2. Published a simple prototype for obfs4 flow obfuscation. 3. Coordinated GetTor progress among anti-censorship team. 4. Published monthly anti-censorship report. 5. More work on pion WebRTC library for snowflake and proxy/broker protocol. Gus 1. Bridges campaign: reach out some partners EDRi and Access Now (probably they will run some bridges for us) 2. Frontdesk: RT backlog: answered +700 RT tickets. There are still ~170 remaining (mostly bridges and orbot) 3. DocsHackathon - busy week! Going well, a lot of pull requests <3 4. Pushing more content to Community Portal Pili 1. OTF Proposal for Browser Team submitted 2. Working on DRL Proposal for Community/UX 3. Docs Hackathon is running this week. Closed 30 tickets so far across Tor Manual, Support Portal and tpo.org 4. Moving forward with website maintenance plans 5. S27 Monthly report was submitted last week. 6. Looking into participating in other volunteer programs such as Hacktoberfest, Outreachy and Google Code-in 7. Finally transitioning last Orfox users to TBA!!! Thanks to Guardian Project and everyone else who has helped to push this over the line. 8. Mostly AFK next week, travelling, holidays and speaking at a conference Antonela 1. End-month duties 2. The #docshackathon is doing great! helping on what is needed 3. Meetings this week and next week in ny isabela: 1. f2f sync with Nah (UX research contractor) about how Tor works and our projects 2. f2f sync w/ Antonela (on Friday) 3. prep work /w Sarah and Beth for my meetings w/ donors this coming week 4. finishing preparations for audit (me and Sue will be in Seattle starting this coming week for our annual auditing process) 5. prep work for YE campaign, closing up BugSmashFund campaign 6. coordinating a talk in Brazil at USP São Carlos, at the end of the month Erin 1. So close to being done with handbook! 2. Organizing personnel files in anticipation of audit 3. General HR stuff anarcat 1. back from vacation, handling backlog

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project