- tor-project - lists.torproject.org

HOPE July 20-22
by George 21 Feb '18

21 Feb '18

We are currently in heavy planning for a TPO presence at HOPE in NYC. It's a large audience with many currently or potentially interested in the project. The TPO plans include: * some people replying to the CFP to do presentations on both technical and non-technical topics. * workshops on specific Tor topics. Topics can be large and small, but hands-on is good. Think "how do I install on an Android phone?" or "how do i teach others about Tor?" We queried for a table and "lounge" space where workshops could be held, and are awaiting more information. We are unclear when the CFP closes. At this point, a good core of TPO people will be attending, but more people means more workshops and bodies at the table. We are working out a lot of other details, including a Saturday night social event, a banner for the table, etc. We are maintaining a pad at https://pad.riseup.net/p/TorHOPEplanning Once we find out the status of the table/lounge and CFP closing, we can hold another #tor-meeting session and continue finalizing details. Input/comments requested, including more people interested in tabling, presenting or hosting a workshop. g -- 34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682

3 2

Network team meeting notes, 20 Feb 2018
by Nick Mathewson 21 Feb '18

21 Feb '18

Hi, all! You can find the proceedings of our latest meeting at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-20-17.59.html Our notes are below: ================== Network team meeting pad, 20 Feb 2018 Welcome to our meeting! Tuesday (normally Mondays) at 1800 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.) Meeting notes from previous weeks: * https://lists.torproject.org/pipermail/tor-project/2018-January/001644.html * https://lists.torproject.org/pipermail/tor-project/2018-January/001647.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001654.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001664.html Old Announcements: * 0.3.3.x is in feature-freeze. No new features (except for #24902, which has permission.). * 0.3.3.2-alpha came out Saturday 10 Feb. * Please, work on bugfixes! It would be great to have this release release on time. (Planned date is 15 April) * There are tons of tiny 0.3.3.x tickets. Maybe if you can do one of them in <X minutes for some small X, you should just do it? * We moved the hackfest 2 days later (Wednesday 30th - Sunday 3rd) to avoid clashing with Memorial Day dgoulet, teor, and isabela are organising it off-list. See the network-team list for updates. * No GSoC for Tor :'( [this time] Announcements: * Jon is booking accommodation for the May hackfest. * The 0.3.4.x merge window opened on Feb 15. * Review-group-32 is open! There are 2 tickets assigned to teor and mikeperry to review. Maybe we can move on to review-group-33? https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * Nick just made a review-group-33. Please take tickets to review. * Please fill in the code subsystems spreadsheet at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… If you review tickets, feel free to add a column with your name. * Team rotation roles was empty last week and this week, ahf have taken this week, but its empty for next week: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * isis cannot attend Rome :( * prop#245 + prop#282 meeting today (tuesday) at 23:00 UTC Discussion: - Topics - Can we remove the *.nmake files in tor.git? I have a feeling that they are unmaintained/unused? - Is all the dates final for the May hackfest? (would like to order tickets early from Europe while they are cheap). - Isabela's heat-mapping exercise with areas of tor work: what are our priorities? https://pad.riseup.net/p/38VbTZUIzG4X ====== teor: * Last week: - Implemented and tested more Experimental PrivCount circuit and onion service stats (1.5 features left, and then it's feature-complete. I hope!) - More May hackfest planning - More Proposal meetings - Detailed design and numerical analysis for uniform random in Rust, but still no code - Reviewed a few tickets, merged a chutney network for bwscanner * This week: - Final Experimental PrivCount features (no, really, this week) - Eventually make a trac user page that lists the tickets I'm working on in priority order. Add something similar to the network team queries page. - I should get time to review or revise more tickets later this week catalyst: last week (2018-W07): - reviewed #25185 (Rust cstr stuff) - learned more Rust stuff, including some doc-test things - patch for #21074 check-changes - travel logistics for Rome meeting and Seattle hackfest - CoC and SoV feedback - helped pastly with IRC moderation stuff this week (2018-W08): - work on 0.3.3 bugs - review more tickets - help out with floating point doom - update roadmappy stuff - more travel logistics - monitor CoC and SoV feedback dgoulet: * Last week: - We got #24902 backported \o/ - Discussion with armadev on #25226 for which it could be that we want a hard limit of cell queue size per circuit. - Did a branch for #17945 as a possible solution. Need feedback. - Opened and worked on #25268 to remove the cmux round-robin algorithm. - I've also started working on a branch to improve our fast path (per cell) within the cmux subsystem. It touches also #25152. Not ready for merge or anything, it was more experimental to see how that would play out. - Worked with asn on the subsystem maintainer sheet. *PLEASE FILL IT UP* - A little bit of May/June Hackfest logistics with Jon. - Was quite a week for bad relays so spent some time there. - Helping atagar with some HSv3 questions and examples for Stem integration - Sent to tor-dev@ my 034 enhancement plans: https://lists.torproject.org/pipermail/tor-dev/2018-February/012949.html - Some ticket triage including 033-must tagging. See timeline: https://trac.torproject.org/projects/tor/timeline?from=Feb+20%2C+2018&daysb… * This week: - Hope to work on 034 enhancement so we can get them early in the merge window. Especially the scheduler stuff. - 033 tickets are still a reality. - Get #24767 in a merge_ready state (asn did a first review) Nick: * Last week: - Too many meetings ;) - Worked on TROVE fixes, rust protover fixes, etc. (See network-team-security, #25250, #25251) - Opened 0.3.4, merged much of backlog. - Administrative stuff for roadmapping/planning - Conferred with isabela about roadmapping etc. * This week: - Pre-announce next week's security releases - Prep for next week's security releases - Review and merge more. - Finish 0.3.3 fixup triage [033-must, continued] - Write up an implementation plan for improved hibernation backend, based on https://gist.github.com/ahf/d22a4a98abe4651d07181a993cebdd21 [continued] - Get an official repo for tor-rust-dependencies - Get an official repo for tracking "latest stable", "latest alpha", etc asn: Last week: - Helped with roadmapping. Revived subsystem maintainer spreadsheet. Please fill it out if you haven't: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… - Triaged tor-hs and tor-guard tickets of 033. - Arranging Tor seminar at ENS Paris at the end of February with the help of maker. - Reviewed #24767. - Reviewed #24343. - Reviewed #21425. This week: - More roadmapping fun. - More reviews/bugfixes. - Think about HS statistics that we could gather (reply to teor's email). Mike: Last week: - Reorganizing and refactoring vanguards repo - Reviewed #22926 - Reviewed guardraction code - are we sure we want to rip it out rather than just disable torrc? [asn: i think we want to rip it off to simplify the codebase. otherwise we could keep it lingering on until and if we have firepower to fix it...] [mike: do we believe that a new from-scratch implementation will be simpler?] [asn: no. i think we just realize we wont ever have enough time to fix it and maintain it] [mike: hrmm.. that seems defeatist and potentially wasteful :/] [asn: might be. it's just that the code has been sitting around for many releases and it's been broken and no one wants to fix it or maintain it. also dirauth ops are complaining about the python script and we should tell them to kill it] [mike: it seems like disabling and deprecating the python script can be separate from removing all of the functionality from tor-core... is this the type of thing that will always be easier to do in an external program, because of statekeeping?] [asn: yes it's because of statekeeping that we do it as external. and i agree that perhap disabling the python script is separate from removing code from tor. as an argument for keeping it, the guardfraction tor code is fairly isolated and abstracted from the rest of the code] ahf: Last week: Sponsor 8: - Walked over S8 roadmap tasks. - Baselined some memory usage experiments with Shadow+dtrace that was done with tor+simpleperf before. - Made a Tor/Orbot APK where Tor stores its log on the device and the device periodically submit some grep'ed lines to a web service. Misc: - Reviewed: #25095 - Went over the different documents discussed at last meeting + the subsystem survey. - Discussed some PT enhancements after the PT meeting in #tor-dev. - Played around with Windows API's and cross compilation of Tor for Windows. This week: Sponsor 8: - Baseline event loop statistics and all the client tests in Shadow Misc: - Look into #24368 (zstd tuning). - Help out with some bugfixing. - Next weekend I hope to get a prototype/demo running with a PT subprocess that can do logging via tor. isis: last week: - finished moat work #24432 - dumped all the unallocated bridges into the new moat distributor to kickstart it #25246 - reviewed #25150 and #24658 and #25071 - tiny fix for duplicate header inclusion #25271 - began making rust wrappers for our C digest code #24659… can i include a new dependency on the digest crate? - researched the safety of zero-sized types accross FFI boundaries this week: - documenting moat reflector setup somehow as much as possible? - continuing large create cells #24986 impl - continuing rust digest wrappers #24659 - continue scheduling proposal meetups and have meetings - meeting this week with teor about prop#245 and prop#282 (and whomever else would like to join) (at 23:00 UTC today) isabela: last week: - started the roadmapping process - today will talk about voting on priorities - met nick o/ - met roger o/ this week: - continuation of roadmapping process - organize first draft of tasks for 6 months roadmap - send out feb network testing emails

1 0

Tor Browser team meeting notes, 20 Feb 2018
by Georg Koppen 20 Feb '18

20 Feb '18

Hi, Here are the meeting notes for the Tor Browser meeting on 20 Feb (we had no meeting last week). The chat log can be found at: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-20-19.00.log… And here come the notes from our pad: Tuesday, February 20, 2018 tjr Spent a lot of time on Timer Rounding and Fuzzing. Spending yet more time on it, but made good progress.. Got a patch written to hide the canvas prompt unless triggered by user input https://bugzilla.mozilla.org/show_bug.cgi?id=1376865 The Keyboard layout patch has problems. It's still leaking data: https://bugzilla.mozilla.org/show_bug.cgi?id=1438795 It breaks a lot of stuff (see Duplicates also): https://bugzilla.mozilla.org/show_bug.cgi?id=1433592 I.... don't really understand this one. Arthur can you walk me through it? (Arthur says: Sure. After the tbb meeting?) Made headway on "Why doesn't MinGW run" - but need assistance debugging https://bugzilla.mozilla.org/show_bug.cgi?id=1411401#c17 Added a MinGW 32 Opt build to TC and am working on a x64 Build There is a draft for the Fingerprinting Protection Help Page https://bugzilla.mozilla.org/show_bug.cgi?id=1397757 mcs and brade: Last week: - Completed some code reviews: - #15599 (Range requests used by pdfjs are not isolated). - #22614 (Make e10s/non-e10s Tor Browsers indistinguishable). - #22659 (Changes to `intl.accept.languages` get overwritten). - For #23136 (Moat integration): - Confirmed that the BridgeDB Moat distributor is now working (thanks Isis!). - Posted a patch for #19910 (Rip out optimistic data socks handshake variant (#3875)). - Found and fixed #25266 (PT config should include full names of executable files on Windows). - Created some test builds for the Moat feature and posted them. Planned for this week: - Debug #23136 (Moat integration) which is not working for Georg. - Review some more patches. - Triage the Tor Launcher bug list (set priorities, close outdated tickets). GeKo Last weeks - Worked on #21777 (I finally got a Tor Browser build somewhat running on Windows by using a clang-based cross-compiler) - Reviews - Release preparations for the alpha This week - More work on #21777 (trying to get mozilla-central built with the new clang-based cross-compilation toolchain) - Reviews - Getting 8.0a2 out - Think about summarizing the security slider discussion we had so far and moving the topic forward - Finally writing the tests for my mixed content blocker .onion patch (#23439) sysrqb -Last week: - Worked on #25260 - merging moz build files into tor-launcher - This ticket is becoming something...different, so I may repurpose it - We had an unofficial group meeting on Monday and discussed some stuff about mobile - Worked some more on the TBA roadmap - This week - Finish TBA roadmap - Continue working on #25260 - Start porting Orfox patches onto mozilla-central - Should we takeover responsibility for Orfox (and release Orfox updates) while we work on TBA? pospeselr: Last weeks: synced with Pari on February's spreadsheet regarding Tor Browser Worked on #25112 - sandboxing issue on Vista Tracked down point of failure (ntdll patching), investigating fix GK: could you ping me offline with the info you mentioned having on getting debug symbols working in windows builds basically printf debugging atm which is fine for now but would like to be more efficient in the future [Full-fledged debug builds are broken right now (but mozilla-central should have that fixed (https://bugzilla.mozilla.org/show_bug.cgi?id=1372958 has the details). Your best bet with a debugger right now is using the optimized build we usually build, however with stripping disabled; make sure you have --disable-strip in your .mozconfig and if you package a build you need --disable-install-strip as well; bobowen is the windows related sandboxing guru and e.g. in #boxing and pretty helpful if you want feedback for patch ideas GeKo] pospeselr: --disable-install-strip was the missing piece, thank you! confirmed fix for #24341 (ubuntu build issue) This week: uplifting patch for #22794, fix for #25112 more bug fixes for the bug gods igt0: Last week: - Investigated the #25247, I was not able to reproduce neither in my machine nor in a debian virtual machine. (Tried different resolutions and pixel densities) - Looked into the https://bugzilla.mozilla.org/show_bug.cgi?id=942652 , the ticket is out to date, good part of the firefox code is already updated to use configured proxy, except the sync code. I am now looking into the sync background service, there is a bug about using a different http lib https://github.com/mozilla-mobile/FirefoxData-android/issues/4 - sysrqb: I assume we'll want to disable Sync at compile-time, so we may not need to do a lot - igt0: interesting, I found these tickets https://trac.torproject.org/projects/tor/ticket/7188 and https://trac.torproject.org/projects/tor/ticket/10368 , i am not sure it reflects the current state. (where it can be enabled for sync bookmarks, passwords and history) This week: - Help sysrqb to write the TBA roadmap/documentation - Contact the Mozilla team working in the sync service about #942652, to make sure we are aligned what is the proper solution. boklm: Last weeks: - worked on some patches for: - Bug 25020: add a tbb_version.json file - Bug 25178: re-enable windows-x86_64 build in 'make testbuild' - Bug 24879: enable fetching of new commits by default for nightly builds - started working on updating binutils (#16472) and gcc (#25304) This week: - help with build of the new alpha release - continue working on: - toolchain updates (#16472 and #25304) - shipping auto-updates for Tor Browser nightly channel (#18867) - testsuite updates/fixes arthuredelstein: Last weeks: - Uplifted patches to Mozilla (checked in) https://bugzilla.mozilla.org/show_bug.cgi?id=1433357 https://bugzilla.mozilla.org/show_bug.cgi?id=1433517 https://bugzilla.mozilla.org/show_bug.cgi?id=1432907 https://bugzilla.mozilla.org/show_bug.cgi?id=1433507 https://bugzilla.mozilla.org/show_bug.cgi?id=1344613 https://bugzilla.mozilla.org/show_bug.cgi?id=1433030 https://bugzilla.mozilla.org/show_bug.cgi?id=1434666 https://bugzilla.mozilla.org/show_bug.cgi?id=1433523 Also worked on (but not finished): https://bugzilla.mozilla.org/show_bug.cgi?id=1438795 https://bugzilla.mozilla.org/1330467 This week: Current remaining patches for uplift: https://torpat.ch/short More uplift! Two bugs mentioned above, and try to finish/uplift https://trac.torproject.org/22343 isabela: - Submitted on Feb 12 SOI to DRL for TB desktop work (small grant - nothing too crazy, implement ux work from anto/otf grant and keep up with mozilla releases/security stuff) - organize team roadmap prep work for Rome - will share more this week (let me know if you have any questions) - moving some work w/ TB team to March because ux team has to get website work done by rome - prep for team meeting day in rome (should we create pads and share stuff before hand or prepare an agenda for the meetings?) Georg

1 0

Network team meeting moved to Tuesday (this week only)
by Nick Mathewson 16 Feb '18

16 Feb '18

Hi! Our regular Monday 1800 UTC meeting on #tor-dev will happen on Tuesday instead this week. (Monday is a US holiday.) peace, -- Nick

1 0

Notes from February 15 2018 Vegas team meeting
by Karsten Loesing 16 Feb '18

16 Feb '18

Notes for February 15 2018 meeting: Nick: 1) Busy; loads of meetings. 2) Trying to prep for upcoming releases, get 0.3.3 out. 3) 0.3.4 merge window is open today, in theory. 4) Team is trying to share load of finishing up 033 better. Make sure that must-fix 033 issues in tor are tagged with "033-must". Please use this label sparingly! 5) Please make sure you test the parts of 033 that you want to work. isabela: 1) some DRL status update - modularization proposal is under evaluation still - sponsor8 Q4 2017 report submitted - submitted SOI for TB desktop (short term 8months) 2) some OTF status update - working on jan monthly reports for them (sponsor4, 17 and 13) - meeting Adam this week to talk about Tor overall 2018 plans & a proposal we submitted on Jan1st 2018 - next week should start writing work completion reports for sponsor4 3) ^^ getting granthub updated with all of the above 4) prep work with Network team to for Rome roadmap/planning ahead sessions 5) prep work with UX team for Rome&Valencia 6) NYC meetup \o/ 7) meeting Roger & Nick f2f :) 8) websites do or die mission - launch support site before Rome and get all design done to present in Rome 9) question - are we having a spreadsheet for organizing sessions in Rome before hand like it was done for Montreal? Arturo: 1) Made a considerable amount of progress on golang OONI 2) Will hold tomorrow a seminar at University of Cape Town on Internet Censorship Measurement: http://www.students.uct.ac.za/event/internet-censorship-measurements 3) Preparing the course for the OONI workshop in Kampala, Uganda 4) Published part 2 blog post on the blocking of instagram in Iran: https://ooni.torproject.org/post/2018-iran-protests-pt2/ 5) Released OONI Probe 2.3.0. See: https://github.com/TheTorProject/ooni-probe/releases/tag/v2.3.0. Debian packages still need some <3 6) Updated test lists for Mali (https://github.com/citizenlab/test-lists/pull/304) & Egypt (https://github.com/citizenlab/test-lists/pull/301) 7) Lot's of progress on mobile app revamping. Should we be looping in the Tor UX team into this process? Karsten: 1) Deployed new metrics-bot badges that have been redesigned by antonela: https://twitter.com/TorAtlas/status/963688006841454593 (country example), https://twitter.com/TorAtlas/status/964104753390252032 (relay example) 2) Refactored our R code for plotting pretty graphs towards using more modern R packages. 3) Held a discussion on tor-relays@ whether to publish bridge contact information or not. The result is that we don't want to make this decision on our own. As the next step we're going to ask the research safety board for advice. Mike: 1) Helping with dev stuff for 0.3.3 2) Booked travel to rome 3) On standby emergency release duty for Tor Browser; so far the coast is clear 4) Checked in with Sukhbir, Isa, and Tommy about thunderbird and OTF. Thunderbird's FOSDEM update is interesting. https://blog.mozilla.org/thunderbird/2018/02/what-thunderbird-learned-at-fo… -- they have GPG and Mobile clients listed as things people kept asking about. Steph: 1) Worked with Tommy and Fabio at Hermes to write a post on the Italian Anti-Corruption Authority adopting onion services, sent out press releases 2) Created a postcard/flyer to encourage people to run relays. Will be handing out at the NYC meetup tonight 3) Working on an accessible one pager for funders to garner support around onion services 4) Working with Giant Rabbit to clean up our press list and prepare for Civi import 5) Giving feedback on the support portal 6) Social media 7) Beginning plans to announce the new style guide Shari: 1) Lots of grant proposals this week and last week. 2) Board meeting yesterday. 3) Finishing up audit. 4) Dealing with various personnel issues. 5) Rome meeting planning. 6) Trying to take vacation around everything else. Back in the office on Friday for a week before heading out again. Roger: 1) On the tail end of three days of meetings in NYC. Meeting with Isa this afternoon. Doing the NYU outreach thing tonight. 2) I am mostly afk next week. 3) Are we doing follow-up on previous items from vegas meetings? Like, Rightscon tickets, or Fastly, or... I don't remember most of them and it makes me nervous. :)

1 0

January Communications Report
by Stephanie A. Whited 15 Feb '18

15 Feb '18

Joining in to serve up a monthly report covering blog posts, social media, press, new materials, etc. In January we started talking more about onion services and encouraging folks to onionize the web. More to come. Team written and/or edited blog posts ================================== - https://blog.torproject.org/secure-communication-gaining-momentum-india - https://blog.torproject.org/explore-tor-nyc-meetup-feb-15 - https://blog.torproject.org/news-orgs-activists-onionize-your-sites-against… - https://blog.torproject.org/volunteer-spotlight-alec-helps-companies-activa… - https://blog.torproject.org/2017-was-big-year-tor Social Media ============ - Transitioned appearance of Twitter, Facebook, and LinkedIn organization profiles after finishing fundraising campaign. (We have a new round of covers up in Feb replacing Jan's using Antonela's relay design!). Twitter ====== Tweets: 69 New followers: 4,516 Top tweets: https://twitter.com/torproject/status/958016026431643648 https://twitter.com/torproject/status/955906896153776128 Facebook ========= Met goal to post at least once every weekday. New likes: 143 LinkedIn ========= New followers: 52 Monthly Newsletter ================= Sent 1/31: https://newsletter.torproject.org/archive/2018-01-31-onionize-against-censo… Press Notables ============= https://news.sky.com/story/iranian-web-crackdown-drives-surge-in-privacy-te… http://www.tomshardware.com/news/tor-7.5-next-gen-onion-services,36397.html http://www.ibtimes.com/tor-browser-75-update-released-whats-new-2645166 o/ -comms -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Key ID: 39A876AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

community team January update!
by Alison Macrina 14 Feb '18

14 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Tor folks, check it out: January 2018 Community Team report Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Cu rrentTeamDiscussions Support and translation ================================================================== Colin worked on fixes for some webml issues with Transifex and the old website, and continued on translation work for the new support portal. We added even more content to the soon-to-be-live support portal. Our Outreachy intern Pari released the January user issues doc: https://storm.torproject.org/shared/XuN4uMdY0Y6vm6G1vOZs0bx9mmRtq-MpSgKo a6WSKLJ Colin has also been working with Localization Lab and the Tor Browser team to get more languages added to the browser. Relay operator love ================================================================== We continued work on the Tor Relay Guide (#24497 and here https://trac.torproject.org/projects/tor/wiki/TorRelayGuide) We're still working on letters of interest to funders who might want to help us support growing the network of relays. Tor talks ================================================================== Sukhbir gave a Tor talk at the Alternative Law Forum in Bangalore, India . Sukhbir gave a Tor talk at the Toronto Public Library in Toronto, Canada . Alison gave a Library Freedom Project talk at the University of Washington in Seattle, USA. Alison gave a Library Freedom Project talk at Georgetown University in Washington DC, USA. A bunch of us worked on plans for the NYC Tor Meetup that will happen on February 15. Library Freedom Institute ================================================================== LFI application recruitment continued through January. We also worked on drafting the schedule and recruiting guest lecturers. Tor Meeting ================================================================== We finalized the location for the end of 2018 Tor Meeting -- Brazil! We analyzed survey feedback from Montreal to make improvements for the upcoming Rome meeting, and we did some other prep work for Rome. Community governance ================================================================== Discussion of the code of conduct text continues on tor-internal@! ================================================================== - -- Alison Macrina Community Team Lead The Tor Project -----BEGIN PGP SIGNATURE----- iQJKBAEBCAA0FiEE+/Dn2xQzAY7lLQ3an8NAicvoPKMFAlqEmdcWHGFsaXNvbkB0 b3Jwcm9qZWN0Lm9yZwAKCRCfw0CJy+g8ozEtD/4qZQYsWAMewqZO1P1QPOgx7g3A PjB6HXCndFoL/5zm/qLJhq25aiSgHjcOgjp5Fg++6Jb1fE5lAG+f4F75NqWX2k2Y OEY2765r8unxcVwWJg0WnsmcgIgIxOvy5ScFV2ywXnqRuePYUzhjcbboIvx/Ee9B wsZB7LvWz7Z343P88RqCzLWY018zYw3kvCtKoOXSgJH2P49sgYWTiUfrH5uPvi04 Hf8Cemd4andqdjdlHTcZDnYPRSqp5Zm4JJotB07vK2wdWIKHaapEtNB2T8wRGwPm /njLxTUIluJQ31Zm2yLPL3smfgTH/Hjf7MGPPsyLNnehK5bVy53LKQHkDwPHfKFd ekYL3GwAPrLM48XRLfrphHKv1xlnjlv1CSxIjOt0MZAFD4Q/B90iw5U+W3FLWIMQ xsMRJip0f4wNbzHr2eeSIlmtfgFD4JN7/uQhoxTdHYYxTzVtrPcHiQK8k4XiRc7X CJfXUKg1IsLe9/7h5zFEMUCJB5CjBveVA59usUt5uQ9kq0PKc4KRqQpIOW7S9Cc9 4NSartZwzVo9vELSTYAKOGAIc9Rk1cqitTTEkR/5Pb2JILhUpkll91yjlkm3G/28 9NUQXqoLDehC7sViv00qOgbjL/LAGTDdZ6x+MIgf0WmgSVR5khKi+axTrdJ+oISX kIO5kcPYh2g3NvSfqQ== =G5YX -----END PGP SIGNATURE-----

1 0

UX Team January 2018 report
by isabela 13 Feb '18

13 Feb '18

The UX team is cooking with gas in 2018!! We did a lot of work this January, and are preparing to share a lot with the community during the Rome Meeting. Keep an eye on the meeting schedule to know when and what o/ We will also be at IFF doing user testing on March 6 (at the tabling thing they will have) from 2-4pm. Here is some really cool stuff we did in January: User Testing in India ===================== - Helped organize Tor Meetup Mumbai 18 - together with Sukhbir and Tor community folks. https://blog.torproject.org/secure-communication-gaining-momentum-india - At the Mumbai Meetup we did somem user testing of .onion services and Tor Launcher Tests methodology and scripts can be found here: https://docs.google.com/document/d/1KdnEsAlXdkQT4EBsRUAEgzqz5lkdmjNBUB29YfE… - We now have our own survey tool which was deployed and tested at meetup in Mumbai This tool will be very useful to collect user feedback. https://survey.torproject.org (also exist as a .onion service!) Website ======= Styleguide - Our styleguide is done! https://styleguide.torproject.org - We also added icons we created for metrics team to it - see ticket #24664 for more info. - Next is to tell the world it exist! Support Portal - Desktop UX/UI is done. Waiting for translations. - Support mockups for Mobile are on development -> https://marvelapp.com/3i2hggg/screen/37876933 - Support portal coding 90% completed. Fixing usability issues and bugs Comms Portal - We start to design our community.torproject.org portal, you can find links to our mocks at the ticket #24133 Collaboration with other teams ============================== Tor Browser - #24918 was updated with some suggestions on how to present the new location of Circuit Display on Tor Browser desktop. https://trac.torproject.org/projects/tor/ticket/24918#comment:3 (this work is still in progress and we are doing another round in Feb) - We worked with the Tor Browser team on the UI for Moat on Tor Launcher, more at #24696 - Tor Browser 7.5 was released!!!! https://blog.torproject.org/tor-browser-75-released Major UI updates on this release, check out the blog post with gifs (if you haven't seem it in your browser yet!! and you should update it then :P) Metrics - Worked with irl on icons for metrics team to use to communicate what the data is about, This is now deployed. https://trac.torproject.org/projects/tor/ticket/24717 Comms team - Created some covers for Comms <3 https://blog.torproject.org/news-orgs-activists-onionize-your-sites-against… https://www.dropbox.com/s/izj7tho5c0i1az0/relays-guide.png?dl=0 https://www.dropbox.com/s/z4vio4xmb9n6oil/volunteer-spotlight-2%3A1.png?dl=0 Gracias y hasta la proxima o/ cheers, UX Team

1 0

Network team meeting notes, 12 Feb 2018
by Nick Mathewson 12 Feb '18

12 Feb '18

Hi! You can find logs from our IRC meeting today at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-12-17.58.html The contents of our pad are below: ======== Network team meeting pad, 12 Feb 2018 These days I use her real name But I don't dare to mention it. She hides from cameras. And now I've gone and put her in a poem. -- Wendy Cope, "Omo" Welcome to our meeting! Mondays at 1800 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.) Meeting notes from previous weeks: * https://lists.torproject.org/pipermail/tor-project/2018-January/001644.html * https://lists.torproject.org/pipermail/tor-project/2018-January/001647.html * https://lists.torproject.org/pipermail/tor-project/2018-February/001654.html Old Announcements: * 0.3.3.x is in feature-freeze. No new features (except for #24902, which has permission.). * No 0.3.4.x patches will be merged till the window opens on Feb 15. * Please, work on bugfixes! It would be great to have this release release on time. (Planned date is 15 April) * There are tons of tiny 0.3.3.x tickets. Maybe if you can do one of them in <X minutes for some small X, you should just do it? * May hackfest has been approved by Shari. dgoulet, teor, and isabela are organising it off-list. See the network-team list for updates. Announcements: * 0.3.3.2-alpha came out Saturday. * Review-group-32 is open! There are 17 tickets for us to review. https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~rev… * Meeting today (2100 UTC) to discuss UTF-8 proposal * No GSoC for Tor :'( [this time] * We moved the hackfest 2 days later (Wednesday 30th - Sunday 3rd) to avoid clashing with Memorial Day Discussion: - any questions about areas of work for our roadmap planning - please review and give feedback / trying to close this by friday feb 16. (Let's review it again!) https://pad.riseup.net/p/LMxcQxvWOvzz-setofareas - 0.3.3 wrapup - 0.3.4 opening ====== Nick: * Last week: * Alpha release of 0.3.3.2-alpha. * Started taking a class about Coq [isis: COOL] * Tons of release-engineering, ticket triage, etc. * Tried to work on numerous small bugs * This week: * Many meetings. * Lunch with Isabela on Friday * Try to get all important stuff backported to stable releases * TROVE-2018-001 * Work on sleep/wakup auditing. [ ahf: I'm doing some experiments with Shadow on this right now - maybe we should talk about joining forces here? ][yes,let's talk for a couple minutes right after this? -nm][ ahf: WFM ] * Open 0.3.4 merge window? [asn: sounds good] [dgoulet: +1, on schedule :)] * Try to finish identifying all must-fix issues for 0.3.3. Please help. [dgoulet: Do you prefer a keyword or we tell you which one we think are must fix or ... ?] [asn: we are also done with review-group-31] dgoulet: * Last week: - Did some roadmap brainstorming with isa/asn - Hackfest in Seattle logistics. - DoS mitigation released (woot!). Final work needed for that was in #25193 along with work nick did in #25183. - Triage and commented on 033 tickets. - Some patches for other 033 tickets can't recall them all (see timeline). - Perf analysis of 033 busy relays. #25152 is a ticket resulting in that investigation. I think 033 is in good shape in terms of CPU cycles. The DoS mitigation doesn't seem to be affecting performance much. Timeline: https://trac.torproject.org/projects/tor/timeline?from=Feb+12%2C+2018&daysb… * This week: - Work on 033 tickets. - I have big patches for 034 in the scheduler so I'm aiming to get them in needs_review very close to when the merge window opens in 3 days. - <whatever comes up this week> isabela: - last week: - sent sponsor8 Q4 report finally o/ - sent a proposal for roadmap(s) planning to the list, please see discussion point above regarding the areas of work exercise/list creation - this week: - finalize areas of work w/ team - notify network testers - start preparing for next phase of roadmap(s) planning - lunch w/ nick on friday ahf Last week: Sponsor 8: - Did some data collection for Isa for the Q4 2017 reporting. - Wrote a log collection script for MainLoopStats log messages (from #24605). - Got Shadow to run with 0.3.2 with the patch from #24605. Misc: - Did some bug triaging for 0.3.3 bugs, moved bugs ahead, closed some duplicates. - Reviewed: #24909, #25162. - Landed fix for: #25120. - Added two possible solutions to #22926 - one was rejected, the second one might be better. - Weekend project: Wrapped my head around Tor's PT implementation and wrote a Quic PT -- was a fun exercise. Next step is to get the source IP change (roaming) feature to play nicely. This week: Sponsor 8: - Go over S8 roadmap tasks. - Wrap my head around using Shadow for all experiments where it is suitable for reproducible results. - Continue memory optimization work. isis: last week: - added extra logging temporarily to the bridgedb server on polyanthum to attempt to debug the remainder of #24432 - fixed a rust memleak #25127 and then never-going-to-happen-but-if-it-did rust FFI panic!() UB - we should maybe be compiling our rust code with `-C panic=abort` to avoid unwinding across FFI? not sure - tried to make utilities for working with static strings across the FFI boundary #25185 - transfered moat google appengine account to TPO ownership - continued a bit of work on organising how the large create cell code should be implemented #24986 - led a proposal meeting for consensus hash chaining prop#239 - began scheduling proposal meetings for prop#267 prop#245 and prop#242 - reviewed the openssl 1.1.1 patches #24978 this week: - more of #24986 - moat debugging / probably writing SQL statements by hand to transfer the "unassigned" bridges to be assigned to moat - going through the appengine instance to try to document how to set one up :/ - more proposal meeting scheduling - prop#285 "make directory documents be utf-8" meeting today at 13:00 PST (starts three hours after this meeting starts) teor: * Last week: - Implemented and tested more Experimental PrivCount onion service stats - Merged the DDoS fixes into Experimental PrivCount, they work well so fat (so fattt!) lol - May hackfest planning - Ticket triage - Proposal meetings - More planning for floating point tests in Rust and C, no code yet [isis: lmk if i can help with anything!] * This week: - Final Experimental PrivCount features - Eventually make a trac user page that lists the tickets I'm working on in priority order - I should get time to review or revise more tickets next week asn: Last week: - Helped isa with roadmapping. - Worked some more on removing guardfraction from the codebase. And prepared some branches: #24456 - Triaged 033 tickets on prop224, tor-hs and tor-guard keywords. Moved some of them on 034, others need further work. - Did some more digging on a skeleton prop#279 implementation. This week: - More work on roadmapping. - Help out with 033 releases and do reviews/bugfixes as needed. - Figure out rome flightplan. catalyst: Last week (2018-W06): - travel arrangements for Rome meeting - Rust protover leak fix review (#25127) yay, master builds on Travis again! - read some more about Rust FFI to help with #25127 - some s8 bookkeeping for isabela - reviewed #25120 (log getrandom failure more quietly) - responding to CoC and SoV feedback - still slowly recovering from this cold This week (2018-W07): - Travis is currently broken on 0.3.2 due to check-changes https://api.travis-ci.org/v3/job/340488056/log.txt - review more Rust cstr stuff - work on some 0.3.3 bugs - CoC and SoV feedback as needed Mike: Last week: - Booked tickets to rome! - Wrote patch for #24769 - Reviewed #22212 - Coordination with Matt Wright & co re adaptive padding in tor-core - Reorganzing and refactoring vanguards repo for easier packaging This week: - More vanguards repo work

1 0

Report on the FOSDEM relays meetup
by Nicolas Braud-Santoni 10 Feb '18

10 Feb '18

Hi, I facilitated the meetup at FOSDEM, last Sunday, and I wanted to report back on what happened, and what worked (or did not). We had around 20 people, with relatively little overlap with the 34C3 meetup (I could be wrong, though, as I'm bad at recognising faces). This seems quite good, esp. considering that the 34C3 meetup was a month before, and that the meetup wasn't announced especially early (we announced ~2 weeks in advance there would be one, but the time and precise location couldn't be fixed until Sat. morning) The room configuration wasn't exactly ideal (typical lecture room, not great if you want people to talk to one another). That's something we can probably improve next year, by organising the meetup at a side-event (say, on Friday early evening) at one of the local hackerspaces or somesuch; this way, we get a better location and we could communicate time & locations much more in advance. Communication-wise, I started publishing the events in blog.tpo (thanks hiro!), which seems to have helped some people; if we organise it as a side-event next year, we shoudl also get it on their website: https://fosdem.org/2018/fringe/ Content-wise, there were some pretty fruitful discussion, but we spent quite a bit of time on questions that recurr at other meetups too: - What's the most useful thing I can bring to the network? (TL;DR: Ideally, fast relays (if possible exits); if you can't contribute more than 1MB/s, make it a bridge) - Can I run my relay on a Raspberry Pi (or similar) ? - Why does my relay (or Internet connection) die once I have TLS connections established to most other relays? (This instance was likely caused by an ISP-provided router with bad TCP connection tracking.) - Why doesn't Tor support IPv6 yet? (Feel free to add more questions if I forgot some here) Those are all somewhat simple, and I think we would definitely benefit from having better, and more visible, FAQs for those. I will try to take the time and make/improve wiki pages for those, but I wouldn't mind some help from one of the website-makers to see how we can make it more visible. Getting people to ask a bunch of questions at the start, and broadly categorizing them, as suggested by Roger last meetup, seemed to work well: we managed to cover all topics people were interested in, and were only 20 minutes over time. However, I had people shortly introduce themselves before adding their question, and that might not be so good in retrospect, as the intros took a bunch of time, and might have been an obstacle to people suggesting more questions. If people are interested, I can start collating advise on how to facilitate tor-relays meetups in some wiki page, though I'm not sure yet how to convey that “nicoo's way of relays meetup” isn't meant to be authoritative or prescriptive at all (read: I have no clue what I'm doing, but hopefully it works not too bad.) Best, nicoo

1 0