commit df399e98642a9d54fbb061fad14874361afb3868 Author: anadahz kojgelo@inbox.com Date: Sun Dec 20 22:01:47 2015 +0100

Add obfs4proxy documentation --- test-specs/ts-011-bridge-reachability.md | 5 +++++ 1 file changed, 5 insertions(+)

diff --git a/test-specs/ts-011-bridge-reachability.md b/test-specs/ts-011-bridge-reachability.md index 194950a..e1f9caf 100644 --- a/test-specs/ts-011-bridge-reachability.md +++ b/test-specs/ts-011-bridge-reachability.md @@ -107,6 +107,8 @@ transport_name:

obfs3: for [obfs3 obfsproxy](https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/...).

+ obfs4: for [obfs4 obfsproxy](https://gitweb.torproject.org/pluggable-transports/obfs4.git/tree/obfs4proxy...). + fte: for [fte-proxy](https://fteproxy.org/)

scramblesuit: for [ScrambleSuit](http://www.cs.kau.se/philwint/scramblesuit/) @@ -135,6 +137,9 @@ bridge_address: obfsproxy_version (since 0.1.1): **string** indicating the version string of the obfsproxy client being used.

+obfsproxy_log (since 0.1.2): + **string** info level log output of obfsproxy + ## Possible conclusions

Which bridges are functioning from the given network vantage point and which