tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

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

12 Sep '19

Hi! You can read today's meeting log here: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-12-14.59.html Below is the agenda from the meeting pad: - can we send notes (notes from the pad and link to log) at the end of the meeting to the tor-project mailing list? - scalability proposal - Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap Next meeting: September 19th cheers, gaba -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Tor Browser team meeting notes, 9 September 2019
by Georg Koppen 10 Sep '19

10 Sep '19

Hello! We held our weekly Tor Browser meeting yesterday in #tor-meeting2. Here is the IRC log: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-09-09-17.30.l… and below are the notes from our meeting pad: Discussion: - Do we have an estimate of how many Tor Browser alpha users there are? (mcs) (GeKo: not really. but we could try to find out. boklm volunteered to file a ticket for the metrics folks) GeKo: Last week: - sent monthly report to tor-project (this time for July and August) - helped with the alpha release (so far nothing exploded, good!) - helped getting 8.5.6 out (looked into #31616 over the weekend) - made progress on #31538: it feels we are close to tracking the issue down, wish me luck ;) - made progress on #30429 - set up macOS system for #30126 - wrote patches for #31450, #31621, #27493 and started to work on #31584 - reviewed #28822, #31598, #30384, #31457, #31562 This week: - Bug 30126: Apple notarization - Bug 31538: Windows reproducibility - moar reviews - #31597 (Mozilla bug review for bugs squashed between Firefox 61-68) - finish missing pieces for #30429 tjr - Worked on the wasm bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1576254 - Think I have it close enough to finish this week. mcs and brade: Last week: - #31457 (disable per-installation profiles). - Created patch which has been reviewed and merged by gk (thanks). - #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - Discussed next steps with gk. - Installed macOS 10.15 beta to a USB hard drive to use for testing. This week/upcoming: - #31607 (App menu items stop working). - #31491 (clean up the old meek http helper browser profiles). - Testing for #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - Work on other tbb-9.0-must-alpha tickets as time permits, - Reminder: we have vacation planned for the week of September 23rd. boklm: Last week: - Helped publish new releases - Worked on #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) - Reviewed https://github.com/torproject/support/issues/12 - Started looking at #31646 (Update abicheck to require newer libstdc++.so.6) This week: - Some reviews: - #31596 (Bump mingw-w64 version to pick up fix for #31567), - #31450 (Still use GCC for 64bit Linux debug builds after switch to 68 ESR), - #31621 (Fix node bug that makes large writes to stdout fail), - #31641 (Provide link to Tor Browser for Android alpha on our alpha download page) - Work on #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) and other tbb-9.0-must-alpha toolchain tickets - Open a ticket to add alpha users update pings to metrics graphs sisbell: Last Week: - #31564: Android bundles not reproducible - poor google documentation, key repo with google vendor code not available is blocker for this approach. Tested out apktool as way forward. Initial results look good, Any objections to moving forward with this? (GeKo: sounds good, but let's use the apktool as it comes with Debian as that saves us time) This week - #31564: Add decompile/recompile of resource apks to project build. - #31568: Gradle how-to - open tickets for tor-android-service patches pospeselr: Last week: - browser privacy meetup, will post my notes somewhere later today This week: - pick back up #31286 - review build for y'all to see the mocked UX - rebase to latest, assuming I can get the local linux build toolchain working acat: Last week: - Fix onboarding regressions + address review comments (#28822). - #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 (needs review) - #30662 - Make sure about:newtab is blank (needs review) - #31601 - Don't let Mozilla recommend extensions again (needs review) This week: - #26345 - Finish Disable tracking protection UI in FF67-esr - There are still requests to mozillla (apart from activity-stream), investigate. (tjr: what're they?) (acat: i don't remember, I think the stack trace of the request pointed to some Updater telemetry file? But it came from RemoteSettingsClient.js, so probably worth checking for all usages of that). (tjr: Ah, this is Kinto/Remote Settings. Could be addon/gpu blocklist, or onecrl, or crlite, or intermediate preloading... many things use remote settings.) - Work on other tbb-9.0-must-alpha tickets. - Investigate if serviceworkers can still see localized msgs in 30683. - Maybe do a bit of mozilla upstream backlog (e.g. 30683). Georg

1 0

minutes from the sysadmin meeting
by Antoine Beaupré 09 Sep '19

09 Sep '19

Here are the minutes from today's sysadmin meeting. # Roll call: who's there and emergencies Anarcat, Hiro, Linus, Peter, and Roger attending. # What has everyone been up to ## anarcat ### July * catchup with Stockholm and tasks * ipsec puppet module completion (should we publish it?) * fixed civicrm tunneling issues, hopefully ([#30912][]) * published blog post with updates from the previous email: <https://anarc.at/blog/2019-07-30-pgp-flooding-attacks/> * struggled with administrative/accounting stuff * contacted greenhost about DNS: they have anycast DNS with an API, but not GeoDNS, what should we do? * RT access granting and audit ([#31249][], [#31248][]), various LDAP access tickets and cleaned up gettor group * [backup documentation][] ([#30880][]) * tested bacula and postgresq restore procedures, specifically, you might want to get familiar with those before a catastrophe * cleaned up services inventory ([#31261][]) all in <https://trac.torproject.org/projects/tor/wiki/org/operations/services> now * worked on getting ganeti into puppet with weasel [#31261]: https://bugs.torproject.org/31261 [#30880]: https://bugs.torproject.org/30880 [backup documentation]: https://help.torproject.org/tsa/howto/backup/ [#31248]: https://bugs.torproject.org/31248 [#31249]: https://bugs.torproject.org/31249 [#30912]: https://bugs.torproject.org/30912 ### August * on vacation the last week, it was awesome * published a summary of the KNOB attack against Bluetooth (TL;DR: don't trust your BT keyboards) <https://anarc.at/blog/2019-08-19-is-my-bluetooth-device-insecure/> * ganeti merge almost completed * first part of the hiera transition completed, yaaaaay! * tested a puppet validation hook ([#31226][]) you should install it locally, but our codebase is maybe not ready to run this server-side * retired labs.tpo ([#24956][]) * retired nova.tpo ([#29888][]) and updated the host retirement docs, especially the hairy procedure where we don't have remote console to wipe disks [#29888]: https://bugs.torproject.org/29888 [#24956]: https://bugs.torproject.org/24956 [#31226]: https://bugs.torproject.org/31226 ## hiro - Collecting all my snippets here https://dip.torproject.org/users/hiro/snippets * catchup with Stockholm discussions and future tasks * fixed some prometheus puppet-fu * some website dev and maintenance * some blog fixes and updates * gitlab updates and migration planning * gettor service admin via ansible ## weasel, for september, actually * Finished doing ganeti stuff. We have at least one VM now, see next point * We have a loghost now, it's called loghost01. There is a /var/log/hosts that has logs per host, and some /var/log/*all* files that contain log lines from all the hosts. We don't do backups of this host's /var/log because it's big and all the data should be elsewhere anyway. * started doing new onionoo infra, see [#31659][]. * debian point releases [#31659]: https://bugs.torproject.org/31659 # What we're up to next ## anarcat * figure out the next steps in hiera refactoring ([#30020][]) * ops report card, see below ([#30881][]) * LDAP sudo transition plan ([#6367][]) * followup with snowflake + TPA? ([#31232][]) * send root@ emails to RT, and start using it more for more things? ([#31242][]) * followup with email services improvements ([#30608][]) * continue prometheus module merges * followup on SVN decomissionning ([#17202][]) [#17202]: https://bugs.torproject.org/17202 [#30608]: https://bugs.torproject.org/30608 [#31242]: https://bugs.torproject.org/31242 [#31232]: https://bugs.torproject.org/31232 [#6367]: https://bugs.torproject.org/6367 [#30881]: https://bugs.torproject.org/30881 [#30020]: https://bugs.torproject.org/30020 ## hiro * on vacation first two weeks of August * followup and planning for search.tp.o * websites and gettor taks * more prometheus and puppet * review services documentation * monitor anti-censorship services * followup with gettor tasks * followup with greenhost ## weasel * want to restructure how we do web content distribution: * Right now, we rsync the static content to ~5-7 nodes that directly offer http to users and/or serve as backends for fastly. * The big number of rsync targets makes updating somewhat slow at times (since we want to switch to the new version atomicly). * I'd like to change that to ship all static content to 2, maybe 3, hosts. * These machines would not be accessed directly by users but would serve as backends for a) fastly, and b) our own varnish/haproxy frontends. * split onionoo backends (that run the java stuff) from frontends (that run haproxy/varnish). The backends might also want to run a varnish. Also, retire the stunnel and start doing ipsec between frontends and backends. (that's already started, cf. [#31659][]) * start moving VMs to gnt-fsn ## ln5 * help deciding things about a tor nextcloud instance * help getting such a tor nextcloud instance up and running * help migrating data from the nc instance at riseup into a tor instance * help migrating data from storm into a tor instance # Answering the 'ops report card' See <https://trac.torproject.org/projects/tor/ticket/30881> anarcat introduced the project and gave a heads up that this might mean more ticket and organizational changes. for example, we don't define "what's an emergency" and "what's supported" clearly enough. anarcat will use this process as a prioritization tool as well. # Email next steps Brought up "the plan" to Vegas: <https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No…> Response was: why don't we just give everyone LDAP accounts? Everyone has PGP... We're still uncomfortable with deploying the new email service but that was agreed upon in Stockholm. We don't see a problem with granting more people LDAP access, provided vegas or others can provide support and onboarding. # Do we want to run Nextcloud? See also the discussion in <https://trac.torproject.org/projects/tor/ticket/31540> The alternatives: A. Hosted on Tor Project infrastructure, operated by Tor Project. B. Hosted on Tor Project infrastructure, operated by Riseup. C. Hosted on Riseup infrastructure, operated by Riseup. We're good with B or C for now. We can't give them root so B would need to be running as UID != 0, but they prefer to handle the machine themselves, so we'll go with C for now. # Other discussions weasel played with prom/grafana to diagnose onionoo stuff, and found interesting things. Wonders if we can hookup varnish, anarcat will investigate yet. we don't want to keep storm running if we switch to nextcloud, make a plan. # Next meeting october 7th 1400UTC # Metrics of the month I figured I would bring back this tradition that Linus had going before I started doing the reports, but that I omitted because of lack of time and familiarity with the infrastructure. Now I'm a little more comfortable so I made a script in the wiki which polls numbers from various sources and makes a nice overview of what our infra looks like. Access and transfer rates are over the last 30 days. * hosts in Puppet: 76, LDAP: 79, Prometheus exporters: 121 * number of apache servers monitored: 32, hits per second: 168 * number of self-hosted nameservers: 5, mail servers: 10 * pending upgrades: 0, reboots: 0 * average load: 0.56, memory available: 357.18 GiB/934.53 GiB, running processes: 441 * bytes sent: 126.79 MB/s, received: 96.13 MB/s Those metrics should be taken with a grain of salt: many of those might not mean what you think they do, and some others might be gross mischaracterizations as well. I hope to improve those reports as time goes on. Feedback, is, of course, very welcome. -- Antoine Beaupré torproject.org system administration

1 0

Community Team monthly report for August 2019
by gus 09 Sep '19

09 Sep '19

Hi, Here's Community Team report for August 2019. Documentation ============= Community Team is responsible to keep the content updated on these websites: Support portal, Tor Browser manual and Community portal. In August we organized all the logistics to a documentation hackathon - #DocsHackathon - to engage volunteers and update our documentation: * Blog post + online registration: <https://blog.torproject.org/join-tors-docshackathon-next-week> * Ticket triage: <https://dip.torproject.org/groups/web/-/issues?scope=all&utf8=%E2%9C%93&sta…> * DocsHackathon wiki: <https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH…> Frontdesk ========= Tickets backlog: from +1000 new tickets in frontdesk queue, we worked to reduce to ~170 new tickets. Community Portal work ===================== Our new shiny portal is taking shape! Some sections are done, others needs more love (and volunteers). Relay operations section is almost done: more pages migration from Trac and old portal to <https://community.torproject.org/relay/> If you want to help with content to Onion Services section, get in touch with us! Sponsor9 work ============= In August Pili and Gus worked on a Training Partnership Agreement to submit to local organizations in countries that we visited during Sponsor 9 phase 1 and 2. We also move forward with our roadmap defined during Stockholm meeting and started to get in touch with partners from Sponsor9 Phase 1 and Phase 2. Outreach ======== * Chaos Communication Camp - CCCamp Activities (Aug 20 - 25th): * Community members organized a booth with Tor t-shirts and flyers in about:freedom cluster: <https://twitter.com/torproject/status/1164178576083755008> * Submitted and organized activities in about:freedom * 2019/08/21 18:00 - Tor Relay Operator Meetup * 2019/08/22 13:30 - Tor Project: running Tor trainings with human rights defenders in Global South * CCCamp activity in main schedule: * 2019/08/23 14:00 - Updates from the Onion - The Road to Mobile Tor and Improved Censorship Circumvention <https://media.ccc.de/v/Camp2019-10340-updates_from_the_onion> * Read more about our activities: <https://events.ccc.de/camp/2019/wiki/Village:Tor_Project> <https://blog.torproject.org/events/cccamp-germany> * After two months without Global South IRC meetings, we're back! Our monthly meeting happened on August 30th on #tor-south channel: * Meeting notes: <https://lists.torproject.org/pipermail/global-south/2019-September/000256.h…> * Next meeting: Friday, Sept 27, 1600 UTC, #tor-south * Cy talked to students from São Paulo University about Tor Project. Funding ======= Working in a funding proposal with Tails and the Guardian Project. Meta ==== * Updated the Community Team meeting format, read our meeting notes here: * Meeting notes, 5 Aug 2019: https://lists.torproject.org/pipermail/tor-community-team/2019-August/00029… * Meeting notes, 12 Aug 2019: https://lists.torproject.org/pipermail/tor-community-team/2019-August/00030… * Meeting notes, 19 Aug 2019: https://lists.torproject.org/pipermail/tor-community-team/2019-August/00030… * Meeting notes, 26 Aug 2019: https://lists.torproject.org/pipermail/tor-community-team/2019-August/00030…

1 0

Tails report for August 2019
by intrigeri 09 Sep '19

09 Sep '19

Hi, we've just published the Tails report for August: https://tails.boum.org/news/report_2019_08/ I'm attaching a slightly cleaned up HTML version, for those who prefer to read this offline. Cheers, -- intrigeri

1 0

Network team meeting notes, 9 Sep 2019
by Nick Mathewson 09 Sep '19

09 Sep '19

Hi! You can read today's meeting log at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-09-17.00.html Below are the contents of our meeting pad: = Network team meeting pad! = This week's team meeting is at Monday 9 September 1700 UTC on #tor-meeting on OFTC. September-October schedule: * Monday 9 September 1700 UTC * Monday 16 September 1700 UTC * Monday 23 September 1700 UTC * Wednesday 2 October 2300 UTC * Monday 7 October 1700 UTC * Monday 14 October 1700 UTC * Monday 21 October 1700 UTC * Monday 28 October 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the tor-project mailing list archive for older notes.) 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 26 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002442.html 4 September: https://lists.torproject.org/pipermail/tor-project/2019-September/002465.ht… == Stuff to do every week = * Coming up: the 0.4.2 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://dip.torproject.org/torproject/core/tor/boards * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. * When you are overloaded, it is ok to say "no" to things. * And it is ok to reschedule things. ------------------------------- ---- 9 September 2019 ------------------------------- == Announcements == On September there is a technical writer (Swati) from Google Season of Docs starting to work with us on rewriting the Tor manual page. She is participating in the network team meetings. Her project: https://developers.google.com/season-of-docs/docs/participants/project-tor We are moving the kanban board from storm into https://dip.torproject.org/torproject/core/tor/boards . This will help lead a plan for migration into dip.torproject.org. People working on sponsor 31 will meet for a second time on Tuesday September 10 at 2300 UTC. We will talk in #tor-meeting and the agenda is here:https://pad.riseup.net/p/IRjuGtQkWNKZLc7qskDb Remember that 0.4.2.x-alpha freezes on 15 September. For large features, the freeze date is 8 September. Bug Smash Fund campaign has been on: https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs The idea is that this will be funding non-sponsor bugs. If you are working on ticket that is not sponsored please tag it with BugSmashFund keyword. Remember to look at transition to gitlab https://lists.torproject.org/pipermail/tor-project/2019-September/002458.ht… == Discussion == * When is the next time origin/master will be open? - (Some non-critical circpad things should go in somewhere, but don't need 042) * Some of our needs_review tickets are getting a bit old, should we give them to other people? == Recommended links == "Testing the boundaries of collaboration" https://increment.com/testing/testing-the-boundaries-of-collaboration/ == Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: (updated on september 4th) Last week (actual): . s31 This week (planned): . s31 report . scalability funding proposal Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 2 September (actual): Urgent: - Roadmap: - Sponsor 31 config.c reviews - Sponsor 31 retrospective and planning Other: - #31549 review - old relays out of the consensus - #31664 triage - guard number config - quick tools and quick fixes that make development easier Week of 9 September (planned): Urgent: - Roadmap: - Sponsor 31 config.c refactor reviews - finish add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - split off bugs I found while writing the control trace code Other: - team policies: commit bit and roles? Week of 9 September (actual): Urgent: - Roadmap: - Sponsor 31 config.c refactor Other: - bug smash on logging bugs #31594 and children (maybe some of these are bugs on other sponsored work) - bug triage - emails Nick: Week of 2 September (planned): - Get 31240 merged if possible, and if it is, solve *all* pending 29211 backlog issues. - S31 Meeting on Tuesday 2300 UTC (rescheduled) - S31 work TBD, pending division of tasks on Tuesday - Start removing work from 0.4.2 milestone, and tagging other work with must/should/can. - Investigate 31570 (mmap crash in 0.4.1) unless somebody else picks it up. - Reviews and merges. - Coordinate role transition plans with ahf and gaba. Week of 2 September (actual): - Resolved several pending 29211 (config refactor) issues (31532 31529 31624 31627 31629) - Took on additional review, merge stuff. - S31 meeting (initial) - Began 0.4.2 triage - Came up with a patch for 31570 (mmap crash) - Review and merge - worked on 31578 (practracker vs make dist) - Added proposals 306, 307 to repository - Began proposal for adding proposals more regularly. - Made myself a checklist to follow before putting things in needs_review. Week of 9 September (planned): - Merge big pending patches. (Sorry asn & dgoulet! :/ ) - Respond to questions on S31 pad before tuesday - Another S31 meeting - Work on circuitpadding doc merge stuff. - Start a PETS review - Work on more 29211 followup issues - More 0.4.2 triage. Mike: Week of 8/26 (planned): - Catch up on mail/tickets - Work on circpad dev doc Week of 8/26 (actual): - Catch up on mail/tickets - Finished rough draft of circpad dev doc; mailed to researchers Week of 9/4 (planned): - Funding proposal catchup + direction - Firefox ESR new feature and network code reviews - Fold in researcher feedback on circpad dev doc Need help with/at risk of dropping this month: - Not doing any code reviews this month, unless on circpad patches. Got enough for Tor Browser - Circpad doc followup/fold-in? (asn?) - Firefox ESR code review - (I am working on this, but unlikely to finish it this month at this rate of interruption+distraction) - Firefox new feature review - Funding proposal review, meetings, coordination, cross-checking estimations, strategy, etc. - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) - Relay community drive/mgmt (and related LTS herding) catalyst: week of 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 week of 08/26 (2019-W35) (actual): - reviews - made some progress on getting #30984 ready for review -- cleaned up some memory management issues, improved some documentation - chasing spurious chutney failures; they turn out to be somehow sandbox-related? thanks to teor for helping diagnose week of 09/02 (2019-W36) (planned): - TPI holiday 09/02 - sponsor31 check-in retrospective (and follow up) - reviews - more work on #30984 week of 09/02 (2019-W36) (actual): - TPI holiday 09/02 - reviews - sponsor31 check-in week of 09/09 (2019-W37) (planned): - more sponsor31 reporting and check-in - reviews - look at gitlab migration plan doc - #30984 need help with: - please help take a look at some jenkins failures: * tor-ci-linux-0.2.9 (old-ish) https://jenkins.torproject.org/job/tor-ci-linux-0.2.9/292/console -- this looks like a travis failure. There's a java exception caused by a timeout, and no builders actually happen. * tor-ci-linux-0.4.1 (new-ish) https://jenkins.torproject.org/job/tor-ci-linux-0.4.1/ARCHITECTURE=amd64,SU… Buster amd64 is failing with what appears to be 08:50:53 08:50:53 FAIL: src/test/test_workqueue_efd.sh 08:50:53 ==================================== 08:50:53 08:50:53 Illegal instruction 08:50:53 FAIL src/test/test_workqueue_efd.sh (exit status: 132) I wonder if this is transient, or if it is a real problem? We didn't change this code any time recently. * tor-ci-linux-master-clang (new-ish) https://jenkins.torproject.org/job/tor-ci-linux-master-clang/3640/ARCHITECT… This is only happening on i686 sid, and it is a compiler segfault. This makes me think it is a bug in the clang package in debian unstable. * tor-ci-mingwcross-* (old-ish) https://jenkins.torproject.org/job/tor-ci-mingwcross-master/2499/ARCHITECTU… This looks like a misconfiguration to me -- it seems to be complaining about not having found a zlib package maybe? * tor-ci-windows-master (old?) https://jenkins.torproject.org/job/tor-ci-windows-master/78/console This looks like it could be a real bug: a unit test is failing. It's in "slow/process/callbacks" -- I believe ahf knows that code best. asn: [Might be for dinner at the time of the meeting] Week of 02/09 (planned): - Hyper focusing on onionbalance+stem #31369. - The goal is to be able to encode and decode v3 descriptors by the end of next week. - Reviews/merges as per the usual Week of 02/09 (actual): - Worked on #31369 - Created stem module that encodes/decodes ed25519 certs - Started work on encoding descriptors - Pending feedback on #31369 by atagar. - Created another stem onionbalance ticket #31648 and started work on it while waiting for atagar feedback on #31369 - Some more findings on old #28970 bugfix ticket. - Did more triaging and updated points on onionbalance master ticket (#29998) Week of 09/09 (actual): - More work on stem side of onionbalance (#31369 and #31648) ahf: Week of 2nd of September (planned): - Returned from long vacation of BornHack and CCCamp. - Harvest reporting. - Reading mailing lists, meeting minutes, catch up on community council things, look at Trac and tor.git changes of August. - Hacking on #5304. - Going to be away Thursday (around Friday) to attend a conference in DK and talk about Tor at the engineers union here in DK. Week of 2nd of September (actually): - Harvest reporting. - Read mailing lists, meeting minutes, cought up on community council things, look at Trac and tor.git changes of August. - Hacking on #5304. <gaba: it says that is merge ready , is that completed?> - Did a talk on Tor at the engineering union in DK. Week of 9th of September (planned): - Solve my laptop situation. - Work on #5304 and #28930. - Work with Nick and Gaba on which tasks to takeover. dgoulet: Week of 02/09 (actual): - Most of my time has been on #30200 parent tasks working on building and running an onion service health tool (#28841). - From the above, several tickets have been opened, see the child tickets of #30200. - I've mostly worked on the service side health. I've moved now on writing the tool analysis part for the client side. - One ticket I opened which was needed for my development branch in #30200 that affects the wider tor (and found a bug): #31608. It is good that we are all awayre of this imo. Week of 09/09 (planned): - Continue making sure #31549 is on track and doesn't stall. - Help write blog post about the above ^ in order to be as loud as we can about this big change in the network. - Continue on #30200 to dig into client side behavior (s27 stuff).

1 0

Network team meeting notes, 4 Sep 2019
by Nick Mathewson 09 Sep '19

09 Sep '19

Hi! Last week's meeting logs can be read at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-04-22.59.html Below is the state of last week's pad, from our pad history. = Network team meeting pad! = This week's team meeting is at Wednesday 4 September 2300 UTC on #tor-meeting on OFTC. September-October schedule: * Wednesday 4 September 2300 UTC * Monday 9 September 1700 UTC * Monday 16 September 1700 UTC * Monday 23 September 1700 UTC * Wednesday 2 October 2300 UTC * Monday 7 October 1700 UTC * Monday 14 October 1700 UTC * Monday 21 October 1700 UTC * Monday 28 October 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the tor-project mailing list archive for older notes.) 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 26 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002442.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.) * Coming up: the 0.4.2 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://dip.torproject.org/torproject/core/tor/boards * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. * When you are overloaded, it is ok to say "no" to things. * And it is ok to reschedule things. ------------------------------- ---- 4 September 2019 ------------------------------- == Announcements == 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. People working on sponsor 31 will meet for a second time on Tuesday September 10 at 2300 UTC. We will talk in #tor-meeting and the agenda is here:https://pad.riseup.net/p/IRjuGtQkWNKZLc7qskDb Remember that 0.4.2.x-alpha freezes on 15 September. For large features, the freeze date is 8 September. Bug Smash Fund campaign has been on: https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs The idea is that this will be funding non-sponsor bugs. If you are working on ticket that is not sponsored please tag it with BugSmashFund keyword. == Discussion == * We need a process for putting proposals into the torspec.git repository, and advancing them forward. Does anybody want to write this? * In the meantime, should I (nickm) handle the pending 306 and 307? {Resolution: nick adds 306 and 307 to repo, then writes a policy proposal.} * Relatedly, we maybe need a process for making sure that proposals eventually move from Draft to some other state, and from Open to some other state. I believe that Teor had started writing one of these. Now that we have a metapolicy, would you like to pick that up again? * Alternatively, I (nickm) can do it. Alternatively, we can defer till later. {Resolution: nick tries to do a draft.} * When is the next time origin/master will be open? - (Some non-critical circpad things should go in somewhere, but don't need 042) == Recommended links == Ricochet Refresh with Tor 0.3.5.8: https://ricochetrefresh.net/ macOS 10.15 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… "Testing the boundaries of collaboration" https://increment.com/testing/testing-the-boundaries-of-collaboration/ == Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: (updated on september 4th) Last week (actual): . s31 This week (planned): . s31 report . scalability funding proposal Help with: teor: (online first week of the month, offline at the usual meeting time) 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: - coverity fixes for #21003, rewrote the function using safe string functions #31549 - CI failure triage and monitoring - CI fixes, reviews, backports Roadmap: - reviewed big config refactor PRs: - #30935 - ready for merge - #31240 - in the middle of the reviews - Sponsor 31 retrospective preparation - double checking follow-ups and blockers for #29211 - OnionBalance v3 crypto help - Tor Browser macOS notarisation help - HSv3 IPv6 and single onion service, feature parity and bug fixes Other: - backports after 0.4.1-stable - add some missing tests/commit hook checks, so CI fails less often - quick diagnostics improvements - better backport tooling - helping relay operators with various issues - IPv6 exit ticket triage - non-roadmap reviews - bug triage Nick: 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. Week of 26 August (actual): - Revisions on 31240, including rebase. - Finished a version of #31241, then decided to table it until caught up with other 29211 (config refactor) work. - Practreacker tests (31477) - Tried to catch up with reviews and merges - Code diagnosis - Fixed some shell issues - Regressions in routerset config handling (31495) - Regressions in disable-module-dirauth compilation (31552) Week of 2 September (planned): - Get 31240 merged if possible, and if it is, solve *all* pending 29211 backlog issues. - S31 Meeting on Tuesday 2300 UTC (rescheduled) - S31 work TBD, pending division of tasks on Tuesday - Start removing work from 0.4.2 milestone, and tagging other work with must/should/can. - Investigate 31570 (mmap crash in 0.4.1) unless somebody else picks it up. - Reviews and merges. - Coordinate role transition plans with ahf and gaba. Mike: Week of 8/26 (planned): - Catch up on mail/tickets - Work on circpad dev doc Week of 8/26 (actual): - Catch up on mail/tickets - Finished rough draft of circpad dev doc; mailed to researchers Week of 9/4 (planned): - Funding proposal catchup + direction - Firefox ESR new feature and network code reviews - Fold in researcher feedback on circpad dev doc Need help with/at risk of dropping this month: - Not doing any code reviews this month, unless on circpad patches. Got enough for Tor Browser - Circpad doc followup/fold-in? (asn?) - Firefox ESR code review - (I am working on this, but unlikely to finish it this month at this rate of interruption+distraction) - Firefox new feature review - Funding proposal review, meetings, coordination, cross-checking estimations, strategy, etc. - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) - Relay community drive/mgmt (and related LTS herding) catalyst: week of 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 week of 08/26 (2019-W35) (actual): - reviews - made some progress on getting #30984 ready for review -- cleaned up some memory management issues, improved some documentation - chasing spurious chutney failures; they turn out to be somehow sandbox-related? thanks to teor for helping diagnose week of 09/02 (2019-W36) (planned): - TPI holiday 09/02 - sponsor31 check-in retrospective (and follow up) - reviews - more work on #30984 need help with: - please help take a look at some jenkins failures: * tor-ci-linux-0.2.9 (old-ish) https://jenkins.torproject.org/job/tor-ci-linux-0.2.9/292/console -- this looks like a travis failure. There's a java exception caused by a timeout, and no builders actually happen. * tor-ci-linux-0.4.1 (new-ish) https://jenkins.torproject.org/job/tor-ci-linux-0.4.1/ARCHITECTURE=amd64,SU… Buster amd64 is failing with what appears to be 08:50:53 08:50:53 FAIL: src/test/test_workqueue_efd.sh 08:50:53 ==================================== 08:50:53 08:50:53 Illegal instruction 08:50:53 FAIL src/test/test_workqueue_efd.sh (exit status: 132) I wonder if this is transient, or if it is a real problem? We didn't change this code any time recently. * tor-ci-linux-master-clang (new-ish) https://jenkins.torproject.org/job/tor-ci-linux-master-clang/3640/ARCHITECT… This is only happening on i686 sid, and it is a compiler segfault. This makes me think it is a bug in the clang package in debian unstable. * tor-ci-mingwcross-* (old-ish) https://jenkins.torproject.org/job/tor-ci-mingwcross-master/2499/ARCHITECTU… This looks like a misconfiguration to me -- it seems to be complaining about not having found a zlib package maybe? * tor-ci-windows-master (old?) https://jenkins.torproject.org/job/tor-ci-windows-master/78/console This looks like it could be a real bug: a unit test is failing. It's in "slow/process/callbacks" -- I believe ahf knows that code best. 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 asn: 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 Week of 26/08 (actual): - Finished up various reviews (plus extra) and did most of merges. - Tons of work on stem side of onionbalance (#31369): - Started understanding stem's ins and outs. - Managed to decrypt both layers of the descriptor - Started work on encoding HSv3descriptors - Started work on encoding/decoding ed25519 certs - Code is seriously dirty but does things. Week of 02/09 (actual): - Hyper focusing on onionbalance+stem #31369. - The goal is to be able to encode and decode v3 descriptors by the end of next week. - Reviews/merges as per the usual ahf (I'm in "normal" danish hour cycle so I might miss the meeting): Week of 2nd of August September (planned): - Returned from long vacation of BornHack and CCCamp. - Harvest reporting. - Reading mailing lists, meeting minutes, catch up on community council things, look at Trac and tor.git changes of August. - Hacking on #5304. - Going to be away Thursday (around Friday) to attend a conference in DK and talk about Tor at the engineers union here in DK. 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

August 2019 report for the UX team
by Antonela Debiasi 09 Sep '19

09 Sep '19

Hello Tor, A recap of August in UX land S9 - Tor Browser ================ Tor Browser 9 will see the light in late October, but we are working towards it hardly. During August we were working on having Tor Network Settings in a familiar place for users. That is how about:preferences#tor will host Network Settings. Great work, pospeselr! You can see how it looks here https://trac.torproject.org/projects/tor/ticket/31286 S9 - User Research ================== The first semester of this year, we visited India, Uganda, Kenya, Indonesia, Colombia, and Mexico. Narrira worked on to summarize and compile our user research activities: user needs findings, community threat modeling, and usability testing over TBA and TB Onboarding. Those user insights will inform our work on further product iterations. https://dip.torproject.org/torproject/ux/research/ During our dev meeting in Stockholm, we shared a printed survey about Tor Browser usage with us, the biggest fans of TB (and also the most biased). I shared a small recap of this data, and we are planning to extend this survey with the broad community. Do you hate captchas? We heard from you. https://lists.torproject.org/pipermail/ux/2019-August/000455.html S30 - Snowflake =============== The anti-censorship team is doing great work on bringing usable options for censored users to access the tor network and also for privileged users to help others. Snowflake is becoming something, and we assisted in designing the first user interface for it. Thanks arlolra, cohosh, dfc, and phw for this implementation! https://trac.torproject.org/projects/tor/ticket/23888 OONI Explorer ============= We are so close to release OONI Explorer. Some minor/major adjustments happened during August. Anxious? Check our beta and report issues if you find them: https://explorer.ooni.torproject.org/ https://github.com/ooni/explorer/issues/new Outreach ======== Antonela spoke at the MediaParty19 in Argentina about Tor Browser. A lot of journalists were interested in using Tor technologies for their daily work! https://mediaparty2019.sched.com/event/UESp/tor-browser-the-interface-for-f… Open Team ========= We have been experimenting with gitlab for hosting our roadmaps and to-do tasks. You can see our in-progress open kanban with tickets here: https://dip.torproject.org/groups/torproject/ux/-/boards Starting August, we were sharing our weekly meeting notes to the ux list. If you missed those, then you can see them here: https://lists.torproject.org/pipermail/ux/2019-August/000452.html https://lists.torproject.org/pipermail/ux/2019-August/000453.html https://lists.torproject.org/pipermail/ux/2019-August/000456.html https://lists.torproject.org/pipermail/ux/2019-August/000458.html Peace and love, A -- Antonela Debiasi UX Team Lead @antonela E2330A6D1EB5A0C8 https://torproject.org

1 0

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

05 Sep '19

Here are our meeting logs: <http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-05-17.00.log…> And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday September 5th 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… --------------------------- --- 5th September 2019 ---- --------------------------- == Announcements == * Bug Smash Fund campaign has been on: https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs The idea is that this will be funding non-sponsor bugs. If you are working on ticket that is not sponsored please tag it with BugSmashFund keyword. == Discussion == * https://bugs.torproject.org/19332 (BridgeDB module for CollecTor) is not on the metrics plate anymore. what next? == Actions == * Update roadmap with what you are working on https://dip.torproject.org/torproject/anti-censorship/roadmap/boards == Interesting links == * == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. hiro: (2019-09-02)(gettor days are Thursday - snippets https://dip.torproject.org/snippets) - Coded ansible recipes for gettor so that the service can be easily maintained by more people: https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… - Fixing some issues about git history taking too much space quota on gitlab and github Next week - use archive.org as new distribution endpoint: upload files to archive.org - reach out to irl about sending gettor stats to metrics - review specs: are specs up-to-date? should we change something in the specs? - review docs: write documentation for web site and ansible playbooks. Help with: - waiting to be told that's fine to upload files to archive.org? Can we start? - review new website. New website should be reviewed. https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… phw: This week (2019-09-05): * Handled our "set up new obfs4" bridges campaign * ~40 new bridges so far * Updated bridge setup guide several times and merged pull requests * More work on improving obfs4's flow obfuscation (#30716) * Met with Micah and Sam to discuss progress * Had a chat with Tobias about state of website fingerprinting attacks * Re-compiled and deployed snowflake broker and server (#31454, #31455) * Started working on exposing BridgeDB's metrics for Tor Metrics (#19332) * Filed a ticket to get rid of BridgeDB's chatspeak (#31528) * Started working on a script to extract stable, unallocated obfs4 bridges for manual distribution * Moved forward with our next default bridge at Karlstad University (#31164) * Revised default bridge requirements in our wiki * Interacted with potential new default bridge operators after Roger contacted professors about it * Wrote monthly anti-censorship team report * Wrote a BridgeDB patch to remove frontdesk(a)tp.o email (#28533) Next week: * Expose BridgeDB metrics for Tor Metrics (#19332) * Send a batch of private obfs4 bridges to NGO for manual distribution Help with: * Review https://trac.torproject.org/projects/tor/ticket/28533 Gaba: (updated September 5th) Last week (): * This week (planned): * ahf Last week: - Worked on #28930 This week: - Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info. - Continued to work on a tool to convert Trac tickets into Gitlab tickets. cecylia (cohosh): last updated 2019-09-05 Last week (holiday on Monday): - spent some time debugging snowflake broker issues (#31425) - debugged pion/webrtc problems (#28942) - looked at gettor status report from hiro - read phw's work on sharknado This week: - make a patch for the proxy---broker communication (#29207) - get fixes upstreamed to pion/webrtc (#28942) - snowflake dogfood - continue work on sequencing layer (#29206) - revisit snowflake reachability scripts, check status of tests, and enhance (#30368) - review of gettor metrics work (https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor…) - review #28533 Help with: - review of progress on sequencing layer (#29206) - the snowflake broker machine is acting up and i don't think it's related to the broker software (#31425) 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-09-05 Last week: - with cohosh, worked on the pion-webrtc build of Tor Browser, got a working windows build for the first time (#28942) - Turbo Tunnel prototyping - Metrics Timeline maintenance Next week: - review Snowflake sequencing layer (#29206) - archive test pion builds from (#28942) - Turbo Tunnel prototyping Help with: - redeploy meek-azure bridge for Go net/http DoS vulnerability (#31455) - needs attention from inf0 at Team Cymru (dcf has sent email)

1 0

Communications Report: July & August
by Stephanie A. Whited 05 Sep '19

05 Sep '19

Hello Tor, We launched two major campaigns in the past 2 months: the Tor Bug Smash and the Run Tor Bridges campaigns. Thanks to everyone who has helped out. The bridge campaign is running through September -- you can share your support of bridges and encourage others to set them up with #RunTorBridges[1]. In July, we prepared materials for two big events in August: DEF CON and CCCamp. Our first booth at DEF CON was a success, and we'd like to thank seeess for creating an onion badge for us[2]. Roger had a talk in the main track on anti-censorship, and I took part in a privacy related panel in the Blockchain Village. Momentum with the cryptocurrency community is still building, and a podcast with multiple Tor people for a popular magazine is in the works. In August, I joined the Tor "money machine" at a training in DC, and we are working on new materials to use for fundraising based around what we learned. We've also begun prep for our EOY fundraising campaign starting soon. July and August in links and stats: == JULY == Blog posts https://blog.torproject.org/reflections-our-stockholm-all-hands Twitter New followers: 3,455 Top tweets https://twitter.com/torproject/status/1146128242979614720 https://twitter.com/torproject/status/1146442235032014848 https://twitter.com/torproject/status/1154100944394694656 LinkedIn https://linkedin.com/company/tor-project/ New followers: 114 Facebook https://facebook.com/torproject New followers: 547 Instagram https://instagram.com/torproject New followers: 361 Mastodon https://mastodon.social/@torproject New followers: 260 Newsletter https://newsletter.torproject.org/archive/2019-07-29-defending-the-open-int… Notable press https://www.wired.co.uk/article/best-privacy-browsers-and-chrome-alternativ… == AUGUST == Blog posts https://blog.torproject.org/run-tor-bridges-defend-open-internet https://blog.torproject.org/join-tors-docshackathon-next-week https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs Twitter New followers: 3,159 Top tweets https://twitter.com/torproject/status/1166048980930879491 https://twitter.com/torproject/status/1156910864391262208 https://twitter.com/torproject/status/1161636416914362369 LinkedIn New followers: 146 Facebook New followers: 603 Instagram New followers: 739 Mastodon New followers: 670 Newsletter https://newsletter.torproject.org/archive/2019-08-30-docsHackathon-run-a-to… Notable press https://www.lifehacker.com.au/2019/08/the-best-privacy-and-security-focused… [1] https://twitter.com/hashtag/RunTorBridges?src=hashtag_click [2] https://twitter.com/see_ess/status/1155223668336861189 o/ -Steph -- 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project