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 'aed4b72389'
${ noResults }
obfs4/ChangeLog

25 lines
1.1 KiB
Plaintext
Raw Normal View History Unescape Escape

Update the ChangeLog (No functional changes).
9 years ago
Changes in version 0.0.5 - UNRELEASED:
Update the ChangeLog (No functional changes).
9 years ago
- Go vet/fmt fixes, and misc. code cleanups. Patches by mvdan.
Change the import path for go.net. The Go developers decided to move the go.net repository to golang.org/x/net, and also to transition from hg to git. This wasn't changed when the go.crypto imports were since the 'proxy' component doesn't have imports that break, so the old code still works. While the change here is simple (just update the import location), this affects packagers as it now expects the updated package. Sorry for the inconveneince, I blame the Go people, and myself for not just doing this along with the go.crypto changes.
9 years ago
- Changed the go.net import path to the new location (golang.org/x/net).
Update the ChangeLog (No functional changes).
9 years ago
Do the release ritual for obfs4proxy-0.0.4.
9 years ago
Changes in version 0.0.4 - 2015-02-17
Improve the performance of the obfs4 handshake test. Exhaustively testing padding combinations is really slow, and was causing timeouts during the Debian ARM package build process. Attempt to improve the situation by: * Reusing the client and server keypair for all of the tests, to cut runtime down by ~50%. * Splitting the client side and server side tests up, as it appears the timeout is per-test case. If this doesn't fix things, the next thing to try would be to reduce the actual number of padding lengths tested, but that is a last resort at the moment.
10 years ago
- Improve the runtime performance of the obfs4 handshake tests.
Change the import path for go.crypto. The Go developers decided to move the go.crypto repository to golang.org/x/crypto, and also to transition from hg to git. The tip of tree code.google.com copy of the code is broken due to the import paths pointing at the new repository. While the change here is simple (just update the import location), this affects packagers as it now expects the updated package. Sorry for the inconveneince, I blame the Go people.
10 years ago
- Changed the go.crypto import path to the new location (golang.org/x/crypto).
Add support for acting as a ScrambleSuit client. This allows obfs4proxy to be used as a ScrambleSuit client that is wire compatible with the obfs4proxy implementation, including session ticket support, and length obfuscation. The current implementation has the following limitations: * IAT obfuscation is not supported (and is disabled in all other ScrambleSuit implementations by default). * The length distribution and probabilites are different from those generated by obfsproxy and obfsclient due to a different DRBG. * Server support is missing and is unlikely to be implemented.
9 years ago
- Added client only support for ScrambleSuit.
Improve the performance of the obfs4 handshake test. Exhaustively testing padding combinations is really slow, and was causing timeouts during the Debian ARM package build process. Attempt to improve the situation by: * Reusing the client and server keypair for all of the tests, to cut runtime down by ~50%. * Splitting the client side and server side tests up, as it appears the timeout is per-test case. If this doesn't fix things, the next thing to try would be to reduce the actual number of padding lengths tested, but that is a last resort at the moment.
10 years ago
Do the release ritual for obfs4proxy-0.0.3.
10 years ago
Changes in version 0.0.3 - 2014-10-01
Change the bridge line format to be more compact. Instead of "node-id" and "public-key" that are Base16 encoded, use "cert" which contains the "node-id" and "public-key" in Base64 encoded form. This is more compact and cuts the length down by 49 characters.
10 years ago
- Change the obfs4 bridge line format to use a "cert" argument instead of the
previous "node-id" and "public-key" arguments. The "cert" consists of the
Base64 encoded concatenation of the node ID and public key, with the
trailing padding removed. Old style separated bridge lines are still valid,
but the newer representation is slightly more compact.
Do the release ritual for obfs4proxy-0.0.2.
10 years ago
Changes in version 0.0.2 - 2014-09-26
Write an example obfs4 bridge line to "obfs4_bridgeline.txt". Write an example client bridge line suitable for use with the running obfs4 server instance to "obfs4_bridgeline.txt" for the convenience of bridge operators.
10 years ago
- Write an example client bridge line suitable for use with the running obfs4
server instance to "obfs4_bridgeline.txt" for the convenience of bridge
operators.
Add a man page for obfs4proxy.
10 years ago
- Add a man page for obfs4proxy.
Do the release ritual for obfs4proxy-0.0.1.
10 years ago
Changes in version 0.0.1 - 2014-09-03
Add a ChangeLog and dump the version when invoked with "-v".
10 years ago
- Initial release.