October 2019 - tor-project - lists.torproject.org

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

17 Oct '19

Here is our meeting log: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-17-16.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday October 17th 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 --------------------------- --- 17th October 2019 --- --------------------------- == Announcements == * == Discussion == * https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/… * New wiki page on how to walk NGO through the process of distributing private bridges * How can we make this process easier? See: https://bugs.torproject.org/28015 * "Moat secret password" is a neat idea * How should we manage our private bridges? * So far, it's just a CSV. We want to keep track of who got what bridge and when. * When should we switch over to the new IPv6-having Snowflake broker? See https://bugs.torproject.org/29258#comment:11 * Design considerations for a new service that tests bridges: * https://trac.torproject.org/projects/tor/ticket/31874#comment:2 * Discuss workflow for gettor * Sponsor 28: status? anything to report? * we have a prototype of new obfs4 flow obfuscator: https://trac.torproject.org/projects/tor/ticket/30716#comment:16 * snowflake is moving forward * Sponsor 30: how are we doing? * https://trac.torproject.org/projects/tor/ticket/31274 * A1- Create an evaluation framework for bridge distribution and selection methods. * https://trac.torproject.org/projects/tor/ticket/31281 * A1 - Improve documentation on how to set up a bridge server and different pluggable transport bridge servers. * A2 - Create scripts and configuration code for setting up a bridge on cloud providers to make it easier for operators to launch a new bridge. * https://trac.torproject.org/projects/tor/ticket/31282 * A2 - Define which censorship scenarios we are going to address. * Should we increase the default Snowflake poll interval? A lot? Last I checked, the broker was getting like 40 requests/second, which is way way more than we need. * Note: https://metrics.torproject.org/collector/archive/snowflakes/ since the release for windows, client usage has gone up by 5-10x but we still have orders of magnitude more idle snowflakes * dcf wonders why there's no apparent change in the bridge statistics https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6… * We could use a dedicated build server for the anti-censorship team to test tor-browser-build.git builds. * It's too big to build comfortably on a development PC/laptop, so devs are getting their own VPSes. * Requirements: 8 CPUs, 200 GB+ disk. * Could be shared with other teams. * Snowflake: Support portal and tb-manual documentation updates == Actions == * == Interesting links == * https://jhalderm.com/pub/papers/conjure-ccs19.pdf * Conjure CCS'19 paper now out * Filed https://bugs.torproject.org/32064 after last week's discussion on web search results on "download tor" == 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: Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. Next Week: - Work on gettor specs - More with review of strings and website content and translation phw: This week (2019-10-17): * Sent five private obfs4 bridges to frontdesk for distribution to users in need. * Finished prototype of obfs4 flow obfuscator: * https://trac.torproject.org/projects/tor/ticket/30716#comment:16 * Filed ticket suggesting that we should only use >=80%-complete languages in BridgeDB: * https://trac.torproject.org/projects/tor/ticket/32035 * Filed ticket on more useful search results for "download tor": * https://trac.torproject.org/projects/tor/ticket/32064 * Created wiki page that documents our process for supporting NGOs with private bridges: * https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/… * Did some prototyping for a bridge test tool: * https://trac.torproject.org/projects/tor/ticket/31874 * Reviewed #31384 and #31253. * Preparation for OTF summit. * Started removing PGP support from BridgeDB: * https://trac.torproject.org/projects/tor/ticket/17548 * Helped dgoulet debug an exitmap bootstrapping issue (culprit was outdated Stem). * Answered question of RACE collaborator on the necessity of obfs4's node ID. * Finally deployed BridgeDB's language switcher (and released v0.9.0): * https://trac.torproject.org/projects/tor/ticket/26543 * May have (accidentally) fixed another translation-related issue while implementing #26543: * https://trac.torproject.org/projects/tor/ticket/19839 * Debugged and fixed BridgeDB's broken email responder: * https://trac.torproject.org/projects/tor/ticket/32105 * If only we had our email monitoring system in place already :( * Changed expiration date of my PGP (sub)key. Next week: * Help with: * Need feedback on https://trac.torproject.org/projects/tor/ticket/31874#comment:2 (bridge test service) 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-17 Last week: Last week: - update webextension version and deploy new versions of snowflake broker and proxies (#31889) - fixed open UDP sockets bug (#31285) - revised and merged snowflake website localization (#31384) and webext packaging script(#31253) - grant writing - progress on snowflake tests (#29259) - review of bridgedb localization ticket - created #32117 for collecting information on bridgedb scraping - did some more snowflake health checks: about 2/3 of all connections open a data channel in < 20s This week: - continue on tests (#29259) - snowflake dogfood and think about how to address bad snowflake health - refactor proxy-pair state machine (#31310) - work on #29207 and #29206 - look at recent improvements to obfs4 (#30716) 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-10-17 Last week: - merged #31685, #31537 - responded to #31765 - started on #31028 Next week: - continue on #31028 - add a build step / documentation for code reuse in cupcake Help with: - look at #31028 if you're curious, but not much to show yet dcf: 2019-10-17 Last week: - archived test pion builds from #28942 - redeployed meek-server instances (#31890) - prototyping KCP and QUIC in obfs4proxy - reviewed #29206 (sequencing protocol for Snowflake) - reviewed Snowflake broker and bridge upgrade (#31889) - helped deploy Snowflake webext-0.0.11 - reviewed Snowflake favicon (#31537) - posted a cleanup patch to remove unnecessary code (#32046) - posted a patch to remove Python LICENSE from Tor Browser (#32068) - reviewed Snowflake LICENSE packaging patch (#31932) - reviewed Snowflake socket leak fix (#31285) - dealt with a goptlib upgrade (#32056, #32076) - investigated a reported problem with the old meek-http-helper code (#32037) - set up a new instance of the Snowflake broker with IPv6 (#29258) Next week: - prototyping KCP and QUIC in obfs4proxy - review #29207 (broker protocol for Snowflake) Help with: - need meek-azure to redeploy meek-server for #31890

1 0

ANNOUNCEMENT: XMPP/Jabber services on torproject.org shutdown in 30 days
by Antoine Beaupré 16 Oct '19

16 Oct '19

Hi! What? ===== The Tor Project's jabber server will be shutdown in thirty days. Why? ==== In a recent review of provided services, the sysadmin team has decided to retire the XMPP/Jabber services offered by the Torproject.org domain. The service was used by only four persons in the last month, out of over thirty registered users and over a hundred users which could use the service. The service is also maintained only by a single person, who agrees on retiring the service. This is not a statement on the merits of the XMPP protocol, the Jabber project, or federation as a whole. Those principles are dear to our hearts, we just feel it's better to direct our energies on services that are used by a larger community. When? ===== In thirty days, the server will be shutdown and unreachable. The machine itself will be kept up for an extra 7 days in case of a serious problem and then decomissioned using our [normal process][]. [normal process]: https://help.torproject.org/tsa/howto/retire-a-host/ How? ==== If you still wish to use another XMPP, you can follow the [Getting started][] instructions on the xmpp.net website. It links to two sites with lists of alternative servers that you could easily switch to. One which we particularly recommend you consider is ran by the good birds at [Riseup.net][], a donation based service ran "for people and groups working on liberatory social change". If you already have an account there, you can already use their XMPP server, see their [chat documentation][] for more information. Riseup is an invite-only service: if you know a friend on Riseup, they can send you an invite, but please do not go around bugging them for invites, they don't give invites to people they don't know. [Getting started]: https://xmpp.org/getting-started/ [Riseup.net] https://riseup.net/ [chat documentation]: https://riseup.net/en/chat Migrating to a different XMPP server can be done by downloading your roster on one host and uploading it on the other. Then you need to ask all your contacts to readd you to *their* roster, on the new server. It's a lossy process because people might have you on their roster without you having them on yours, but it might mean you get rid of spammers, on the upside. Here are instructions on how to migrate your roster from various clients. Gajim ----- 1. register with the new server and configure it in Gajim -> Accounts (control-shift-a) -> Add account 2. click on the new account 3. choose "Import contacts" 4. select the old account Gajim will then transfer the roster between the two accounts. This was tested in Gajim 1.1.2 Pidgin ------ As far as we could tell, there's no easy way to transfer rosters between accounts in Pidgin. Tkabber ------- 1. log into the old account (Tkabber -> Log in...) 2. export the roster (Tkabber -> Roster -> Export roster...) 3. log out (Tkabber -> Log out...) 4. log into the new account (Tkabber -> Log in...) 5. import the roster (Tkabber -> Roster -> Import roster...) Tkabber will then create the contacts in the roster of the new account. Tested with Tkabber 1.1.2. Jabber Migrate -------------- Finally, there's a tool that's designed specifically for migrating roster between servers, simply called "migrate". It used to be maintained on [Sourceforge][], but it seems to be abandoned there. Two forks have shown up on GitHub, from [jirutka][] and [spiculator][]. Note of those tools have been tested or reviewed by Torproject.org people. Use at your own risk. [Sourceforge]: http://migrate.sourceforge.net/ [jirutka]: https://github.com/jirutka/jabber-migrate [spiculator]: https://github.com/spiculator/jabber-migrate Who? ==== This effort has been accepted by the current service admin (dgoulet) and is led by the current sysadmin team lead (anarcat). Either person can be reached for comments or just by replying to this email. -- Antoine Beaupré torproject.org system administration

1 1

LDAP sudo passwords change now in effect
by Antoine Beaupré 16 Oct '19

16 Oct '19

Hi, As announced last month, I have just finished deploying the change in the PAM configuration requiring a special password to authenticate with sudo on all of torproject.org servers. Preliminary tests do not show any problems, but it's possible you might have trouble running jobs with sudo if there's a configuration problem. Again, that password can be changed in the web interface here: https://db.torproject.org/login.html For all the details, see the original announcement: https://lists.torproject.org/pipermail/tor-project/2019-September/002509.ht… ... also included below. A. -- Antoine Beaupré torproject.org system administration

1 1

[ticket system] registrations of users & next trac/gitlab meeting
by Gaba 16 Oct '19

16 Oct '19

Hi! At the last meeting there was a lot of discussion [0] around the registration of users in https://dip.torproject.org and people had a few suggestions to deal with spam and allow people to easily send bugs and track them (some suggestions were to create a web interface for anonymous users in front of gitlab, continue with cypherpunk account, install a forum with discourse). It seems that this last decision is the only blocker right now to move forward with a date for the migration. All the suggestions proposed involve extra work/resources right now that we do not have. With the objective of getting this done soon with the requirements we have, let's choose the minimum solution for moving to our gitlab instance and resolve all the other problems later. It would mean having registration open (at first at least but we can close it anytime) in https://dip.torproject.org and get a few of us (at least Pili and me are volunteering for this) to moderate who is registering and creating issues. Gitlab has a way for people to report users and we can monitor new accounts closely. And there is a way to whitelist and black list domains for sign-ups. If we see that this is a lot more work volume that what we have now in trac, we can close regisration and open accounts on request. Other gitlab instances have a lot of issues dealing with spam and it seems that it could get worst than at trac but we will deal with this once the migration to gitlab is done. Next meeting is on October 15th at 17 UTC on #irc-meeting and the agenda should be: * dates for migration * review steps for the migration [1] cheers, gaba [0] https://lists.torproject.org/pipermail/tor-project/2019-October/002517.html [1] https://nc.riseup.net/s/SnQy3yMJewRBwA7 -- 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

3 2

Trac migration Meeting Notes, October 15th
by Gaba 15 Oct '19

15 Oct '19

Hi! Logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-15-17.01.html Content of the pad: https://pad.riseup.net/p/e-q1GP43W4gsY_tYUNxf Agenda October 15th * review agenda * registration of users * review steps for the migration [1] * dates for migration [1] https://nc.riseup.net/s/SnQy3yMJewRBwA7 Notes Registration of Users Proposal: gitlab with open registration with a moderation team (geko, pili, ahf, gaba) - with the possibility of closing registration (having by invite/request only) if is too much work for us Reviewing doc: https://nc.riseup.net/s/SnQy3yMJewRBwA7 Wiki migration: It will be migrated into the 'legacy' project in gitlab. Rough timeline: 1. have a full migration into legacy in Mid November. 2. ask people to find errors the last two weeks of November 3. migration early december Next meeting: November 5th for migration status and discuss repos -- 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

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

15 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. Things are looking OK. Nick would like to see all 042-must tickets done before 1st of November such that we can begin to roll out release candidates. 2) We skipped going over Kanban board since dip.torproject.org was having some problems. 3) We skipped going over review assignments because none had been assigned at the given time due to vacation and public holiday. 4) We discussed how to handle the larger GSoD changes in the future and that Catalyst and Nick will work together on making progress on the current ticket. 5) Alex made an announcement about the monthly tor-project reports and people got a pad link to update during the month, such that we can get the October report out earlier. 6) We shortly discussed some of the proposals that are being discussed now and there was some confusion around the different proposals and ownership of them. No changes was decided here. 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-14-16.59.html Below are the contents of our meeting pad: gaba: (updated on september 30th) Last week (actual): . s30 coordination with all teams involved . s31 This week (planned): 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 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)? Week of 7 October (actual): - Releases 0.4.2.2-alpha - Sent out C style survey. (I'm hoping for feedback from network team folks, but if you want to see it, it's at https://people.torproject.org/~nickm/netteam-c-survey.py ) - Worked on 042-should items: - Got some thoughts on #31683/#31364 (microdesc corruption) but no solution. - Deferring work on #31078 (config docs/renames/refactors) till I have more feedback - #31909 -- regression test for #31495 - #31705 -- coccinelle-related fixups. Took much longer than I had planned. - Drafted sections of collaborative webpost. - Reviews and merges - Opened 0.4.3 Week of 14 October (planned): - More 042-should items if they come up - Wrap up C survey - Edit collaborative webpost? - Review and merge - S31 work: - tor-guts documentation work - more config.c refactoring once #32003 is reviewed - possibly, help with relay modularization work. Mike: 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? Week of 10/07 (actual): - Finished Firefox networking review? Checking followups on ticket.. - Did some analysis for the https://trac.torproject.org/projects/tor/ticket/31561 fix wrt Vanguards Week of 10/14 (planned): - Respond to Firefox networking review followups - Do some of Firefox Feature Review - Check in with Tobias re circpad perf issues and simulator plan - Blog post writing? - Tor blog discussions 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 10/07 (2019-W41) (planned): - reviews - look at policy proposals some more - be available for GSOD help as needed week of 10/07 (2019-W41) (actual): - reviews - reviwed policy proposals - looked at GSoD work; tried to straighten out some Asciidoc things - helped nickm and arma with some O_APPEND mysteries week of 10/14 (2019-W42) (planned): - reviews - more GSoD feedback 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 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. Week of 7. October (actually): - S30 meeting happened. - Booked trip to Zurich and started doing slides. - Requested funding to go to Freedom not Fear with Gus. - Fixed `_commentN` issue with Gitlab migration, tried to do a full fetch, seemed to work. - Wrote test for #31810 that seems to work, no clue yet for how to test #31091. - Managed to reproduce #31036. Week of 14 October (planned): - Gitlab migration meeting. - Kill todo list items: some CC, some Network Team policy stuff, an old review. - Resubmit #31810 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 Network Team
by Alexander Færøy 14 Oct '19

14 Oct '19

Hello Tor Project people, In September, the Network Team have worked on the following items: - Work on various new policy proposals in the network team: 1. PR policy. 2. Merge policy. 3. Commit policy. - Retirement of EOL relays. - 0.4.1.6 release - 0.4.2 release prep. We froze the 0.4.2.x series to new series, identified all the issues we want to fix on the 042Status page, put out an alpha, and started working on the pending issues. - C code style discussion Nick started working on a survey to figure out where we stand on issues of consistent code style. # Project to improve Onion Service [0] We started work on adopting OnionBalance features into onion services v3. We kicked off this activity by working on stem support for v3 descriptors. There is currently no support in stem to get descriptor information for v3 onion services (HSv3) and we have been tackling this issue by: 1. Implementing HSv3 descriptor encoding in stem, 2. Adding code to stem to calculate the Hidden Service Directories (HSDirs) that are responsible for these v3 descriptors, and 3. Investigating the best way to implement key blinding for HSv3 in stem. Additionally, we have been working on enhancing onion services overall by working on a number of bugfixes and improvements. We are very excited to announce that we now have complete support for IPv6 in v3 onion services. We have also been working on identifying bugs related to HSv3 timeouts[8] through the use of a health monitoring tool. As a result of this work we have now identified four new bugs and are in the process of writing fixes for them. We have also been making progress investigating an issue with missing HSv3 descriptors when setting up an intro circuit. All of these help to make v3 Onion services more scalable and stable which we hope will help with their adoption. We have also been busy working with the SecureDrop team over the past few months and are happy to share that the latest SecureDrop v1.0.0 release has added support for enabling v3 onion services. Other than that, work has continued on the Denial of Service (DoS) defenses with the implementation and merge of proposal 305 which allows HSv3 operators to send a number of DoS defense parameters to their introduction. We are also still in discussions regarding whether our proposed fix for an attack that forces rotation of the intro point for an onion service is good enough or whether we need to go back to the drawing board to find a better solution. Once the outstanding issues on these items are resolved, these features should be available from the first tor v0.4.2 stable release. # Project on Modularization of Key Aspects of the Tor Network [1] We have been working on refactoring our code to make the modules more resilient, segregated, and automatically testable. We started setting up a system to change how Tor modules should communicate, designed to reduce module complexity and maintenance burden. For that we created a generic publish/subscribe system for cross-module communications. We worked on rearranging files for the module dirauth so that more directory authority code can be compiled out when unneeded and spent time fixing bugs related the refactoring of key modules. We also refactored crypto_digest.c to have fewer ifdefs. We are working on distributing the config.c module across several modules [5][39][46]. It initializes many other modules, and provides the proper amounts to a set of global variables for the configuration settings. Similar to config.c, we are working to distribute the functionality of control.c across several modules [29] [47]. control.c queries and manipulates the internal states of many different subsystems, so it currently needs to know about all those internals. [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor27 [1] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor31 All the best, Alex. -- Alexander Færøy

1 0

S27: Onion Services meeting this week - Tuesday 15th October
by Pili Guerra 14 Oct '19

14 Oct '19

Hi everyone, We will have our regular meeting for Sponsor 27: Onion Services this week on Tuesday 15th October @ 15UTC. 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

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