nettune

The server component (`nettune server`) requires root privileges to modify system-level network configurations (sysctl, qdisc, systemd), which is a significant security consideration. The client-server communication uses HTTP with Bearer token authentication, but the README explicitly warns that TLS termination (e.g., via a reverse proxy) is recommended for production, implying non-encrypted communication by default. API keys are passed via command-line arguments, posing a risk if shell history or process lists are compromised. The Go adapters execute external commands (`tc`, `sysctl`, `systemctl`, `ip`), raising potential concerns for command injection if user-supplied profile parameters are not rigorously sanitized (though validation is present). The JavaScript wrapper downloads binaries from GitHub releases, and while it performs SHA256 checksum verification, the trust chain relies on GitHub's integrity. Running this server on an internet-exposed host without proper firewalling and TLS is highly risky.