summaryrefslogtreecommitdiff
path: root/transports/transports.go
AgeCommit message (Collapse)Author
2019-10-21Removed termmon and fixed compiler warningsBluesaxorcist
2019-10-21added dialer to the modes and removed unneccessary codeBluesaxorcist
2019-10-13renamed all of the iatMode strings to iat-modeBluesaxorcist
2019-10-07Added Replicant Config ParserBluesaxorcist
2019-09-30Renamed Optimizer clientBluesaxorcist
2019-09-22Fixed the problem with pointers to interfacesBluesaxorcist
2019-09-21added cases for parsing to OptimizerBluesaxorcist
2019-09-16fixed transports to use configsBluesaxorcist
2019-09-15Added Dust, Meeklite, and Replicant to dispatcher modesBluesaxorcist
Still needs fixing
2019-09-14refactoring the modesBluesaxorcist
2019-08-23Added a new way to parse transport options that allows for nested JSONDr. Brandon Wiley
2019-08-16commented out an unusable importBluesaxorcist
2018-10-15Updated list of supported transportsDr. Brandon Wiley
2017-02-22Removed obsolete client factoriesBrandon Wiley
2016-12-11Temporarily disabling all transports that have not yet been migrated to the ↵Brandon Wiley
PT 2.0 Go API
2016-11-15Changed import paths to use shapeshifter-transports instead of obfs4Brandon Wiley
2016-03-21Updated import pathsBrandon Wiley
2015-10-29Add the "meek_lite" transport, which does what one would expect.Yawning Angel
This is a meek client only implementation, with the following differences with dcf's `meek-client`: - It is named `meek_lite` to differentiate it from the real thing. - It does not support using an external helper to normalize TLS signatures, so adversaries can look for someone using the Go TLS library to do HTTP. - It does the right thing with TOR_PT_PROXY, even when a helper is not present. Most of the credit goes to dcf, who's code I librerally cribbed and stole. It is intended primarily as a "better than nothina" option for enviornments that do not or can not presently use an external Firefox helper.
2015-06-01Delay transport initialization till after logging has been setup.Yawning Angel
2015-02-17Add support for acting as a ScrambleSuit client.Yawning Angel
This allows obfs4proxy to be used as a ScrambleSuit client that is wire compatible with the obfs4proxy implementation, including session ticket support, and length obfuscation. The current implementation has the following limitations: * IAT obfuscation is not supported (and is disabled in all other ScrambleSuit implementations by default). * The length distribution and probabilites are different from those generated by obfsproxy and obfsclient due to a different DRBG. * Server support is missing and is unlikely to be implemented.
2014-08-17Massive cleanup/code reorg.Yawning Angel
* Changed obfs4proxy to be more like obfsproxy in terms of design, including being an easy framework for developing new TCP/IP style pluggable transports. * Added support for also acting as an obfs2/obfs3 client or bridge as a transition measure (and because the code itself is trivial). * Massively cleaned up the obfs4 and related code to be easier to read, and more idiomatic Go-like in style. * To ease deployment, obfs4proxy will now autogenerate the node-id, curve25519 keypair, and drbg seed if none are specified, and save them to a JSON file in the pt_state directory (Fixes Tor bug #12605).