Hello,
The people that have been following Pluggable Transport development may
know that I have been working on something tentatively called obfs4
recently. It's rapidly approaching the point where I would like to
open it up for review and feedback, hence the e-mail.
A quick and dirty
David Fifield:
Have you ever wondered what makes the Tor protocol fingerprintable, and
makes pluggable transports necessary? Have you wondered how obfs3
obscures byte patterns in Tor? What a flash proxy WebSocket connection
actually looks like, and why it defeats IP blocking but not DPI?
You could use one of the controller libraries (stem if you want
synchronous, txtorcon if async/Twisted) to do this; they don't have to
modify the torrc directly, just manipulate configuration via GETCONF and
SETCONF. For Tails, this probably won't work unless you're root until
#11291 is fixed
obfs4 is ScrambleSuit with djb crypto. Instead of obfs3 style
UniformDH and CTR-AES256/HMAC-SHA256, obfs4 uses a combination of
Curve25519, Elligator2, HMAC-SHA256, XSalsa20/Poly1305 and
SipHash-2-4.
Elligator... cool!
* Development was done with go1.2.x, older versions of the
Thanks, this is really helpful.
On 05/20/14 21:10, meejah wrote:
Micah Lee mi...@micahflee.com writes:
When you run onionshare.py, it modifies /etc/tor/torrc and reloads the
Tor config, and when it's done it restores the original torrc and
reloads again.
You could use one of the
On Wed, 21 May 2014 12:22:46 +
David Stainton dstainton...@gmail.com wrote:
obfs4 is ScrambleSuit with djb crypto. Instead of obfs3 style
UniformDH and CTR-AES256/HMAC-SHA256, obfs4 uses a combination of
Curve25519, Elligator2, HMAC-SHA256, XSalsa20/Poly1305 and
SipHash-2-4.
