Shapeshifter-Swift-Transports

Shapeshifter Swift Transports is a set of Pluggable Transports, written in Swift, implementing the upcoming (currently unpublished) Swift API from the Pluggable Transports 2.1 specification

Shapeshifter Transports

This is the repository for the shapeshifter transports library for the Swift programming language. If you are looking for a tool which you can install and use from the command line, take a look at the dispatcher instead.

The transports implement the Pluggable Transports 2.1 draft 1 specification available here Specifically, they implement the Swift Transports API v2.1 draft 1.

The purpose of the transport library is to provide a set of different transports. Each transport implements a different method of shapeshifting network traffic. The goal is for application traffic to be sent over the network in a shapeshifted form that bypasses network filtering, allowing the application to work on networks where it would otherwise be blocked or heavily throttled.

The following transports are currently provided by this library:

Wisp

Wisp is a native Swift transport that is compatible with obfs4 servers.

See the README for information on usage.

Optmizer

Optimizer is a pluggable transport that uses one of several possible “Strategies” to choose between the transports you provide to create a connection. It is not a standalone transport, but is rather a mechanism for choosing between various transports in order to find the one best suited for the user’s needs.

See the README for information on usage.

Protean

Protean is a pluggable transport that allows you to configure your own obfuscation.

See the README for information on usage.

Installation

This library can be installed using Swift Package Manager. Please see instructions for using an individual transport in that transport's readme.

Usage

Each transport can be used in place of a Network.Framework Connection. It is necessary to create an instance of a connection factory for the given transport and use that to create your connection. From that point forward the transports are designed to look and behave in your code in the same manner as Network.Framework. Please see the readmes for the individual transports for information on how to get a Connection instance for that transport.