- tor-project - lists.torproject.org

TPA wiki migrated to GitLab
by Antoine Beaupré 24 Jun '20

24 Jun '20

Hi, Just a short note to let you know that the sysadmin (AKA TPA) wiki, previously known as: https://help.torproject.org/tsa/ ... was migrated to GitLab: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/home Redirects to the new wiki are in place, so you don't absolutely have to update your bookmarks, but I figured it was worth announcing it to avoid any surprises. That project is also, incidentally, where you file support requests to us: https://gitlab.torproject.org/tpo/tpa/team/-/issues The migration was somewhat interesting, because I had to rewrite the ikiwiki-specific Markdown content into GitLab's Markdown. I also had to make up a migration procedures for git repositories, which we may want to reuse for other repositories. All the gory details are, of course, documented in this GitLab issue: https://gitlab.torproject.org/tpo/tpa/team/-/issues/34437 As usual, if you need our help, the "how to get help" support policy is where you find that info: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-2-support… Thank you for your attention, a. -- Antoine Beaupré torproject.org system administration

1 0

Have "anything goes" blog post?
by Philipp Winter 24 Jun '20

24 Jun '20

We have many comments on our blog that are unrelated to the respective blog post but still bring up reasonable topics. To make it easier for our users to be heard, why not have an "anything goes" blog post once a month? A user suggested this idea over here: <https://blog.torproject.org/comment/288185#comment-288185> The idea is for users to comment on any topic as long as it's not in violation of our blog comment policy (minus the "on topic" requirement): <https://trac.torproject.org/projects/tor/wiki/doc/community/blog-comment-po…> Hopefully, this will give our users an opportunity to talk about problems they have, ask us questions, and request features. How does that sound? I can draft the blog post and help moderate comments but would appreciate a few people helping with that. I propose June 26th -- the last Friday this month. I suggest giving it a shot as a one-off experiment and repeat if it goes well. Cheers, Philipp

10 15

The Gitlab ticket workflow of the network team
by George Kadianakis 23 Jun '20

23 Jun '20

Hello, me and David assigned reviews today and here is the procedure we came up with. Unfortunately, because we dont use merge requests in gitlab yet, we cannot use the natural procedure of gitlab when it comes to code reviews, so we had to hack something up with labels for now. == Marking something for review == When you write code and you want to mark it for review, please add the "Needs Review" label. == Assigning reviews == When me and David assign reviews, we use the "Reviewer" label and then assign the ticket to the right reviewer. == Finding your reviews == To find your reviews you use this query: ahf: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… nickm: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… asn: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… dgoulet: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%9… == Reviewing your reviews (happy path) == When you do your reviews, the happy path is that the patch was good and you merge it and you move forward. Because ahf can't commit yet, when ahf reviews code, he can add the label "Merge Ready" and then its our responsibility to merge it. Hopefully ahf will start committing next week and we won't need to do that. == Reviewing your reviews (sad path) == If the patch was not good, you need to put it in needs revision. This is crammy in our workflow (because of lack of MRs) but we suggest the following procedure: - You add the "Needs Revision" label. - You don't change any other label. It's now the responsibility of the code author to notice this label, and revision the code. It's also the responsibility of the reviewer to poke the code author if they haven't done this in a reasonable amount of time. == TODO == How to handle backports? Transition to MR workflow which will greatly improve the sad path above.

2 3

PrivChat w/ Tor - you're invited!
by Al Smith 23 Jun '20

23 Jun '20

Hi Tor people! Next Tuesday, we're hosting Tor's very first PrivChat (https://torproject.org/privchat) a live conversation and Q&A event series designed to bring together experts in the privacy, tech, and human rights space + host a platform for the community to ask questions and get answers + raise funds for Tor. You are invited!!! What: PrivChat with Tor | Online Privacy in 2020: Activism & COVID-19 When: Tuesday, June 23 @ 18:00 UTC / 2:00pm Eastern / 11:00am Pacific Where: https://youtu.be/gSyDvG4Z308 Panelists: -- Carmela Tronsco (EPFL) -- Daniel Kahn Gillmore (ACLU) -- Matt Mitchell (Ford Foundation) -- and facilitated by our very own Roger Dingledine Fundraising element: Event is free. We are encouraging attendees to consider becoming monthly donors if they feel inspired by the content of PrivChat, but watching is free and there is no registration. Hashtag: #PrivChatWithTor. Please help us spread the word! Even a retweet from @torproject to your people would be great. We'd love your support during our first PrivChat. <333 Al -- Al Smith (they/them) Fundraising • Communications The Tor Project

1 1

Tor Browser release meeting - June 23rd 1800UTC
by Gaba 22 Jun '20

22 Jun '20

Hi! Next Tor Browser release meeting is happening on Tuesday June 23rd at 1800 UTC in irc.oftc.net #tor-meeting. You can find the meeting's pad in : kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-browser-release-meeting-keep cheers, gaba -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Re: [tor-project] February - May 2020 User Feedback Report (Nicolei Ocana)
by Nicolei Ocaña 22 Jun '20

22 Jun '20

Georg > Is that essentially Windows-only? No, there were some tickets where users attached screenshots of their prompts - Windows, Mac, and Linux user interface windows. > For the Windows ones, do we know how many of those issues are due to #10416 > (https://gitlab.torproject.org/tpo/core/tor/-/issues/10416)? >From the screenshots that users shared, none alluded to this issue. > What do you mean by "blocking larger media elements by default" There is no logic in Tor > Browser that is blocking media elements depending on their size. Additionally, Tor Browser > should not block anything by default in its standard security mode. I misspoke. I was incorrect in my statement; I should have wrote "NoScript blocks media on security levels Safer and Safest." You are absolutely right on both fronts. Thanks for clarifying these aspects: Tor Browser does not block any media by default; NoScript allows for media in the Standard security level. > So, what is happening in those cases? Do you have an example of a report by chance? So, I'll admit, I was mistaken. To make a long story short - one user took a screenshot of NoScript blocking out its media yet I neglected to pay attention that the user had the Safer security level set. I presumed this occurred by default. After clearing up the confusion, those cases contained Flash-based XSS attempting to show a movie. Below is the example: >> Hi >> Tried to watch this on Tor: >> https://www.brighteon.com/be689f32-5526-4601-a627-48dc4f896cf9 >> And several other videos. but they come up with a red circle with a monster with teeth in >> the middle. An even when I choose one of the responses it still won’t play And another thing is that many Tor users are now having issues to watch YouTube: "Our systems have detected unusual traffic from your computer network. Please try your request again later. Why did this happen? This page appears when Google automatically detects requests coming from your computer network which appear to be in violation of the Terms of Service. The block will expire shortly after those requests stop. ..."

1 0

Tor browser meeting notes, 22 June 2020
by Gaba 22 Jun '20

22 Jun '20

Hi! Tor Browser meetings are happening every Monday at 1800UTC on #tor-meeting in irc.oftc.net We had a meeting on June 22nd and here are the logs and notes. Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-22-17.59.log… Pad: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Contents of the pad for today: == Tor Browser meeting pad! == Next meeting is at Monday 29 June 1800 UTC on #tor-meeting on OFTC. June Schedule: * Monday 15 June 18:00 UTC * Monday 22 June 18:00 UTC Release meetings: https://pad.riseup.net/p/tor-browser-release-meeting-keep Tuesday June 23th 18:00 UTC Tuesday July 7th 18:00 UTC (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Upcoming Releases and other important dates 2020.06.30: 9.5.1 and 10.0a2 - ESR68.10, ESR78.0 Latest Releases: 2020.05.22: 9.5a13 https://blog.torproject.org/new-release-tor-browser-95a13 2020.06.02: 9.5 Stable https://blog.torproject.org/new-release-tor-browser-95 2020.06.02: 10.0a1 https://blog.torproject.org/new-release-tor-browser-100a1 == Previous notes == (Search the tor-project mailing list archive for older notes.) June 15th - https://lists.torproject.org/pipermail/tor-project/2020-June/002878.html == What project we are working on? == SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements - soon to be moved to gitlab Parent ticket: https://trac.torproject.org/projects/tor/ticket/33664 Wiki page: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 Timeline: https://nc.torproject.net/s/ow2r6cLgL7Cd9BA == Stuff to do every week == Check reviews not taken! How reviews from last week worked? Any blocker? For S58: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… - soon to be moved to gitlab ------------------------------- ---- 22 June 2020 ------------- ------------------------------- == Announcements [please date] == == Discussion [please date] == Is confirmed the TB release meeting tomorrow June 23rd? - yes (June 22nd) gitlab labels for applications group labels for usability issues https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/4 how reviews in gitlab will happen- using MRs (June 22nd) S58 (June 22nd) blog moderation (June 22nd) Please take a look at dev.tpo content structure and point me what im missing https://gitlab.torproject.org/tpo/web/trac/-/issues/24132#note_2681345 (June 22nd) Needs review https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 Log June 22nd: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-22-17.59.log… == Status Updates == 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. ahf: Week of 2020-06-15 (actual): - Lots of Gitlab stuff Week of 2020-06-22: - Back to working on Fenix and Tor integration. boklm: Week of 2020-06-15 (actual): - Made patches to use rootless containers and was able to do builds of Tor Browser for windows-x86_64 and osx-x86_64 (tor-browser-build#23631 and rbm#40001). For some unknown reason the builds based on wheezy are not working. Week of 2020-06-22 (planned): - Add some documentation for rbm#40001 and set the patch as Needs Review - Improve patch for rbm#32272 to handle Ctrl+C Mike: Week of 06/15 (planned): - gecko-dev proxy audit Week of 06/15 (actual): - Looked over previous proxy audit notes for plan - metrics tickets followup - Funding proposal work - Congestion control work for funding proposal (see email) Week of 06/15 (planned): - Wrap up congestion control proposal draft - gecko-dev proxy audit mcs and brade: Week of June 15th (actual): - Created revised patches for: - tor-browser#33851 (Patch out Parental Controls detection and logging). - tor-browser#33998 (stop using XUL <grid> soon). - tor-browser#33848 (Disable Enhanced Tracking Protection). - Spot-checked acat’s 33533+6 branch (the updated ESR78 rebase). - Created a patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1642754 - This is a spin-off of Mozilla bug 1642404 and covers the remainder of tor-browser#28885. - Our fix was merged into mozilla-central \o/ - Provided feedback on anti-censorship/trac#40004 (Sponsor 30 O3.2 UX Flow). - Started to review Firefox release notes and closed bugs for Firefox 75-78. Week of June 22nd (planned): - Continue review of Firefox release notes and closed bugs for Firefox 75-78. - Follow up on https://bugzilla.mozilla.org/show_bug.cgi?id=1642404 (upstreaming of tor-browser#28885). - We are not sure why this has not yet been merged to mozilla-central. sysrqb: Week of 15 June (planned): Really, really finish #33939 Review testsuite patches and merge them so we have a working...testsuite Catch up on current 9.5/10.0a tickets Finally land vpx patch upstream Week of 15 June (actual): Really, really finish #33939 (no) Review testsuite patches and merge them so we have a working...testsuite (no) Catch up on current 9.5/10.0a tickets (no) Finally land vpx patch upstream (small progress, but not complete yet) Followed up on a Mozilla browser fingerprinting bug Helped with some GitLab migration tasks Fallout from OTF and USG changes Tried counting the number of active Tor Browser instances Week of 22 June (planned): Really, really finish #33939 Review testsuite patches and merge them so we have a working...testsuite Catch up on current 9.5/10.0a tickets Finally land vpx patch upstream Review https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 Continue tracking OTF/DRL situation Audit GitLab labels Release prep GeKo: Week of June 15 (planned): Gitlab work Finish review of #33533 Work on application-services build Week of June 15 (actual): Gitlab work Review of #33533 (but not finished) Week of 22 June Finish review for #33533 Finish build of application services help with releases were fit Gitlab label situation/workflow Antonela: Week of 2020-06-22: - Review HTTPS-E Names https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010#n… - Work on S58 tickets TBA UI - Waiting for tbb-dev review in S30 https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 acat: Week of 15th June (planned): Possibly address GeKo's feedback on #33533 Finish uplift #32414 (Make Services.search.addEngine obey FPI) Document rebase process for tor-browser-spec Maybe start covering some patches with tests Week of 15th June (actual): Found out uplift #32414 was not needed, as the API is removed in 78. Done #33954: Consider different approach for "2176: Rebrand Firefox to TorBrowser" Picked some fixes for #33533 (esr78 rebase) tor-browser-spec#40001: initial work for Document/improve/automate Tor Browser rebasing process Week of 22 June: Possibly address GeKo's feedback on #33533 Add tests in tor-browser-bundle-testsuite: 40001: Add test for "Communicating security expectations TB patch" 40002: Add test for "Add v3 onion services client authentication prompt" TB patch 40003: Add test for "Implement Onion-Location" TB patch 40004: Add test for "Implement .onion alias urlbar rewrites" TB patch 40005: Add test for "Replace security slider with security level UI" TB patch Rebase #33533 to latest beta and test tor-browser-spec#40001 process -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network meeting notes, 22nd June 2020
by Gaba 22 Jun '20

22 Jun '20

Hi! Network meetings are happening every Monday at 1700UTC on #tor-meeting in irc.oftc.net We had a meeting on June 22nd and here are the logs and notes. Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-22-16.59.log… Pad: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Contents of the pad for today: == Network meeting pad! == Next meeting is at Monday 29th June 1700 UTC on #tor-meeting on OFTC. June Schedule: * Monday 29 June 17:00 UTC Welcome to our meeting! We meet each month at: Mondays at 1700 UTC 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 tor-project mailing list archive for older notes.) 1 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002857.html 8 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002865.html == Stuff to do every week == Let's check and update our roadmap: What's done, and what's coming up? Any change? All the trac tickets for the roadmap are in the team's page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam <-- This will be moved to Gitlab ASAP S28 & S30 - Continue after October - Ahf S55 - Nickm & dgoulet Non sponsor stuff DoS defenses = Dgoulet + Asn Library Size reduction = Ahf + Dgoulet sbws = Ahf + Juga 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… Go over our 0.4.4 status page at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… . (If maint-0.4.4 were released as stable tomorrow, what would we regret?) - scheduled to enter feature freeze on Monday June 15th == 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. * Check other's people call for help in their entries. Volunteers need help. Please help them when you are around. Maybe we should have times of day when different people are responders, and expectations of who helps. ------------------------------- ---- 22 June 2020 ------------------------------- == Announcements [please date] == Assigned reviews (Will put on gitlab when gitlab becomes RW again): dgoulet -> #33816 Fill in missing IPv6 addresses in extend cells nickm -> #34065 Make routerset_contains_router() support IPv6 asn -> #34433 Replace clang-format.sh with a faster, better version == Discussion [please date] == [June 22nd] Please take a look! (antonela) in the next 2 weeks -> https://gitlab.torproject.org/tpo/web/trac/-/issues/24132#note_2681345 [Next meeting - June 29th] Sponsor 55 Status - https://pad.riseup.net/p/FaSoXgt5tF0BkWYcG2So === Active Proposed Policies === * Pull Request Guidelines (stalled) === Design proposals under discussion === 315: require more fields in directory documents (still waiting [6/1]) 316: flashflow (asn and nickm are reviewing, should schedule discussion with pastly. [5/18]) 317: dns (under discussion on ML [5/18]) 318: limit protovers (waiting for more commment; needs discussion [6/1]) 319: wide everything (nick replied on ml; waiting for more discussion [6/1]) 320: tap out again - Do we have a consensus to replace this with a "deprecate v2 onion services" proposal? If so, who writes it? [6/1] protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18]) 321: happy families (need feedback [6/1]) 322: dirport linkspec (need feedback [6/1]) == Recommended links == == Updates == 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! Nick: Week of 15 Jun (planned): - Get chutney actually working with assumereachable disabled (34445 through 34449) - Work on aftermath of gitlab migration. - Work with dgoulet to advance S55 planning. - Get S55 reachability test more advanced. - Release 0.4.4.1-alpha. Week of 15 Jun (actual): - Released 0.4.4.1-alpha - Worked on aftermath of gitlab migration: - Label hacking - checklist hacking - learning curve. - Chutney and S55 hacking: - Chutney relays now actually run self-tests! - Wrote code on #34067 to make ipv6 self-testing get treated as separate flag Week of 22 June (planned): - Go through backlog - Work on misc 0.4.4.x issues - Fix S55 bugs - More gitlab stuff, probably. - catch up on email backlog? ahf: Week of 15/6 planned: - Back to Fenix stuff with Browser Team - Support Gitlab people if we go with that. Week of 15/6 actually: - Lots of Gitlab support. Started the label cleanup. Moved more and more projects over. Week of 22/6 planned: - Trying to minimize myself in the Gitlab stuff for now. - Need to deal with review backlog. - Back to doing Fenix + Tor integration. - Get Tor network extension working on device with TGP sponsorship. asn: Week of 15/06 (planned): - More work on PoW proposal. Fold in David's work on the scheduler and derive results from that. - Hopefully merge #32040. - More reviews & merges. Week of 15/06 (actual): - Published latest version of PoW proposal with lots of revisions: https://lists.torproject.org/pipermail/tor-dev/2020-June/014381.html - Analyzed PoW scheduler results with dgoulet and David ended up finding an epic bug: #40006 - Wrote a patch for guards + metrics: #40001 - Got folded into an online hackathon and have been reviewing code from two participants who implemented two features for OBv3: status socket support and SIGHUP support. - Getting used to gitlab. Week of 22/06 (planned): - More work on PoW proposal: - Folding in more scheduler performance measurement results. - Think of effort estimation and minimum effort. - More OBv3 hackathon grooming. - Reviews & merges jnewsome: Week of June 1 (actual): - Added GH milestones and issues in shadow/shadow - Sent out Tor Project update - Added more thread/interposition APIs in shadow/phantom to support more syscalls. - Did some straceing to identify more syscalls we need for tor Week of June 8 (planned): - Hand off OnionPerf work for now (#33974: update to tgen 1.0) - Identify more syscalls needed to simulate Tor. (use nm/objdump; chutney; src/lib/sandbox) - Figure out (how to avoid implementing) netlink - Check whether we already can interpose Tor's name lookups (via libevent) Week of June 8 (actual): - shadow/phantom: Identified and documented syscalls needed for Tor, based on strace + sandbox config. https://github.com/shadow/shadow/issues/849 - Reviewed PR to add file IO support for shadow/phantom - More review for adding yaml config for shadow/shadow Week of June 15 (planned): - Work out logging from the shim with the new file IO design - Help flesh out support for syscalls and libraries needed to run Tor - Start looking into code-coverage tools (gcov) Week of June 15 (actual): - Fixed logging destination from the shadow/phantom shim - Patched libc from package sources to allow benchmarking for "preload" interposition mechanism without having to reimplement more of libc - A little bit of initial benchmarking of shadow/phantom. (So far much slower, but have some ideas for improvement) - Backported centos 7 fixes for shadow https://github.com/shadow/shadow/pull/851 Week of June 22 (planned): - More profiling of shadow/phantom and start work on optimizations pastly: Week of 18 May (planned): - Finish bones of external FlashFlow repo (python?) to control tor clients that perform FF measurements - Finish bones of little-t tor changes s.t. measurement can be performed - Discuss FlashFlow with network team devs as they have questions c: Week of May 25 (planned): - close up work on #33609 - get started on other s55 tickets, potentially knock out 'easy' ones first and take it from there - update https://trac.torproject.org/projects/tor/wiki/doc/gsoc with my information Week of May 25 (actual): - #33609 ready for review - started hunting down and working on other Sponsor55-can and -must issues - talking in #tor-project about wiki Week of June 1 (actual): - opened and made #34381 ready for review - IPv4 part of #32888 Week of June 8 (planned): - #33598 - IPv6 part of #32888 <-- do you have a ticket for it? Week of June 8 (actual): - #32888 IPv6 PR: https://github.com/torproject/tor/pull/1932 - requested reproducibility info for https://bugs.torproject.org/33598 -- maybe I'll start thread on tor-dev@ since trac is read-only - wrote Outreachy blog post explaining Tor's IPv6 goals Week of June 15 (planned): - during meeting, poke someone about https://github.com/torproject/chutney/pull/66 - chutney work with nickm (#34445 - #34448) - force myself to remain regularly active on tor-dev@ so we can get things done more efficiently :) - in general just check behind myself and others to clean up open issues in need of commentary or review Week of June 15 (actual): - started work on more chutney documention - opened discussions on gitlab about chutney components Week of June 22 (planned): - continue chutney discussion/work - #32888 / work on Address config to support IPv6 dgoulet: Week of 15/06 (actual): - prop312: Worked on #33233. Almost done! Needs clean up but it was way longer than I expected. - Helped the way I could with Gitlab migration - Worked with asn on PoW proposal (technical appendix) - While measuring HS DDoS performance, I found #40006. Week of 22/06 (planned): - Continue on s55 work (prop312) - Reviews and merges. - If time allows, patch for #40006. -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

February - May 2020 User Feedback Report
by Nicolei Ocaña 22 Jun '20

22 Jun '20

Hiya Welcome to the User Feedback Report for the months of February to May 2020. Hopefully, everyone is staying safe and socially distant/healthy :) tl;dr: Questions with minimal to no information (other than "Tor Browser won't open," "Tor unexpectedly exited. This might be due to a bug in Tor itself, another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start," and "Gah! Your tab just crashed!") (26 occurrences), video playback questions (14), "Run as administrator" issue [1] (6), letterboxing feature (6), and CAPTCHA loop issue on some websites (5) dominated RT. Reddit is constantly questioning letterboxing and trying to identify the true The Hidden Wiki (there is none). Metrics from Frontdesk queue: in the last month we answered more than 325 requests on Frontdesk queues. We still have a lot of spam that we clean every day. ## Frontdesk highlights a) Tor Browser: Users are unaware of the purpose of Letterboxing. They are under the impression that this is a Tor Browser layout bug. b) Browsing: Users identified the CAPTCHA while browsing with Tor Browser. Some users reported that infinite CAPTCHA loop included trac.torproject.org and sites where users logged into email or bank accounts. b) Browsing: Users remarked not being able to watch YouTube videos on YouTube.com. Users are unaware that NoScript blocks larger media elements by default. For users connecting on Tor Exit nodes blocked by YouTube/Google, we recommended to use <https://invidio.us/> as a workaround. c) Website: Users installed the Windows 64-bit version of the desktop version of the Tor Browser because they presumed by clicking the "Download for Windows" button, their platform would be auto-identified by the website. d) VPN products, fake Tor Browsers and "Tor Browsers": Users are confused which application, both desktop version and mobile, are created by the Tor Project. Users cite issues with "The Tor Browser," confusing us for Tor Browser + Private VPN combinations, the Tor Browser version offered on Tails, or the Tor Browser on iPhones. We had some occurrences of iOS users asking support for their money back because they installed an App that wasn't Tor Browser / Onion Browser. Now, on to the feedback! Scroll further down to see a summary of Reddit posts, some points from Google Play Store reviews, a list of the most common Stack Exchange tags from the month, and a collection of some notable issues and bugs mentioned by users in the past few months. ## Common questions on Frontdesk - Questions regarding Letterboxing: "Last update of my Tor-Browser has an issue, it does not go full screen, well it goes full screen, the browser itself but not the web page, the web pages i open don't fill up the browser and it is annoying." User titled tickets: "Graphical glitches - Tor 9.5" and "How to enable normal screen resolution !?" - Questions involving the CAPTCHA loop - Questions regarding video playback. - Questions regarding donations (can't donate on Tor Browser, follow-up on gifts, etc.) - Questions with the prompt: "Tor unexpectedly exited. This might be due to a bug in Tor itself, another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start." - Question with minimal to no information other than "Tor Browser won't open" (or something similar) - Questions "Where I can download Tor Browser in my language?" and "How can I change the website language?" - Users with "proxy errors" or requesting bridges on countries that are censoring the internet or are blocking Tor. - Questions involving dll files are missing: "I have windows 7 I downloaded TOR with no trouble but when I try to run it a message comes up saying, my computer does not have ms-win.crt 11-1-0.dll. I dont know what that means. Can you help." - Questions explicitly stating that "I cannot download the Tor Browser from <https://www.torproject.org/>" - Questions concerning installing the Windows 32-bit version - Questions regarding using the Onion Browser for iOS Phones - Questions concerning using fake Tor Browsers from App Store not developed or endorsed by The Tor Project ## Most common questions of Reddit (/r/TOR) - Tor exited unexpectedly - Questions regarding using Tor and a VPN - Can my ISP see that I am using Tor? - What's the difference between using Tor Browser, Orbot: Tor for Android, and Tor Browser (Alpha) - Tor blocked everywhere ## TBA Reviews & Feedback on Google Play Store The average review score is 4.3 stars with 38,215 total reviews. Below are some common problems mentioned by users in Google Play reviews: - Can't Can't take screenshots [3] - Browsing speed a bit slow and sluggish - Save Image option doesn't work [7] - How does one ask for a "New Tor Circuit for This Site" on mobile [6] ## Most common stack exchange tags tor-browser-bundle: 15 asked in June configuration: 14 June hidden-services: 9 June anonymity: 7 asked since February security: 7 asked since February relays: 6 asked in June ## Notable bugs, fixes, & issues mentioned by users - #29470 [2] - error message torBrowser-8.0.5-osx6 No Mountable file systems - OPEN - #27987 [3] - Add setting for enabling/disabling flag_secure in Android browser (a.k.a. Mobile screenshot issue ) - OPEN - #25959 [4] - Add uBlock Origin to Tor Browser Bundle - CLOSED - #22089 [5] - Add Decentraleyes to slighten off a bit Exit traffic and work around some CDNs blocking of Tor - OPEN - #25764 [6] - Improve how circuits are displayed to the user on Android - OPEN - #33702 [8] - RSA_get0_d could not be located in the dynamic link library tor.exe - OPEN --- Other user suggestions: - "Great browser, but it would be nice if an update brought a dark theme and the torbutton from the PC version (the little onion button). If some how a tor developer see's this please add those two things for the mobile version and thank you for making a great browser." - "I'd request uBlock Origin to be added to Tor, it's been recommended several times and there's multiple forum posts and Reddit posts about it. Not having it only decreases privacy and security. Also, could you add an option to donate to Tor via bitcoin, seems incredibly inadequate that an organization preaching for privacy and security does not have any means of supporting them through any alt coins." --- Whew! Those were a lot of months to cover! Thanks for reading! Hopefully we go back to these per month :)! ## Annotations 1. https://trac.torproject.org/projects/tor/ticket/33702 2. https://trac.torproject.org/projects/tor/ticket/29470 3. https://trac.torproject.org/projects/tor/ticket/27987 4. https://trac.torproject.org/projects/tor/ticket/25959 5. https://trac.torproject.org/projects/tor/ticket/22089 6. https://trac.torproject.org/projects/tor/ticket/25764 7. https://trac.torproject.org/projects/tor/ticket/31013 8. https://trac.torproject.org/projects/tor/ticket/33702

2 1

Anti-censorship meeting notes, 18 Jun 2020
by Philipp Winter 18 Jun '20

18 Jun '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-18-16.00.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday June 18th 16:00 UTC Weekly meetings, every Thursday at 16: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: * Roadmap will go into https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam <-- it will be moved into gitlab * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 <-- it will be moved into gitlab * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 <-- it will be moved into gitlab * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep == Announcements == * == Discussion == * proposal on how to use gitlab https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/28 == Actions == * == Interesting links == * Ongoing Internet measurement village talks this month: https://ooni.org/post/2020-internet-measurement-village/#schedule * https://wwdaacc20.com/ Worldwide Developers Against Apple Censorship Conference, June 22 == Reading group == * We will discuss Geneva on June 25th * https://censorbib.nymity.ch/#Bock2019a * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-06-18): * Reviewed #31282. * Wrote patch for #29184. * Deployed test branch of BridgeDB-internal metrics and fixed bugs that I discovered. * Worked on #33647. * Familiarising myself with Gitlab. * Wrapped up #33162. * Worked on #34260. Next week: * Wrap up #34260. Help with: * #33647 * #29184 cecylia (cohosh): last updated 2020-06-18 Last week: - getting used to and helping with gitlab migration - reviewed a bunch of snowflake proxy on android code - worked on getting snowflake set up for sponsor 28 test range - updated GetTor releases to Tor Browser 9.5 release - fixed a small typo in the GetTor Gitlab provider links - implemented NAT behaviour discovery at proxies and matching at broker (#34129, #33666) - began trial integration of GetTor with BridgeDb autoresponder code This week: - look at viatsk's work on NAT test suite (#25595) - revisions and hopeful merge/deployment of #34129 - add more stun servers (#30579) - Break up BridgeDB's autoresponder code and do a trial re-implementation of GetTor (#3780) - Follow up on discussions of debian obfs4proxy package - sponsor 28 evaluation prep - translations? Needs help with: juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-06-11 Last week: - Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-06-18 Last week: - provided some feedback on NAT-aware broker rendezvous (#34129) Next week: - share access to the snowflake broker CDN configuration (#30510) Help with: Antonela: 2020-06-18 - brought the TB10.0 proposal to the browser team. They are reviewing it. - reviewed personas with Dunqan this week, we will have a draft for your review by the end of the month agix:2020-06-11 Last week: -Started taking a look at #34318 -(Will be occupied due to university exams till 06-26) Next week: -Work on fixing #34318 Help with: - thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with: HashikD: 2020-04-28 Last week: - Made a code patch for most tickets related to Part A of project. Next week: - Learning about WebSocket and deciding on WebSocket library. Help with:

1 0