Changes between Version 1 and Version 2 of doc/PluggableTransports/SnowFlakeEvaluation


Ignore:
Timestamp:
Jul 8, 2016, 9:07:07 PM (3 years ago)
Author:
yawning
Comment:

Update. to fix a brainfart.

Legend:

Unmodified
Added
Removed
Modified
  • doc/PluggableTransports/SnowFlakeEvaluation

    v1 v2  
    5959
    6060=== 3.2 Is the implementation cross-platform?  How about mobile support? ===
     61The implementation is cross platform assuming it is supported by a modern version of Go and runs an operating system supported by Chromium's WebRTC implementation.
    6162
     63The main bottleneck to portability, including mobile support, is likely the actual WebRTC implementation's portability rather than the Go or intermediary proxy applications.
     64
     65=== 3.3 What is the implementation's build process like, how easy is it to deploy, and what is deployment scaling like? ===
    6266The implementation is [https://github.com/keroserene/go-webrtc/issues/29 not capable of being built deterministically], though the preliminary work has been done to integrate it into Tor Browser's build process.
    6367
    6468Deployment scaling is primarily handled via having people include the proxy code on their websites (nb: The [https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/proxy/README.md instructions for embedding] currently 404).  There has not been a drive to do so due to the early stage of development, and it is an open question to how many sites will volunteer, and how many site visitors allow and support WebRTC.
    65 
    66 The main bottleneck to portability, including mobile support, is likely the actual WebRTC implementation's portability.
    67 
    68 === 3.3 What is the implementation's build process like, how easy is it to deploy, and what is deployment scaling like? ===
    69 
    70 basket2proxy is capable of being built deterministically and is planned to be integrated into the Tor Browser's build process.  Deployment scaling is similar to any other bridge based Pluggable Transport.
    7169
    7270=== 3.4 How is the implementation's code from a security and maintainability perspective? ===