This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
Releases: chadsr/NordVPN-NetworkManager
Releases · chadsr/NordVPN-NetworkManager
v0.5.0
- Set default best score to -1, to catch cases where all available options score 0 (resulting in no connection added) + raised load percentage to 95% to yield a 0 score (#84)
- Custom DNS servers via settings is now possible (#79)
- Correct Onion over VPN -> Onion Over VPN (#85)
- Experimental 'slow-mode' (sync -s) (#83, #84)
- Live progress during benchmarking
- RPM package fix for wrongly used library directory (#78)
- Executable now installed to /usr/bin instead of /usr/local/bin
- Settings/input case fixes (everything is converted to lower-case)
v0.4.0 - DNS Update + Benchmarking Statistics + Fixes
- More detailed benchmarking statistics
- Updated DNS nameservers
- Bug fixes and usage improvements
v0.3.3 - New Configs Endpoint + Small Fixes
- Updated the location configuration files are downloaded from, to the new NordVPN endpoint.
- Fixed package requirements to work for Debian installs.
- Made the README a little more concise.
- Refactors
v0.3.2 - DNS & Dependencies Patch
- /etc/resolv.conf wasn't always being released when a VPN disconnected, causing NordVPN DNS servers to still be enforced and stopping domain resolves from working. This should now be fixed.
- .deb and .rpm packages were missing the iputils (specifically ping) dependency, causing problems on distributions which don't use iputils by default.
- README updated to show the new repository installation methods.
Typo Fixes, Packaging Fixes
Small patch release for some typos and to fix requirements for the deb package, which were preventing installation on Ubuntu.
v0.3.0 - Change your MAC Edition
nordnm mac
command for changing the NetworkManager MAC address configuration, allowing for randomisation and many other privacy related settings (Only supported in NetworkManager 1.4.0 onwards).- Credentials are verified upon entering (#59).
- Configuration files are only downloaded if they have changed, to save time and bandwidth.
- Pinging during benchmarking will now be somewhat faster (around 2x from testing so far).
- Experimental building of .deb and .rpm packages for easier installation.
- Version argument... for checking the version.
v0.2.1 - DNS Leak Fix (Ubuntu & Friends)
A patch release for Ubuntu based systems (and possibly more, it's hard to say)
- Fixed DNS leak protection for Ubuntu and related distros
Long explanation:
Ubuntu uses /etc/resolv.conf
as a symlink to /run/resolvconf/resolv.conf
. This caused my method of locking down nameservers to not function correctly.
This fix temorarily moves the symlink, so the script can handle /etc/resolv.conf
manually, without relying on trusting resolvconf or any other service to stop leaks.
v0.2.0 - DNS Leaks Be Gone!
- /etc/resolv.conf is now explicitly modified and "frozen" (made immutable) so that nameservers can not be modified, when an VPN is active. This should hopefully prevent any future possibilities of DNS request leaks.
- Old nordnm files that are no longer used will be cleaned up by newer versions of itself.
- The scoring function has been changed to not accept servers with greater than 90% load. The function itself now uses an inverse exponential score, which gives a better spread.
- You can now list active servers with their metrics using
nordnm list --active-servers
- On auto-connect, server metrics are now shown
- I will begin experimenting with builds on Launchpad, but this has a long way to go, still (Debian build/release process is horrible).
- Refactors and cleanups
v0.1.0 - Improved Arguments, New Features & Fixes
- Switched to semantic versioning.
- Out of 'Alpha' development. I now consider this project stable enough to get a normal version string :).
- Overhauled arguments to allow for more diverse behaviour.
- Disabling VPN is optional when syncing/benchmarking.
- Some minor refactors.
Auto-Connect / Kill-Switch Fix
Auto-Connect and Kill-Switch scripts were not working on certain distributions due to differences in execution environment.
This update should now fix these differences.