2.1.6

This should have been released on Mar 21, 2023.

• Minor changes on a warning log.
• Customized resolver (only for developers currently).
• Fix support for handling large wg packet (e.g. setting a larger MTU on WireGuard interface and resulting in UDP fragmentation).
• Fix timeout when not specified in the configuration file.

2.1.5

Now you can load the WireGuard server private key from a file, just like PrivateKeyFile= in the systemd.netdev(5).

2.1.4

Minor changes on traffic obfuscation.

2.1.3

Fix a theoretically possible KPA in the traffic obfuscation.

2.1.2

Change to a much more user-friendly json5 library.

2.1.1

Fix a bug that may cause packet loss when obfuscation is enabled.

2.1.0

Added optional obfuscation.

Now we have a new option named "obfs" in the config. This option should be set to the same string for the mwgp-client and mwgp-server. Set it to empty or remove it will disable the obfuscation.

Highlights of mwgp obfuscation:

• Zero MTU overhead.
• Obfuscate the whole MessageInitiation, MessageResponse, and MessageCookieReply, we also append random bytes at the end of those messages to randomize their length.
• Only obfuscate the first 16 bytes of MessageTransport for maximum performance, as the remaining payload has been already encrypted by chacha20-poly1305.
• mwgp-server will auto distinguish obfuscated and non-obfuscated peers, and it still accepts non-obfuscated peers while obfuscation is enabled. So you can still connect to the mwgp-server endpoint with the official WireGuard client even if you are using an environment that cannot run mwgp-client easily (such as WireGuard on Android).

2.0.0

The first release of mwgp!