tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

Network team meeting notes, 17 Jun 2019
by Nick Mathewson 17 Jun '19

17 Jun '19

Hello! You can find our meeting log at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-17-17.01.html . Below are the contents of our meeting pad. = Network team meeting pad! = This week's team meeting is at Monday 17 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 17 June at 1700 UTC * 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.) 20 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002335.html 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 == 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. ------------------------------- ---- 10 June 2019 ------------------------------- == Announcements == [REMINDER] WIP Schedule for Tor meeting https://nc.riseup.net/s/FFkikRBmKDZyLw9 [INFRA] Do you have problems with email? Please report any problem (or not) that you may have here: https://trac.torproject.org/projects/tor/ticket/30608 (also https://help.torproject.org/tsa/doc/reporting-email-problems/) 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. == Discussion == Please comment on the draft meeting agenda, see the tor-meeting list for details Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity ahf -> ahf (ahf takes another week here after having talked with asn who is at mozilla all hands). coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) ^ is from last week, what happened this week? 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 nickm -> teor I think I'm up-to-date, but please let me know if there are any unhandled piles of tickets that you think I should go back to -nm. == 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): . stockholm meeting planning . scalability meeting This week (planned): . sponsor v and 2 . sponsor 31 adjustment with new tickets . more gitlab Help with: teor: (offline at the usual meeting time) Week of 10 June (planned): Urgent: - More HR stuff - Fallback directory mirror list rebuild (#28793) - Get gus access to the fallback-scripts repository - Get gus an LDAP account - Help close Sponsor 19? - code reviews - work on stem CI hangs? - do end of life tasks for 0.3.4 Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - revise reject bridge descriptors on authorities (#16564) - waiting for an initial review - still need to do another review of #29280 - work out which roadmapped work to do next: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - off-by-default module practices (#29224) - remove unneeded dependencies for tor roles: client, relay, etc. (#29227) - merge add chutney to tor's CI (blocked on stable Tor CI) - backport backlog (blocked on stable Tor CI) Low-Priority: - document disabled CI (#30745) - 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? - revise tor_addr_port_lookup() is overly permissive (#30721) - improve documentation for chutney warnings in make test-network-all (#30455) Week of 10 June (actual): Urgent: - code reviews - Fallback directory mirror list rebuild (#28793) - Get gus access to the fallback-scripts repository - Get gus an LDAP account - did end of life tasks for 0.3.4 - made progress on stem hangs, turns out tor needs more logging to diagnose them (#30901) Important: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - made progress on add chutney to tor's CI (#29280) - merged chutney pull requests - merged CI backport backlog, still need to triage the rest of the backlog - try to work out how to write a pool abstraction, to help us solve bootstrap issues - helped fix some critical sbws issues - triaged some of the tickets where I am the owner on trac Low-Priority: - Fix Tor's address parsing so it's more consistent (#30721), turned out harder than I thought - improve documentation for chutney warnings in make test-network-all (#30455) 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 - Fallback directory mirror list rebuild (#28793) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) 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? Nick: Week of 10 June (planned): - Open 0.4.2. - Deprecate 0.3.4. - More analysis for walking onions, time permitting - Review and merge - Revise chutney/CI improvements: - 29280 (Use Chutney in Tor's CI) - 29024 (chutney and PTs) - 30459 (Let chutney tell Tor whether a network is supported) - Finish handle refactoring and cleanup (29218) - Plan configuration refactoring - More modularization? Week of 10 June (actual): - Started on 29211 (refactoring config code): planning, testing, initial refactoring. - Revisions on chutney-ci 29280 - Unrecommend a big pile of versions. - Revise 29024 and 30459 (chutney related) - Triage rotation 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. Mike (not at meeting; travel to Mozilla): Week of 6/10 (planned): - Mozilla all hands planning/discussion - Scalability metrics review/page reorg - Peer feedback - Register for PETs - Circpad documentation? Week of 6/10 (actual): - Mozilla all hands planning/discussion - Scalability metrics review/page reorg - Peer feedback - Register for PETs Week of 6/17 (planned): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization catalyst: week of 06/10 (2019-W24) (planned): - reviews - some sponsor31 tickets week of 06/10 (2019-W24) (actual): - reviews - bureaucracy - some control.c refactoring - figured out some mysteries about code that coccinelle has trouble looking at - chatted with nickm week of 06/17 (2019-W25) (planned): - reviews - control.c refactoring 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. ahf Week of 10/6 (planned): Network team: - Finish #28930. - Talk with traffic-obfuscation list people about #28849 - Talk to Cecylia and DCF about patches for #29736 and friends. Misc: - Presentation Thursday evening at the local union about Tor. - CI/Coverity role. Week of 10/6 (actually): Network team: - Went over #29736 and friends with Cecylia. We decided to ignore the proxy authentication part for now and continue with the rest, but in a way where it can be disabled on the broker side in case of a problem. It is a very big change to the Snowflake codebase, so that seems reasonable. - Hacked a bit on the Snowflake changes for #29736 after the conversation with Cecylia. - Hacked on #28930. - Some relay setup for asn and david for some experiments they are doing. Misc: - Did presentation on Tor at the union's youth department in Odense. Went well. - CI/Coverity wasn't bad. - Some conversations about upcoming CC election. 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. 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

Tor Browser team meeting notes 17 June 2019
by Pili Guerra 17 Jun '19

17 Jun '19

Hi, Here is the IRC log from our weekly meeting: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-17-17.31.l… and here are the items from our pad: Discussion: - Please review the list of dev meeting sessions and identify any gaps: https://nc.riseup.net/apps/onlyoffice/s/FFkikRBmKDZyLw9 - Is there any infrastructure that people in the tor browser team is using? Please fill in the spreadsheet: https://nc.riseup.net/apps/onlyoffice/s/QEM4MNBA8MmWW4x pili: Last week: - not very productive in Tor Browser terms, was afk for a public holiday on Monday and tonsilitis on Friday - Some general roadmap cleaning + work planning - dev meeting schedule - This week: - Dev meeting schedule - Helping GSoD candidates with their proposals - Tor Browser release meeting this week 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 #29285 (Improve the PT spec and how PTs interface with Tor). 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). - Soon: #29197 (remove use of overlays from Tor Launcher) - Soon: #30429 (ESR 68 Rebase — updater patches). acat: Last week: - Progress on DTD locale leak issue (https://bugzilla.mozilla.org/show_bug.cgi?id=467035) - Investigated why theme extensions were not enabled in ESR68 rebased branch (#30845). - Addressed GeKo's review comments on torbutton integration patch (#10760) - Some work on torbutton cleanup/refactor (#28745) This week: - Address review requested changes for https://bugzilla.mozilla.org/show_bug.cgi?id=467035. - torbutton cleanup/refactor (#28745) - maybe "Properties in dom/locales/$lang/chrome/ allow detecting user locale" (#30683). boklm: Last week: - helped with publishing 9.0a2 - made small patch for #30863 (Fix tor-android-service and tor-onion-proxy-library filenames) - finished patch for #28672 (Android reproducible build of Snowflake), now ready for review - updated patch for #30549 (Add script to remove expired sub-keys from a keyring file) - reviewed #30334 (build_go_lib for executables) - started reviewing #30585 (Provide standalone clang 8 project usable across all platforms) This week: - look at remaining failing testsuite tests - work on #30320 (Adapt Tor Browser toolchains for Firefox 68 ESR) child tickets. Not sure which yet. - fill infrastructure spreadsheet 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? [matt is out today, will keep it here for next week -A] - TB - ESR68 - reviewing acat proposal - TB - #30577 - pili: could we sync with sstevenson/steph to have some content for it? If we use the same code, is just text replacing. [for release meeting this week -A] - S27 - reviewing #30024, met stakeholders - Collecting/listing user problems for prioritization during the dev meeting pospeselr: Last week: - tracked down the cause of the reason for the accessibility crash of 32 and 64 bit tor browser on 64 bit windows (#27503) - caused by fix introduced by one of the wine devs to fix another of our crashes This week: - working with wine devs to fix this last crash - introduce the widl fix into tor-browser-build - babysit the fix submissions into wine tree 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 Release Meeting this week: Wednesday 19th June
by Pili Guerra 17 Jun '19

17 Jun '19

Hi everyone, It’s that time again :) Please join us for the Tor Browser Release meeting this week on Wednesday 9th June at 18:00UTC on #tor-meeting. 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

May 2019 report for the Tor Browser team
by Georg Koppen 14 Jun '19

14 Jun '19

Hello! We are late this time, but here finally comes the report from the Tor Browser team for May. In May we made four releases, Tor Browser 8.0.9[1], 8.5a12[2], 8.5[3], and 9.0a1[4]. Tor Browser 8.0.9 and 8.5a12 were emergency releases dealing with Mozilla's add-on certificate disaster[5][6], which disabled NoScript in Tor Browser. We lost some days for our Tor Browser 8.5 preparation due to that issue but were pleased to get that new major version out later, on May 21. It contains a lot of new features and improvements, most notably the first stable bundle of Tor Browser for Android[7], improved security settings accessibility[8], and compatibility with Firefox's Photon user interface[9][10]. Tor Browser 9.0a1 picked up the fixes that went directly into 8.5 and were not available in the alpha series before. Moreover, it's the first alpha that updated parts of our compile environments[11] for our Firefox ESR transition. Apart from release related work we made progress with enabling accessibility support for Windows users again[12], even though we did not manage to finish that work by the end of May. We are confident to have the final patches ready in June, though. Additionally, we started to work on our toolchain update for Firefox ESR 68[13] and rebasing our patches[14]. We were close as well to get Snowflake for Android integrated[15] into our build system and hope to finish that work in June, too. The full list of tickets closed by the Tor Browser team in May is accessible using the `TorBrowserTeam201905` keyword in our bug tracker.[16] Apart from finishing up our patches for the Windows accessibility bug and the Snowflake integration mentioned above we'll mostly continue working on our toolchain and patch rebasing for ESR 68. If all things go well we'll have some substantial progress for onion service authentication support in the browser by the next monthly report, too.[17] All tickets on our radar for this month can be seen with the `TorBrowserTeam201906` keyword in our bug tracker.[18] Georg [1] https://blog.torproject.org/new-release-tor-browser-809 [2] https://blog.torproject.org/new-release-tor-browser-85a12 [3] https://blog.torproject.org/new-release-tor-browser-85 [4] https://blog.torproject.org/new-release-tor-browser-90a1 [5] https://blog.torproject.org/noscript-temporarily-disabled-tor-browser [6] https://hacks.mozilla.org/2019/05/technical-details-on-the-recent-firefox-a… [7] https://trac.torproject.org/projects/tor/ticket/5709 [8] https://trac.torproject.org/projects/tor/ticket/25658 [9] https://trac.torproject.org/projects/tor/ticket/25702 [10] https://trac.torproject.org/projects/tor/ticket/28622 [11] https://trac.torproject.org/projects/tor/ticket/29307 [12] https://trac.torproject.org/projects/tor/ticket/27503 [13] https://trac.torproject.org/projects/tor/ticket/30321 [14] https://trac.torproject.org/projects/tor/ticket/30429 [15] https://trac.torproject.org/projects/tor/ticket/28672 [16] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [17] https://trac.torproject.org/projects/tor/ticket/30237 [18] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

April and May 2019 report and June 2019 plans for the metrics team
by Karsten Loesing 14 Jun '19

14 Jun '19

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in April and May 2019 as well as a few expected highlights for the current month, June 2019. On behalf of the Tor metrics team, Karsten April and May 2019: Blogged about Collecting, Aggregating, and Presenting Data from The Tor Network [1] which concludes sponsored work [2] to document our pipeline and identify areas that could benefit from modernization. [1] https://blog.torproject.org/collecting-aggregating-and-presenting-data-tor-… [2] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor13 Update OnionPerf circuit round-trip latencies graph [3] to contain lowest and highest values that are not considered outliers, similar to the whiskers in a box plot. [3] https://metrics.torproject.org/onionperf-latencies.html Added a new graph on OnionPerf throughput [4] including lowest and highest values that are not considered outliers. [4] https://metrics.torproject.org/onionperf-throughput.html Discussed including more detailed error codes [5] in OnionPerf's .tpf file output to better distinguish reasons behind failures and timeouts. [5] https://bugs.torproject.org/29787 Started archiving bandwidth files [6, 7] from bandwidth authorities. [6] https://metrics.torproject.org/collector.html#type-bandwidth-file [7] https://metrics.torproject.org/collector/archive/relay-descriptors/bandwidt… Started improving operational monitoring of Tor Metrics services [8]. [8] https://gitweb.torproject.org/user/irl/metrics-cloud.git/ Put out new releases [9]: metrics-lib 2.6.0/2.6.1/2.6.2, CollecTor 1.9.0/1.9.1, ExoneraTor 4.1.0. [9] https://dist.torproject.org/ June 2019: Attend Mozilla All Hands to further discuss Tor performance and scaling topics and the role of the metrics team in future measurements and evaluations. Import Tom's existing archive of bandwidth files [10]. [10] https://bugs.torproject.org/21378

1 0

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

13 Jun '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-13-17.00.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday June 13th 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. --------------------------- ---- 13th June 2019 ---- --------------------------- == Announcements == * == Discussion == * How should we proceed with our BridgeDB statistics collection? * We now have a response from Tor's safety board: https://bugs.torproject.org/9316#comment:25 * Let's run an initial one-off experiment for one week and re-evaluate if the data is safe to publish? == Actions == * Please share your experience with the pluggable transports specification in this thread: * https://lists.torproject.org/pipermail/tor-dev/2019-June/013879.html * Think about anti-censorship sessions you want to lead/attend in Stockholm * https://pad.riseup.net/p/_kDAK09C16xL2lBRQ7sJ == 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: This week (2019-05-16): - Revised gettor code with phw - Merge new code - Deploy gettor - See who has access to gettor repository in torgit - Sync torgit repository with dip - Port tickets from roadmap to dip Next week: - Add more tests to gettor - Work on twitter distribution channel Past week: - Rebase gettor PR with phw - Started testing framework phw: This week (2019-06-13): - Wrote and deployed patch for BridgeDB to discontinue email support for Yahoo accounts https://bugs.torproject.org/28496 - Merged and deployed BridgeDB translations https://bugs.torproject.org/30157 - Merged and deployed various BridgeDB housekeeping patches https://bugs.torproject.org/30706 - Released BridgeDB v7.0 and v7.1 and blogged about it https://blog.torproject.org/new-release-bridgedb-071 - Heard back from Tor's safety board regarding our BridgeDB proposal https://bugs.torproject.org/9316#comment:25 We can proceed carefully - Wrote a BridgeDB patch that replaces leekspin with a stem script https://bugs.torproject.org/22755 - Filed a ticket and wrote patch because default obfs4 bridges in orbot are all offline https://bugs.torproject.org/30870 - Filed ticket to study if China broke any of our bridge distribution channels https://bugs.torproject.org/30872 - Reviewed #29279 and wrote summary of what we learned - Asked tor-dev@ about shortcomings of our pluggable transports v1.0 spec https://lists.torproject.org/pipermail/tor-dev/2019-June/013879.html Pointed several PT implementers to this thread - Reviewed Nima's patch for obfs4PortScan https://github.com/NullHypothesis/obfs4PortScan/pull/1 - Had a brief meeting with researcher who's studying the GFW - Sponsor 28: Pointed RACE integration team to our PT spec and libraries - Reported machinery that our team is using to sysadmin team - Set up a private obfs4 bridge and handed it to censored user - Reviewed two FOCI papers Next week: - Move forward with new PT spec - Review #21315 Help with: Gaba: Last week: * follow on s28 and s30 This week (05/30): * preparing tor meeting schedule ahf (will be AFK due to Ascension Day here in DK) Last week: - Uploaded rebased patches for #29736, #29207, and #29260 at https://github.com/ahf/snowflake/tree/features/websocket_r5 - Been playing around with a method that I think will allow us to load shared libraries of PT's for Tor (on Linux only for now). - Hacking on #28930 - Got OK from dcf on #28849! Thanks! Next step is to talk to the PT adapter person. This week: - Hacking on #28930 - Prepare presentation for some conference next week in Switzerland. - Away Thursday/Friday for "Ascension Day". kat5: Last week (May 20): - Added more content from tickets - Added Tails content This week (May 27): - Marked finished sections complete - Final edits - Hand off for submission to DARPA - NEEDS HELP: - Sign-off from phw dcf: 2019-06-13 Last week: - dealt with some Azure CDN billing issues - Metrics Timeline maintenance - tried archiving some early pluggable transports browser bundles but encountered problems (https://bugs.torproject.org/29697#comment:12 ) Next week: - look at WebExtension changes in https://bugs.torproject.org/23888#comment:24 - look at reliability layer (#29206) - publish post-sanitization broker logs (#30731) - add resources I manage to the infrastructure survey Help with: cecylia (cohosh): last updated 2019-06-13 Last week: - reachability tests: - stopped obfs4 probes - updated results for snowflake probes (#30368) - snowflake - determined missing mingw libraries for windows build (#25483) - re-evaluated broker stats and implemented missing pieces (#21315) - started implementing unit tests for proxy-go (#30867) Next week: - update default STUN configuration (#26348) - continue increasing test coverage for snowflake (#29259) - expand snowbox to simulate censorship events for user experience testing - familiarize self with PT spec Help with: - incremental review of reliability layer (#29206) - broker stats (#21315) needs both a metrics team and a code review - browser team help for mingw toolchain (#25483) catalyst: week of 06/06 (planned): - unparent open children of #28018 and tag them usefully, so we can close #28018 week of 06/06 (actual): - rearranged bootstrap tickets somewhat, including unparenting open children of #28018 week of 06/13 (planned): - mostly focusing on sponsor31 arlolra: 2019-06-06 Last week: - nothing This week: - get back to the snowflake webextension Help with: - nothing

1 0

Tor Browser team meeting notes 10 June 2019
by Georg Koppen 10 Jun '19

10 Jun '19

Hello! Our weekly Tor Browser meeting just ended. The IRC log can be found at http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-06-10-17.31.l… and the contents from our pad are: Discussion: - Reminder: The monthly Tor/Mozilla meeting is tomorrow at 8 AM Pacific Time / 11 AM Eastern Time 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). - Helped with bug triage: - #30565 (Corrupted Linux 64bit browser). - #30718 (Tor is inconsistent on virtual disk drives) - #30732 ("Your Firefox is critically out of date" banner). - Thought about how to test the fix for #18101 on macOS (IP leak from Windows/macOS UI dialog with URI). 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). - Maybe: #29197 (remove use of overlays from Tor Launcher) - Maybe: #30429 (ESR 68 Rebase — updater patches). sysrqb: Last week: Rebasing mobile/ commits onto FF68 branch Some BridgeDB reviews Updated only-private-tabs on Android (#24920) Filed "Begin bootstrapping immediately after success" (#30756) Stumbled over "search.disconnect.me don't work for a long time now" during rebase (#27437) Some alpha release prep This week: Understand why the new alpha release is rejected by Google Play and resolve it. (GeKo: We'll block the mobile part of the release but proceed with the other platforms) Alpha release More rebasing and begin testing FF68 branch Fastlane (#26844) F-Droid (#27539) Bug fixing boklm: Last week: - helped with publishing 8.5.1 - helped with building 9.0a2 - made patch for #30779 (OpenSSL 1.1.1c is not built reproducibly) - worked on #28672 (Android reproducible build of Snowflake): finally managed to build some snowflakeclient.aar file. I still need to clean-up patches, and find where the snowflakeclient.aar file should be put. This week: - help with publishing 9.0a2 - try to finish #28672 (Android reproducible build of Snowflake) - look at remaining failing testsuite tests - update patch for #30549 (Add script to remove expired sub-keys from a keyring file) after review acat: Last week: - Rebased onion security expectation patch to ESR68 (#30429). - Found out some things preventing tbb-tests/mochitests from being run in ESR68 branch. - Some torbutton refactor work. - Pushed patch to https://bugzilla.mozilla.org/show_bug.cgi?id=467035, but changes will be needed. - Built rebased ESR68 with GeKo's linux_esr68_v6 tor-browser-build branch. Next week: - More #30429 work (patches remaining, find out why themes extensions are not installed...) - Fix patch for 467035. - torbutton cleanup/refactor/integration work (#28745, #10760) pospeselr: Last week: - fixed macos icons for #30631 (blurry tor browser icons in macOS chrome) - finished rebasing widl changes into a digestable patch chain, submitted to wine-devel dev list for review - squashed widl changes into a patch for mingw and put up a patch for tor-browser-build - changes cause crash on 64-bit windows (both 64-bit tor browser and 32-bit tor browser runing WoW which is surprising) - got my functional ia2 test working on 64 bit windows - initial investigation here indicates likely another typeformat string issue (the generated code that's used to determine data marshalling logic at runtime) This week: - replicate my debug environment in 64-bit and fix this 64 bit issue - update tor-browser-build patch tjr (very little) - Planning for Whistler - Confirmed we still have an x86 crash in mingw-clang (Bug 1547519) after glandium's work. This is high-concern, going to follow up with him GeKo Last week - helped with releases - reviews (#30779, started with #27503, #30631, #24920) - looked at #10760 and started with reviews for for the rebase work - finally figured out why rust barfed during esr68 build (still need to update #30321 with that fun bug) - going over blog comments and filed tickets where needed - HackerOne bugs - started to plan work for June This week - finish review of #10760 and #30429 - figure out 32bit Linux build issues for esr68 branch (part of #30321) - help with releases where needed - Whistler prep - planning work for remaining June Georg

1 0

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

10 Jun '19

Hi! You can find our meeting logs at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-10-17.00.html Here are the contents of our meeting pad for this meeting: = Network team meeting pad! = This week's team meeting is at Monday 10 June at 1700 UTC on #tor-meeting on OFTC. June schedule: * Monday 10 June at 1700 UTC * Monday 17 June at 1700 UTC * Monday 24 June at 1700 UTC July schedule: * Wednesday 3 or Thursday 4 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: Tuesday 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.) 13 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002325.html 20 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002335.html 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 == 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. ------------------------------- ---- 10 June 2019 ------------------------------- == Announcements == [INFRA INVENTORY] Sysadmin Team is asking for people at the Tor project to fill information about resources they are using right now. Please add your resources: https://nc.riseup.net/s/QEM4MNBA8MmWW4x purpose (e.g. service running) location (e.g. hetzner, amazon, etc) age/lifecycle (e.g. 2008, ephemeral containers, etc) memory (e.g. 24GB RAM) disk (e.g. 2TB SSD or HDD) cores (12 CPU) cost (100$USD/mth) [INFRA] Do you have problems with email? Please report any problem (or not) that you may have here: https://trac.torproject.org/projects/tor/ticket/30608 (also https://help.torproject.org/tsa/doc/reporting-email-problems/) [PROCESS] Please comment on CI role's proposal from Teor: https://trac.torproject.org/projects/tor/ticket/30759 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. == Discussion == Creating the agenda for Tor meeting. This year we only have 3 days and we need to go through a process of selection of which sessions we want to have. Which sessions you are all thinking are important to have in the face to face meeting? https://pad.riseup.net/p/_kDAK09C16xL2lBRQ7sJ Rotation updates: (CI/coverity teor->ahf; bug triage mikeperry->nickm) See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… . coverity (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) jenkins (seems ok) Travis Stem failure is happening very frequently. Test_rebind failure less so. teor wrote patches to: allow failures for stem, and disable test_rebind on Travis macOS using an env var Appveyor (seems ok) Bug triage Can we move the patch party and first team meeting of the month to Wednesday or Thursday 2300 UTC ? (ahf: +1 for Thursday, I already have the anti-censorship team meeting there, so I keep that night off in the calendar, also OK with Wednesday.) [catalyst: Wednesday 2300 UTC works better for me; i have a periodic conflict with Thursdays at 2300 UTC] teor would like to have their Wednesdays off (UTC+10). nickm has no objection to any particular 2300 UTC except Friday. * https://pad.riseup.net/p/54diULYSxeRrckkdKdOQ -- Nickm asks if we should send this to the relevant dirauth operators. It is a list of Tor versions that we should un-recommend. == 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): . check sponsor V work until now . stockholm meeting planning This week (planned): . more stockholm meeting planning . scalability meetings Help with: . moving sponsor 19 tickets (https://pad.riseup.net/p/x3G09tvOfODGflMcjW83 ) . please add sessions to the stockhom meeting pad this week as it may be harder to fit in things later teor: (offline at the usual meeting time) Week of 3 June (planned): Urgent: - 041-must - Quick CI fixes, disable failing tests and document them - code reviews - Help close Sponsor V - Help close Sponsor 19 - Fallback directory mirror list rebuild - HR stuff Important: - chutney merge backlog (blocked on stable Tor CI) - merge add chutney to tor's CI (blocked on stable Tor CI) - backport backlog (blocked on stable Tor CI) Week of 3 June (actual): - It is flu season, looks like it got me, took some time off Urgent: - HR stuff - Decided to defer PrivCount until we have specific funding. (It was Sponsor V, but we ran out of time.) - Quick CI fixes, disable failing tests and document them - code reviews: chutney, docs, etc. - Help close Sponsor V - some progress on Fallback directory mirror list rebuild Important: - sbws triage: - it is probably safe to deploy sbws to one more authority (we now have 2, we can have 3) - identified 4 blockers for deploying sbws to more than 3 authorities - worked on deployment and comparison plan - reject bridge descriptors on authorities (#16564, Sponsor 30) - also did some refactoring to make practracker happy, but now the file is bigger - found and fixed #30782, to make authorities cache fetched outdated descriptors - did some backport triage - tor bootstrap sometimes hangs (#21969, #16844), it's complicated, looks like we need a proposal (#30817) - merged chutney merge_ready tickets - re-did chutney #30279 and #30820 because they didn't work Deferred: - stem CI logging fixes, because the control messages are not in the log (or stem hangs before logging them) Week of 10 June (planned): Urgent: - Fallback directory mirror list rebuild (#28793) - Get gus access to the fallback-scripts repository - Help close Sponsor 19? - code reviews - More HR stuff Important: - work out which roadmapped work to do next: - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - off-by-default module practices (#29224) - remove unneeded dependencies for tor roles: client, relay, etc. (#29227) - merge add chutney to tor's CI (blocked on stable Tor CI) - backport backlog (blocked on stable Tor CI) - work on stem CI hangs? - revise reject bridge descriptors on authorities (#16564) - improve documentation for chutney warnings in make test-network-all (#30455) Low-Priority: - document disabled CI (#30745) - revise tor_addr_port_lookup() is overly permissive (#30721) Week of 10 June (actual): Urgent: - Important: - Low-Priority: - Nick: Week of 3 June (planned): - Release 0.4.1.2-alpha - Possibly, release 0.4.0.6 - Open tickets from team retrospective - Try to finish 041-should items - Try to solve CI failures. Week of 3 June (actual): - Finished most 041-should items - Opened tickets and did followup from retrospective - Worked on analysis for walking onions paper - Released 0.4.1.2-alpha - Worked on handle refactoring (29218) - Other review and merges Week of 10 June (planned): - Open 0.4.2. - Deprecate 0.3.4. - More analysis for walking onions, time permitting - Review and merge - Revise chutney/CI improvements: - 29280 (Use Chutney in Tor's CI) - 29024 (chutney and PTs) - 30459 (Let chutney tell Tor whether a network is supported) - Finish handle refactoring and cleanup (29218) - Plan configuration refactoring - More modularization? Mike: Week of 6/03 (planned): - More scalability followup (KIST+EWMA+sbws -> wiki; metrics updates; Mozilla all hands meeting planning) - Peer feedback - Register for PETs - #30649 - Circpad documentation? Week of 6/03 (actual): - Laptop issues - More scalability followup (KIST+EWMA thread; funding meeting; metrics categories) - work on circpad relay-side warn log bug (https://trac.torproject.org/projects/tor/ticket/30649) - Work on #29034 (hs circuit re-purpose leaks) - Code reviews Week of 6/10 (planned): - Mozilla all hands planning/discussion - Scalability metrics review/page reorg - Peer feedback - Register for PETs - Circpad documentation? catalyst: week of 06/03 (2019-W23) (planned): - reviews - rearange bootstrap tickets more logically - teor's on CI rotation but i can try to help with CI stuff, especially our persistent spurious failures week of 06/03 (2019-W23) (actual): - reviews - medical and financial bureaucracy - tried and failed to find an easily configured SOCKS5 proxy daemon that requires auth (as part of a patch review) - rearranged bootstrap tickets more logically -- unparanted still-open children of #28018, etc. week of 06/10 (2019-W24) (planned): - reviews - some sponsor31 tickets 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. ahf Week of 3/6 (planned): Network team: - Hack on #28930. - Talk with traffic-obfuscation list people about #28849 - Talk to Cecylia and dcf about patches for #29736 and friends. Misc: - End of month tasks. - At a conference Wednesday and Thursday in Switzerland doing a presentation on Tor. Week of 3/6 (actually): Network team: - Hacked on #28930. Misc: - End of month tasks: Harvest, etc. - Did a talk about Tor at a conference. They seemed excited. Week of 10/6 (planned): Network team: - Finish #28930. - Talk with traffic-obfuscation list people about #28849 - Talk to Cecylia and DCF about patches for #29736 and friends. Misc: - Presentation Thursday evening at the local union about Tor. - CI/Coverity role. 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: Week of 06/03 (actual): - Call with asn on #15516 next steps. - Unit testing on #30382 - tor-scaling discussions. - Some urgent work on #30771 and #30775 041-alpha2 release blocker. - Review s27 tickets: #30381 - Started sketching some ideas for #30790 - Got my brain smashed by #30628 issue. Fortunately, fixed now! - Emailed a big HS operator for some introduction stats in order to learn more to make a better choice on #15516 parameters. - prop304 is in tor-spec.txt! :) - Some merges and reviews. Week of 06/10 (planned); - Continuing s27 work on the anti-DoS side. - Add consensus params for #15516 and hopefully propose baseline values. - Hope to get #30790 in a Draft state. - 042 window is opened so some merges need to happen in master.

1 0

May 2019 report for the UX team
by Antonela Debiasi 07 Jun '19

07 Jun '19

Hello Tor o/ #S27 During May, we continued working on S27. After the official kick-off last month, we've worked on the two new Tor Browser features we want to achieve for this sprint: onion-auth and onion prioritization. You can follow our work on the relevant tickets: https://trac.torproject.org/projects/tor/ticket/30024 https://trac.torproject.org/projects/tor/ticket/30237 #User Research dunqan has been working for a few months now to consolidate our first Tor users Persona tool. We are planning to have a session during the next dev meeting to introduce this tool to the teams and collect feedback for the next iteration. https://lists.torproject.org/pipermail/ux/2019-May/000449.html #Community Portal The community portal is taking shape. We are still writing and reviewing content, fixing UI bugs, and polish the mobile view. You can sneak peek our progress here https://community.torproject.org/ Clash gave us support on the various front last month. The most relevant was the help in updating our training material for the community portal. Thanks, Clash! #Tor Browser 8.5 The last week of May, Tor Browser 8.5 was released. It included the new UI for security settings, the new app icon, and four new locales: cs, el, hu, ka. This release also made available a stable version for Tor Browser in Android. There is a lot of work to do yet, but we are proud to offer this efficient way to connect to the Tor network for mobile Android users. https://blog.torproject.org/new-release-tor-browser-85 #OONI After the OONI Explorer Beta release, we have been working on prioritizing the features we want to get done for the stable version and supporting the design needs. Thanks, A

1 0

Notes from June 6 2019 Vegas team meeting
by Karsten Loesing 07 Jun '19

07 Jun '19

Notes for June 6 2019 meeting: Gaba: 1) Untagging remaining tickets from sponsor 19, looking for s19 tickets for new sponsors (phw and network team working on it) and updating roadmaps. The same with sponsor V. 2) Added sponsor 28 and 30 to trac. Going through checklist of new grants. 3) OONI meeting to update roadmap. 4) Creating the agenda for Tor meeting. This year we only have 3 days and we need to go through a process of selection of which sessions we want to have. Add the sessions you are all thinking are important to have in the face to face meeting. Thoughts on how to select/prioritize sessions? https://pad.riseup.net/p/_kDAK09C16xL2lBRQ7sJ 5) [INFRA INVENTORY] Sysadmin Team is asking for people at the Tor project to fill information about resources they are using right now. Please ask your team to add the resources they are using: https://nc.riseup.net/s/QEM4MNBA8MmWW4x - purpose (e.g. service running) - location (e.g. hetzner, amazon, etc) - age/lifecycle (e.g. 2008, ephemeral containers, etc) - memory (e.g. 24GB RAM) - disk (e.g. 2TB SSD or HDD) - cores (12 CPU) - cost (100$USD/mth) 6) helping with grant application 7) meeting with simple secure about new metrics data portal 8) meeting to talk about scalability projects for funding 9) looking at capacity starting in july for sponsor work Pili: 1) Helping Season of Docs candidates with their proposals 2) Polishing up Community Portal before sharing for feedback 3) Looking at different Open Source initiatives to attract volunteers and/or committers. 4) Helping with Tor meeting agenda 5) Updated New Grants Checklist and added template for project kick off meetings 6) UX Ticket triage 7) S27 meeting 8) Tor Browser Release meeting Nick: 1) another alpha release came out 2) another stable soon, after alpha has seen more testing Mike: 1) Tor-scaling making progress towards Mozilla all-hands 2) Helping with 0.4.1 fixes Karsten: 1) Updated circuit round-trip latencies graph to include worst-case latency: https://metrics.torproject.org/onionperf-latencies.html 2) Added throughput graph including worst-case throughput: https://metrics.torproject.org/onionperf-throughput.html 3) Merged OnionPerf branch to include more detailed error codes in .tpf files for later analysis and/or visualization. Antonela: 1) did frontend work for the community portal 2) working with OONI - OONI Explorer issues review, prioritization toward stable - reviewing tickets that require UX efforts for this month 3) supported the Pride Month initiative by the comms team 4) sent RSVP to OTF invite for the Taiwan summit 5) working on TBA - reviewing #24920 and #30540 6) working on S27 - will meet syverson_ next week to discuss/learn about his ideas for O2A3 7) working on Defenders of Privacy campaign for the fundraising team 8) made assets for the Bug Smash Fund campaign for the fundraising team Erin: 1) General HR stuff Anarcat: 1) hardware survey in progress 2) pushed back on request to open SMTP authentication with request for concrete bug reports of delivery failures 3) usual sysadmin stuff

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project