VPN Manager 0.2.0

What's new

• Each App on its own in the traffic path. On the Overview, every managed App in a strict sandbox now has its own node with its own live download and upload, instead of one combined "App sandbox" node. The split follows the ports each App's processes hold and the port forwards that end at it; traffic of a connection opened within the last couple of seconds counts toward the sandbox total until the App is seen holding its port.
• Getting-started steps removed from the Overview.
• Socket folder checks. vpnctl, the web UI's controller and the sandbox launcher check, before connecting to VPN Manager's sockets, that the folder belongs to you and that nobody else can write to it.
• macOS, enforced proxy: Apps reach their proxy port over IPv4 only. Java programs need -Djava.net.preferIPv4Stack=true (the README and the capability text say so).
• Clearer messages when a connection or an operation is not found.

For developers

• A stricter static baseline for the Rust and scripts code (more Clippy and rustc lints, rustfmt, cargo-deny, typos, taplo, ShellCheck, shfmt); the setup is in docs/development.md.
• Tests create their folders with explicit modes, so they also pass under a umask of 002.

Install or upgrade

curl -fsSL https://raw.githubusercontent.com/DennySORA/vpn-manager/main/scripts/install.sh | sh

Running it again over 0.1.0 upgrades in place; if the new version does not start, the previous one comes back. Managed Apps restart during the upgrade.

Each installer has a .sha256 and a .notices.txt (the licences of the software it contains). vpnd, and so the installers, are distributed under GPL-3.0-or-later because they include the AirVPN adapter; the rest of the source is MIT OR Apache-2.0 (see NOTICE).

VPN Manager 0.1.0

The first public release of VPN Manager.

Run several WireGuard exits side by side on your own computer, and decide which programs use which one: each exit is a local SOCKS5/HTTP proxy, and a program you choose can be started so that the tunnel is its only way out. Protected traffic either leaves through the tunnel of its connection, or it fails.

README: English · 繁體中文 · 日本語

Install

Linux (x86_64 or aarch64, glibc 2.35 or newer, with a systemd user session) or macOS 11 or newer (Apple silicon or Intel). No root needed.

curl -fsSL https://raw.githubusercontent.com/DennySORA/vpn-manager/main/scripts/install.sh | sh

Or download the installer for your platform below, check it against its .sha256 (sha256sum -c, on macOS shasum -a 256 -c), make it executable and run ./vpn-installer-0.1.0-<os>-<arch> install. Then open http://127.0.0.1:18765.

File	Platform
vpn-installer-0.1.0-linux-x86_64	Linux x86_64
vpn-installer-0.1.0-linux-aarch64	Linux aarch64
vpn-installer-0.1.0-darwin-arm64	macOS, Apple silicon
vpn-installer-0.1.0-darwin-x86_64	macOS, Intel

Each installer comes with a .sha256 and a .notices.txt that holds the licences of the third-party software inside it (vpn-installer licenses prints the same text).

Good to know

• This is an early release. It is used every day on Linux x86_64; the macOS and Linux aarch64 builds have had much less use, and strict isolation is Linux only. The API, the configuration and the data formats may still change in incompatible ways.
• There is no login. By default the web interface and the API answer only on this computer and only to programs of the same user; whoever can use them can start programs as you.
• The macOS installers are not signed or notarized. If macOS blocks one that a browser downloaded, remove the quarantine attribute (xattr -d com.apple.quarantine <file>) before running it.

Licence

MIT OR Apache-2.0, except the AirVPN adapter, which is GPL-3.0-or-later; vpnd and the installers contain it and are therefore distributed under GPL-3.0-or-later. The source of this release is this repository at the tag v0.1.0. See NOTICE.