- tor-project - lists.torproject.org

Tor Browser team meeting notes, 16 July 2018
by Georg Koppen 17 Jul '18

17 Jul '18

Hi all! We had another Tor Browser meeting yesterday. The IRC log can be found at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-07-16-18.05.log… and here come, as usual, the meeting notes from our pad: Monday July 16, 2018 Discussion: - I think the Sandboxing Meeting is scheduled for next Tuesday 15:00 UTC? (GeKo: Yes) - We should think about possible sessions we could offer for the mexico dev meeting open days; we'll have a talk about Tor Browser 8 then (please volunteer if you want to do the talking part) but I think we are a big team with lots of things going on and we could contribute more - mcs: some ideas: UX changes in Tor Browser 8, a design overview (aka “How is Tor Browser different from Firefox?”), sandboxing futures. - arthuredelstein: I'd like to talk about browser privacy testing (For Tor Browser and other browsers with "Tor mode") - Tor Browser on Github? boklm: Last week: - reviewed #26355 (Make sure only Windows users on Windows7+ are trying to use Tor Browser based on ESR60) - reviewed #26251 (Adapt macOS snowflake compilation to new toolchain) - made patch for #26569 (Redirect pre-8.0a9 alpha users to a separate update directory) - looked with sisbell at list of things to do to integrate Tor Browser for Android into tor-browser-build and opened some tickets: #26693, #26695, #26696, #26697 This week: - on vacation sysrqb: Last week: Investigated report of proxy-bypass (#21863) Investigated Android APK signing key (#26536) Discussed and researched some Android localization with Emma (#26536) Helped with BridgeDB things Prepared HOPE presentation slides for talking about Tor Browser, TBA, and Tor on Mobile Scheduled Sandboxed Tor Browser meeting on next Tuesday, 24 July at 15:00 UTC This week: Helping talk about Tor with high schoolers on Monday Talking at HOPE on Friday with other Tor people tjr: - Worked on #26476 with sukbir a bunch. Currently blocked on needing to increase the file descriptor ulimit inside the container. Don't know how. - I've tried increasing the ulimit for user account and root on the host; but it did not propagate into container. - We know the issue is --gc-sections, we don't know why it happens to Tor and not Mozilla; we're investigating that. (It's not the sandbox or any Tor patches.) - Jacek finished his contract: - He got --enable-stylo working: https://reviewboard.mozilla.org/r/256840/diff/1#index_header - He landed most of his patches into -esr60 - I have a few more to land for him, plus the build job - Not done for mingw-clang: --enable-sandbox, x86, debugging pdbs - I need to investigate test failures for the x64 build, and then I can land that in esr60 - I am getting fuzzyfox reviewed, and then we could experiment with it maybe GeKo: Last Week: -Vacation This Week: -Deal with my backlog -Help with the mobile alpha release as needed -Finish investigating Stylo related reproducibility issues on macOS (#26475) -Continue network review (#22176) -reminder to do the status: updates at least daily -reviews -Is there anything anybody needs from me urgently? (igt0: Not urgent, however I believe #26401 has high priority) (GeKo: Yes, I finish my comments tomorrow) pospeselr: patch for #26456 (HTTP onion sites inheriting HTTPS certs) could use a review (GeKo: that's on my list for tomorrow, too) Last Week (s): - found a potential solution for #26540 (pdfjs FPI violations) and have a patch up little janky, people should definitely take a look at it - needs to be tweaked for multi-process (ie browser.tabs.autostart = true) - medical stuff - took care of a bunch of moving related bs This Week: - partial vacation in Portland this week, working mornings in cafes - fixup #26540 patch - #25555 looks like interesting, so I'll grab that one (reimpleent Optimisitc SOCKS feature) Next Week: - moving apartments (hopefully) on the 24th, I'm sure there will be tons of problems to deal with/people to yell at but we'll see igt0: Last Week: - Took a look in the tor browser settings: #26574 - Fixed a typo in the mobile addon handler: #26704 - Tested torbutton functionalities on mobile: domain isolator, dragDropFilter, content-policy - meeting about TBA release This week: - More preparation for TBA release arthuredelstein: Last Week: - Patches for: #26590 (SVG isn't blocked in Safest security setting with 8.0a9) #26603 (remove obsolete http pipelining prefs) #26353 (speculative connect violating FPI) #26237 (fix ordering of toolbar) - Investigated: #18598 (disabled WebSpeech by default) #16339 (ensure ImageCapture API is disabled) - Proposed #26765 (Add Tor Browser indicator where Firefox PB indicator is) - Worked on my HTTP2 patch #14592, in progress This week: - Keep working on #14952 - More fingerprinting / ff60esr patches Following week: - I will be on vacation week July 23 - 27. Am I the only one who finds this sandstorm document very hard to use? Wondering if I'm doing something wrong or if we could switch to an etherpad. (GeKo: There are more folks that seem to apply workarounds. Let's resume this discussion once everyone was able to think about it) sisbell: Last Week: Got android and build dependencies in build container for RBM build Added stretch for containers This Week: Get Android license acceptance working in build Get mach build commands working on container build sukhe: Last Week: - I am still working on #26476 (crash on Windows) with tjr and #12968 (HEASLR). Picked up #26251 (Snowflake) again. - Since these all are blocking currently, is there anything else I can focus on in the meantime? (GeKo: Yes, #25485 would be helpful) This Week: - Continue the above and find something else to work on based on "Last Week" isabela: - request (about TBA release) Georg

1 0

Network team meeting notes, 16 July 2018
by Nick Mathewson 17 Jul '18

17 Jul '18

Hi! Our meeting transcript is at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-07-16-17.01.html Below are the notes from our pad = Network team meeting pad, 16 July 2018 = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) == Previous notes == 11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html 18 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001835.html 25 June: https://lists.torproject.org/pipermail/tor-project/2018-July/001863.html 2 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001866.html 9 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001884.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! [but see discussion] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == Announcements == * 035 triage has happened; we may need another round, though. * HOPE is this week; some folks are (or will be) offline. * PETS is next week; some folks will be away. == 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 == Discussion == * Should we schedule meetings for these? * Discuss prop 295 (New crypto from Tomer Ashur et al) {actually, let's see what we think after Tuesday's patch-party time.} * Revise roadmap to match current staffing. * 035-roadmap-proposed items (Backlog seems significant-ish) * Shall we just use the same pad, week after week, rather than creating a new one each week? teor: works for me, but how do we get rid of old content? dmr: can just move it below, or delete it (tbb-team just moves it below) asn: reasonable idea! (if this software had tabs we could even make a new tab for each meeting) ahf: Cool with me. I think we made a new one out of concern for vandalism? dgoulet: I don't mind but lets remember that Riseup pad expire so as long as we send the report regurlarly on tor-dev@, I'm ok! dmr: I think as long as the pad is constantly used, it won't expire == Updates == Nick: * Last week: * Merged a bunch of merge-ready stuff * Reviewed SOCKS refactor/trunnel patch from rl1987 again; added fuzzing support to test it. * Finished some post-refactoring cleanup work. * Released 0.3.3.8 and 0.3.4.4-rc * Cleared through my fast-fix items for 0.3.5 * Helped find and diagnose an apparent configuration bug in sid's clang that was making some clang jenkins builds fail. * Wrote up first draft of templates for announcements * Experimented with porting tor crypto to NSS. Some progress made; digest and rand are ported. (How) should I procede? * Added more guidelines about what is _not_ supported long-term in LTS releases. * This week: * TBD depending on roadmap revisions * PETS discussions. * CI rotation * More NSS, possibly? teor (offline): last week: - Reviewed removing Tor2web mode (#26367) - Dealt with my bwauth backlog (I think! pastly and juga please let me know if I missed anything) - Bwauth code and spec reviews and fixes (#26694, #26740, #26694, #3723) - Bwauth documentation (#26702) - Chutney bwauth network (#26801) - More work on the sbws bandwidth measurements https://github.com/pastly/simple-bw-scanner/issues/182 - Trac spam - Tried to work out why Travis builds are leaving a coredump behind (#26787/#26788) - Email and IRC backlogs - More setup tasks & admin this week: - Book Mexico travel - Work out timesheets - Fix and test an onion service ed25519 id mismatch bug (#26627) - Finish PrivCount in Tor blinding and secret sharing branch (#25669) - work out what to do about Rust i128 miscompilation - Implement PrivCount in Tor noise (#26637) - Work out if I need to test C code from Rust (#26398) - Work on a per-relay / per-consensus / per-counter noise spec for PrivCount in Tor (part of #25153) - Reduce my other review and revision backlogs, if I get time Mike (maybe offline?): last week: - Vangaurd post ready - Research post half-ready This week: - Finish & post research post - Make pip packages for vanguards; post asn: Last week: - Reviewed vanguard blog post by Mike. Also made some drawings that could be used. Let me know what else is there to be done, Mike. - Made some final touches to vanguard proposal. Mike: it's still not merged. Let me know if you want me to merge it. - Revised #25552 based on Nick's review, and found an important bug during log analysis. I've since fixed the bugs and been testing the branch. It works really great. - Spent some time discussing client auth and revising HSv3 spec to fit the UX we are looking for. Useful decisions were reached. - Prepared HOPE slides with David. - Reviewed #26663 - Opened some hsv3 tickets #26769, #26768. This week: - Finalize #25552 branch. - Meet with Isa in NYC and fix up the onion service proposal. - Finalize prop224 spec wrt client auth. - Publish vanguard blog post. - Will be on the Tor panel at HOPE conf. haxxpop: Amazing!, I will wait to watch your presentation on Youtube! - Catch up with [tor-dev] UX improvement proposal: Onion auto-redirects using Alt-Svc HTTP header ahf: Last week: Sponsor 8: - Began rewriting transports.c to receive events from the event loop (should be last step before a merge) for bug #25502. - Filled out Isa's S8 Q2 reporting. Misc: - Attempted fix for a couple of Coverity errors in #26780. - Rebased #26437 to fix AppVeyor issue. - Lifted Linux specific Sandbox code into its own file. Began work on cleaning up configuration interface to work with MacOS too. Bug #26374 This week: Misc: - Make #24546 mergable after recent restrcture. - Harvest reporting. - Enjoy vacation in NY including going to HOPE. Back Wednesday the 25th. catalyst: Last week (2018-W28): - community guide rotation -- opened #26785 for a gcc warning disabling issue; shepherded #26492 somewhat - reviewed a few tickets related to Rust builds - wrote more stuff in the github strategy doc This week (2018-W29): - bug triage rotation - code review - ping a few people about big patches doc - swap in stuff about bootstrap-related roadmap items haxxpop: Last week: - Discussed with asn dgoulet and nickm about client auth spec This week: - If the client auth spec is finalized, I will fix and rebase my client auth PR dgoulet: Last week: - Worked on #20700 HSv3 client authorization specification along with haxxpop, asn and nickm. - Patch for #26367 which is the removal of Tor2web (roadmap item). Now in merge_ready. - Reviewed the remaning code refactoring tickets from nickm. - Worked on the slide for our HOPE talk. - HSv3 reachability issue that I might have found the problem on Saturday! See #26709 for the gist of my findings. Running an experiment. - Worked with Roger and gman to help with the new Bridge Authority setup. This week: - I leave for NY (HOPE) on Wed morning so I'm here today and tomorrow. haxxpop: Amazing!, I will wait to watch your presentation on Youtube! - Do as much as possible onto #20700 before meeting asn f2f to discuss outstanding issues. - Try to fix the two HS important issues we have namely #26709 and #26806. - I'm Community Hero this week but most of it will be at HOPE eheh... - I'll need to switch with someone next week for Bug Triage, I won't be there. isabela: reiviewing pm candidates thanks for the information about sponsor8 work on Q1 o/ I will compile all answers received from network folks for the github survey and start oganizing all the teams answers so a proposal can come out of it picking up the onion services proposal this week (trying to get it done before hope) on vacation next week o/ i am thinking of a possible plan to get modularization phase1 (1year of work) payed by a different sponsor (from the one we already applied this project proposal and has been on review for a looong time already) dmr: - not sure whom to talk with, to get a mirrored nyx repo on GitHub - would like to discuss best way to manage several minor improvements to torspec WIP branch: https://github.com/dmr-x/torspec/commits/WIP-torspec-improvements

1 0

Notes from July 12 2018 Vegas team meeting
by Karsten Loesing 13 Jul '18

13 Jul '18

Notes for July 12 2018 meeting: Roger: 0) new bridge auth, and with luck new bridgedb operator 1) fosdem plans? (belgium invite) Nick: 1) Nothing new since last thurs. 2) I'll need to know more about the how & when of the bridgeauth change. Mike: 1) Nothing new for the group isabela: 1) Continue to review candidates for PM 2) Sent sponsor9 phase 2 plan - this week working on countries support doc to send by Friday 3) Getting started on onion services full proposal to OTF and collecting ideas for a proposal so OCF related to relay operators 4) Got NCE for Metrics team work with sponsor13 (new deadline is March 31st 2019) 5) Getting started on sponsor8 Q2 report (due end of July) 6) Prep-work for Tor Browser for Android alpha release [ https://storm.torproject.org/shared/HQq4zW-G7dcAHjDbzuRKShaDSr5-AizVeU4hzO2… ] 7) Finishing interviews and selection of Fundraising Director 8) Trying to get my visa application for Taiwan (OTF meeting) 9) Looks like the GNUHealth conference will indeed happen in November (I was invited to talk about how Tor can be useful for health care systems). 10) HOPE is next week! and the week after (Monday 23rd) I will be on vacation o/ 11) Does anyone has an idea for what do we use our current Azure account? I am looking into it to know if we can use that or need a new one to have Moat working w/ Azure Steph: 1) preparing for HOPE presentation and booth 2) preparing for presentation at NYU Tandon on Monday 3) helping with TBA copy 4) behind on blog posts 5) responding to an inquiry Shari: 1) catching up after a week out of the office 2) putting out job offer for new fundraising director 3) hopefully starting interviews for new project manager(s) 4) reviewing several grant reports/proposals due between now and end of month 5) signing a few NCEs and other important things Karsten: 1) Made a couple of Onionoo changes that we're planning to release and deploy early next week. 2) Started working on a grant proposal for metrics team work related to supplementary data about relays. Alison: 1) finalizing plans for HOPE 2) LFI is in week 6 3) preparing for LFI in-person weekend in August 4) Mexico City meeting planning 5) working on sponsor9 support doc 6) Colin is finalizing PETS plans 7) Gus is getting ready to go to Kenya Arturo: 1) Starting UX interviews next week 2) Making progress on OONI Probe desktop apps 3) Investigating case of Tor blocking in venezuela 4) Will start looking at the tor_api.h this week or the next 5) Updated South Sudan test list (based on research): https://github.com/citizenlab/test-lists/pull/366 6) Maria is giving a lecture about OONI in Kiev tomorrow, and she's facilitating an OONI workshop in Kiev on Saturday 7) Submitted footage and materials for OONI MOOC

1 0

[TSoP] stem.client - status report #4
by Dave Rolek 13 Jul '18

13 Jul '18

Hi everyone! This is my fourth status report for the stem.client TSoP project [1]. You may see my previous reports on the tor-project ml. [2][3][4] This report is much of a week late - I'm quite sorry about that. # Updates I've still been feeling ill, and it's been a bit unpredictable for when symptoms flare up, so that's been tough to deal with and work around. (I'm still moving forward, though, just not as effectively as I'd like.) Some of my progress comes in longer-term plans than I can effectively showcase here, but I'll try. ## GitHub mirroring I think #26197 [5] sparked a lot of discussion on Tor's use of GitHub as a mirror and means to accept PRs. Preliminary discussions when trying to move the ticket forward by bringing it up in a network-team meeting revealed a bit of uncertainty into how mirroring was done, and (iiuc) eventually led to Isa getting involved to survey all the teams on current and future usage. It looks like things are working out well for stem now :), and overall Tor's GitHub usage seems better understood and better standardized! (For instance, the most recent PR was marked as auto-merged/closed by 'torproject-pusher' today [6]) I'll continue to be involved as needed to facilitate stem and nyx needs w.r.t. GitHub repos. (Damian mentioned he's got a lot on his plate already and asked if I could take the lead on this.) nyx still doesn't have a repo, so I'll be sure to follow up on this. ## stem.client - re-roadmapping I continued to push some lingering things in code review [7] and architecture [8] discussions forward. That led to a reconsideration of goals and roadmap between Damian, teor, and me. Based on the primary goal of prototype allowing exit traffic, I've mapped out the main tasks of the remainder of the project as follows: 1. refactor: Relay cell encryption/decryption/processing 2. centralize ORPort reads/sends (demux/mux) at connection level 3. implement required RelayCell subclasses (e.g. parsing of decrypted body) 4. <potentially: other RelayCell subclasses> 5. use these RELAY cells in Circuit / Stream construction/management 6. re-envision Circuit.send() and other methods (e.g. Circuit.extend()) 7. refactor into Stream class, subclass(es) 8. introduce "dumb" path selection for exit traffic This roadmap will be re-evaluated as progress on #1-3 is made. ## stem.client - further review, fixes A few tickets/PRs have been done to follow up on Damian's changes [9], which followed up on the previous commits I did from code review. [10] These two tickets/PRs include bug fixes and some other improvements: * NetinfoCell doesn't preserve unused content during unpacking [11] * Cell unused content is ignored while packing [12][6] ## stem.client - RELAY cells I've started outlining the class hierarchy for the required RELAY cells, tackling roadmap items #1-3. It's still in very early stages, so I don't have changes ready to push. ## stem, general Nothing to show this time around. I've taken minor notes for 'dev' tickets, but I won't be pursuing much of these yet, in the interest of focusing on the roadmap first. ## tor protocol, general I'm still glancing through the tor-design paper [13][14][15] and updates [16][17][18] while reading the specification. I think I've read through enough of the paper now that I won't need to glance often, but I'm still keeping it in mind. As I've been working through the spec, I've been tracking changes to make that improve it. Some of these are just shorthand notes (so I don't have them available to share in an understandable way), but others have made it to (probably) solid commits. I've pushed a WIP branch to GitHub [19], which I will be rebasing / force-pushing as necessary. *Please* feel free to check it out - just don't rely on it to be git-stable. # What's next ## stem.client I'll be working on the roadmap mentioned above. The first thing I'll be working out into commits is moving some of the bytes-level handling of RELAY cells out of the Circuit class and into cell.py, since this handling currently seems to violate the abstractions we want. ## stem, general I still have a few 'dev' tickets I'd like to work on. For a while I've wanted to work on the tox configuration, but I may break that up into more important and nice-to-have changes to it. ## tor-spec As aforementioned, I'll continue to push forward on improvements to tor-spec.txt. Again, you may see what I've got mostly push-ready in my WIP branch on GitHub. I'll bring this up in the next network-team meeting and figure out the best logistics for merging these in. # Other Tor things Not too much on the side - still an advocate for Tor in-person when people chat with me, but it hasn't happened as much in the past few weeks. Still trying to attend the Community team meetings when I can. # Closing As with before, I've been active and reachable over IRC, where my nick is dmr. Please don't hesitate to reach out to me via IRC or email! I've been *much* less proactive in reading scrollback recently, in order to combat some of the reduced capacity due to illness. Please mention my nick if you'd like to get my attention, otherwise it's *very* unlikely I'll see it outside of a meeting! Thanks, Dave [1] https://lists.torproject.org/pipermail/tor-dev/2018-April/013090.html [2] https://lists.torproject.org/pipermail/tor-project/2018-May/001811.html [3] https://lists.torproject.org/pipermail/tor-project/2018-June/001830.html [4] https://lists.torproject.org/pipermail/tor-project/2018-June/001858.html [5] https://trac.torproject.org/projects/tor/ticket/26197 [6] https://github.com/torproject/stem/pull/5 [7] https://trac.torproject.org/projects/tor/ticket/26227 [8] https://trac.torproject.org/projects/tor/ticket/26226 [9] https://gitweb.torproject.org/stem.git/log/?id=3818cf41cae98ae7558f5002ef3a… [10] https://github.com/torproject/stem/pull/1 [11] https://trac.torproject.org/projects/tor/ticket/26684 [12] https://trac.torproject.org/projects/tor/ticket/26766 [13] https://www.torproject.org/docs/documentation.html.en#DesignDoc [14] https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf [15] https://svn.torproject.org/svn/projects/design-paper/tor-design.html [16] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-1 [17] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-2 [18] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-3 [19] https://github.com/dmr-x/torspec/commits/WIP-torspec-improvements

1 0

community team updates for May and June 2018
by Alison Macrina 12 Jul '18

12 Jul '18

May 2018 Community Team highlights Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Tor Meeting ================================================================= Mexico City meeting planners began having regular meetings to work out the details before the September meeting. Outreachy and Summer of Privacy ================================================================== Jaruga began working on cleaning up and improving documentation (her work can be tracked here [1], and Cy began working on collecting Tor user issues from around the web. Jaruga also identified major issues with Tor Wikipedia pages, and the community team discussed mitigation strategies. community.torproject.org ================================================================== We worked on modular Tor slides that will eventually live on the community portal, and we tested them out during the Uganda trip. Library Freedom Institute ================================================================== Alison worked on finalizing plans for LFI, which began on June 1. Tor talks and outreach ================================================================== Cryptorave took place on 5 and 6 May in Brazil with Isabela keynoting and 10 talks and activities about Tor and Tails. We worked on plans for the HOPE conference in NYC in July, organizing Tor talks, workshops, and a table. dmr's June event at the Ann Arbor Library was posted [2]. dmr is also planning some local events to take place around Aaron Swartz Day. Alison went to Uganda with Antonela as part of our combined community and usability team work. We met with local activists, human rights defenders, and digital rights organizations, did Tor trainings, collected user feedback, and incorporated what we learned into our work on the website redevelopment and usability improvements. We started scheming about an October NYC Tor meetup. Gus began planning for Tor events at FISL (International Free Software Forum) in Porto Alegre/Brasil this July. Relay advocate ================================================================== Colin began his new role as the relay advocate! He started by planning a relay operator meetup at PETS in Barcelona this July, handing off duties from his former role as support and translation coordinator, and introducing himself to all the relay operators. The biggest request he's heard so far from operators is that they want to see Tor Weather revived, so he's looking into that possibility. Colin's intro blog post for his new role is here [3]. Community liaison ================================================================== We conducted interviews for the community liaison position, and we are very happy that Gus (ggus) accepted the offer! His began by organizing the trip to Colombia with the usability team, creating the 2018 Global South events calendar [4], making preliminary plans for the Kenya trip, and working on plans for the Mexico City meeting. Other stuff ================================================================== We discussed changing the meeting time again to be more friendly to team members in South Asia. ================================================================== [1] https://tor.dial.ga/ [2] https://aadl.org/node/372209 [3] https://blog.torproject.org/get-help-running-your-relay-our-new-advocate [4] https://lists.torproject.org/pipermail/global-south/2018-May/000173.html -------------------------------------------------------------------- June 2018 Community Team highlights Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Tor Meeting ================================================================= We continued working on the Mexico City meeting plans, particularly focusing on creating a great schedule for the open days. Outreachy and Summer of Privacy ================================================================== Cy published the user issues spreadsheet for May [1] and Jaruga continued working on cleaning up documentation [2]. Website portals ================================================================== We worked on a bunch of docs that will eventually go on the community portal when it's ready. Gus translated the training slides bundle to Spanish with Antonela's help. Gus also translated and published the Tor Relay Guide to PT-BR [3]. Colin helped Tommy take over the Tor Browser Manual duties. We also did testing and editing for the support portal. Library Freedom Institute ================================================================== Library Freedom Institute began on June 1! Tor talks, meetups, and outreach ================================================================== Gus went to Colombia with the usability team and conducted Tor trainings and usability work with multiple organizations in several cities. We continued working on plans for the HOPE conference in NYC in July, organizing Tor talks, workshops, and a table. Gus and Cy continued planning for FISL in Porto Alegre, Brasil. Gus continued organizing Kenya events for August, and also began contacting other community members in new countries for future Sponsor9 work, as well as other places in the Global South to do community events. Colin continued planning the PETS relay operator meetup, as well as other Tor events at PETS. Here's the blog post [4]. dmr held a Cryptoparty workshop at the Ann Arbor library on [5]. Alison gave a talk at Brandeis University. Alison did some Tor and LFP promotion at the American Library Association conference in New Orleans. kushal continued working on dplug summer privacy training [6]. Steph is giving a Tor talk for young women at an NYC high school in July. kevun held a meeting for the Tor community in Portugal and it was really successful (double the capacity of the room!) so he's planning on organization more of these events. Colin will give a Tor talk at a Canadian hackerspace called SkullSpace in August or September. Relay advocacy ================================================================== In addition to planning the PETS meetup, Colin continued working with relay operators on the issues that got brought up after his initial contact email. He's also planning a relay operators' blog post for July. Other stuff ================================================================== We completed our June to October roadmap [7]. [1] https://ethercalc.org/may_2018 [2] https://tor.dial.ga/ [3] https://trac.torproject.org/projects/tor/wiki/TorRelayGuide-ptbr [4] https://blog.torproject.org/meetup-tor-community-night-pets [5] https://aadl.org/node/372209 [6] https://dgplug.org/summertraining18/ [7] https://storm.torproject.org/shared/viIzDFX1I_LUw4iGMRBzsIaIq8XbBwEIKegjBft…

1 0

Network team meeting notes, 9 July 2018
by Nick Mathewson 09 Jul '18

09 Jul '18

Logs at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-07-09-16.58.html Notes below: = Network team meeting pad, 9 July 2018 = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) == Previous notes == 23 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001747.html 30 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001750.html 7 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001760.html 14 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001769.html 21 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001806.html 11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html 18 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001835.html 25 June: https://lists.torproject.org/pipermail/tor-project/2018-July/001863.html 2 July: https://lists.torproject.org/pipermail/tor-project/2018-July/001866.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! == Announcements == * Let nickm know asap if there are problems with the releases in https://people.torproject.org/~nickm/volatile/src/ , or else he will release them. * Remember that 035 triage is in progress. I plan that on Wednesday I will remove all the stuff that isn't included for some reason. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TicketT… * I have 3 points on my update that are reminders for all the team (isa) == 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 release! * The git master branch is now 0.3.5! == Discussion == * I've marked 0.3.5 as an LTS release. Can we restrict the configurations in which it's LTS? For example, I would like to say that there will be no Rust-LTS until our rust support is farther along. -nm == Updates == teor (offline): last week: - Tried to work out whether the sbws bandwidth measurements are ok https://github.com/pastly/simple-bw-scanner/issues/182#issuecomment-4032488… - Fixed 1/3 of an onion service ed25519 id mismatch bug https://trac.torproject.org/projects/tor/ticket/26627#comment:8 - Planning for PrivCount in Tor https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/PrivCou… - Bwauth code reviews, let's watch out for scope creep - Caught up with some backlogs - Minor setup tasks - Personal stuff this week: - Finish PrivCount in Tor blinding and secret sharing branch nickm: what is the status of your PrivCount blinding rust branch? (#25669) Did we merge it? Should I review it? What's it called? (I believe my code is here -- there's no Tor branch for it yet. Let's talk about next steps soon?) - Implement PrivCount in Tor noise - Work on a per-relay / per-consensus / per-counter noise spec for PrivCount in Tor - Reduce my review and revision backlogs - Book Mexico travel (well, maybe the week after) Nick: last week: - Tons of admin :/ - PETS reviews - finished splitting src/common and src/or - Began documenting src/common and src/or - Prepped for releases - 034 ticket triage - Began 035 ticket triage (not yet done) - Small hack to fix 26568 (broken controlportwritetofile in 0.3.4) - Booked Mexico travel this week: - Merge many merge-ready things - Fixed a bug that broke compilation with --disable-memory-sentinels (which we recommend for fuzzing) - Complete 0.3.5 ticket triage. - PETS discussions - Advance discussion of relay crypto. - Post-refactoring cleanups. - Release 0.3.3.8 - Release 0.3.4.4-rc - Try to fix all my 0.3.5 fast-fix tickets - Time permitting, grab something from the roadmap. :) catalyst: last week (2018-W27): - coverity rotation -- nothing new (but just noticed that last build was dated Jun 24) [ahf: yeah, i'd very much like this to be rerun to see how many things were fixed] [I will debug post-meeting -nm] - github org consolidation discussions - CC stuff - looked a bit at #26376 (cross compiling docs) - travel bureaucracy - continued dealing with flaky internet access this week (2018-W28): - community guide rotation - code reviews - follow up on github org consolidation stuff and related documentation - make some progress on s8 stuff with ahf and asn ahf Last week: Sponsor 8: - Dusted off some of the old shell scripts I made during the sponsor 4 period for memory profiling of new compression algorithms which can be reused for s8 (bug #26630) - Checked if gprof and Android's simpleperf yieled similar results on 64-bit desktop and 64-bit arm device. Looks OK. Misc: - Reviewed #24546. - Progress on MacOS/Seatbelt Sandbox refactoring in #26374. - More Windows OS studying. This week: Sponsor 8: - Continue profiling work in the early parts of the week (#26630). - Back to PT error reporting (#25502). Misc: - Book flights to Mexico. - Still have a backlog of Coverity issues from week #25 I need to fix. - Promised to help out with some additional triage last week, wasn't useful at all here and not very productive at all late Thursday and Friday. Nickm: Did you do what you wanted to do here or can I still be of help? [I think I'm okay, but I wouldn't mind help when it comes time to do the next step. For now, just remember to do the triaging stuff described at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TicketT… ] - Look at Isa's S8 reporting. dgoulet: Last week: - Reviewed nickm's refactoring tickets as they were coming in. - 035 ticket triage. - Failed to resolve #26300 ... I've attempted to reproduce it in chutney considering what we know now but unsuccessful. - Most of my time was in review world, very little bug squashing. This week: - I will attack big roadmap items now that the refactoring has settled a bit for now and code base won't move much. I'm thinking memory profiling and Authenticated SENDMEs probably (#26288). - Ideally, I want to bring #20700 to a mergeable state. Will sync with haxxpop. - Will work on HOPE slide (shouldn't be too long but still need to produce 5-10). haxxpop: Last week: - Revise some code in the PR This week: - Continue revising the code. So sad, currently I have so little free time :( asn: Last week: - Reviewed #21349, #26269. - Triaged 035 tickets. - Feedback in #4700 - Did some debugging on #26627. This week: - Help isa with onion proposal. - Get up to date with 035 deliverables. mike: what is there to do in vanguard land now? you want me to help with writing blog post? catalyst/ahf: anything new in s8 #22266/#25502 land? how can i help here? isabela: - sponsor 8 Q2 report (need help collecting information about work done in April, May and June - here is our pad for it: https://storm.torproject.org/shared/b9rOzSr3fIWLG11DCb9QXDwkUDfJJWUJ1NZQ_qH… ) - onion services full proposal - will kick off the work this week and hope to finish it before hope - catalyst and dgoulet and teor worked on the survey I sent to the team - please look at their answers and make sure you are good with it. The surveys will be used to build a process/guidelines for tor to use github that meets all teams needs.

1 0

[TSoP 2018] Bandwidth scanner update - report #4
by juga 07 Jul '18

07 Jul '18

Hi, since the report #3, these has been the tasks i have worked on: Bandwidth List format specification: -------------------------------------- - Fix minor mistakes in the bandwidth-file dir-spec entry [0] - add MaxAdvertisedBandwidth [1] - Fix Bandwidth file Timestamp to be the latest scanner result [2] Core Tor: ---------- - Report version of bwscanners in votes [3] - Delay descriptor bandwidth reporting on established relays [4] - Create unit test for dirserv_read_measured_bandwidths [5] Simple Bandwidth Scanner (sbws): --------------------------------- - Fix bug calculating median on empty list [6] - Fix bug writing bandwidth file [7] - Add UML diagrams to the documentation [8] - Add package metadata [9] - Refactor fixture for tests [10] - Catch Tor controller expections [11] - Increment required python version [12] - Make scanner continue when there are not exits [13] - Move write method to bandwidth file class [14] - Fix bug parsing JSON results files [15] - Review changes on limiting the measured bandwidth the advertised one [16] [0] https://trac.torproject.org/projects/tor/ticket/26541, https://github.com/torproject/torspec/pull/18 [1] https://trac.torproject.org/projects/tor/ticket/8494, https://github.com/torproject/torspec/pull/17 [2] https://trac.torproject.org/projects/tor/ticket/26155, https://github.com/torproject/torspec/pull/10 [3] https://trac.torproject.org/projects/tor/ticket/3723, https://github.com/torproject/tor/pull/195 [4] https://trac.torproject.org/projects/tor/ticket/24104, https://github.com/torproject/tor/pull/184 [5] https://trac.torproject.org/projects/tor/ticket/25947, https://github.com/torproject/tor/pull/106 [6] https://trac.torproject.org/projects/tor/ticket/26666, https://github.com/pastly/simple-bw-scanner/pull/229 [7] https://trac.torproject.org/projects/tor/ticket/26671, https://github.com/pastly/simple-bw-scanner/pull/228 [8] https://github.com/pastly/simple-bw-scanner/pull/226 [9] https://github.com/pastly/simple-bw-scanner/pull/227 [10] https://github.com/pastly/simple-bw-scanner/pull/225 [11] https://github.com/pastly/simple-bw-scanner/pull/225, https://github.com/pastly/simple-bw-scanner/issues/192 [12] https://github.com/pastly/simple-bw-scanner/pull/221, https://github.com/pastly/simple-bw-scanner/issues/194 [13] https://github.com/pastly/simple-bw-scanner/pull/220, https://github.com/pastly/simple-bw-scanner/issues/211 [14] https://github.com/pastly/simple-bw-scanner/pull/213, https://github.com/pastly/simple-bw-scanner/issues/197 [15] https://github.com/pastly/simple-bw-scanner/pull/212, https://github.com/pastly/simple-bw-scanner/issues/210 [16] https://github.com/pastly/simple-bw-scanner/pull/191

1 0

June 2018 report for the Tor Browser team
by Georg Koppen 06 Jul '18

06 Jul '18

Hello! June was a busy month for the Tor Browser team. We released 4 new Tor Browser versions: 7.5.5[1] and 8.0a8[2] picked up a security fix in Firefox (52.8.1esr). Tor Browser 7.5.6[3] shipped a new Tor (0.3.3.7) and a number of backports from the alpha series. It is planned to be the last stable release based on Firefox 52 ESR. Which brings me to our fourth release, Tor Browser 8.0a9[4]. It is the first one based on Firefox 60 ESR. We rebased all our patches, made our extensions compatible, and adapted our toolchains as needed. We have working bundles available for Win32/64, macOS, and Linux 32/64. Major improvements are the newly designed circuit display[5], and .onion security indicators[6]. A first glimpse of our new logos, which are compatible to Firefox' Photon UI, is visible in the updated Torbutton icon.[7] Please give this alpha a try, if you can, and report bugs. We track all Firefox 60 ESR related tickets with the `ff60-esr` keyword.[8] Apart from release related tasks we made progress on the network code and new feature audit to make sure we don't miss criticial changes for Tor Browser and patch them if necessary. The first round of bugs for the latter got filed and we started to work on them. On mobile we streamlined our work towards the first alpha release of Tor Browser for Android which is planned for later this July. Among the work we did was rebasing the mobile patches for Firefox 60 ESR[9] and investigating and fixing potential proxy bypass issues[10]. All tickets related to the mobile alpha release are easy to follow as they are child bugs of bug 26531.[11] The full list of tickets closed by the Tor Browser team in June is accessible using the `TorBrowserTeam201806` keyword in our bug tracker.[12] For July we plan to close as many ESR 60 related issues for the desktop browser and aim at releasing another alpha at the end of the month. For mobile, resolving the loose ends and getting our UX related pieces ready for the release will consume most of our time. In parallel we are finally working on getting the mobile browser build integrated into our reproducible builds system,[13] which is another, important step towards parity with the desktop bundles we currently ship. All tickets on our radar for this month can be seen with the `TorBrowserTeam201807` keyword in our bug tracker.[14] Georg [1] https://blog.torproject.org/tor-browser-755-released [2] https://blog.torproject.org/tor-browser-80a8-released [3] https://blog.torproject.org/tor-browser-756-released- [4] https://blog.torproject.org/new-release-tor-browser-80a9 [5] https://bugs.torproject.org/24309 [6] https://bugs.torproject.org/23247 [7] https://bugs.torproject.org/26430 [8] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… [9] https://bugs.torproject.org/26401 [10] https://bugs.torproject.org/21863 [11] https://bugs.torproject.org/26531 [12] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [13] https://bugs.torproject.org/25164 [14] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0

[TSoP 2018] Ahmia status update ~ report #4
by Stelios Barberakis 06 Jul '18

06 Jul '18

Hello all, This an update for the ongoing development of ahmia.fi, as part of Tor Summer of Privacy 2018. The last week the following things have been done: * [ahmia-site]: Replaced uwsgi with gunicorn. The main reasons were that the former wasn't reporting django startup errors, and presented mysterious permission problems. Juha has deployed the new environment. [#552dfec <https://github.com/ahmia/ahmia-site/commit/552dfec391074770f3443c564d1dabc7…> ] * [ahmia-site]: Started implemented usage statistics (e.g #queries, #unique_queries, #clicks, etc) as proposed by George. To be commited after front-end update. More stats may be added. * [ahmia-site]: Fixed blacklist page search query to be compatible with current Elasticsearch version & schema. [#880df27 <https://github.com/ahmia/ahmia-site/commit/880df27d0ef1ccd54e709d43d309d786…> ] * [ahmia-index]: Started collecting in a bash script, useful maintenance snippets, fixes, for issues that we may encounter. [#f24b121 <https://github.com/ahmia/ahmia-index/commit/f24b1215ec52f6c6c936965070e329e…> ] The week before that I was on vacation. Best Regards, Stelios -- PGP key: http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xBF6EA91B7CBE3998

1 0

Mirroring the #tor-meeting channel with the OONI slack
by Arturo Filastò 06 Jul '18

06 Jul '18

Hi list, I am wondering if it would be OK to mirror the #tor-meeting channel (which already mentioned in the topic that it’s publicly logged) with the OONI slack. This would allow people that are not too familiar with IRC and that are on the OONI slack (we currently have 200+ people in there) to participate in the meetings that happen in that channel and to easily access the backlog. Is this something that people would be OK with? Ideally I would like to have this setup before todays Network Traffic Obfuscation meeting happening in there. ~ Arturo

4 4