Obfsy McObfsface

Yawning Angel 87c1e0ed50 Add a gitignore file. 4 years ago
crypto 374790b515 Consolidate the x25519 stuff living under ext/ to a single package. 4 years ago
ext 374790b515 Consolidate the x25519 stuff living under ext/ to a single package. 4 years ago
framing bf0c8d0e2d Initial (incomplete) client implementation. 4 years ago
handshake 76f6d342bc Enforce the minimum padding length at the handshake obfuscation layer. 4 years ago
.gitignore 87c1e0ed50 Add a gitignore file. 4 years ago
CODE_OF_MERIT.md f71885fdfd Initial import. 4 years ago
LICENSE 9ca113c4af Add a LICENSE file, no functional changes. 4 years ago
README.md 8978100bf0 Switch the identity code over to golang.org/x/crypto/ed25519. 4 years ago
client.go 0a0b910989 Clamp the various read sizes to plausible/sensible values. 4 years ago
common.go 0a0b910989 Clamp the various read sizes to plausible/sensible values. 4 years ago
padding_null.go 6b6297d047 Add code for re-enabling Nagle's algorithm. 4 years ago
server.go 0a0b910989 Clamp the various read sizes to plausible/sensible values. 4 years ago
version_check.go bf0c8d0e2d Initial (incomplete) client implementation. 4 years ago
version_check_stub.go bf0c8d0e2d Initial (incomplete) client implementation. 4 years ago

README.md

basket2 - Obfsy McObfsface

Yawning Angel (yawning at schwanenlied dot me)

basket2 is the next transport in the obfs series. It derives inspiration primarily from obfs4 and predecessors, and incorporates ideas initially prototyped in the experimental basket transport.

Features:

  • Authentication, data integrity, and confidentiality.
  • Active probing resistance.
  • Passive fingerprinting resistance, significantly improved over obfs4.
  • Client driven dynamic negotiation of runtime padding to better suit various adversary models.
  • Better separation between the handshake obfuscation and the authenticated key exchange mechanisms.
  • Significantly improved link layer framing.
  • Optional user authentication.
  • Post-quantum forward secrecy.
  • License switch from 3BSD to AGPL for more Freedom.

Dependencies:

  • Go 1.6.x or later - (May work with older versions, don't care if they don't)
  • golang.org/x/crypto - SHA3, Curve25519, Ed25519, Poly1305
  • github.com/dchest/siphash - SipHash-2-4
  • git.schwanenlied.me/yawning/a2filter.git - Active-Active Bloom Filter
  • git.schwanenlied.me/yawning/chacha20.git - (X)ChaCha20
  • git.schwanenlied.me/yawning/newhope.git - New Hope
  • git.schwanenlied.me/yawning/x448.git - X448

Notes:

  • I am waiving the remote network interaction requirements specified in Section 13 ("Remote Network Interaction; Use with the GNU General Public License") of the AGPL, per the terms of Section 7 ("Additional Terms"), for users that:

    • Are using the software exclusively to operate a publically accessible Bridge to provide access to the public Tor network as a Tor Pluggable Transport server. This means:

      The Bridge publishes a descriptor to the Bridge Authority, and is available via BridgeDB OR is a default Bridge pre-configured and distributed with Tor Browser, and uses basket2 as a server side Pluggable Transport for said Bridge.

  • All other users MUST comply with the AGPL in it's entirety as a general rule, though other licensing arrangements may be possible on request. I will likely be fairly liberal here, so please contact me if the current licensing is unsuitable for your use case.

  • The post-quantum cryptography does not apply to active attackers in posession of a quantum computer, and only will protect pre-existing data from later decryption.

  • If your system has busted PMTUD, this probably won't work at all. Not my problem. Complain to your OS vendor.

  • This COULD have been based on Trevor Perin's noise protocol framework, but I already had the framing layer design, didn't feel like bolting on PQFS to someone else's protocol, and I had to click on street signs to view said protocol's documentation.

TODO:

  • Write a formal specification.

  • Write an AVX2 optimized Poly1305 implementation.

  • Someone that's not me should write assembly optimized ChaCha20 for ARM and i386. I may do both if I feel bored enough, but no promises.

  • Write optimized assembler versions of things for gccgo (or C if that's easier). Low priority.

  • Define more padding primitives.