Releases: NHAS/wag
Releases · NHAS/wag
v1.4.0-pre-release
Upgrades the wag database to handle a new 'endpoint' field to resolve #12
Bug Fixes:
- After hot upgrade the wireguard endpoint watcher no longer automatically de-authenticate all users as wireguard device creation sets device endpoints to their previous value
Changes:
- make upgrade message a bit clearer to differentiate when a binary needs to be manually copied or is automatically copied
- Wag now stores the last user device endpoint in the SQLite3 database
- wag can now automatically upgrade its own database
v1.3.2-pre-release
This release is incompatible with previous versions of wag.
It is recommended that the systemd service file is updated to the current version in the respository.
Major Changes:
WgDevName
has been moved into a new configuration structureWireguard
and is now calledDevName
- Wag will now create and populate a wireguard device using netlink, when the device specified by
DevName
is not present - Wag no longer relies on
wg-quick
configuration for peers
Features:
- Netlink interoperability allows
wag
to setup/teardown a wireguard device - Hot upgrading, the VPN now does not need to be fully stopped in order to upgrade the golang components of wag this is added with the
./wag upgrade
command - Improved
control
package, now every action can be done using it
Changes:
- When a user exceeds the lockout number of attempts the error message they now get is "account locked"
- Wags XDP component is now more obviously labeled as wag in tools such as
bpftool
- The wag socket now allows whatever process group wag is in to read/write (allows for better integrations)
- No longer use the default http mux for the control mux just in case it becomes exposed
- Once a TOTP code is used, it cannot be reused
Bug Fixes:
- Fix firewall list command not outputting data
-config
is now no longer required for every cli command- Add a minimum time to registration request completion to stop timing attacks (now will take ~1 second)
v1.1.1
v1.1.0
Major Changes:
SessionTimeoutMinutes
has been replaced byMaxSessionLifetimeMinutes
to make room for sliding window sessions, that require MFA after a period of time without activity.
Features:
SessionInactivityTimeoutMinutes
, a new option in the json file which will de-authenticate/sign out users after a period of time without any network activity.- Unit testing of EBPF program
Bug Fixes:
- Fix multiple issues that occurred when
SessionInactivityTimeoutMinutes
orMaxSessionLifetimeMinutes
were disabled (set to -1)
Changes:
- Config parsing will now fail if an unknown json field is present
v1.0.6
Features:
- MFA session timeout can now be disabled by setting SessionTimeoutMinutes to -1 (this will not effect lockouts that occur due to network change)
- Add DNS option to configuration file, this automatically allows DNS addresses and will generate wg0.conf's with the DNS= option
Changes:
- Log output is now easier to parse for SIEM ingestion
Bug Fixes:
- Specifying a route as public after it has been declared as MFA now has no effect. MFA check takes precedence.
v1.0.4
v1.0.3
v1.0.2
Fix numerous bugs
- Allow clients to ping tunnel address
- Fix minor text bug in reload help text
- Fix empty private key issue if public key is supplied during registration process
- Use ParseKey instead of NewKey for base64 encoded key during registration
- Url decode registration parameters
- Fix use of nil map in config