GoVPN: News

News

Release 4.2

Fixed non-critical bug when server may fail if up-script is not executed successfully.

Release 4.1

Argon2d is used instead of PBKDF2 for password verifier hashing.
Client’s identity is stored inside the verifier, so it simplifies server-side configuration and the code.

Release 4.0

Handshake messages can be noised: their messages lengths are hidden. Now they are indistinguishable from transport messages.
Parallelized clients processing on the server side.
Much higher overall performance.
Single JSON file server configuration.

Release 3.5

Ability to use TCP network transport. Server can listen on both UDP and TCP sockets.
Ability to use HTTP proxies (through CONNECT method) for accessing the server. Server can also emulate HTTP proxy behaviour.
Updated Poly1305 library with ARM-related bugfixes.
Go 1.5+ version is highly recommended because of performance reasons.

Release 3.4

Ability to use external EGD-compatible PRNGs. Now you are able to use GoVPN even on systems with the bad /dev/random, providing higher quality entropy from external sources.
Removed -noncediff option. It is replaced with in-memory storage of seen nonces, thus eliminating possible replay attacks at all without performance degradation related to inbound packets reordering.

Release 3.3

Compatibility with an old GNU Make 3.x. Previously only BSD Make and GNU Make 4.x were supported.
/dev/urandom is used for correct client identity generation under GNU/Linux systems. Previously /dev/random can produce less than required 128-bits of random.
Updated user manual examples.

Release 3.2

Deterministic building: dependent libraries source code commits are fixed in our makefiles.
No Internet connection is needed for building the source code: all required libraries are included in release tarballs.
FreeBSD Make compatibility. GNU Make is not necessary anymore.

Release 3.1

Diffie-Hellman public keys are encoded with Elligator algorithm when sending over the wire, making them indistinguishable from the random strings, preventing detection of successful decryption try when guessing passwords (that are used to create DSA public keys). But this will consume twice entropy for DH key generation in average.

Release 3.0

EKE protocol is replaced by Augmented-EKE and static symmetric (both sides have it) pre-shared key replaced with server-side verifier. This requires, 64 more bytes in handshake traffic, Ed25519 dependency with corresponding sign/verify computations, PBKDF2 dependency and its usage on the client side during handshake.
A-EKE with PBKDF2-based verifiers is resistant to dictionary attacks, can use human memorable passphrases instead of static keys and server-side verifiers can not be used for authentication (compromised server does not leak client’s authentication keys/passphrases).
Changed transport message structure: added payload packet’s length. This will increase transport overhead for two bytes, but heartbeat packets became smaller
Ability to hide underlying packets lengths by appending noise, junk data during transmission. Each packet can be fill up-ed to its maximal MTU size.
Ability to hide underlying packets appearance rate, by generating Constant Packet Rate traffic. This includes noise generation too.
Per-peer -timeout, -noncediff, -noise and -cpr configuration options for server.

Release 2.4

Added ability to optionally run built-in HTTP-server responding with JSON of all known connected peers information. Real-time client’s statistics.
Documentation is explicitly licenced under GNU FDL 1.3+.

Release 2.3

Handshake packets became indistinguishable from the random. Now all GoVPN’s traffic is the noise for men in the middle.
Handshake messages are smaller (16% traffic reduce).
Adversary now can not create malicious fake handshake packets that will force server to generate private DH key, preventing entropy consuming and resource heavy computations.

Release 2.2

Release 2.1

Release 2.0

Release 1.5

Release 1.4

Release 1.3

Release 1.1

Release 1.0