Changes between Initial Version and Version 1 of org/meetings/2018MexicoCity/Notes/AntiCensorshipTeam

Oct 1, 2018, 10:59:53 PM (9 months ago)



  • org/meetings/2018MexicoCity/Notes/AntiCensorshipTeam

    v1 v1  
     2- There are places where Tor is blocked, we need to strengthen the story
     3- Need to make the network and techniques more resilient, and *also* improve the user experience
     4- What should the scope of our anti-censorship team be?
     5- PTs, BridgeDB/Bridges, Tor Browser UX, Rapid Response, Education / Advocacy, Relationships
     8- Tor Metrics and OONI identify use/blockages and generates report
     9- Tor does work in many places with/without bridges!
     10- Debugging / investigation does happen via individuals on Tor IRC, other channels
     11- We have many things in Tor that deals with censorship circumvention user story
     12- We have partners, researchers, communities that are working on this
     13- Funding coming/available to focus on anti-censorship of Tor
     16- We don't make censorship measurement actionable; we have piecemeal solutions, but not integrated
     17- Don't have anyone on the team today to consume alerts/data/input
     18- No public point of contact, collab around Tor censorship
     19- Many censorship circumvention techniques are unmaintained, or not resourced enough
     20- Pluggable Transports not actively maintained by anyone
     21- Tor Browser UX is needed for users (ala bridge request / mote work)
     22- Need to balance anonymity vs anti-censorship use cases and needs
     23- PT development is mostly done outside of Tor, no ownership of productization side
     24- People aren't aware of the Support portal, how can we work with partners with help desks to upstream support
     27- Create a known point of contact to report Tor censorship
     28- Identity all countries where Tor is blocked, then research methodoligies, techniques, so we can respond
     29- Rapid Response and Education Materials
     30- Network Team is looking into this, but need to find way for good handoff to incoming anti-Censorship team/developer
     31- Anti-Censorship Team should be connected/with the Network Team as onboarding/transition
     32- Team should be broad and include community partners from PT community, Adversary lab, Guardian Project, etc other working on anti-censorship project
     33- Adversary Lab tool can be used to analyze blocking, generate new forms of PT's
     34- Need more PT / bridges, in more places
     35- Create new easy packages for volunteer bridge operators
     36- Anti-Censorship developer maybe should also be coordinator/manager of virtual/community team
     39- Mainstream ISPs in Mexico block Tor DirAuth, so they cannot run relays; home's can't run relays
     40- ISPs blocking legitimate use of the network, because it looks like reselling the network connection
     41- Anti-censorship event will likely happen within months, and we'll feel pressure from urgent situation
     42- This needs to be prioritized and not subsumed by other things
     46- Do we have something in place if Tor is blocked in a place?
     47-- We don't have a systematic, automated (realtime?) way
     48-- Tor metrics graphs can show something odd (drop in connections, traffic)
     49-- Some cases are annotated in trac list, or send out via mailing list
     50-- OONI has tests for this, testing vanilla Tor, and bridges shipped in Tor Browser are blocked
     52- What are challenges in automating alerts when there are spikes in Tor Metrics?
     53-- There were some experimental stuff in anomaly detection, by several groups
     54-- Nobody on the receiving side of the data; need humans to check for false positives
     55-- Can we look at change in daily average users? No one watching those charts
     57- What does "Rapid Response" mean?
     58-- 1) figure out is it happening?
     59-- 2) how/what is happening?
     60-- 3) publish ways to work around through public communication
     61-- .... 6) prevent this blocking from the future