Archives
/
obfs4
mirror of https://gitlab.com/yawning/obfs4
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
obfs4proxy-0.0.14
obfs4proxy-0.0.13
obfs4proxy-0.0.12
obfs4proxy-0.0.11
obfs4proxy-0.0.10
obfs4proxy-0.0.9
obfs4proxy-0.0.8
obfs4proxy-0.0.7
obfs4proxy-0.0.6
obfs4proxy-0.0.5
obfs4proxy-0.0.4
obfs4proxy-0.0.3
obfs4proxy-0.0.2
obfs4proxy-0.0.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b8da220f08'
${ noResults }
obfs4/go.mod

13 lines
406 B
Modula-2
Raw Normal View History Unescape Escape

Change the canonical upstream repo location to gitlab This commit changes the upstream repo location to: https://gitlab.com/yawning/obfs4.git Additionally all the non-`main` sub-packages now have an import comment annotation. As a matter of courtesy, I will continue to push to both the existing github.com and git.torproject.org repos for the foreseeable future, though I reserve the right to stop doing so at any time.
5 years ago
module gitlab.com/yawning/obfs4.git
port to a Go module The biggest win is that we now declare what versions of each dependency we require to build. This way, building a certain version of obfs4 will always use the same source code, independent of the master branch of each dependency. This is necessary for reproducible builds. On top of that, go.sum contains checksums of all the transitive dependencies and their modules, so the build system will also recognise when the source code has been changed. Updated the build instructions accordingly. We don't drop support for earlier Go versions, but those won't get the benefit of reproducible builds unless we start vendoring the dependencies too.
6 years ago
require (
internal/x25519ell2: Initial import Replace agl's Elligator2 implementation with a different one, that fixes the various distinguishers stemming from bugs in the original implementation and "The Elligator paper is extremely hard to read". All releases prior to this commit are trivially distinguishable with simple math, so upgrading is strongly recommended. The upgrade is fully backward-compatible with existing implementations, however the non-upgraded side will emit traffic that is trivially distinguishable from random. Special thanks to Loup Vaillant for his body of work on this primitive, and for motivating me to fix it.
2 years ago
filippo.io/edwards25519 v1.0.0-rc.1.0.20210721174708-390f27c3be20
transports/meek_lite: More utls related changes * Bump the module import to a new tag * Bump the rest of the dependencies while I'm here * Add some new fingerprints from upstream * Disable my fork's AES timing sidechannel defenses
5 years ago
git.torproject.org/pluggable-transports/goptlib.git v1.0.0
transports/meeklite: uTLS for ClientHello camouflage There's still some interesting oddities depending on remote server and what fingerprint is chosen, but I can watch videos online with the chosen settings and the TBB Azure bridge. Note: Despite what people are claiming in the Tor Browser bug tracker it isn't all that hard to use the built in http client with utls. And yes, the `transport.go` code does negotiate correctly in a standalone test case (apart from compatibility related oddities).
5 years ago
github.com/dchest/siphash v1.2.1
internal/x25519ell2: Initial import Replace agl's Elligator2 implementation with a different one, that fixes the various distinguishers stemming from bugs in the original implementation and "The Elligator paper is extremely hard to read". All releases prior to this commit are trivially distinguishable with simple math, so upgrading is strongly recommended. The upgrade is fully backward-compatible with existing implementations, however the non-upgraded side will emit traffic that is trivially distinguishable from random. Special thanks to Loup Vaillant for his body of work on this primitive, and for motivating me to fix it.
2 years ago
gitlab.com/yawning/edwards25519-extra.git v0.0.0-20211229043746-2f91fcc9fbdb
golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97
golang.org/x/net v0.0.0-20210226172049-e18ecbb05110
port to a Go module The biggest win is that we now declare what versions of each dependency we require to build. This way, building a certain version of obfs4 will always use the same source code, independent of the master branch of each dependency. This is necessary for reproducible builds. On top of that, go.sum contains checksums of all the transitive dependencies and their modules, so the build system will also recognise when the source code has been changed. Updated the build instructions accordingly. We don't drop support for earlier Go versions, but those won't get the benefit of reproducible builds unless we start vendoring the dependencies too.
6 years ago
)
common: Replace the extra25519 import with an internal package I really didn't want to do this, but this should make `go get` work again, and maybe people will leave me alone.
4 years ago
Do the release ritual for obfs4proxy-0.0.12
2 years ago
go 1.16