|Yawning Angel 9ca113c4af Add a LICENSE file, no functional changes.||4 years ago|
|crypto||4 years ago|
|ext||4 years ago|
|framing||4 years ago|
|handshake||4 years ago|
|CODE_OF_MERIT.md||4 years ago|
|LICENSE||4 years ago|
|README.md||4 years ago|
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.
ed25519- Ed25519, Edwards curve field arithmatic
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 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.
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.
Using a PQ signature algorithm such as SPHINCS256 would solve this problem, however the key and signature sizes are still larger than what I feel comfortable with being able to obfsucate.
Yeah, this uses SHA3 instead of whatever trendy BLAKE variant kids like these days.
If your system has busted PMTUD, this probably won't work at all. Not my problem. Complain to your OS vendor.
Write a formal specification.
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.