- tor-project - lists.torproject.org

Anti-censorship team monthly report: June 2019
by Philipp Winter 02 Jul '19

02 Jul '19

Hi everyone, Here's a summary of the anti-censorship team's progress in June: BridgeDB ======== * Blacklisted 53 bridges whose obfs4 port was unreachable. Most of these bridges had no contact info. Some did, but the operators did not respond to our emails. * Tried to understand why BridgeDB responded to many requests with no bridges: <https://bugs.torproject.org/30441> - Eventually, the problem seems to have fixed itself. - We'll keep a close eye on the logs. * After hearing back from Tor's research safety board, we implemented a new feature that lets BridgeDB export statistics: <https://bugs.torproject.org/9316> The feature is currently under review. * Removed support for Yahoo email accounts: <https://bugs.torproject.org/28496> * Published a blog post about BridgeDB's new 0.7.1 release: <https://blog.torproject.org/new-release-bridgedb-071> Snowflake ========= * We released a prototype for snowflake's webextension! For Firefox, you can get it here: <https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/> We're still working on getting it published in Chrome's web store. By installing the addon, you turn your browser into a circumvention proxy for censored users. * Working on integrating pion/webrtc to ease builds and reduce dependencies: <https://bugs.torproject.org/28942> * We wrapped up a ticket to collect statistics on snowflake's broker: <https://bugs.torproject.org/21315> * Brainstormed mechanism for snowflake update versioning: <https://bugs.torproject.org/30704> Pluggable transports ==================== * Implemented a patch to reorder PT/proxy phases: <https://bugs.torproject.org/28930> The patch is currently under review. * Brainstormed ideas for obfs4's successor: <https://bugs.torproject.org/30716> - We decided to first study the "long tail" of network traffic because it will allow us to make better design decisions: <https://bugs.torproject.org/30986> * We made some progress on improving our PT spec: <https://bugs.torproject.org/29285> - For now, we have been collecting a list of issues with the v1 spec. * We made some progress with loading shared libraries for PTs into the Tor executable (on Linux for now). Miscellaneous ============= * Deployed <https://bridges.torproject.org/scan/>. The service allows obfs4 operators to test the reachability of their obfs4 port -- at least until we are done with the following ticket: <https://bugs.torproject.org/30477> * We wrapped up our "does the GFW block obfs4?" ticket: <https://bugs.torproject.org/29279> The answer is: no. * Published a blog post that introduces our anti-censorship team and our Sponsor 19 report: <https://blog.torproject.org/tors-new-anti-censorship-team-defending-open-in…> * Asked tor-relays@ to set up more obfs4 bridges: <https://lists.torproject.org/pipermail/tor-relays/2019-June/017419.html> * Worked with a handful operators whose obfs4 bridges were broken. Several operators believed that only a bridge's OR port must be externally reachable. Others forgot to configure port forwarding for their obfs4 port.

2 1

minutes from the sysadmin meetign
by Antoine Beaupré 01 Jul '19

01 Jul '19

Here are the minutes from today's sysadmin meeting. # Roll call: who's there and emergencies Anarcat, Hiro, Qbi and Weasel present. No emergencies. # What has everyone been up to ## anarcat * scraping collection patch was merged in prometheus puppet module, finally! still 3 pending patches that need unit tests, mostly * more vegas meeting and followup, in particular with email. discussions punted to stockholm for now * reviewed the hardware inventory survey results, not very effective, as people just put what we already know and didn't provide specs * more hiera migration, static sync stuff left * documented possible gitlab migration path and opened #30857 to discuss the next steps * expanded storage for prometheus to 30 days (from 15) landed at 80% disk usage (from 50%) so doubling up the retention only added 30% of disk usage, which is pretty good. * archive.tpo ran out of space, reached out to software heritage and archive.org to store our stuff, both which responded well, but requires more engineering to move our stuff off to IA. heritage are now crawling our git repos. and setup a new machine with larger disks (archive-01) to handle the service. tried to document install procedures in the hope to eventually automate this or at least get consistent setups for new machines * usbguard and secureboot on local setup to ensure slightly better security in my new office * started reading up on the PSNA (see below) * regular tickets and security upgrades work ## qbi Created a new list and other list admin stuff, also some trac tickets. ## hiro * continued documenting and developing websites. we now have a secondary repository with shared assets that can be imported at build time * almost done with setting up a second monitoring server * did some hiera migrations * finished torbrowser packages syncing on github and gitlab for gettor * went to rightscon ## weasel Was busy with work and work trips a lot. Haven't really gotten to any big projects. # What we're up to next ## anarcat * Vacation! Mostly unavailable all of july, but will work sporadically just to catchup, mostly around Stockholm. Will also be available for emergencies in the last week of july. Availabilities in the Nextcloud calendar. * Need to delegate bungei resize/space management (#31051) and security updates. archive-01 will need some oversight, as I haven't had time to make sure it behaves. * Will keep on reading the PSNA book and come up with recommendations. ## hiro * more website mainteinance * would like to finish setup this second monitoring server * documentation updates about setting up new machines * need to cleanup logging on dip * need to figure out how to manage guest users and a possibly anonymous shared account * following up the migration discussion, but unsure if we're still on the same goal as the three-year-old survey we did back then * need to post july/august vacations ## qbi Mostly traveling and on holidays in july and beginning of august ## weasel Maybe july will finally see ganeti stuff, now that we have funding. Will be in Stockholm. # Holidays and availability We've reviewed the various holidays and made sure we don't have overlap so we have people available to respond to emergencies if they come up. We're not sure if the vacations should be announced in pili's "Vacation tracker" calendar or in weasel's "TPA" calendar. # Stockholm meeting prep We managed to get a full roadmapping day set aside for us. We can make a spreadsheet to brainstorm what we'll talk about or we can just do it ad-hoc on the first day. There's also a "Email or not email" session that we should attend, hosted by anarcat and gaba. Finally, anarcat can present our work to the "State of the onion" session on the first day. # Other discussions Weasel noted the meeting was a bit long, with lots of time spent waiting for people to comment or respond, and asked if we could speed it up by reducing that latency. Hiro also proposed to dump our "previous/next" sections in a pad *before* the meeting so we don't have to waste synchronized time to collectively write those up. This is how vegas proceeds and it's very effective, so we'll try that next time. # Next meeting August 5th, 1400UTC. We will try to make the meeting faster and prepare the first two points in a pad beforehand. -- Antoine Beaupré torproject.org system administration

1 0

Notes from June 27 and 20 2019 Vegas team meeting
by Karsten Loesing 01 Jul '19

01 Jul '19

Notes for June 27 2019 meeting: Georg: 1) Back from All Hands keeping track of and doing all the follow-ups 2) We should decide about follow-up sessions we need for our dev meeting. I am fine waiting with that for the scaling meeting tomorrow, if we want. Pili and I agreed the Tor Browser vision session is not as important right now and we could fill it with one of those sessions. Maybe specific Tor Browser related performance/metrics items that came out of All Hands (as the more network team related ones would overlap with part of the network retrospective). [gaba_hijacking_space: sounds good. I'm removing the Tor browser vision session. Can we briefly discuss here the state of the onion if everybody agree on who is going to be there (sheet in https://nc.riseup.net/s/FFkikRBmKDZyLw9 ) ] [says file not found] [now it should work] 3) We finally got all chemspill releases out on all platforms. Big thanks to boklm for driving this and doing the bulk of the work. 4) started with preparations for network health session at dev meeting 5) HackerOne backlog Antonela: 1) UR - Coordinating with Nah the reporting of latest africa trip. 2) OONI - Met Maria before her vacs to sync about Explorer and Apps, working and reviewing related issues 3) TB - Banner for donations is done, waiting for approval (#30577) [I added a comment that I think it looks great and ask that we leave the newsletter sign-up] 4) S27 - reviewed #30024, put together https://nc.riseup.net/s/WH6HHZyjQjdwewF 5) S28 - worked with snowflake webextension UI 6) Asked pili to move forward with the Media folder organization. Steph: could you review the doc she made and tell us what do you think, if we can proceed, if you want to have some specific things there that we don't have right now (but exists), etc? [I checked it out, and it looks good to me! -steph] [cool! hiro, pili and I will work on it during the dev meeting - A] 7) Stockholm meeting - coordinating with dunqan for the Persona's session - planning a Tor Browser prioritizing user problems session - organizing S27 UX work to make sure we are making decisions on what is needed Sarah: 1) Getting caught up after vacation. 2) Getting some nice cryptocurrency donations - ~$25,000 total this month. Included in that is another large donation from privcoin.io. 3) Working on organizing fundraising brainstorm for dev meeting. Any thoughts can be added here: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… 4) BTCPayServer will soon launch a campaign on our behalf. Just waiting on one more detail. 5) Patches for our monthly givers - Defenders of Privacy - are being produced now. Will begin sending to current monthly donors. 6) Planning for DEF CON. Steph: 1) newsletter going out today 2) community portal edits 3) edited anti-censorship team blog post 4) preparing for longer form media pitch 5) coordinating tv interview for isa Gaba: 1) blogpost on anti-censorship team with phw 2) s27 monthly report 3) feedbacks with nick 4) trac/roadmaps gardening 5) starting to prep sessions for Tor meeting 6) getting ready to travel to stockholm next week 7) schedule https://nc.riseup.net/s/WCk5xjAGcXgGSJY Anarcat: 1) getting ready for july vacations and stockholm meeting with the team 2) archive.tpo setup in progress to resolve the disk storage situation there 3) some mail issues resolved https://trac.torproject.org/projects/tor/ticket/30911 4) working on a broader, long-term analysis of our needs and requirements, using good reference material (Tom Limoncelli's Practice of Network and System Administration) might come up with a "what are our pain points, time sinks and bottlenecks" survey or discussion Nick: 1) Release 0.4.1.3-alpha 2) Working on feedback summaries; gaba is helping me. Planning to send them out rsn and try to schedule 1:1:1s to happen pre-Stockholm. Mike: 1) Tor-scaling planning for Stockholm - Thinking of changing the "Growing the Tor Network" meeting or adding more sessions 2) Working on summary email of Mozilla All Hands Roger: 1) asn can make it to the OTF summit. I'm talking to OTF to get the right invites. 2) I'm full-time on the NSF proposal revision for the next week. Karsten: 1) Catching up after All Hands. --- Notes for June 20 2019 meeting: Nick: 1) Work goes on; team is mostly working on 0.4.2 stuff 2) Looks like 0.4.1 is likely to become stable on-schedule!? - All teams: Please let us know if you have any bugs that really need to get fixed between 0.4.1.x-alpha and 0.4.1.x-stable. Gaba: 1) we have several options on what to do with email at the organization and a decision could be made soon https://nc.riseup.net/s/9iExsYaZC4mP8p8 (conversation will continue in Stockholm - options 2 and 4 are the one possible right now) 2) started collecting feedback about nextcloud migration https://nc.riseup.net/s/atdNpRScNiBfKrM 3) follow up on gitlab/trac migration https://trac.torproject.org/projects/tor/ticket/30857 4) follow up on CI role as permanent versus rotating at the network team. 5) small changes/follow up on draft Tor meeting schedule. https://nc.riseup.net/s/FFkikRBmKDZyLw9 6) RT/Frontdesks: pili created an account for me. 7) gettor is happening on https://dip.torproject.org/anti-censorship/gettor/boards (updating it from trac myself) 8) other tasks like roadmaps update/checking. 9) sponsor 19 report can be public now. Steph: we (phw, cohosh, kat, arma, karsten) are coordinating a blogpost for next week. pili: 1) Worked on feedback reviews 2) Working with more GSoD candidates 3) S9 Phase3 Work Plan responses 4) Community Portal 5) Finally looked into Frontdesk/rt - There's a lot of spam, most of it in polish, I cleaned up a lot of it and tried to remove the culprits from rt, hopefully that will help with ticket volume - I would say about 50% or more of the tickets on the first page are related to people requesting bridges or reporting issues with bridges. (Phw and me are in the loop about this here. --gaba) - around 25% of tickets on the first page have no subject and no content... - There's probably around 50 new legitimate tickets every week that are going unanswered - Still need to do more analysis but that's a quick summary of what I've seen so far 6) Working on a plan for re-organising media.tpo. Steph: we should sync about this when I have a clear plan [yes, let's! exciting :) lmk if you want any help with planning] 7) Working on plans for website maintenance in future 8) Organising work for monthly donors fundraising banner on TBB isa: 1) Met with Ford on Tuesday 2) Start the work with Beth Grupp consultation 3) Finalizing small things regarding the dev meeting (board meeting day, vegas leads meeting day, space logistics) 4) Will meet with Trevor Timm (tomorrow/friday) 5) Tea Time session on tor-internal 6) Working on reviewing working plan for sponsor9 Erin: 1) back from vacation; playing catch-up Karsten: 1) At All Hands. Steph: 1) Def Con preparation 2) Community portal copy 3) Bug campaign prep 4) Getting resettled after holiday Antoine: 1) partly resolved archive.tpo situation, with IA and Software Heritage and infrared contacts, latter might develop in more hosting options 2) worried about physical security in co-working space 3) finished email proposal (see gaba point) 4) working on evaluating our infrastructure using formal sysadmin methods (#30881) which will show where the flaws in our infra are and help with a long term map

1 0

RACE meeting notes, 27 June 2019
by Philipp Winter 27 Jun '19

27 Jun '19

These are the first meeting notes for Tor's RACE project, which is our Sponsor 28. If you have no idea what this is, then fret not, for it is all documented in our wiki: <https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28> Here are our meeting logs: <http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-27-18.00.html> And here is our meeting pad: # S28: Resilient Anonymous Communication for Everyone Information about the sponsor: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 Next meeting: Thursdays 1800 UTC (every 2 weeks) at #tor-meeting The goals for this periodic meetings are: 1. share what is happening with the rest of organizations in the project 2. share progress on Tor side 3. get the monthly report started ----------------- JUNE 27TH ----------------- TECHNICAL REPORT FOR APRIL-JUNE: https://nc.riseup.net/apps/onlyoffice/s/MdNwgWk8CL8FBis What Philipp did: * Attended RACE brainstorming meeting about obfs5 * Updated description of https://bugs.torproject.org/30716 with feature ideas * We decided to first study the "long tail" of network traces because it will inform our obfs5 design * Filed https://bugs.torproject.org/30986 * Lots of reading to get up to speed on PT spec and obfs4 issues * Reached out to PT spec implementers to see what suggestions they had * Only one person responded :( What Philipp will do: * Understand PT spec issues on Android (sysrqb and nathan know the details) * Help Micah with studying the "long tail" of network traces * Maybe also reach out to a new contact at a network provider What cohosh did: - Attended brainstorming meeting - Attended integration meetings - Shared PT spec with other groups What gaba did: - read mails is the only thing :) - update roadmap (trying to keep track of what you all are doing)

1 0

Anti-censorship meeting notes, 27 June 2019
by Philipp Winter 27 Jun '19

27 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-27-17.00.html And here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 27th 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://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Our roadmap consists of a subset of trac tickets. * Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team" * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 27th June 2019 ---- --------------------------- == Announcements == * Sponsor 28 (RACE) next meeting will be on June 27th 1800 UTC at #tor-meeting Agenda/Notes: https://pad.riseup.net/p/tor-censorship-S28-keep * Please add your June 2019 highlights for our monthly reports here: https://pad.riseup.net/p/h4FrASe8pVEaAfmUs_IG == Discussion == * Problems with bridges. BridgeDB unusable? * what tickets people are working on right now? * 9316 BridgeDB should export statistics * 30441 Stop BridgeDB from handing out offline bridges * what needs to be done to have it usable? * Let's test our obfs4 setup guide by asking people on tor-relays@ to set up new obfs4 bridges? * snowflake webextension update? #30931 ? == Actions == * == Interesting links == Censorship-Resilient Proxy Distribution Using Game Theory https://www.ndss-symposium.org/ndss-paper/enemy-at-the-gateways-censorship-… == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. hiro: (gettor days are Thursday) This week: Next week: Past week: phw: This week (2019-06-27): * Sent "call for new obfs4 bridges" email to tor-relays(a)tp.o. * One person contacted me directly after setting up a new bridge. They thought the instructions worked very well. * Worked on #30931 so arlo, dcf, cohosh, and I can all manage our snowflake webextension * Arlo already submitted the extension to Firefox and Chrome! * Worked with more operators of broken obfs4 bridges. * Sent ten of BridgeDB's unallocated obfs4 bridges to activist for manual distribution. * Lots of work on #30441, to stop BridgeDB from handing out offline bridges. * The problem may have fixed itself? * Blacklisted 53 broken obfs4 bridges. * Added debug log messages and discovered bot that's scraping bridges. * Brainstormed obfs4 improvements over at #30716. * For now, we decided to understand the "long tail" of network traffic first (#30986) * Once we have a better understanding of the long tail, we'll continue with obfs5 * Attended RACE call in which we discussed all of this. * Filed #30946 to port BridgeDB to Python 3. * Published blog post that introduces the anti-censorship team and our Sponsor 19 report. * https://blog.torproject.org/tors-new-anti-censorship-team-defending-open-in… * Lots of help from gaba and stephw! * Had a brief look at the popularity of an active probe's cipher suite over at #30500. * Caught two probes that had a different cipher suite; one quite common, but not the other * Pushed a feature branch for our BridgeDB metrics (#9316) which is now in 'needs_review'. Next week: * More RACE work (PT spec and network trace "long tail") Help with: * Try requesting different types of bridges from bridges.torproject.org and let me know if you got 0 bridges. Gaba: (updated 2019-06-20) Last week: * tor meeting schedule intil the meeting This week (05/30): * bridgedb plan * sponsor 28 update 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. kat5: Last week (May 20): This week (May 27): dcf: 2019-06-27 (will miss today's meeting) Last week: Next week: - try the Snowflake WebExtension - publish post-sanitization broker logs (#30731) Help with: cecylia (cohosh): last updated 2019-06-27 Last week: - got snowflake client to use pion/webrtc (#28942) - continued investigating the fixes we need in pion for the large message drops - addressed dcf's feedback on the sequencing layer (#29206) - worked on Turn On/Off toggle for web extension (#30934) Next week: (AFK on Monday) - try to figure out if there are any popular STUN servers in places where googles are blocked - move forward with sequencing layer (#29206) - continue work on improvements to pion/webrtc (#28942) - webextension translations (#30310) - some serious snowflake dogfood - familiarize self with PT spec Help with: - broker stats (#21315) code review - review of #30934 - review of fixes in #29206 but i can keep moving forward with it - review of work so far with #28942 catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 week of 06/20 (actual): - mostly sponsor31 - helped ahf with some bootstrap stuff week of 06/27 (planned): - mostly sponsor31 arlolra: 2019-06-27 Last week: - a bit of snowflake webextension This week: - getting the webextension published (#30931) Next week: - review #30934 Help with: - fixing our websocket server implementation (#30998)

1 0

Tor Browser team meeting notes, 24 June 2019
by Georg Koppen 25 Jun '19

25 Jun '19

Hello! Here come the notes from our latest weekly Tor Browser meeting. Our IRC log can be found on: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-24-17.32.l… Apart from the usual discussion about topics that are/were relevant in the upcoming and past week the log contains some report back from All Hands as well, for those of you who are interested in that. Additionally, here come the items from our pad: Discussion: -upcoming macOS signing changes (GeKo: mcs/brade will start looking closer at the actual requirements; we have #30126 for tracking) -state of the Windows bundle (GeKo: see: https://www.windowscentral.com/how-enable-controlled-folder-access-windows-… for starters as it might be (part) of the underlying problem; I filed #30976) GeKo: Last week: - All Hands and a bit release help (many thanks to boklm for managing the whole fuck-up essentially himself) This week: - catching up with backlog - review, review, review - get all Linux patches for ESR 68 toolchain into reviewable shape mcs and brade: Last week - Worked on #30000 (Integrating client-side authorization to onion services v3). - Continued to work on the Onion Services client auth prompt (#30237). - Commented in #30943 (Show Tor Browser version on Android). This week: - Review for #18101 (IP leak from Windows/macOS UI dialog with URI). - at the same time, test Snowflake on macOS 10.9.x. - More work on the Onion Services client auth prompt (#30237). - We plan to post work-in-progress patches this week and then work with Antonela on UX. - Soon: #29197 (remove use of overlays from Tor Launcher) - Soon: #30429 (ESR 68 Rebase — updater patches). pili: Last week: - Frontdesk message forwarding ;) - We had some messages from Windows - There's also some interest on continuing development on Tor Messenger - And some bug reports This week - Tying up loose ends before vacations - afk from 26th June - 1st July - are we on track for the fundraising banner to be released with the next security update? (GeKo: acat will work on that this week) acat: Last week: - Addressed review changes for https://bugzilla.mozilla.org/show_bug.cgi?id=467035, now waiting for review. - Continued torbutton cleanup/refactor (#28745) - Patch for Properties in dom/locales/$lang/chrome/ allow detecting user locale (#30683). This week: - File uplift bugs for suitable rebased ESR68 patches (start with #24056, #23104, #26353, #26514, #21830). - Continue torbutton cleanup/refactor (#28745) - Add Fundraising Banner with next TBB security update (#30577) boklm: Last week: - building, signing, releasing some releases - started looking at rebasing #28672 (Android reproducible build of Snowflake) on #30334 (build_go_lib for executables) - started looking at #30320 child tickets (Adapt Tor Browser toolchains for Firefox 68 ESR) This week: - look at remaining failing testsuite tests - fix reproducibility issues of snowflake build for android (#28672) - look how we can build 32bit mar-tools: https://trac.torproject.org/projects/tor/ticket/30321#comment:10 - look at how to upload tor browser releases on archive.org for #29697 pospeselr: Last week: - seem to have tracked down all the issues in widl preventing screen readers from working - posted candidate builds with all the patches applied - started fixing widl patches based on feedback from wine devs This week: - finish up widl changes - figure out what needs to happen to get updated widl into mingw - update tor-browser-build's 27503.patch to final widl version antonela: This week: - Looking at https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~Tor… issues - TBA - what we will do with #24920? and #30540? Any updates on #29955? - TB - ESR68 - reviewing acat proposal (#10760) - TB - Banner for donations is done, waiting for approval (#30577) - S27 - reviewed #30024, waiting for onion auth wip for review - planning a Tor Browser prioritizing user problems session for the dev meeting sysrqb: Last week: All Hands Laptop hard-drive corruption This week: Laptop data recovery 68esr rebase Read backlog from the last week sisbell: Last week: - #30607: Testing Android Q problems on actual device - tor loads and runs fine. Firefox 60 is incompatible with Android Q. Will need to wait until 68. - #Did clean update of gradle dependencies for topl/tor-android-service for toolchain This Week - Move toolchain and related projects changes to GeKo branch - # 30199 tor-android-service cleanup - #Submit PR to TOPL - #Follow up about TOPL mirror Georg

1 0

Network team meeting notes, 24 June 2019
by Nick Mathewson 25 Jun '19

25 Jun '19

Hello! You can read the logs from yesterday's meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-24-17.00.html Below are the contents of our meeting pad. = Network team meeting pad! = This week's team meeting is at Monday 24 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 24 June at 1700 UTC July schedule: * Wednesday 3 July 2300 UTC * Monday 8 July at 1700 UTC * (In-person meeting 12-14 July) * Monday 22 July 1700 UTC * Monday 29 July 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 list archive for older notes.) 28 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002338.html 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html 10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html 17 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002365.html == Stuff to do every week = * How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailu… * Let's check the 0.4.1 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… Click on 'all boards' and then the network team one. Filter by your name and check the 'in progress' column is correct. * 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… Any blocker from last week? == 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. ------------------------------- ---- 24 June 2019 ------------------------------- == Announcements == [REMINDER] WIP Schedule for Tor meeting https://nc.riseup.net/s/FFkikRBmKDZyLw9 The master branch is now 0.4.2.x. 0.4.1.x development continues on maint-0.4.1 and release-0.4.1. 0.3.4.x is now end-of-life. Summary the mail thread on proposal from Dgoulet https://nc.riseup.net/s/gQGT8kjNgt3C6cd == Discussion == Retrospective on Thursday. How people want to do the retrospective? (please vote) jitsi +1 +1 irc other? #29697 Anybody up to team with boklm to coordinate archive.tpo Please update https://pad.riseup.net/p/network-team-draft-CI-role and vote yes/no on the change into a permanent role for CI. Can we start soon? Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity ahf -> catalyst coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) Looking at coverity -- it seems our builds may have been stuck. I've cancelled the stuck builds. Also, they say they are going to have a planned outage to upgrade their backend, starting today and lasting about 3-4 days. Friday would be a good day to have another look. -nm jenkins Travis teor did some work on stem failures, we need to add a control message trace to tor to diagnose (#30901) waiting for catalyst's advice, because they are refactoring this code Appveyor Bug triage teor -> ahf Everything seems ok, I might have missed some patches and things earlier in the week. == Recommended links == == Updates == NOTE NEW FORMAT! 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: Last week (actual): . gitlab This week (planned): . sponsor 31 adjustment with new tickets . more gitlab Help with: teor: (offline at the usual meeting time) Week of 17 June (planned): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fix existing open tickets where I have added the sponsor - Fallback directory mirror list rebuild (#28793) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - merge chutney pull requests - disown or quick fix tickets: I should only be owner on tickets I will work on in the next month - bug triage rotation Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Low-Priority: - backlog: router_have_consensus_path() logs an incorrect "no exits in consensus" (#27448) - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Week of 17 June (actual): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fixed some existing open tickets where I have added the sponsor - some code reviews - merged some chutney pull requests - Fallback directory mirror list rebuild (#28793) - draft list - need to work out why the list is so short this time (#30952) - some bug triage - sbws triage and fixes - Fixed PT extra-info bugs introduced in 0.4.1.1-alpha and 0.2.7.2-alpha (#30956, #30958) - disowned some tickets, more next week Important: - reviews of new onion service DoS code - designed API for pool abstraction - work on proposal/questions for possible trac migration - travel prep - process changes Week of 24 June (planned): Urgent: - fix existing open tickets where I have added the sponsor - Continue fallback directory mirror list rebuild (#28793) - need to work out why the list is so short this time (#30952) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - disown or quick fix the rest of my tickets: - I should only be owner on tickets I will work on in the next month - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Week of 24 June (actual): Urgent: - Important: - Low Priority: - Help needed: - catalyst, do you have advice on: - add tor controller trace logging to diagnose stem hangs (#30901) [catalyst: i'll try to look at it this week] Nick: Week of 17 June (planned): - Summarize employee feedback - PETS review - 0.4.0.6 release, maybe. - Reply to proposals 303 through 305, maybe. - Reviews and merges - 29211 -- refactor configuration code. - 29280 -- needs_revision, chutney in ci code - 27801 -- review proposed API for launching sockets with embedded tor - 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Week of 17 June (actual): - Code reviews - PETS review - Work on various 29211 subtickets. (configuration refactoring) - Start summarizing employee feedback. (4/6 done) - Defer 0406 release; start 0413 release - try to catch up with backlog Week of 24 June (planned): - Retrospective on Thursday - More 29211 work - 0413 release - attempt: Reply to proposals 303 through 305, maybe. - attempt: review 27801 api - attempt: 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Mike: Week of 6/17 (planned): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/17 (actual): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/24 (planned): - Bitcoin conference - code reviews - Catch up on mail catalyst: week of 06/17 (2019-W25) (planned): - reviews - control.c refactoring week of 06/17 (2019-W25) (actual): - chatted with ahf re #28930 (msybe reorder some PT/proxy bootstrap phases) - bureaucracy - wrote up #30911 to document some inbound email problems - cleaned up my owned tickets a little week of 06/24 (2019-W26) (planned): - CI+Coverity rotation - reviews - take a closer look at dgoulet's "radical changes" email thread - help teor with #30901 (control port trace logging for debugging test-stem hangs) - more bureaucracy - starting Stockholm trip prep - hopefully have time to work on control.c refactor asn: Week of 06/03 (planned): - Finalize s27 o2a1. - Help organize our AllHands experience. - Fix #30578 circpadding bug (041-must). - Do more work on HS DoS. - Some more travel prep for allhands. Week of 06/03 (actual): - Finally managed to get #30381 in needs_review. - Wrote some scaling emails. - Worked on #30578 (041-must). - Did some work on HS DoS: https://lists.torproject.org/pipermail/tor-dev/2019-June/013873.html - Cleaned most of my review backlog, but there is still more. - Merged prop304 to torpec. Week of 06/10 (planned): - #30381 is now in needs_revision. Need to do that. - More prepping for AllHands. Flying out on Sunday. - Try to do some work on s27 #26294 (intro point rotation dos) - Still got reviews hanging. In particular #30382. - I also got lots of hanging merges... Help needed: - teor, I still have troubles mapping all the pieces of #22029 in my brain. Perhaps at some point you can take over the review of that ticket, and I can take one big review from you? I don't see you having any big reviews this week, so perhaps we can wait until next week. teor says: I assigned myself as reviewer on this ticket. neel is still working on it, when he finishes, I will split off some of the small features so other people can review them. ahf Week of 17/6 (planned): Network team: - Finish off patches for #29736 so we can discuss the big changes at the Thursday meeting. - Continue with #28930. Misc: - Figure out what needs to be doing on some of the PT spec tickets I have. Week of 17/6 (actually): Network team: - Discussed #29736 and authentication patches during anti-censorship team meeting. - Rebased and discussed current changes for #28930 with catalyst and decided next step. - Wrote patches for CI build failures for Stem and Chutney in #30928. - Figured out next steps for #5304 Week of 24/6 (planned): Network team: - Continue iteration of #28930 and discuss progress with catalyst. - Write Tor patch for #5304 (spec is OK) - Bug Triage duty. - Work a little bit on 'untrac' (a small tool to import Trac tickets into Gitlab that Gaba and I talked about during my 1:1 last Friday). juga(offline): Week of 05/20 (planned) - Add Tor version to the bandwidth file (#30196) Week of 05/20 (actual) Week of 06/03 (plan) - Continue with #30406: Refactor header constants in sbws to use Stem's one dgoulet: (might be offline, getting sleep has been very rough in the last days...) Week of 06/10 (actual): - Tested and experimented with #15516. Had to wait a bit to get new machines from a friend at a hosting provider in order to start limited bw relays. Thanks to ahf for providing assistance with his fast relays. - Wrote prop305 (on tor-dev@) about ESTABLISH_INTRO parameters. See #30790. Thanks from teor/asn for early feedbacks! - Merges and reviews as always. Week of 06/17 (planned): - Finalize #30382 from asn's review. - Continue work on #15516. I'm hoping to drop the experimental results on the ticket, finzlie the branch for upstream merge. And then move on to prop305.

1 0

S27: Onion Services meeting this week: Tuesday 18th June
by Pili Guerra 25 Jun '19

25 Jun '19

Hi everyone, This is a reminder of our fortnightly S27: Onion Services project meeting happening this Tuesday 18th June at 15UTC on #tor-meeting. Please join us if you’d like to participate or feel free to just lurk :) 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

2 4

Anti-censorship meeting notes, 20 June 2019
by Philipp Winter 20 Jun '19

20 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-20-17.00.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 20th 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://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s… * Our roadmap consists of a subset of trac tickets. * Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team" * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 20th June 2019 ---- --------------------------- == Announcements == * Sponsor 28 (RACE) next meeting will be on June 27th 1800 UTC at #tor-meeting == Discussion == * do we want to move to gitlab for snowflake? (try only with one component for now) --> we are going to wait until the issue of "guests filling tickets in gitlab" is resolved. * gaba created https://dip.torproject.org/anti-censorship/pluggable-transports/snowflake/b… * Let's test our obfs4 setup guide by asking people on tor-relays@ to set up new obfs4 bridges? * WebSocket in Snowflake: next steps. (ahf) * trac management: can we 'own' tickets only when we are working on them? if you are interested in a ticket then add yourself to cc. * is #23888 going to be able to happen on time? do we need to take it? == Actions == * == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. hiro: (gettor days are Thursday) This week: Next week: Past week: phw: This week (2019-06-20): * Reviewed #21315 (publish some realtime stats from the broker?) * Mostly implemented #9316 (BridgeDB should export statistics) * Got a frontdesk account and had a look at bridge-related tickets * With Cecylia's help compiled summary of what we know about the GFW and active probing * Pinged ICLab team again to see if they can periodically scan at least our default bridges * Sent more emails to PT implementers * So far only one response * Tested #23888 (Creating a Snowflake WebExtension addon) and left feedback * Went through old tor-dev@ threads to compile feedback on improving the PT spec Next week: * More work on moving forward with PT spec * More thinking about improving obfs4 * Get #9316 reviewed * Create a blog post for our sponsor 19 report #2. Help with: * Brainstorming features of obfs4 successor, and how to improve PT spec Gaba: (updated 2019-06-20) Last week: * playing with gitlab for snowflake: https://dip.torproject.org/anti-censorship/pluggable-transports/snowflake/b… * prepare tor meeting schedule This week (05/30): * ahf Last week: - Talked with Cecylia about WebSocket + authentication patches in https://github.com/ahf/snowflake/tree/features/websocket_r5 and what we should do next. (#29736 and friends) - Hack on #28930 This week: - Work on #28930 kat5: Last week (May 20): This week (May 27): dcf: 2019-06-20 Last week: - brainstormed some problems with the PT spec (https://bugs.torproject.org/29285#comment:5 ) - wrote ideas about protocol versioning and backward compatibility (#30704) - reviewed sequencing layer (#29206) - added meek-azure bridge, meek-azure CDN, and snowflake-broker CDN to the infrastructure survey Next week: - will be mostly offline next week, will miss 2019-06-27 meeting - look at WebExtension changes in https://bugs.torproject.org/23888#comment:24 - publish post-sanitization broker logs (#30731) Help with: cecylia (cohosh): last updated 2019-06-13 Last week: - submitted some PR's for pion/webrtc - starting modifying our snowflake code to use pion/webrtc as the library (#28942) - started familiarizing myself with Chutney - took a look at the snowflake webextension changes (#23888) Next week: (AFK on Friday) - update default STUN configuration (#26348) - address dcf's feedback on the sequencing layer (#29206) - continue work with integrating/evaluating pion/webrtc (#28942) - familiarize self with PT spec Help with: - broker stats (#21315) need a metrics team review (should we deploy what we have and store the output locally?) - browser team help for mingw toolchain (#25483) catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 arlolra: 2019-06-20 Last week: - nothing This week: - a bit of snowflake webextension Help with: - getting the webextension published (#30931)

1 0

CANVAS talk on ethical Internet measurement
by Philipp Winter 20 Jun '19

20 Jun '19

A few months ago, while still affiliated with CAIDA, I gave a talk on "Ethical Internet measurement: From outages to anonymity" at the CANVAS workshop in Bamberg, Germany. Part of my talk covered ethical research on the Tor network. The recordings are now online: <https://canvas-project.eu/videos/Workshop-Bamberg-Philipp-Winter.html> My slides are available here: <https://nymity.ch/pdf/canvas19-slides.pdf> Cheers, Philipp

1 0