- tor-project - lists.torproject.org

Tor Browser team meeting notes, 3 September 2019
by Georg Koppen 04 Sep '19

04 Sep '19

Hello! We held our weekly Tor Browser sync yesterday in #tor-meeting as usual. The log can be found at: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-09-03-17.29.l… The notes from the pad are: Discussion: [tjr] We currently have a team IRC highlight for 'tbb-team'. I recently joined #tor-bots and get regular highlights there for the owner changing to tbb-team. Is this a mild annoyance to anyone else? If so, I know renaming trac accounts is not possible, but maybe in gitlab we could have a different name for the account; or try to migrate our highlight? (Or maybe the answer is "Yes it's not ideal, but it's not worth changing.") GeKo: Last week: - release preparation for 8.5.5 and 9.0a6 - built release candidates for both series - signed the 8.5.5 bundles - reviewed loads of patches to get 9.0a6 into alpha shape (it seems we managed to do so!) - helped pili with time estimations for tickets and roadmapping for September - staring at Windows reproducibility issue (#31538) - helped with diagnosing Windows updater issue (#31567) (thanks to pospeselr for stepping up and diagnosing the issue) - provided patches to smaller issues (#30800, #27493 - filed already a number of issues against our ESR 68-based Tor Browser This week: - help with getting the releases out - continue to work on #31538 - macOS notarization? (GeKo will chat with mcs/brade after the meeting) - reviews - monthly reports (I'll combine July and August) mcs and brade: Last week: - #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - Added a comment to the ticket that lists the remaining things that we need. - #29430 (Use uTLS for meek TLS camouflage in Tor Browser). - create Torbutton patch to avoid breaking circuit display. - #30429 (ESR 68 Rebase). - tested the updater on Windows. - created and helped with #31567 (NS_tsnprintf() does not handle %s correctly on Windows). - Discussed recent Mozilla updater security fix patches with gk. - Started to look at #31457 (disable per-installation profiles). This week/upcoming: - #31457 (disable per-installation profiles). - Work on other tbb-9.0-must-alpha tickets as time permits, e.g., #31491 (clean up the old meek http helper browser profiles). - More ESR68 updater testing. - We will be away from keyboard this Thursday and Friday (September 5th and 6th). - As we mentioned at the dev meeting, we have vacation planned for the week of September 23rd. tjr: - Some minor build uplifts to esr 68 - There is a path forward on the wasm for extensions thing: https://bugzilla.mozilla.org/show_bug.cgi?id=1576254 - Currently pretty far behind on things pospeselr: Last Week: - #31567 investigation (printf fun) - #31548 (verify mingw HEAD builds ff with working screen reader support) - #31286 work: - finished prototype UX, sent review build to antonela - started work to wire tor-launcher code into new about:preferences configuration This Week: - make a test Linux build with bridge UX for y'all to review (#31286) - labor day off - SF for browser privacy meet-up acat: Last week: - Fixed #31396 - Communication with noscript for security settings not working in nightlies - Reviewed latest #31010 changes. - Fixed some esr68 tbb-9.0-must-alpha bugs. - Investigated onboarding regressions (#28822). This week: - Fix onboarding regressions + address review comments (#28822). - #26345 - Disable tracking protection UI in FF67-esr - #31562 - The circuit display is not visible on error pages in Tor Browser based on ESR68 - #31575 - Firefox is phoning home during start-up in Tor Browser based on ESR 68 - #30662 - Make sure about:newtab is blank - #31601 - Don't let Mozilla recommend extensions again - Maybe others tbb-9.0-must-alpha boklm: Last week: - Reviewed mingw-w64-clang patches (#28716, #28238) - Made patch for #30384 (Use 64bit containers to build 32bit Windows Tor Browser) - Made small patches for #31606 (Update website update instructions in Tor Browser release process) - Helped with new releases build - Started looking at #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) - Looked a little at #31564 (Android bundles based on ESR 68 are not built reproducibly anymore) - Commented on #28942 (Evaluate pion WebRTC) and #28325 (Use go 1.11 module versioning support) - Reviewed #31264 (tar.gz output files contain non-reproducible timestamps) This week: - Finish publishing new releases - Investigate #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) - Review #30334 (build_go_lib for executables) - Other tbb-9.0-must-alpha toolchain tickets: #29013 - Review #31596 (Bump mingw-w64 version to pick up fix for #31567) pili: Last week: - OTF Browser Proposal - September Roadmap and estimations This week: - Final Orfox update!! sisbell: - #31568: Creating grade dependencies - determined cause of multiple artifact entries (proposed solution but needs to be implemented) - #30461: Update tor-android-service: redid config/build to use older version of project until we get latest updates merged into tor repo - #31293 - found that adding JVM settings overrides the no-daemon flag for gradle. This causes network interface failures in some build environments - #31564 - Reproducibility - tried various solutions, including upgrading, downgrading gradle plugin. All caused failures of Firefox build - Various Changes to Firefox build to get it building with full set of options This week: - For reproducibility - try downloading google source and see if we can patch it. - Fix for #31568 Georg

1 0

OONI Monthly Report: August 2019
by Maria Xynou 03 Sep '19

03 Sep '19

Hello, Below we share what the OONI team worked on in August 2019. ## Report on censorship events in Ethiopia We published a research report documenting new censorship events in Ethiopia, titled: "Resurgence of Internet Censorship in Ethiopia: Blocking of WhatsApp, Facebook, and African Arguments". The report is available here: https://ooni.io/post/resurgence-internet-censorship-ethiopia-2019/ This report is a follow-up to our previous study, which documented the blocking of WhatsApp and Telegram in Ethiopia in mid-June 2019: https://ooni.io/post/ethiopia-whatsapp-telegram/ ## Progress on OONI Probe desktop app We completed the integration of the new golang probe-engine into the OONI Probe CLI that powers the desktop app: https://github.com/ooni/probe-cli/pull/46 We also did some more research and testing on auto-update support: https://github.com/ooni/probe-desktop/pull/37. ## Progress on OONI Probe mobile apps We released the beta of OONI Probe Mobile v.2.2.0 (Android and iOS) for internal testing. The new version allows users to download JSON files from OONI Explorer, copy OONI Explorer URLs, and it includes support for the auto-deletion of measurement logs and JSON files that have already been uploaded. Android: https://github.com/ooni/probe-android/pull/249 https://github.com/ooni/probe-android/pull/250 https://github.com/ooni/probe-android/pull/251 https://github.com/ooni/probe-android/pull/253 https://github.com/ooni/probe-android/pull/254 iOS: https://github.com/ooni/probe-ios/pull/303 https://github.com/ooni/probe-ios/pull/304 https://github.com/ooni/probe-ios/pull/305 We also started doing a bit of research on integrating react-native which will allow us to maximize code-sharing between the OONI Probe desktop and mobile apps. ## New test development We implemented the OONI Probe Telegram test using the new golang engine, paving the way to making it easier to implement new tests in go: https://github.com/ooni/probe-engine/pull/41 ## Progress on revamping OONI Explorer In preparation for the launch of the revamped OONI Explorer, we continued to make a series of improvements to the beta (https://explorer-beta.ooni.io/) throughout August 2019. More specifically, we merged the following pull requests: https://github.com/ooni/explorer/pull/234 https://github.com/ooni/explorer/pull/239 https://github.com/ooni/explorer/pull/242 https://github.com/ooni/explorer/pull/244 https://github.com/ooni/explorer/pull/245 https://github.com/ooni/explorer/pull/247 https://github.com/ooni/explorer/pull/254 https://github.com/ooni/explorer/pull/262 https://github.com/ooni/explorer/pull/263 https://github.com/ooni/explorer/pull/265 https://github.com/ooni/explorer/pull/276 We also opened the following pull requests: https://github.com/ooni/explorer/pull/280 https://github.com/ooni/explorer/pull/279 https://github.com/ooni/explorer/pull/251 ## Pipeline work We fixed a major bug in the OONI data processing pipeline and ran the backfilling process: https://github.com/ooni/pipeline/issues/214 As part of our work on this, we also improved the quality of end-to-end tests in the pipeline: https://github.com/ooni/pipeline/pull/216 https://github.com/ooni/pipeline/pull/215 https://github.com/ooni/pipeline/pull/208 https://github.com/ooni/pipeline/pull/220 https://github.com/ooni/pipeline/pull/221 This allows us to have greater confidence in deploying changes to the data processing pipeline as we get ready to deploy the speed improvements and add support for ingesting metadata from new tests. We made progress in extracting metrics from the Telegram instant messaging test: https://github.com/ooni/pipeline/pull/177 As part of the fast-path branch, we made progress on reducing the time to process measurements and on the creation of events for the RSS feed: https://github.com/ooni/pipeline/pull/213 ## Infrastructure work We did some work on cleaning up old deprecated machines, making it easier to ensure that all our infrastructure is redeployable. See: https://github.com/ooni/sysadmin/pull/338 & https://github.com/ooni/sysadmin/pull/337 During the Chaos Communication Camp (where we met in person), we brainstormed on strategies to make our infrastructure more available. ## Community activities ### Chaos Communication Camp 2019 OONI's Arturo, Maria, and Federico traveled to Germany to attend the Chaos Communication Camp 2019 (CCCamp) between 21st-25th August 2019: https://events.ccc.de/camp/2019/wiki/Main_Page At CCCamp, we facilitated an OONI session: https://events.ccc.de/camp/2019/wiki/Session:OONI:_Measuring_internet_censo… We also held an OONI hackathon: https://events.ccc.de/camp/2019/wiki/Session:OONI_Hackathon During the hackathon, we engaged participants with OONI data analysis and we discussed the development of new OONI Probe tests. At CCCamp, we also hosted an OONI village (https://events.ccc.de/camp/2019/wiki/Village:OONI) where we distributed OONI t-shirts and stickers, collected community feedback on OONI tools and methodologies, and otherwise engaged participants with the OONI-verse. Our village was part of the About:freedom cluster (https://events.ccc.de/camp/2019/wiki/Village:About:freedom) consisting of multiple organizations defending digtial rights and promoting free software. ### OONI workshop in Venezuela Our partner, IPYS Venezuela, held an OONI workshop in Venezuela for local journalists (see: https://twitter.com/ipysvenezuela/status/1162365664008515585) As part of the workshop, they explained how to participate in censorship measurement research through the use of OONI Probe and OONI data. ### OONI data presented at the Latin America and Caribbean Internet Governance Forum Our partner, IPYS Venezuela, presented censorship findings from Venezuela based on OONI data at the Latin America and Caribbean Internet Governance Forum. Through the use of OONI Probe, IPYS Venezuela documented hundreds of censorship events in Venezuela throughout 2018. Further information is available via their report: https://ipysvenezuela.org/alerta/reporte-ipysve-la-escalada-de-la-censura-d… ### OONI outreach material for Bolivia Our partner, Internet Bolivia.org, published outreach material in Spanish to help promote the use of OONI Probe in Bolivia: https://drive.google.com/file/d/1IGQCxWDRrpgvNW02T67Aj4mo5emdgHl4/view ## Userbase In August 2019, OONI Probe was run 375,421 times from 5,272 different vantage points in 214 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

torproject.org content updates and next steps
by Pili Guerra 03 Sep '19

03 Sep '19

Hi everyone, There's been a lot of work over the past year (and before!) to migrate the website to lektor, to use a consistent styleguide[1], make it more modular[2] and structured it in a way that it is easier for people to find the underlying content for a page. With the potential move to gitlab, we can also make it easier for more people to submit change requests using the gitlab interface to update this content. We have been thinking about a good process for keeping our www.torproject.org website content up to date for a while. This is something that we can all own a small part of and we shouldn't have to rely on a single person for updates. We had a session about this in Stockholm[3] and we recently had another meeting to formalise the next steps to delegate ownership and updates for different sections of the websites. I believe we're now in a good position to start trying this process out for www.torproject.org and using it as a model for other future websites, e.g the upcoming developer portal. I have been reaching out to some of you individually to help us out with this and now I would like your input on which sections need updating and potential owners. The idea here is that different people can submit change requests to update content on the different website sections and the people in the webwml group, but mainly Community and UX team members, can review and merge these changes. We will also be updating the current webml group members to better reflect those people who are currently involved, so please reach out if you believe you are a member of this group and would like to remain involved. So, to wrap up :), please take a look at the following table[4] and feel free to update it or email me if there are any sections that need to be added and/or that you'd like to own in future. Thanks! Pili [1] https://styleguide.torproject.org/ [2] https://gitweb.torproject.org/project/web/lego [3] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… [4] https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… — 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, 29 Aug 2019
by Philipp Winter 29 Aug '19

29 Aug '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-08-29-16.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday August 29nd 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… --------------------------- ---- 29th August 2019 ---- --------------------------- == Announcements == * Our obfs4 bridge campaign is now live! * https://blog.torproject.org/run-tor-bridges-defend-open-internet == Discussion == * == Actions == * Let me know what we should include in our monthly report: https://pad.riseup.net/p/ThKAw7J-lXGU3AY3uBwp == 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-08-29)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) - Add script to update download endpoints from gettor VM: https://dip.torproject.org/torproject/anti-censorship/gettor/blob/master/sc… - Configure github and gitlab so that getulum can push - Add script to export stats in CSV: https://dip.torproject.org/torproject/anti-censorship/gettor/blob/master/sc… - Delete old gettor instances on gettor VM - gettor should use ansible for deployment and updates: started coding recipes Next week - use archive.org as new distribution endpoint: upload files to archive.org - review specs: are specs up-to-date? should we change something in the specs? - review request channels: We are currently only using email. Is it worth to have a chat bot on twitter to distribute links? should we consider other chat platforms instead? - statistics for help emails are not summing up correctly - prepare repo and web for locales hiro: (2019-08-22)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) This week: gettor-web: updates to documentation and website (current website is outdated) gettor: fix pipeline. Talk to browser team about the recommended version file format (so that our scripts do not break) check documentation how to make deployment easier. can it be done via jenkins? ci? Next week: gettor: use archive.org as new distribution endpoint: upload files to archive.org review specs: are specs up-to-date? should we change something in the specs? review request channels: We are currently only using email. Is it worth to have a chat bot on twitter to distribute links? should we consider other chat platforms instead? Past week: on vaca! phw: This week (2019-08-29): * Helped with launching Tor bridge campaign * Tested new obfs4 bridges and worked with some operators who ran into issues * Interacted with university folks who may be able to run new default bridges for us * RACECAR meeting to discuss progress on obfs4 improvements * Made some progress on obfs4 improvements (#30716) * Read up on website fingerprinting literature to understand status of ML-based attacks * Made me realise that obfs4's flow obfuscation was misguided * Experimenting with improving the way obfs4 shapes its flows * Re-built and re-deployed snowflake broker (#31454) * Re-built and re-deployed meek-server on BridgeDB (#31455) * Filed ticket to get rid of BridgeDB's silly chatspeak (#31528) * Started working on code to extract stable and unallocated bridges from BridgeDB for manual distribution * Worked with our new default bridge operator (#31164) Next week: * More work on obfs4 improvements Help with: * Gaba: (updated August 22nd) Last week (): * added september issues to the gitlab kanban board https://dip.torproject.org/torproject/anti-censorship/roadmap/-/boards This week (planned): * ahf - on leave 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-08-29 Last week: - deployed /metrics handler (#31376) and updated snowflake metrics spec (#31493) in preparation for CollecTor integration - implemented and updated snowflake webextensions with fix for session termination (#31385) - implemented and deployed a fix for the proxy ID reuse vuln (#31460) - moved snowflake metrics spec to snowflake repo (#31407) - fiddled with snowflake metrics spec to get it working for collecTor (#31493) - finally got around to updating snowbox - made progress on sequencing layer (#29206) - started reading up on NSF SaTC TTP This week: - make a patch for the proxy---broker communication (#29207) - stay updated on pion rbm build (#28942) - snowflake dogfood - continue work on sequencing layer (#29206) - revisit snowflake reachability scripts, check status of tests, and enhance (#30368) Help with: - review of progress on sequencing layer (#29206) - review of putting snowflake spec in git repo (#31407) - quick review of proposed protocol changes for proxy---broker (#29207) <-- not urgent, i can move forward with what i have catalyst: week of 08/22 (planned): - reorienting after leave - mostly sponsor31 stuff week of 08/22 (actual): - mostly sponsor31 stuff week of 08/29 (planned): - mostly sponsor31 stuff (control protocol refactoring that will hopefully lead to better bootstrap reporting) 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-08-29 Last week: - merged the meek-http-helper port to WebExtension (#29347) - read and summarized the Point Break paper from Usenix 19 https://lists.torproject.org/pipermail/anti-censorship-team/2019-August/000… - tried to reproduce a Snowflake packaging problem on Debian 9 (#31380) - reviewed serna's patch for broker-controlled Snowflake poll interval (#25598) - Helped deploy snowflake proxy webext-0.0.10 (#31385, #31200, https://archive.org/details/snowflake-webextension-0.0.10 ) - Redeployed my meek-server instances to mitigate a Go HTTP/2 DoS (#31455) - reviewed a patch to remove proxy IDs from broker /debug (#31460) - worked on an rbm build of Snowflake with pion-webrtc (#28942) - applied a documentation fix for file ownership in snowflake.tpo deploy (#31496) - filed a ticket to link Cupcake from snowflake.tpo (#31497) - Turbo Tunnel prototyping. Next week: - review Snowflake sequencing layer (#29206) - add snowflake to the Windows build with pion-webrtc (#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 has sent email) - someone to try to reproduce my checksums from https://bugs.torproject.org/28942#comment:43

1 0

Roadmap for hypothetical network health team
by Roger Dingledine 29 Aug '19

29 Aug '19

Here is an area list for a hypothetical future "network health" team. I say hypothetical because we have no near-term plans to form such a team -- but imo the task areas make sense together. Some of them are being handled by other teams right now, but some of them aren't getting as much attention as they need. (1) track community standards about what makes a good relay - publish up-to-date expectations for relay operators - set best practices for how to set relay families - detect and resolve bad relays - exitmap, sybil detection, hsdir traps (2) anomaly analysis / network health engineer [with network team] - establish baselines of expected network behavior - look for and resolve denial of service issues - track connectivity issues between relays - look for relays hitting resource limits (3) make sure usage/growth stats are collected and accurate - track network performance, relay diversity by various metrics - count users [with network team and metrics team] - monitor bridge growth and usage [with censorship team] (4) relay advocacy [with community team] - maintain docs for setting up and running relays and bridges - grow a cohesive community of relay operators so they have peers - keep relays on the right tor versions - relaunch a gamification / badge system for lauding good relay progress - strengthen relationships with non-profit orgs that run relays - help companies that want to offset their tor network load (5) maintain the components of the network - maintain directory authority relationships - keep bandwidth authorities working (including setting the right balance between speed and location diversity) - have enough tor browser default bridges, and keep them running smoothly [with censorship team] - update the fallbackdirs list

3 2

Campaign: Run a Tor Bridge
by Stephanie A. Whited 28 Aug '19

28 Aug '19

** *Hello Tor, * * You all know the importance of Tor bridges for circumventing censorship, and today we’re calling on our community to help censored users by running them. Bridges are relatively easy, low-risk, and low bandwidth to operate, but they have a big impact on people where the internet is under oppressive control. We now have new documentation for how to set them up. We have guides for several Linux distributions, FreeBSD, OpenBSD, and docker [1]. If you set up a bridge before September 30, you could be one of 10 bridge operators to be randomly selected for a Tor t-shirt. More details can be found in phw’s post [2]. If you cannot set up a bridge now, you can still help. You can share your support of running or using Tor bridges on social media with the hashtag #RunTorBridges [3] and a link to the post. Please also share the post with any friends or communities you think would be able to help. If there’s someone you think would be helpful for us to reach out to, please let me know. Thanks for your support. Best, Steph [1] https://community.torproject.org/relay/setup/bridge/ [2] https://blog.torproject.org/run-tor-bridges-defend-open-internet [3] https://twitter.com/hashtag/RunTorBridges?src=hashtag_click * -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Fingerprint: E976 9771 7D46 2E63 9697 9F6D 6D6B 72C3 39A8 76AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

nextcloud: next steps
by Gaba 27 Aug '19

27 Aug '19

Hi! We have been evaluating Nextcoud [0] this year as a replacement for storm [1] and some of us have been using it and giving feedback [2][3] . The next step is to meet with all people interested in this transition (or not) to - discuss cons/pros of nextcloud for Tor and try to make a decision on moving forward. The meeting day will be: Tuesday August 27th, 1800 UTC at #tor-meeting in irc.oftc.net If you can't come to the meeting but you still want to say something please reply to this mail in tor-project@ or send me or Linus a private message. Thanks! gaba [0] https://trac.torproject.org/projects/tor/wiki/org/operations/services/nextc… [1] https://storm.torproject.org [2] https://trac.torproject.org/projects/tor/ticket/30869 [3] https://trac.torproject.org/projects/tor/ticket/29415 -- 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

2 2

Join Our DocsHackathon Next Week - Sept 2nd - 6th 2019
by gus 27 Aug '19

27 Aug '19

Hi, Documentation is extremely valuable to the health of open source software projects, but it is often overlooked. Due to the amount of interest we received during our search for a Google Season of Docs candidate, we're kicking off a week-long documentation hackathon Monday 2nd September 00:00UTC to Friday 6th September 23:59UTC. This is your opportunity to help us keep our documentation up to date and relevant for millions of Tor users around the world. We’ll also be rewarding the top 3 contributors with prizes at the end of the week. We are looking for copywriters, front-end devs, testers, and content reviewers to help us improve our documentation and its relevancy. Don't feel like any of these apply to you but still want to help out? Chat with us on IRC (#tor-www - irc.oftc.net) or the community team mailing list to join us and get involved - <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team>. ## How to participate in the DocsHackathon 1. Register: https://survey.torproject.org/index.php/726752?lang=en 2. Take a look at all of the tickets marked with the "DocsHackathon" keyword on Gitlab - <https://dip.torproject.org/groups/web/-/issues?scope=all&utf8=%E2%9C%93&sta…> 3. If you have a documentation issue that is not currently reflected in Trac, Gitlab or GitHub, create it, tag it and let one of us know on IRC channel #tor-www so we can assign some points to it. 4. Choose a ticket and start working on it! You can submit Pull Requets on GitHub or register on our Gitlab instance to submit merge requests there. 5. A contribution will be counted when your PR or merge request is merged to the master branch of the relevant repository. 6. The awards and prizes to contributors will be announced after all the merges were done. For more details on how you can contribute, check out our DocsHackathon wiki <https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH…>. We are a small nonprofit with a big mission, and we sincerely appreciate your help getting our documentation up to speed. We're looking forward to working with you next week!

1 0

Tor Browser team meeting notes, 26 August 2019
by Georg Koppen 27 Aug '19

27 Aug '19

Hello! We had our weekly browser meeting yesterday held in #tor-meeting2. Here comes, as usual, the IRC log http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-08-26-17.31.l… and our items from the pad: Discussion: sysrqb: what is the expectation of our mozconfigs in tor-browser.git? (GeKo: #23656. They should be the canonical ones I think so that both local and rbm builds are in sync) mcs and brade (will miss the meeting today): Last week: - #30429 (ESR 68 Rebase). - revised the updater patches in response to acat’s feedback (thanks!) - #29430 (Use uTLS for meek TLS camouflage in Tor Browser). - posted patches for review (but it seems that they need more work). - created ticket and patch for #31487 (Modify moat client code so it is compatible with ESR68). - created ticket and patch for #31488 (moat: support a comma-separated list of transports in Tor config). - created #31491 (clean up the old meek http helper browser profiles). - created core Tor ticket #31495 (cannot configure bridges). - Responded to Antonela's comments in #30237 (Onion Services client auth prompt). - Did a little testing for #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - Did some quick testing of the new macOS ESR68 Tor Browser nightly build. - Helped with triage of incoming tickets. This week/upcoming: - #29430 (Use uTLS for meek TLS camouflage in Tor Browser). - investigate circuit display breakage when meek is used. - #30429 (ESR 68 Rebase) — rebase updater patches. - test the ESR68-based updater on Windows. - We have several family commitments this week and had planned to only be working on Tuesday and Wednesday (27-Aug and 28-Aug). - Now Tuesday 27-Aug will be a partial day because we will attend the funeral of a friend. - We will be away from keyboard on September 5th and 6th (and Monday September 2 is a U.S. holiday). Pili: Last week: - OTF Browser proposal - S27 meeting This week: - Task re-org meeting tomorrow (Tuesday 27th @ 15UTC) - Tor Browser Release meeting on Wednesday 28th @ 18UTC - September Roadmapping and capacity planning - imported tickets for August in gitlab to help me with roadmapping for September - we need to look at what's going to be carried over to September and discuss time estimates - Team capacity for the month is currently 79 person days taking into account holidays and vacation (mcs, brade and sysrqb) - Please let me know if there's any other planned vacation/afk time I should know about - Please fill out the areas of expertise on the spreadsheet: https://nc.riseup.net/s/pLxWcGQD3THrXEd - S27 August report - OTF Browser proposal GeKo: Last week: - presentation at CCCamp (went well even though the acoustics were awful) - finished macOS toolchain (#30323) - thought more about notarization issue (#30126) - worked on windows toolchains (#28716 and #28328); final tests; patches for the former are up for review and I'll post patches for the latter later (barring unforeseen issues) - helped with the OTF proposal - again dealing with backlog This week: - release prep and building - final reviews for #30429 and #10761 - finish outstanding Windows toolchain issues - backlog tjr: - Began the WASM-support-for-extensions work: https://bugzilla.mozilla.org/show_bug.cgi?id=1576254 - Did a bunch of little mingw build patches last night - nothing urgent for Tor to worry about, they'll get to ESR68 when they get there - Still ( :( ) waiting in alloc/dealloc patch review https://bugzilla.mozilla.org/show_bug.cgi?id=1547519 - This is the only outstanding esr68 problem. esr68 needs --disable-malloc which is not in-tree. acat: Last week: - Ported #30683 and #31298 to esr68. - Updated rebased esr68 branch (#30429). - Added mcs/brade updater patches. - Added newer missing desktop patches from tor-browser-60.8.0.esr-9.0-1. - Backported patches (#2760 and #28711). - Patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1573276 (DTD locale leak patch regression) - Investigated changing noscript from security settings not working in nightlies (#31396). Next week: - Fix #31396. - Possibly address review comments on latest #30429 changes. - Review latest #31010 changes. - Try to upstream some patch in the backlog. - Keep testing nightly, file/fix tickets. sysrqb: Last week: Mostly 68esr rebase and testing Wrote draft Orfox R.I.P. blog post This week: Continue testing 68esr builds Help with build system, as needed Get nightly android builds? Publish Orfox blog post OTF proposal Next week: AFK mostly after release (until 12 Sep) boklm: Last week: - Backlog from previous weeks - Worked on #31449 (Signing tools for 32bit Linux are 64bit now) - Reviewed #30323 (macOS toolchain updates for esr68) and #31465 (tor-browser-build changes for macOS notarization) - Started looking at #31517 (Simplify macOS related bits in Firefox project) This week: - Verify that our esr68 mar-tools can be used for signing - Review #28716 (Create a mingw-w64-clang project) and other toolchain tickets - Investigate #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) - Review #30334 (build_go_lib for executables) and #31264 (tar.gz output files contain non-reproducible timestamps) - Help with new releases build Antonela: - #31286 - Tor network settings - are we OK using a plain-color version of the Tor Browser icon for the Tor network settings? mockup -> https://trac.torproject.org/projects/tor/raw-attachment/ticket/31286/C-abou… (GeKo: looks good to me, +1) pospeselr: Last Week: - network settings work (#31286) - completed the about:preferences xul and layout - started prototyping the 'request bridge' dialog - misc widl followup (#31458) This Week: - finish request bridge dialog xul, move on to wiring in logic from tor-launcher (#31286) - get a windows build with latest mingw and verify screen readers work as expected (#31458) I tried building release/nightly windows i686/x86_64 a couple times over the weekend and ran into some issues (first cbindgen not building which seems to be resolved, and now the firefox project pointing to a tag that supposedly doesn't exist ( tor-browser-68.0esr-9.0-1-build2 ), haven't investigate further, but is there a known working windows sku in tor-browser-build right now?) (GeKo: let me give you some bundles after the meeting; I have patches to enabled Windows nightly builds again) sisbell: - #30665: Get Firefox 68 ESR working for Android. Additional fixes to mozconfigs. Now working for arm7, arm8, x86. Ready for integrating patches. This week: - #30665: Work with sysrqb on getting patches applied. There is a build break if we disable webrtc, so will investigate this - Add x86_64 android support Georg

1 0

Network team meeting notes, 26 August 2019
by Nick Mathewson 26 Aug '19

26 Aug '19

Hi! You can find the transcript of our latest meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-08-26-17.00.html Below are the contents of our meeting pad when the meeting was done: = Network team meeting pad! = This week's team meeting is at Monday 19 August 1700 UTC on #tor-meeting on OFTC. We have changed the day from Tuesday to Wednesday. August schedule: * Monday 12 August 1700 UTC * Monday 19 August 1700 UTC * Monday 26 August 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.) In-person meetings: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… 22 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002401.html 29 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002408.html 7 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002418.html 12 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002431.html 19 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002435.html == Stuff to do every week = * Let's check the 0.4.1 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. * When you are overloaded, it is ok to say "no" to things. * And it is ok to reschedule things. ------------------------------- ---- 26 August 2019 ------------------------------- == Announcements == AFK ahf will be AFK all of August for BornHack and CCC Camp, but will be on IRC every now and then On September there is a technical writer from Google Season of Docs starting to work with us on rewriting the Tor manual page. She will be 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. The release date for 0.4.1.x-stable is postponed to 20 August, so that it will come out _after_ Nick is back from vacation. Please get all 041 blockers fixed and merged if possible? People working on sponsor 31 will meet on Thursday August 29th at 2300 UTC. We will talk in #tor-meeting and the agenda will be here:https://pad.riseup.net/p/IRjuGtQkWNKZLc7qskDb == Discussion == * [gaba] There are some tickets left from August in the Roadmap. Do we icebox them? https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… teor says: it's still August for 8 more days? * [gaba] do we schedule next network team retrospective? It may be a good idea to skip until end of September as many people were on leave in August. <-- It will be on late September --> == Recommended links == Ricochet Refresh with Tor 0.3.5.8: https://ricochetrefresh.net/ macOS 10.5 has a read-only system volume and a redesigned path structure. Standard Unix tools shouldn't be affected, but some builds or apps might be: https://eclecticlight.co/2019/08/21/its-time-to-test-your-scripts-against-c… the onion talk at ccc camp https://media.ccc.de/v/Camp2019-10340-updates_from_the_onion == 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 august 23rd) Last week (actual): . roadmap in gitlab: uploaded september issues . s31: scheduling check-in for this week . ipv6 funding proposal This week (planned): . s31 . scalability funding proposal Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 19 August (planned): Urgent: - config.c refactor code review (#30914), because we want to get it done by the end of August Roadmap: - 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 - finish small 0.4.1 tasks - finish remaining code reviews, except for neel's big PR that I will split up Other: Week of 19 August (actual): Urgent: - CI monitoring - IPv6 funding proposal - release notes fixes for 0.4.1.5 Roadmap: - finished some code reviews - reviewed big config refactor PRs: - #30914 - merged - #30935 - ready for merge - #31240 - in the middle of the review - responded to reviews on my code - practracker bug fixes for #30979 and #31462 - backport deciding, tagging, and making backport branches from master PRs - bug fixes for monotime coarse conversion overflows (bug only in master) #31482 - diagnosing another bug in the token bucket refactor #31483 - implemented #23818 and #23507 and the associated spec change Other: - worked on #21003 so I could see the IPv6 addresses in logs to review #31088 <<-- gaba: this is not in the roadmap. what was the priority about it? Thanks! I was talking about #21003 and not the review -->> - I was assigned #31008 to review. I needed to see the IPv6 addresses in logs as part of the review. So I did #21003. - For more details see https://trac.torproject.org/projects/tor/ticket/21003#comment:17 - We can also make it Sponsor27-can, because it is useful for debugging #23818 and #23507 - helping with rustc version CI changes - helping relay operators with various issues Week of 26 August (planned): Urgent: - CI monitoring - config.c refactor code review, because we want to get it done by the end of August Roadmap: - 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 - finish small 0.4.1 tasks - finish remaining code reviews, except for neel's big PR that I will split up - do the backports that are due after the 0.4.1.5 release, switch hidden tags - backport deciding Other: - team policies: commit bit and roles? Week of 26 August (actual): Urgent: Roadmap: - reviewed big config refactor PRs: - #30935 - ready for merge - #31240 - in the middle of the review Other: - helping relay operators with various issues Nick: Week of 19 August (planned): - Release 0.4.1.5 (stable) - More 29211 (configuration refactor) work. Hoping to reach the point where 1 module is module-wise configured - Review and merge - Revise old branches after they're reviewed. - Finish and submit walking onions paper. Week of 19 August (actual): - Stopped new work on 29211 pending catch-up from reviews - Released 0.4.1.5 stable - Review and merge - Worked on Walking Onions paper - Pending Coverity issues (pending) Week of 26 August (planned): - Revisions for 31240 (make confparse handle compound formats and objects) - Review and merge - Finish 31241 (refactor conf validation), make it needs_review - If we catch up with merge and revision on 29211: move on to 30866. - Practracker tests (31477) - Start early on September roadmap items, time permitting. Mike: Week of 8/19 (planned): - Medical leave Week of 8/19 (actual): - Medical leave Week of 8/26 (planned): - Catch up on mail/tickets - Work on circpad dev doc Need help with/at risk of dropping this month: - Circpad doc writing? (asn?) - Firefox ESR network code review - Deep-thought-required research project followup (masque, BGP, ECN, etc) - Relay community drive/mgmt (and related LTS herding) - Circpad documentation + Sponsor 2 report catalyst: week of 08/19 (2019-W34) (planned): - catching up after leave - skimming IRC highlights; please email me if you think i've missed something important - reorient on current CI status week of 08/19 (2019-W34) (actual): - made progress on #30984 (key-value lines for control replies) -- fixed some memory management issues, started improving documentation - worked some partial days (medical) week of 08/26 (2019-W35) (planned): - reviews - investigate some Jenkins failures - get #30984 ready for review (key-value lines for control replies) -- still documenting some things asn: Week of 19/08 (planned): - Read [tor-dev] [prop305] Introduction Point Behavior - Check open hackerone issue. - Finish up with reviews and merges before CCC camp. - Attend CCC camp and participate in the talk. - Speak with the onionbalance maintainer during camp to make plans for v3 onionbalance. Week of 19/08 (actual): - Replied to [tor-dev] threads - Cleared up hackerone issue. - Reviewed and revised #30924 (DoS ticket) - Finished all urgent reviews/merges but not all of them. - Worked on onionbalance: - Met with Donncha at camp and talked onionbalance. - Spoke with atagar about #31369 and reviewed his new code. - Mapped out what needs to be done in #31369 from my side. - Did the talk at camp! Week of 26/08 (planned): - Finish up reviews/merges that piled up further. - More work on stem side of onionbalance (#31369) - Find time to watch the recording from the latest mozilla meeting - Think about HS issue: #20212 ahf: - on leave Week of 22/7 (planned): - Do reimbursement - Go over all notes from Stockholm that seems relevant to me. - Follow up on pre-Stockholm items: - Continue figuring out some info on a potential Danish funder. - Continue with #5304 and #28930 Week of 22/7 (actually): - Did reimbursement - Went over all notes from Stockholm. - Followed up on pre-Stockholm items: - Continue figuring out some info on a potential Danish funder (postponed until they are back from vacation). - Continued work with #5304 and #28930 Week of 29/7 (planned): - Finish off #5304 and #28930 before going on vacation. - Review Roger's DEFCON slides. - Do you need any help from me before I leave? dgoulet: Week of 19/08 (actual): - #30924 has been revised and now merge_ready - Worked on HS timeout issues (#30200 + #28841). Built a tracing system to follow the HS dance coupled with circuit build time and timeout. Already paid off, #31490 is a bug that came out of it. - Spent time chasing a EWMA cell scheduling issue but fell off the radar after some hours, lack of time to continue. Week of 26/08 (planned): - Continue on #30200. - Address revisions needed for #30924 if any comes.

1 0