This is a look-like nothing obfuscation protocol that incorporates ideas and concepts from Philipp Winter's ScrambleSuit protocol. The obfs naming was chosen primarily because it was shorter, in terms of protocol ancestery obfs4 is much closer to ScrambleSuit than obfs2/obfs3.
The notable differences between ScrambleSuit and obfs4:
As an added bonus, obfs4proxy also supports acting as an obfs2/3 client and bridge to ease the transition to the new protocol.
It's my protocol and I'll obfuscate if I want to.
Since a lot of the changes are to the handshaking process, it didn't make sense to extend ScrambleSuit as writing a server implementation that supported both handshake variants without being obscenely slow is non-trivial.
Build time library dependencies are handled by the Go module automatically.
If you are on Go versions earlier than 1.11, you might need to run
go get -d ./... to download all the dependencies. Note however, that modules always use
the same dependency versions, while
go get -d always downloads master.
go list -m -u allfor build time dependencies.
`go build -o obfs4proxy/obfs4proxy ./obfs4proxy`
To install, copy
./obfs4proxy/obfsproxy to a permanent location
Client side torrc configuration:
ClientTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy
Bridge side torrc configuration:
# Act as a bridge relay. BridgeRelay 1 # Enable the Extended ORPort ExtORPort auto # Use obfs4proxy to provide the obfs4 protocol. ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy # (Optional) Listen on the specified address/port for obfs4 connections as # opposed to picking a port automatically. #ServerTransportListenAddr obfs4 0.0.0.0:443
On modern Linux systems it is possible to have obfs4proxy bind to reserved
ports (<=1024) even when not running as root by granting the
CAP_NET_BIND_SERVICE capability with setcap:
# setcap 'cap_net_bind_service=+ep' /usr/local/bin/obfs4proxy
obfs4proxy can also act as an obfs2 and obfs3 client or server. Adjust the
ServerTransportPlugin lines in the torrc as
obfs4proxy can also act as a ScrambleSuit client. Adjust the
ClientTransportPlugin line in the torrc as appropriate.
The autogenerated obfs4 bridge parameters are placed in
DataDir/pt_state/obfs4_state.json. To ease deployment, the client side
bridge line is written to
We found that 0xacab.org/leap/obfs4-deprecated demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket installs a GitHub app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.