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


Ignore:
Timestamp:
Apr 3, 2017, 3:58:13 PM (2 years ago)
Author:
alison
Comment:

formatting changes

Legend:

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

    v1 v2  
    11== Pluggable Transports ==
    22
    3 * We started with an overview Tor's existing PT system:
     3We started with an overview Tor's existing PT system:
    44
    5 * tor launches obfs4proxy, which is written in Go, as a separate process.
     5tor launches obfs4proxy, which is written in Go, as a separate process.
    66tor communicates with obfs4proxy via an IPC mechanism defined in the PT 1.0
    77specification. This IPC mechanism consists of three methods of
     
    2020TorBrowser.
    2121
    22 * We then discussed new developments in the PT ecosystem: PT 2.0,
     22We then discussed new developments in the PT ecosystem: PT 2.0,
    2323Shapeshifter, and Transport Canaries.
    2424
    25 * The PT 2.0 specification [
     25The PT 2.0 specification [
    2626https://www.pluggabletransports.info/spec/pt2draft1] was created by a
    2727committee of censorship circumvention tool developers: Tor, Lantern,
     
    3535mechanism, which allows for larger parameters.
    3636
    37 * Shapeshifter is an implementation of the PT 2.0 specification. It is forked
     37Shapeshifter is an implementation of the PT 2.0 specification. It is forked
    3838from obfs4proxy. It has two components: shapeshifter-transports and
    3939shapeshifter-dispatcher. shapeshifter-transports provide PT 2.0 Go
     
    4444obfuscation.
    4545
    46 * Transport Canaries is a project to test reachability of PTs on networks
     46Transport Canaries is a project to test reachability of PTs on networks
    4747where they might be blocked. The goal of this project is to provide
    4848packet-level network traffic capture data of PT blocking so that better PTs
     
    5050high-level PT reachability statistics to OONI.
    5151
    52 * We then talked about next steps for PTs and Tor. In order for tor to be PT
     52We then talked about next steps for PTs and Tor. In order for tor to be PT
    53532.0 compliant, the code in tor that talks to obfs4proxy must be upgraded so
    5454that it can use the PT 2.0 IPC mechanism. It is a small change, and can be
     
    5757what would be necessary in a patch was added.
    5858
    59 * In addition to patching tor, a PT 2.0-compliant implementation of the
     59In addition to patching tor, a PT 2.0-compliant implementation of the
    6060transports is needed. There are two basic options. The first option is that
    6161obfs4proxy can be replaced with Shapeshifter. The second option is that PT
     
    7373those code paths are not included when the executable is built.
    7474
    75 * Open issues to be discussed in the future are who the point of contact
     75Open issues to be discussed in the future are who the point of contact
    7676should be within Tor to discuss PT issues, how the decision making process
    7777will be made between adopting Shapeshifter vs. porting changes to
     
    7979in the Trac ticket.
    8080
    81 * We also discussed the continuing need for the development of new PTs,
     81We also discussed the continuing need for the development of new PTs,
    8282particularly as obfs4 is currently being blocked on some networks.
    8383