tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

minutes from the sysadmin meeting
by Antoine Beaupré 14 Apr '20

14 Apr '20

Hello everyone! We held our usual meeting a week late in April. But still, here are the minutes, preceeded by a usual, carefully hand-crafted variable header by your favorite editor (the human, not the software). Stay safe, inside, wash your hands, and take care of each other. :) # Roll call: who's there and emergencies anarcat, hiro and weasel are present (gaba late) # Roadmap review We changed our meeting template to just do a live roadmap review from Trac instead of listing all the little details of all the things we did in the last month. The details are in Trac. So we reviewed the roadmap at: <https://trac.torproject.org/projects/tor/wiki/org/teams/SysadminTeam> SVN, Solr got postponed to april. kvm3 wasn't completed either but should be by the end of the week. hopefully kvm4 will be done by the end of the month but is also likely to be postponed. We might need to push on the buster upgrade schedule if we don't want to miss the "pre-LTS" window. We also note that we don't have a good plan for the GitLab deployment, on the infrastructure side of things. We'll need to spend some time to review the infra before anarcat leaves. # Voice meetings Anarcat and hiro have started doing weekly checkups, kind of informally, on the last two mondays, and it was pretty amazing. We didn't want to force a voice meeting on everyone without first checking in, but maybe we could just switch to that model it's mostly just hiro and anarcat every week anyways. The possibilities considered were: 1. we keep this thing where some people checkin by voice every week, but we keep a monthly text meeting 2. we switch everything to voice 3. we end the voice experiment completely and go back to text-monthly-only meetings Anarcat objected to option 3, naturally, and favored 2. Hiro agreed to try, and no one else objected. A little bit of the rationale behind the discussion was discussed in the meeting. IRC has the advantage that people can read logs if they don't come. But we will keep minutes of the monthly meetings even if they are by voice, so people can read those, which is better than reading a backlog, because it's edited (by yours truly). And if people miss the meeting, it's their responsability: there are announcements and multiple reminders before the meeting, and they seem to have little effect on attendance. So meetings are mostly hiro and anarcat, with gaba and weasel sometimes joining in. So it makes little sense to force IRC on those two workers to accomodate people that don't get involved as much. Anarcat also feels the IRC meetings are too slow: this meeting took 30 minutes to evaluate the roadmap, and did not get much done. He estimates this would have taken only 10 minutes by voice and the end result would have been similar, if not better: the tickets would have been updated anyways. So the plan for meetings is to have weekly checkins and a monthly meeting, by voice, on Mumble. * weekly checkins: timeboxed to 15 minutes, with an optional 45 minutes worksession after if needed * monthly meetings: like the current IRC meetings, except by voice. timeboxed to 60 minutes still, replacing the weekly checkin for that week We use Mumble for now, but we could consider other platforms. (Somewhat off-topic: Anarcat wrote a [review of the Mumble UX][] that was somewhat poorly received by the Mumble team, so don't get your hopes up about the Mumble UI improving.) [review of the Mumble UX]: https://anarc.at/blog/2020-04-09-mumble-dreams/ # Other discussions No other discussion was brought up. # Next meeting Next "first monday of the month", which is 2020-05-04 15:00UTC (11:00:00EDT, 17:00CET). # Metrics of the month * hosts in Puppet: 76, LDAP: 80, Prometheus exporters: 123 * number of apache servers monitored: 31, hits per second: 168 * number of nginx servers: 2, hits per second: 2, hit ratio: 0.89 * number of self-hosted nameservers: 6, mail servers: 10 * pending upgrades: 1, reboots: 0 * average load: 1.03, memory available: 322.57 GiB/1017.81 GiB, running processes: 460 * bytes sent: 211.97 MB/s, received: 123.01 MB/s * completion time of stretch major upgrades: 2020-07-16 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

Tor Browser Release meeting this week - Wednesday 15th April @ 18UTC
by Pili Guerra 14 Apr '20

14 Apr '20

Hi everyone, This is your usual reminder of the Tor Browser Release meeting happening this Wednesday 15th April @ 18UTC. We will be discussing the 9.5stable release date this week, among other things :) Thanks, Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

Tor Browser Team Meeting Notes, 06 January 2020
by Matthew Finkel 13 Apr '20

13 Apr '20

Hello everyone, Our first meeting of 2020 was held on 6 January. 2020 will be an exciting year for Tor Browser! We have a busy year ahead of us and we're hitting the ground running. The logs are available at http://meetbot.debian.net/tor-meeting2/2020/tor-meeting2.2020-01-06-18.29.l… Summary: 1) Discussed how we can move forward with implementing per-site settings 2) Discussed how long it will take before we start writing 2020 instead of 2019 on documents 3) Discussed future plans for Namecoin integration (adding more platforms, timeline for adding in Alpha, etc.) With regard to (3), Namecoin is currently available in Tor Browser Nightly builds on Gnu/Linux 64-bit. Please provide feedback is you try it! ================================ Week of January 6, 2020 Discussion: How long will we be dating things 2019 when signing documents? Will this decade be as roaring as the 1900s version? - if it will be, is that a good thing pospeselr: Last weeks: - #31855 (remove end of year fundraising campaign) - small progress on Mozilla 1601040 and 1594455 This week: - continue baby-sitting above Mozilla tickets - #30570 (implement per-site security settings) - what do folks think about the discussion in the ticket? - tldr: looks like to build something consistent with the design laid out there requires a lot of work basically reimplementing what NoScript does, or heavily refactoring/redesigning NoScript's internals :/ - look into umatrix extension as an alternative to NoScript - put umatrix findings in a doc or on the ticket mcs and brade: Last few weeks: - #32636 (Clean up locales shipped with Tor Launcher). - Code review for #31855 (Remove EOY Campaign from about:tor). - Sponsor 27 work: - #19757 (permanent storage of client auth keys and associated management UI). - Time off for Christmas and end of year. This week/upcoming: - #19757 (permanent storage of client auth keys and associated management UI). boklm: Last few weeks: - Made patches for: - #32768 (Create a build-infos.json file containing firefox platform_version and buildid) - #32805 (Make creation of downloads.json optional) - Worked on #25102 which is almost finished (Add script to sign nightly build mar files, generate update-responses xml and publish the new version) - Looked at blog comments This week: - Help with publishing new releases - Finish work on #25102 (script to sign nightly build mar files, generate update-responses xml and publish the new version) and remaining things for #18867 (Ship auto-updates for Tor Browser nightly channel) - Try #32768 (Make script to optimize upload and download of Tor Browser releases) - Look at macOS signing situation sysrqb: Last few weeks: Mostly distracted by holidays, family, etc. Preparing releases for this week This week: Releases Reviewing roadmap for Q1 2020 Finishing remaining items we didn't finish last year Jeremy Rand: Last few weeks: #30558 is merged, yay. Attended 36C3; gave a talk and workshop; ran into boklm there :) This week: Ponder next steps for Namecoin now that the initial merge to Linux Nightly has happened. ================================ - Matt

1 11

Anti-censorship team monthly report: March 2020
by Philipp Winter 13 Apr '20

13 Apr '20

Hi friends, Here's what the anti-censorship team has accomplished in March 2020: Snowflake ========= * Released version 0.2.2 of the Snowflake WebExtension: <https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/> <https://chrome.google.com/webstore/detail/snowflake/mafpmfcccpbjnhfhjnllmma…> * Posted a third draft of Snowflake–Turbo Tunnel packages, allowing one Snowflake proxy to be shared among many upstream connections <https://lists.torproject.org/pipermail/anti-censorship-team/2020-March/0000…> * Made some progress on debugging and detecting Snowflake proxy issues: <https://bugs.torproject.org/33666> <https://bugs.torproject.org/32938> * Added module support to make builds and versioning easier: <https://bugs.torproject.org/33330> * Updated versions of Snowflake and pion-webrtc in Tor Browser: <https://bugs.torproject.org/33578> <https://bugs.torproject.org/33576> * Removed unused server-webrtc code: <https://bugs.torproject.org/33636> * Updated Snowflake license: <https://bugs.torproject.org/33637> * Investigated the work for making a Debian package of Snowflake: <https://bugs.torproject.org/19409> BridgeDB ======== * We added instructions to BridgeDB explaining how to add bridges on mobile platforms: <https://bugs.torproject.org/30317> * Worked with the Metrics Team to add a "bridge distribution mechanism" field to Relay Search, allowing bridge operators to see how their bridge is distributed: <https://bugs.torproject.org/33008> * Re-determined the success rate of both users and (what we believe to be) bots in how well they solve our newly-created BridgeDB CAPTCHAs: <https://bugs.torproject.org/24607#comment:17> * Made progress on having BridgeDB report internal metrics: <https://bugs.torproject.org/31422> * Debugged an issue in BridgeDB's deployment scripts: <https://bugs.torproject.org/33709> * Merged a patch (thanks to agix!) that makes BridgeDB use a CSPRNG when selecting cached CAPTCHAs: <https://bugs.torproject.org/31967> * Noticed that BridgeDB wouldn't allow bridges to change their distribution mechanism; i.e., if a bridge is first assigned to the HTTP mechanism, it wasn't able to change this by setting its BridgeDistribution config option. Implemented a fix for this issue: <https://bugs.torproject.org/33631> GetTor ====== * Patched updated procedure for Gitlab provider: <https://bugs.torproject.org/33034> * Make sure GetTor always responds to (malformed) emails too: <https://bugs.torproject.org/33543> * Overhaul of GetTor help and links message bodies: <https://bugs.torproject.org/23226> * Deployed fix for ignoring quoted messages in GetTor: <https://bugs.torproject.org/23225> Obfs4 ===== * Obfs4's extra25519 dependency changed, which breaks versioning-agnostic builds but as long as one is using Go modules (like Tor Browser does), it still works: <https://bugs.torproject.org/33464> * Merged a patch (thanks to thymbahutymba!) that makes our obfs4 docker image support docker-compose. This simplifies the deployment process. Miscellaneous ============= * Filed a ticket to get our noisebridge01 default bridge removed from Tor Browser because it no longer has a maintainer: <https://bugs.torproject.org/13727> * Worked with prospective GSoC students on their proposals. * Finished writing our NSF TTP grant. * We let bridge operators of soon-to-be-obsolete versions know that it's time to upgrade: <https://bugs.torproject.org/32672>

1 0

Tails report for March 2020
by intrigeri 12 Apr '20

12 Apr '20

Hi, here is the Tails report for last month: https://tails.boum.org/news/report_2020_03/ For your convenience, I'm attaching a simplified version of that web page. Cheers!

1 0

Notes from Vegas Meeting APRIL 9 2020
by Erin Wyatt 10 Apr '20

10 Apr '20

Vegas Team Meeting Notes April 9 2020 + GENERAL NOTES Georg 1. Network health work (sbws, reacting to issues with bandwith authorities) 2. More work on the licensing/copyright issue for TPI folks 3. Planning for the coming weeks and months Antoine 1. migrated trac/troodi, forrestii/fpcentral to the new ganeti cluster 2. tweaked monitoring for the ganeti cluster so we see total memory usage, opened #33810 to followup on more monitoring work 3. established roadmap for the CRM machine migration with hiro, #32198 4. *finally*, chiwui retired (our last "jessie"/LTS machine) #29399 5. routine (reboots, patch review, email aliases, pgp key updates Steph 1. Promoting Stellar org XLM match 2. Preparing for webinar next week 3. OTF learning lab reviewing 4. Media inquiries 5. Working on Community Portal Sarah 1. Prep for Monday's funder webinar. We currently have 12 attendees. 2. Received a total of $5,300 from Stellar campaign so far. $500 (so far) of that will be matched at the end of April. 3. Attending webinars about fundraising in this crazy time. Gus 1. Reviewing DocsHackathon pull requests. 2. Schedule online session "Tor UX Feedback, Challenges, and Lessons Learned from At-risk user" with a partner in Uganda. 3. Contacted training partners in global south to check how they're doing on this crisis. 4. Updated Tor people page with latest membership audit. 5. Answering Outreachy candidates. 6. Working on Community portal public launch. Alex: 1. Team seems to be doing well. 2. Roadmap meeting went well. 3. Back at doing regular Gitlab status meetings. 4. Ongoing development: working on Windows things this week. Erin: 1. HR/Ops stuff Charly 1. Continuing to write various non-technical documents 2. Sent Isa a draft for Vegas meeting format based on team feedback and hers 3. Isa stuff...calendar, reminders, etc... 4. Finished draft for syncing NextCloud calendars to Thunderbird. https://nc.torproject.net/f/28943 \o/ Pili 1. S27 end of month and work completion reports 2. Research on certificate options for Onion services 3. GSoC and Outreachy wrangling 4. Preparing for public launch of Community Portal week after next 5. Kicking off S58 6. Working a checklist for what needs to be done when releasing new features in Tor Browser. 7. Usual trac triage, mailing list moderation and general admin Gaba 1. Roadmap for teams 2. S30 Q2 report 3. HS DoS defenses proposal meeting with funder 4. Gitlab migration gets weekly meetings now Philipp 1. Worked with OTF applicants to get them a letter of support from Tor 2. Made good progress on sponsor 30; in particular creating feedback loop between BridgeDB and OONI 3. Reviewed Tor safety board submission 4. Got in touch with noisebridge person, and we may still have a new noisebridge default bridge 5. More sponsor 30 business as usual Antonela 1. Regular work with s9, s30 and planning s58 2. Working on finishing OnionBrowser UI/UX review to share with Guardian 3. Moving OTF learning lab work forward 4. Working on community.torproject.org final release 5. Waiting for TB 9.5a11 release Isabela 1. Organized documents for Board meeting and did Board meeting on wednesday 2. Working on the presentation for foundations on monday 3. Having meetings w/ sponsors and major donors Nick: 1. working on walking onions, reviews, etc 2. need to help pick outreachy/gsoc applicants by end of next week 3. likely next tor release (0.4.3.4-rc) on Friday. Or Monday. Mike: 1. Working on HS DoS proposal 2. Working on congestion control trajectory mail Karsten: 1. About to update user number estimates (#18167, #18203).

1 0

Anti-censorship meeting notes, 09 Apr 2020
by Philipp Winter 09 Apr '20

09 Apr '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-04-09-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday April 9th 18:00 UTC Weekly meetings, every Thursday at 18: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 ------------------------- --- April 9th 2020 -- ------------------------- == Announcements == * == Discussion == * == Actions == * Please jot down your March 2020 highlights for our monthly team report * https://pad.riseup.net/p/GDSSo-bqhi_dE1oJENyP == Interesting links == * == Reading group == * We will discuss "SymTCP: Eluding Stateful Deep Packet Inspectionwith Automated Discrepancy Discovery" on April 16 * https://censorbib.nymity.ch/#Wang2020a * 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 (related to anti-censorship work). Help with: - Something you may need help with. phw: This week (2020-04-09): * Made sure that my feedback was still covered in catalyst's rebase of #5304. * Left some feedback in #10831. * Found a new maintainer of a next default bridge in noisebridge. * Finally wrapped up #13727 now that noisebridge01 is no longer in Tor Browser. * Wrapped up #29686 and #30941. * Filed #33835. * Reviewed Tor Research Safety Board submission. * Organised letter of support for an OTF application that seeks to distribute bridges in Turkey. * Made good progress on #32740. Next week: * Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones * Make BridgeDB report internal metrics (#31422) * Will have to tackle #32740 (Implement a feedback loop between BridgeDB and OONI) Help with: * Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective cecylia (cohosh): last updated 2020-04-09 Last week: - diagnosed proxy issues (#33666) - some grant submission things - started looking into building a test suite for NAT topologies (#25595) - investigated setting up a TURN server (#25596) - gave feedback on #32740 - team retrospective - popets things (paper reviews, artifact review) - sent an email to the pion peeps about testing NAT topologies (#25595) This week: - Resume obfs4 tests (#31701, #32657) - see if i can help push snowflake for android along (#28672) - set up some kind of NAT topology testing suite (#25595) - look into setting up a TURN server (#25596) - take a look at reviving the twitter responder in GetTor (#33036) - review GSoC proposals Needs help with: juggy : This week: - Tried to study Moat to implement audio captchas Next week: - Implement audio captchas in moat - Keep studying BridgeDB to write architectural overview Help with: - Question about current Moat implementation - it seems to be using XUL, which is deprecated by Firefox if I'm not wrong. I saw a thread in trac discussing reimplementing it with the newer Web Extensions API (but that was years ago)- is that still going on? arlolra: 2020-03-26 Last week: - merged #33665 Next week: - maybe the proxy parts of #19026 - start on #31201 Help with: - review of #19026 but also answer the question there dcf: 2020-04-09 Last week: - worked on branches for snowflake turbotunnel merge (#33745) - helped test snowflake proxy failures (#33666) - removed uniuri dependency from snowflake (#33800) Next week: - branches for snowflake turbotunnel merge (#33745) - share access to the snowflake broker CDN configuration (#30510) Help with: cjb: 2020-04-09 Last week: - gonna be afk with kids Next week: Help with: antonela: 2020-03-26 - working with Babatunde's interviews (OTF Fellowship) from Nigeria and Cameroon. Shared preliminar notes with Tunde and Nah (#32811) - started to work on this user research document, we still stick to the plan of running it during April (#31870) Help with: - nothing yet :) agix:2020-04-09 Last week: - Worked on #19997, but the issue seems to be in check.torproject - Worked on #33835, patch needs a few more tests before submission Next week: - Check out check.torproject's code base Help with: - catalyst: 2020-04-09 last week: - network team roadmapping and estimating s28/s30 tickets this week: - looking into how best to coordinate work on reachability testing (thanks, teor) 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: Hiro: (last updated before 2020-01-09) Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation

1 0

April's roadmap for the metrics team
by Gaba 07 Apr '20

07 Apr '20

Hi! Last week we met to discuss priorities and roadmap for April for the metrics team. You can read about it in the team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam 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

roadmap for the network team
by Gaba 07 Apr '20

07 Apr '20

Hi! Today we met to discuss priorities for the next 3 months as well as roadmap. If you are interested in it we have updated the team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam Any needed changes to the roadmap will be discussed during the team's weekly meetings. 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

March 2020 report for the Network Health team
by Georg Koppen 07 Apr '20

07 Apr '20

Hello! Here come the highlights from the network health work in March: 1) We made substantial progress fixing the last critical bugs before we can deploy sbws and replace Torflow as our bandwidth scanner. We, additionally, mapped out the remaining work for April and started to tackle that, too. 2) As I indicated in my previous status report I've been working on detecting and resolving DNS resolution issues of exit relays[1]. I managed to get the analysis done and contacted relay operators provided they had a valid ContactInfo. Those, that were not able to fix their setup got the bad exit flag which should improve performance for Tor Browser users and other clients. It's been, however, only a first step in helping exit operators diagnosing and resolving those DNS problems. We need to do more work in this area in the future. For April the only big item on our list is getting sbws in a shape so it finally can replace Torflow as our bandwidth scanner. Georg [1] https://trac.torproject.org/projects/tor/ticket/32864

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project