Changes between Version 1 and Version 2 of org/meetings/2017Amsterdam/Notes/AntiCensorship


Ignore:
Timestamp:
Apr 12, 2017, 11:19:31 PM (20 months ago)
Author:
alison
Comment:

add notes

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2017Amsterdam/Notes/AntiCensorship

    v1 v2  
    88Anti-censorship technology in Tor:
    99
    10 * pluggable transports: obfs*, meek, etc.
    11 * tor is not doing super well as an anti-censorship tool
     10- pluggable transports: obfs*, meek, etc.
     11- tor is not doing super well as an anti-censorship tool
    1212
    13 * obfs4 may be blockable? there's some trac ticket
     13obfs4 may be blockable? there's some trac ticket
    1414
    15 * future PT: snowflake, using webRTC
     15future PT: snowflake, using webRTC
    1616
    17 * goal: we should be able to easily see at any point in time, which places tor works and which places it doesn't
     17goal: we should be able to easily see at any point in time, which places tor works and which places it doesn't
    1818
    19 * secret entry into the Tor network as the default / common case instead of a special case?
     19secret entry into the Tor network as the default / common case instead of a special case?
    2020
    21 * Broader development / deployment of domain fronting techniques?
     21Broader development / deployment of domain fronting techniques?
    2222
    2323Can we make other protocols look like Tor?  For instance, could services with large user bases have their users use PTs to connect to their services?