- tor-project - lists.torproject.org

Anti-censorship meeting notes, 21 May 2020
by Philipp Winter 21 May '20

21 May '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-21-15.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 21st 16:00 UTC Weekly meetings, every Thursday at 16: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://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep == Announcements == * == Discussion == * Shall we post our monthly report on the blog instead of (or in addition to) the mailing list? == Actions == * == Interesting links == == Reading group == * We will discuss "Conjure: Summoning Proxies from Unused Address Space" on May 28 * https://censorbib.nymity.ch/#Frolov2019b * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-05-21): * Reviewed #27330. * Reviewed and merged #31528. BridgeDB isn't silly anymore. * Wrote a patch for #30586 (onionperf). * Lots of work on wolpertinger. * OONI started using our public endpoint. * Made some API improvements. * Created API endpoint to POST measurements. * Improved authentication thanks to OONI's feedback. * Started working on shim that relays between wolpertinger and bridgestrap. * Filed #34253 and several S30-related tickets. * Set up GetTor email autoresponder test on our monit instance. * Wrote a fix for #34154. * Made some progress on #34260. * Updated BridgeDB translations (not deployed yet though). * Checked in on #33945; looks like BridgeDB's email autoresponder is healthy again. Next week: * Make wolpertinger fetch OONI's test results from S3 bucket. Help with: * #34154 (extend bridgedb's blockedbridges table) * #33945 (fix bridgedb's failed assertion) cecylia (cohosh): last updated 2020-05-21 Last week: - off Monday (public holiday) - worked with HashikD on GSoC tasks - more work on sponsor 28 evaluation - ran a check for STUN servers that support RFC 5780 - started implementing RFC 5780 support for pion/stun (#34129) - some grant writing tasks This week: - Continue work on STUN servers (#34129 and #25591) - More work on reviving the twitter responder in GetTor (#33036, #27330) - look at old GetTor mirrors (#33893) - investigate #33669 - Follow up on discussions of debian obfs4proxy package - translations? Needs help with: - creation of snowflake repo (#34222) from git-admin juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-05-07 Last week: - webext repo versioning / publishing #34140, #34126, #34132, #34127 Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-05-21 Last week: - helped debug Moat in Tails https://lists.torproject.org/pipermail/tbb-dev/2020-May/001093.html - tried NAT discovery STUN server (#34129) Next week: - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: agix:2020-05-21 Last week: - was held up with university stuff Next week: - Continue work on #27984 & submit/test first patch Help with: - thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with: HashikD: 2020-04-18 Last week: - Learning how to compile the WebRTC library from Google source. - Learning the broker API. - Implementing to test the WebRTC API into a test project. - Getting ICE candidates and forming the SDP on the client-side. (Answer) Next week: -Learning how to format the SDP (Serialize) to send it to the broker and Deserialize the SDP offer from the broker to assign it to the local descriptor of peer connection. - Setting up the project. Help with: - SDP serialization .

1 0

Metrics meeting notes, 21st May 2020
by Gaba 21 May '20

21 May '20

Hi! Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 21st: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-21-15.01.html And here is the pad notes: ----------------------------------------------------- Agenda Thursday, May 21st, 15 UTC ----------------------------------------------------- OnionPerf project: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59 Update OnionPerf to TGen 1.0.0 (#33974) karsten emails jnewsome about getting access to a testing VM. requirements are not included in setup.py (#30586) acute writes an update on the ticket. Analyze unusual distribution of time to extend to first hop in circuit (#34257) dennis started looking at the analysis and will look more. karsten tries to get two new hosts in Florida and Amsterdam for comparison. Reduce the number of 50 KiB downloads (#34023) karsten comments on the ticket to say that there were no major concerns at the weekly meeting and that we're doing it. Reduce timeout and stallout values (#34024) karsten updates the ticket to say that we agree that this is an improvement, and we're going to do it. Allow users to select Onion Service version to measure (#33434) asn replied on the ticket. Update metrics-web to only plot "official" data (#33397) Remove existing Tor control log visualizations (#34214) Harmonize TTFB/TTLB definitions with Tor Metrics plots (#34215) Fix message logging and filtering (#29369) leaving this here as something to pick up for writing code. Combine multiple analysis files into single data set (#34191) leaving this here as something to pick up for writing code. Python style anarcat suggested pyflakes3 and black acute suggested pylint and yapf phw and jnewsome suggested flake8 as being used in bridgedb and shadow karsten tries out these tools, and we'll discuss them again next week. Reviews (tag with metrics-team if needs review) karsten adds metrics-team to auto-cc for (new) Metrics/OnionPerf tickets. there are 4 tickets that needs reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

NYC HOPE to nine days
by George 19 May '20

19 May '20

FYI: > > > Greetings, > > While we all want things to go back to normal, the science just doesn't > make that possible. July and August may still seem far away, but there > simply is no way the COVID-19 crisis will be over by then, even in the > best-case scenario. We had planned on waiting until June to make a final > decision, but it's become clear that planning an in-person conference > simply wouldn't be the responsible thing to do. Nothing matters more than > the health and safety of our attendees. Yes, this will be a financial > kick in the teeth for us. But it's one we'll willingly take as the mere > possibility of putting any of you at risk is unconscionable. > > We want to be clear on one important point. Apart from the obvious > disappointment of not being able to host this historic event at a new > venue we were so looking forward to, we want everyone to come out of this > not feeling dissatisfaction beyond that. More on that later. > > This is what we're now looking at: > > We are NOT canceling HOPE. Instead, we are changing what this year's HOPE > will be. > > HOPE 2020 will now be a NINE DAY EVENT, beginning on Saturday, July 25th > and running until Sunday, August 2nd, 2020. Why did we add an entire week? > Because we want some good to come out of this and we believe our community > is in a position to do just that. We all know what we WON'T have without a > physical conference, but let's now focus on what we CAN have with some > imagination and collaboration. That's what the hacker community is all about. > > We intend to have around the same number of talks as we normally do, but > spread out over a much longer period and available for viewing on a high > capacity stream. Those of you who bought tickets will have exclusive access > to the presenters so you can ask questions, participate in workshops, and > interact with other conference attendees. In addition, you will also > receive a conference t-shirt and badge that won't ever be made available to > anyone else. > > We plan on having NINE keynote speakers, again with exclusive Q&A access > for our attendees. > > Participation in HOPE will no longer be bound by visas and worries of arrest > by certain controversial types. So expect a dynamic and varied cast of > characters. It wouldn't be HOPE without that, but now we can REALLY remove > some barriers. > > In addition to ongoing talks and panels, we'll also have workshops for the > duration of the nine day event. Expect everything from lockpicking to > soldering instruction to our infamous ham radio exams. > > For the overnight hours, we're planning on having concerts, DJs, and other > fun stuff. HOPE will remain a 24 hour event, but for nine days! > > All of this has been - and will continue to be - a daunting task. The > COVID-19 pandemic has affected all of us in varying ways. The continued > survival of 2600 was quickly put into doubt as our distributors stopped > paying us, bookstores with our issues in them shut down, and new issues > were left in loading zones. We've lost more than half a year's income at > last count and have had to stop getting paid in order to continue to > survive. Making this year's HOPE a success is really the only way we can > come through this. > > As mentioned above, we don't want anyone to feel extra unhappy because of > this. If you want a refund, we will give you one. But with all of the > losses we've already suffered, we won't be able to continue existing if we > have to issue very many of those. That's why we're hoping we can put > together the best event possible and make this the highlight of our summer > despite all that's happened. > > We are in the process of accepting talk and workshop proposals that have > already been submitted. We will be providing technical support so that > presenters will be able to participate smoothly in a virtual environment. > We are now opening up the submission process to include many more > participants from all around the globe, something we never really had the > ability to do before. We hope to have talks, workshops, and musical > presentations from a truly international community, no longer bound by a > physical presence. > > While we have a dedicated team of volunteers already working on making this > happen, we can definitely use many more, especially as the event draws > closer and becomes bigger. Email volunteers(a)hope.net and let us know how > you think you can help. We're looking for people with experience setting up > and producing live online broadcasts. We are also looking for emcees, > moderators for online forums, and people to fulfill other behind-the-scenes > roles. > > If we get through all of this, we fully intend to hold a physical HOPE in > 2021 (the first odd-year HOPE since 1997). This will also enable us to > continue publishing once bookstores start opening again. All of this depends > on our hacker spirit getting us through the toughest times we ever could > have imagined. And if you share our enthusiasm over what this new incarnation > of HOPE will mean, this summer will indeed be one to look forward to. > > Stay safe. > > The HOPE Staff > _______________________________________________ > hope-announce mailing list -- hope-announce(a)lists.2600.com > To unsubscribe send an email to hope-announce-leave(a)lists.2600.com >

1 0

May 18th Meeting Notes for SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements
by Gaba 18 May '20

18 May '20

Hi! We are meeting every Monday at 18UTC via voice in a BBB room to coordinate the work related to Sponsor 58, where we are completing the migration of Tor Browser for Android from Fennec to Fenix. You can read more about it at Parent ticket: https://trac.torproject.org/projects/tor/ticket/33664 Wiki page: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 If you want to participate in this meetings please send us a message about how to join. The pad we are using is: https://pad.riseup.net/p/_kbebKhZvNcUuqxQL5NV And here are the pad's notes: NEXT MEETING: MAY 25TH AT 18UTC IN BBB Reminder: please own a ticket when you start working on it. Agenda Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… (any block from last week review, reviews not assigned yet) -> #27105 and #30832 not ready yet but geko will start reviewing it. -> #33932 and #34013 will be taken by ahf. Look at what people need help with. Status updates: GeKo: Last week: - finished all of the toolchain migration for projects already in tor-browser-build and addressed first review comments) (#34187, #33626, #33973, #33564, #33561, #33563, #33558, #33559) - made progress on review of acat's rebase work (#33533) - looked a bit over dependencies we want to keep/rip out (#33939) This week: - wire up geckoview into fenix - update android-components build patch and wire custom one into fenix as well - finish review of acat's rebase work (#33533) Blocked on decision for #33939 acat: Last week: - #30832: Fix tor-browser tbb-tests - Tested fix for https://github.com/EFForg/https-everywhere/issues/19102 - Revised and landed dns leak uplift followup https://bugzilla.mozilla.org/show_bug.cgi?id=1636411 - #34196: Update site info URL with the onion name - Reviews: Bug 34206: Tor Launcher button labels are missing (Firefox 76) Bug 34209: about:tor and about:tbupdate fail to load in debug build of Tor Browser Bug 34164: Tor Launcher hangs with 33533+5 branch Not blocked This week: - Fix intermittent test failure for https://bugzilla.mozilla.org/show_bug.cgi?id=1636411. - Try to run some tor-browser tests in try. - #30832 followup (tbb-testsuite). Alex: Week of 11/05 actually: - DNS proposal and changes being discussed on tor-dev(a)lists.torproject.org. - Sent revised patches for TROVE-2020-001 with Taylor's suggestions included. - Got OnionBrowser to build and reproduced the iOS Tor 0.4.2+ issue. - Done with emails from April. - Review of various patches for tor.git. - Managed to reproducibly compile GeKo's geckoview patches on two devices. - Code review of GeKo's geckoview patches to Tor Browser (#33626, #33973, #33113). Not blocked on anything. Week of 18/05 planned: - Write documentation for `Onion-Location:` for nginx. - Continue to work with the browser folks. - Hopefully nail down the iOS bug. - Thursday and/or Friday is a public holiday here in DK that I might make use of. Mike: Last week - 5/11: - Got TBB building in Ubuntu 'multipass' vms (https://multipass.run/) Is pretty straight-forward - Congestion control, FlashFlow proposal, TorFlow #33871 help, org discussion email - Got diffs of gecko-dev for proxy audit Blocking: - This week - 5/18: - gecko-dev proxy audit sysrqb: Last week - 11 May: Mostly reviewed patches and preparation for 9.5a13 Began #33939 This week: Finish #33939 Release prep for 9.5a13 and reviewing #31918 MAY 11TH Reminder: - please own a ticket when you start working on it. Agenda - Tickets for AHF - 33973 and 33626 - O2.2 with geko - Review ux-team tickets and set timelines -> #33658 is the first issue to solve in June https://trac.torproject.org/projects/tor/query?cc=~&keywords=~ux-team&spons… - Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… only #30832 needs a review - #33534 is still owned by pospeselr Status Updates: Name: What did you do last week? Anything anybody is block on? What is the plan for this week? Alex: Last week: - Got Fenix compiled on desktop and laptop with Android dev environment. - Moved the build to remote build host. - Started looking at the TB tickets we apply on top of Firefox. - Not blocked on anything, but I am interested in which tickets we should allocate to me. This week: - Look into the build-system patches from GeKo. Test and review. sysrqb: Last week: Tor Browser releases (Some) S58 ticket triage Make progress on setting up replacement Nightly build machine Blocked: No. This week: #33939 - Decide which components of Fenix to rip out, disable, or use Catch up on status of tickets GeKo: Last week: - worked on lots of toolchain tickets and put a bunch of them into review (#33557, #33561, #33626, #33760, #33833, #33973, #34011, #34012, #34013, #34014, testing currently #33801 and figuring out issues in #33563) - I started to look at writing the script for toolchain changes (#34108) - I started to look into #33939 to unblock me but I can't make a decision here alone - I looked into glueing mozilla-beta into fenix/android-components - I looked into fallout from rebasing to mozilla-beta (#34145) and worked around it - review of acat's rebased patches (#33533) Blocked: - Still on a decision for #33939 This week: - finishing #33801 and #33563 - trying to finish review of acat's rebased patches (#33533) - glueing the different components together - setting up missing projects in tor-browser-build (likely android-components) at least acat: Last week: #31918: Rebase and squash mobile and desktop patches #33533: Rebase Tor Browser patches to 77 beta #34125: Fix torbutton proxy api due to change in Firefox 77. #33962: Uplift patch for 5741 (dns leak protection) Started working on #27105: Fix Tor Browser testsuite Blocked: Not blocked, but not sure whether working on #27105 (Fix Tor Browser testsuite) is the right priority, or I should switch to something else. Next week: #27105: Fix Tor Browser testsuite -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network meeting notes, 18 May 2020
by Gaba 18 May '20

18 May '20

Hi! Network Meetings are happening every Monday at 17UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 18th: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-18-17.00.html Pad for 2020: https://pad.riseup.net/p/tor-netteam-2020.1-keep And here is the pad notes for today: == Network meeting pad! == Next team meeting is at Monday 25 May 1700 UTC on #tor-meeting on OFTC. May Schedule: * Monday 11 May 17:00 UTC * Monday 18 May 17:00 UTC * Monday 25 May 17:00 UTC Welcome to our meeting! We meet each month at: Mondays at 1700 UTC 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.) 23 March: https://lists.torproject.org/pipermail/tor-project/2020-April/002804.html 1 April - 4 May: we skipped meetings while transitioning TPI == Stuff to do every week == Let's check and update our roadmap: What's done, and what's coming up? Any change? All the trac tickets for the roadmap are in the team's page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam S27 - Asn & Dgoulet - ends at the end of May S28 & S30 - Continue after October - Ahf S55 - Nickm S69 - Nickm - ends at the end of May Non sponsor stuff DoS defenses = Dgoulet + Asn Library Size reduction = Ahf + Dgoulet sbws = Ahf + Juga 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… Go over our 0.4.3 status page at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… . (If maint-0.4.3 were released as stable tomorrow, what would we regret?) == 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. * Check other's people call for help in their entries. Volunteers need help. Please help them when you are around. Maybe we should have times of day when different people are responders, and expectations of who helps. ------------------------------- ---- 18 May 2020 ------------------------------- == Announcements [please date] == == Discussion [please date] == [18 May] pastly asks: Current plan is that FlashFlow will consist of a program that controls tor clients via the Control Port. Like Simple Bandwidth Scanner and Torflow. Would writing this code in Rust make it non-transitionable? Does the network team know enough Rust? The other idea is Python 3. Is that way better? [resolution: rust isn't a blocker. maybe using stem would be a compelling reason to use python though. the best choice would be to do whatever you think can deliver the better code: "maintainable well-factored rust is much better than undocumented spaghetti python, and vice versa :)" [18 May] nickm asks: anybody able to help with 0.4.4 triage? We need to identify what we're doing between now and the freeze on 15 June. === Active Proposed Policies === * Pull Request Guidelines (stalled) === Design proposals under discussion === 315: require more fields in directory documents (?? [5/18]) 316: flashflow (asn and nickm are reviewing, should schedule discussion with pastly. [5/18]) 317: dns (under discussion on ML [5/18]) 318: limit protovers (nick needs to reply on ML [5/18]) 319: wide everything (nick needs to reply on ML [5/18]) 320: tap out again (nick needs to reply on ML [5/18]) protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18]) == Recommended links == == 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! Nick: Week of 11 May (planned): - Re-review PETS artifacts - Final S55 handover: - Make sure I can repro and experiment with Teor's work on ipv6 probing - 33898 (real_addr) - - merge and review - answer a ton of pending email. - catch up with proposal review - Finalize a bunch of walking onions sub-proposals - get an official location/repo for walking onions proposal. - identify most critical missing pieces of w.o. proposal, and pick them up. Can anybody pick up: - 33850 (log fd issue) Week of 11 May (actual): - merge and review - lots of pending email catch-up - walking onions sub-proposals - walking onions: more family analysis - lots of reading up on S55 stuff - network team idea for next steps - Release 0.4.3.5 as stable! - (much persnoal disorganizatioon) * * this was originally a typo, but I think it gives a fair picture of my mental state (same space here..) Week of 18 May (planned): - 0.4.4 triage - walking onions: try to finish. - s55: review and merge, identify steps to make wip-stuff mergeable. - review and merge in general - keep an eye on blog comments - Reply to prop316 - reply to email about protovers ahf: Week of 4/5 (actual) - Review of some GCC warnings. - Wrapping my head around Browser build-system and Mozilla Fenix. - Mac upgrade to help TGP and to debug iOS/Mac issues. - Got through the emails that was skipped in April. Week of 11/05 planned: - Continue to work with the browser team. - Wrap my head around DNS patches. - Execute next steps on TROVE-2020-001. Week of 11/05 actually: - DNS proposal and changes being discussed on tor-dev(a)lists.torproject.org. - Sent revised patches for TROVE-2020-001 with Taylor's suggestions included. - Got OnionBrowser to build and reproduced the iOS Tor 0.4.2+ issue. - Done with emails from April. - Review of various patches for tor.git. - Managed to reproducibly compile GeKo's geckoview patches on two devices. - Code review of GeKo's geckoview patches to Tor Browser (#33626, #33973, #33113). Week of 18/05 planned: - Write documentation for `Onion-Location:` for nginx. - Continue to work with the browser folks. - Hopefully nail down the iOS bug. - Thursday and/or Friday is a public holiday here in DK that I might make use of. (please take it) asn: Week of 11/05 (planned): - Work on PoW funding proposal - Email backlog Week of 04/05 (actual): - PoW proposal done. - Start reviewing flashflow proposal. - More onion services stuff - Did OTF learning lab meeting - Did HTTPS-E meeting. Week of 18/05 (planned): - Still more reviewing flashflow. - Still more emails. - Still more reviews. - Still more PoW. jnewsome: Week of May 4 (actual): - Some LD_PRELOAD behavior investigation to guide shadow-Phantom design decisions - Added more tests covering next-to-be-implemented shadow-Phantom syscalls - Mentored/reviewed a volunteer PR - Kickoff OnionPerf meeting Week of May 11 (planned): - Start digging into OnionPerf - Start familiarizing myself with Shadow *usage* for Tor simulations - tor-project@ Shadow update email Week of May 11 (actual): - Worked on improving Shadow logging framework - Helped volunteer get their PR to improve tests into mergeable shape and merged - Started poking at OnionPerf Week of May 18 (planned): - tor-project@ shadow update email - finish logging improvement PR - More digging into OnionPerf. #33974: update to tgen 1.0 \o/ pastly: Week of 18 May (planned): - Finish bones of external FlashFlow repo (python?) to control tor clients that perform FF measurements - Finish bones of little-t tor changes s.t. measurement can be performed - Discuss FlashFlow with network team devs as they have questions -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Metrics meeting notes, 14 May 2020
by Gaba 14 May '20

14 May '20

Hi! Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 14th: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-14-15.01.html And here is the pad notes: ----------------------------------------------------- Agenda Thursday, May 14th, 15 UTC ----------------------------------------------------- Stop generating .tpf files (#34141) Add CSV file export of graphed data (#33258) Record download times of smaller file sizes from partial completion times (#26673) Reminder: We are tracking Onionperf work at https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59 cheers, gaba -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Anti-censorship meeting notes, 14 May 2020
by Philipp Winter 14 May '20

14 May '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-14-16.00.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 14th 16:00 UTC Weekly meetings, every Thursday at 16: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://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * Next planning session: last week of April * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep ------------------------- --- May 14th 2020 -- ------------------------- == Announcements == * Set up monit instance on phw's personal VPS. It's now sending outage alerts to anti-censorship-alerts(a)lists.tp.o * Monitoring targets available at: https://gitlab.torproject.org/torproject/anti-censorship/monit-configuration * We recently got a batch of censorship measurements from our friends at ICLab. Anyone interested in analysing it? Phw tool a brief look and has some Python code to get started. == Discussion == * Roger's mail about the overlap between BridgeDB and GetTor and how maybe they should merge https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000097… * Run a call for testing for Snowflake * before or after the stable release? before: we want to ramp up users so we know we can handle a stable release * use cases? * we want to involve/share with orgas in global south. There is not strict censorship in Colombia nor Chile, but snowflake can help users who don't want to disclose the fact that they are using Tor to their ISP. So may work. * Do we want users to do specific tasks like visiting a website or watching a video? Do we want users to use snowflake for a period of time and report back with feedback? What is more useful? * Are we looking for breakage? are we looking for perceived performance? * lists? * tor-qa * tor-ux * tor-project but with **bolds** on advertising that is an alpha version * S30 UX work this week == Actions == * == Interesting links == * https://github.com/greatfire/envoy * The GreatFire folks developed a library that helps make Android apps resistant to censorship. * From what I understand from looking at the sample patches, it provides easy-to-use hooks to do domain fronting and HTTP proxying, generalizing their project FreeBrowser. == Reading group == * We will discuss "Salmon: Robust Proxy Distribution for Censorship Circumvention" on May 14 * https://censorbib.nymity.ch/#Douglas2016a * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? Roger's notes for Salmon design questions: https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000100… == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-05-14): * Set up monit on my VPS and configured it to send outage alerts to our list. * https://gitlab.torproject.org/torproject/anti-censorship/monit-configuration * Tests everything except BridgeDB's and GetTor's autoresponders. * Some interaction with OONI to move forward with BridgeDB feedback loop. * Syncing MetaDB is too involved; will download raw measurements from S3. * Reviewed onionperf Python 3 port. * Sponsor 30 roadmap maintenance. * Reviewed #33835. * Filed #34154 to extend BridgeDB's BlockedBridges SQLite table. * Attended DARPA PI meeting (RACE) remotely. * Deployed #33945 test branch on BridgeDB. No sirens so far. * Quite a bit of progress with wolpertinger. * API end point live at https://bridges.torproject.org/wolpertinger/fetch * Summarised future plans with BridgeDB and posted them to anti-censorship team list. * Updated our docker bridge setup guide after a user in #tor pointed out an issue. Next week: * Help with: * Let me know your smart thoughts on BridgeDB's future: * https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000096… * #34212 Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective cecylia (cohosh): last updated 2020-05-14 Last week: - GSoC things - work on broker documentation (#34198), snowbox, snowflake READMEs - read dcf's plans for multiplexing (#25723) - started on using STUN servers for NAT type discovery (#34129) - writing up a funding proposal for GetTor - so many sponsor 28 meetings (all day Monday, Tuesday, part of Wednesday) - created ticket to make new snowflake repo for Hashik's GSoC work (#34222) This week: - Continue work on STUN servers (#34129 and #25591) - More work on reviving the twitter responder in GetTor (#33036, #27330) - look at old GetTor mirrors (#33893) - investigate #33669 - Follow up on discussions of debian obfs4proxy package - translations? Needs help with: - review of GetTor twitter fixes (#27330) - creation of snowflake repo (#34222) from git-admin juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-05-07 Last week: - webext repo versioning / publishing #34140, #34126, #34132, #34127 Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-05-14 Last week: - reviewed fix for Chrome proxy hang (#31278) Next week: - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: agix:2020-05-14 Last week: - Started work on #27984 Next week: - Submit a fix for #27984 Help with: - Review of #31528 catalyst: 2020-04-16 last week: - more work on #5304 (PT outbound bind address) - started looking at #29128 (assemble bridge line) this week: - more background research and work on s28/s30 tickets thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with:

1 0

Tails report for April 2020
by sajolida 12 May '20

12 May '20

Releases ======== * Tails 4.5 was released on April 7: https://tails.boum.org/news/version_4.5 * Tails 4.6 was released on May 5: https://tails.boum.org/news/version_4.6 * Tails 4.7 is scheduled for June 2. The following changes were introduced in Tails 4.5: - Tails now starts on computers with Secure Boot enabled. - Update *Tor Browser* to 9.0.9. This update fixes several vulnerabilities in *Firefox*, including some critical ones. Documentation and website ========================= Installation instructions ------------------------- - Updated our installation instructions to the support of Secure Boot: * On PC: https://tails.boum.org/install/win/usb#start-tails * On Mac: https://tails.boum.org/install/mac/usb#start-tails * When adding boot options: https://tails.boum.org/doc/advanced_topics/boot_options - Added a link to try downloading from another mirror in case the download fails. (#15754) Click on Download USB image and the link below it changes. https://tails.boum.org/install/download - Fixed a buggy content reuse on the cloning instructions for PC and Mac. (#17502) https://tails.boum.org/install/clone https://tails.boum.org/install/mac/clone - Added shortcuts to download for DVDs and virtual machines from install. (#17609) https://tails.boum.org/install/dvd-download https://tails.boum.org/install/vm-download - Added a **Skip download** link on the download only pages. (#17549) https://tails.boum.org/install/download Terminology ----------- - Implemented the terminology *Persistent Storage* consistently in all our documentation. (#8948) https://tails.boum.org/contribute/how/documentation/style_guide#persistent-… https://tails.boum.org/doc/first_steps/persistence - Renamed *Tails Greeter* into *Welcome Screen*. (#15122) https://tails.boum.org/doc/first_steps/welcome_screen Known issues ------------ - Documented that importing OpenPGP public keys using the *Passwords and Keys* utility is broken since Tails 4.0 (October 2019). (#17183) https://tails.boum.org/doc/encryption_and_privacy/gpgapplet/#import - Documented that opening *VeraCrypt* volumes fails if the passphrase is more than 64 characters long. (#17474) https://tails.boum.org/doc/encryption_and_privacy/veracrypt#parameters - Removed warnings about *Electrum* not working in Tails (#17581) User experience =============== - Andrés Fernández Cordón finished the illustrations for the new Home and About pages. https://anhdr.es/ https://tails.boum.org/about/staging/home https://tails.boum.org/about/staging/about sajolida finished writing and testing the written content and most of the responsive web design. - Changed our sidebar to a top bar. (#15112) It has a better contrast for accessibility, prevents right-rail blindess, and is more visible on mobile. Funding ======= - Sent 2 grant applications: * To the OTF Core Infrastructure Fund to improve the user experience of connecting to Tor and using Tails to circumvent censorship. https://tails.boum.org/blueprint/network_connection * To Reset.tech to integrate mobile messaging applications (Signal, Telegram, Wire, Matrix, etc.). - Redesigned our **Donate** button to fit in the top bar, even on mobile. - Added ourselves to a list of non-profits who accept lumens: https://lumenthropy.com/nonprofit-list/ Translations ============ ## All the website - fr: 85% (5541) strings translated, 7% strings fuzzy - es: 49% (3172) strings translated, 7% strings fuzzy - de: 32% (2087) strings translated, 13% strings fuzzy - it: 29% (1878) strings translated, 9% strings fuzzy - fa: 23% (1551) strings translated, 13% strings fuzzy - pt: 22% (1479) strings translated, 9% strings fuzzy ## Core pages of the website - fr: 85% (1577) strings translated, 10% strings fuzzy - es: 83% (1538) strings translated, 10% strings fuzzy - it: 55% (1023) strings translated, 21% strings fuzzy - de: 55% (1012) strings translated, 22% strings fuzzy - pt: 41% (772) strings translated, 17% strings fuzzy - fa: 28% (524) strings translated, 19% strings fuzzy ## Core pages of the website for languages not activated on the website yet - zh_TW: 28% (427) strings translated, 12% strings fuzzy - zh: 14% (225) strings translated, 6% strings fuzzy - ru: 10% (160) strings translated, 5% strings fuzzy - pl: 8% (133) strings translated, 4% strings fuzzy - tr: 8% (133) strings translated, 4% strings fuzzy - ar: 7% (119) strings translated, 5% strings fuzzy - ca: 7% (115) strings translated, 5% strings fuzzy - id: 5% (91) strings translated, 2% strings fuzzy - sr_Latn: 4% (62) strings translated, 1% strings fuzzy Metrics ======= * Tails has been started more than 936 560 times this month. This makes 31 219 boots a day on average. That's 8.7% more than in March and the biggest increase in usage since 2015. It's most likely due to the COVID-19 quarantine and people staying at home but it might also be a good sign from the support of Secure Boot and an easier adoption by new users. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0

New Contributor
by Mruga Shah 11 May '20

11 May '20

Hi All, I am a Computer Science student at Drexel University and have taken up a class that teaches us about Open Source software world. As a part of that class, we have to contribute to an open source project and I was really interested in working with your project team. I am writing this email to get myself introduced to the team and get in touch so as to get an idea of how I can contribute to the project. Thank you, With Regards Mruga Shah

2 1

minutes from the sysadmin meeting
by Antoine Beaupré 11 May '20

11 May '20

# Roll call: who's there and emergencies anarcat and hiro, tons of emergencies: * trac spam (#34175) * ganeti crash (#34185) # Part-time work schedule We're splitting the week in two, so far anarcat takes the beginning and hiro the end, for now. This might vary from one week to the next. The handover, or "change of guard" happens during our weekly mumble meeting, which has been moved to 1400UTC, on Wednesdays. # Roadmap review We reviewed the sysadmin roadmap at: <https://trac.torproject.org/projects/tor/wiki/org/teams/SysadminTeam> Since we're in reduced capacity, the following things were removed from the roadmap: * website migration to lektor (#33115) -- should be handled by the "web team" * solr search (#33106) -- same, although it does need support from the sysadmin team, we don't have enough cycles for this * puppetize nagios (#32901) -- part of the installer automation, not enough time * automate installs (#31239) -- same, but moved to october so we can check in progress then The ganeti cluster work got delayed one month, but we have our spare month to cover for that. We'll let anarcat do the install of fsn-node-06 to get that back on track, but hiro will learn how to setup a new node with (hopefully) fsn-node-07 next. The listera retirement (#33276), moly migration (#29974) and cymru hardware setup (#29397) are similarly postponed, but hopefully to june (although this will likely carry over to october, if ever). # Next meeting Change of guard on 1400UTC wednesday May 20th, no minutes. Formal meetings are switched to the first *wednesday* of the month, at 1400. So the next formal meeting will be on Wenesday June 3rd at 1400UTC. # Metrics of the month * hosts in Puppet: 74, LDAP: 78, Prometheus exporters: 120 * number of apache servers monitored: 30, hits per second: 164 * number of nginx servers: 2, hits per second: 2, hit ratio: 0.88 * number of self-hosted nameservers: 6, mail servers: 10 * pending upgrades: 0, reboots: 33 * average load: 0.55, memory available: 358.27 GiB/949.25 GiB, running processes: 383 * bytes sent: 210.09 MB/s, received: 121.47 MB/s * planned buster upgrades completion date: 2020-08-01 Upgrade prediction graph still lives at https://help.torproject.org/tsa/howto/upgrades/ Now also available as the main Grafana dashboard. Head to <https://grafana.torproject.org/>, change the time period to 30 days, and wait a while for results to render. -- Antoine Beaupré torproject.org system administration

1 0