Repository navigation
Releases
Mavi VPN 1.3 - Android pause and more reliable connections
Mavi VPN 1.3 - Android pause and more reliable connections
Mavi VPN 1.3.0 adds timed VPN pauses on Android and improves reconnection,
credential persistence, network cleanup, and desktop session status. It includes
the dependency and security-check updates merged since release 1.1.0.
Downloads
| Archive | Contents |
|---|---|
windows-builds.zip |
Windows x64 MSI and NSIS installers, CLI, service, and WinTUN DLL |
android-apk.zip |
Debug APK with ARMv7, ARM64, x86, and x86_64 native cores |
SHA256SUMS.txt contains the SHA-256 checksums of both archives.
What's changed since 1.1.0
- Timed Android pause: Pause an active VPN for 5, 15, 30, or 60 minutes,
see the remaining time, and resume manually or automatically. Pause recovery
also handles service restarts and Android idle mode. Android can delay the
wakeup alarm; pause is unavailable when "Block connections without VPN" is on. - Connection cancellation and recovery: Android connection attempts and
reconnects can be cancelled. Temporary server rejections no longer prevent
automatic reconnection. Desktop indicators follow the active VPN session,
including when a different saved profile is selected. - Credential persistence: Linux CLI secrets move to the OS keyring, and
Linux and Windows CLI clients retain rotated Keycloak refresh credentials.
Desktop credential updates and Android login state are coordinated with the
current user, profile, and session to avoid stale writes. - Network and service cleanup: Routing and DNS cleanup preserve unrelated
host configuration. Windows GUI removal preserves networking used by a
running VPN service. Linux startup recovery, IPv6 cleanup, and installer
behavior receive additional fixes. - Authentication and transport hardening: Windows IPC verifies its server
and caller identities. Server configuration rejects placeholder auth tokens;
HTTP/2 framing, resource limits, split-tunnel validation, and OAuth policy
checks are tightened. An empty optional HTTP/2 listener no longer prevents
the default Docker configuration from starting. - Dependency and CI updates: Compatible Tauri Rust and JavaScript versions
are aligned, certificate and XML dependencies are updated, obsolete security
exceptions are removed, and the remaining exceptions have documented review
dates. Rust, Android, frontend, and GitHub Actions dependency PRs are included. - Current transport forks: All seven h2, h3, and Quinn packages continue to
use the latest checkedzerox80branch commits recorded inCargo.lock.
Upgrade notes
- Versions are synchronized to
1.3.0across the Rust workspace, desktop GUI,
and Android app. Android's version code increases from5to6. - The Android download is the same debug APK format used by previous
releases. Android requires the same signing certificate for an in-place
update; a different CI debug key can require reinstalling and configuring
the app again. Production Android builds require a stable signing setup and
a verified HTTPS OAuth App Link. - A VPN pause disconnects the tunnel until it resumes. Android may postpone
automatic resume while the device is idle. - Windows clients still require complete IPv6 tunnel settings from the server.
Configure host IPv6 forwarding and setVPN_DISABLE_IPV6=falsebefore
connecting Windows clients. - Linux CLI uses the OS keyring/Secret Service for persistent credentials.
Without one, Keycloak tokens remain in memory and the next run requires
login; preshared keys can fall back to a permission-restricted config file.
See the Linux client guide
for setup and recovery details.
Full changelog: Changes since 1.1.0.
Build provenance
Both archives were built from commit
9c46f1a
in Build Clients run 39825419669.
Archive integrity, GitHub artifact SHA-256 digests, Windows installer versions,
Android versionCode/versionName, APK signature, and all four native ABIs were verified.
Mavi VPN 1.1 — Packet memory and connection lifecycle improvements
Mavi VPN 1.1 ” Packet memory and connection lifecycle improvements
Mavi VPN 1.1.0 improves packet memory ownership, HTTP/2 connection cleanup, and
Windows service IPC setup. It includes the server connection-setup hardening
introduced in 1.0.2.
Downloads
| Archive | Contents |
|---|---|
windows-builds.zip |
Windows x64 MSI and NSIS installers, CLI, service, and WinTUN DLL |
linux-cli.zip |
Linux x64 CLI binary, DEB, and RPM |
linux-gui.zip |
Linux x64 GUI DEB and RPM |
android-apk.zip |
Debug APK with ARMv7, ARM64, x86, and x86_64 native cores |
SHA256SUMS.txt contains the SHA-256 checksums of all four archives.
Built from 6808837.
What's changed since 1.0.2
- Bounded packet storage on the server: Queued packets now own only their
own bytes. A slow client can no longer retain a shared multi-megabyte buffer
through a small queued packet. Queue capacity is reserved before allocating
the packet copy. - HTTP/2 transport cleanup on Linux: Dropping the final session handle stops
its connection driver and capsule tasks. Failed or cancelled setup also stops
the connection driver, preventing abandoned transport tasks from remaining
active after disconnects or unsuccessful handshakes. - Less allocation in MASQUE framing: CONNECT-IP datagram capsules are encoded
directly into one correctly sized buffer, preserving the existing wire format. - Windows service IPC setup: The service resolves the active console user's
SID through Windows APIs instead of launching PowerShell for each lookup.
Each lookup checks the current console session, including after user switching,
and fails closed if a console user cannot be resolved. - Current transport forks: The release lockfile is refreshed against the
latestzerox80/quinnandzerox80/h3mainbranches and thezerox80/h2
masterbranch. All seven fork packages remain branch-tracked. - Build dependencies: Updated Rust, Android, and frontend dependencies,
including Vitest 5 and Rust 1.98 Docker builder images.
Upgrade notes
- Update the server for the packet-storage improvement, the Linux client for
HTTP/2 task cleanup, and the Windows client/service for native console-user
lookup. The capsule encoding remains compatible with the existing format. - Windows clients still require a complete IPv6 tunnel configuration. Enable
host IPv6 forwarding and setVPN_DISABLE_IPV6=falseon the server before
connecting Windows clients. - Package versions are synchronized to
1.1.0across the Rust workspace,
desktop GUI, and Android app. Android's version code increases to5, above
the4used by release 1.0.2. - The existing Android CI produces a debug APK. A production Android release
build requires a verified HTTPS OAuth App Link and a configured signing setup. - The separate
mavi-vpn-dockerimage followsmain; itslatesttag is not a
versioned 1.1.0 image. Update that deployment withdocker compose pullfollowed
bydocker compose up -dafter a successful image publication.
Full changelog: Changes since 1.0.2.
Mavi VPN 1.0.2 — Server connection hardening
Mavi VPN 1.0.2 hardens server connection setup against stalled QUIC and HTTP/3 peers and improves deployment and client setup documentation.
What's changed
- Bounded QUIC connection setup: A single 10-second deadline now covers the transport handshake, authentication, and tunnel configuration delivery. Setup progress, keepalives, and blocked stream or response flow control cannot restart or extend that deadline.
- Pending connection limit: The server accepts at most 100 simultaneous QUIC connections awaiting setup, alongside the existing 1,000-connection limit. Pending slots are released when setup completes or the connection exits.
- Reliable setup cleanup: Timed-out raw QUIC and HTTP/3 connections are closed, releasing connection slots and any allocated tunnel addresses. The deadline also covers stalled HTTP/3 camouflage responses.
- Established tunnel continuity: Successfully initialized tunnels are no longer subject to the setup deadline. Regression tests cover raw QUIC and HTTP/3 tunnel survival, stalled responses, address cleanup, and the transition from setup to an active tunnel.
- Clearer setup documentation: Expanded instructions for prebuilt Docker deployment, release downloads, Windows/Linux/Android clients, authentication, transport selection, and troubleshooting, including Windows IPv6 requirements.
Upgrade notes
Update the server to receive the connection-setup hardening. These changes apply to raw QUIC and HTTP/3; HTTP/2 behavior is unchanged. Clients must complete QUIC setup within 10 seconds, and new connection attempts may be rejected while all 100 pending slots are occupied.
Windows clients still require complete IPv6 tunnel settings from the server. Configure IPv6 networking and forwarding and set VPN_DISABLE_IPV6=false before connecting Windows clients.
Release versions are synchronized to 1.0.2 across the Rust workspace, desktop GUI, and Android app. Android's version code increases to 4.
Full changelog: Changes since 1.0.1.
Mavi VPN 1.0.1 — CLI reliability and connection fixes
Mavi VPN 1.0.1 improves CLI error reporting, Android connection defaults, and connection lifecycle cleanup across platforms.
What's changed
- CLI error reporting: Linux and Windows
start,stop, andrepairnow return a nonzero exit code when the daemon/service rejects a request, IPC communication fails, or the response does not match the command. Errors retain their diagnostic details and are written to stderr. - Windows scripting: Explicit CLI commands exit without the final "Press Enter" prompt. Unknown commands also return a nonzero exit code. The interactive launch keeps its exit prompt.
- Android default port: New configurations and service start requests without a port now use 10443, matching the Docker Compose default. Previously saved ports are preserved; update an existing profile manually if it still has the old default.
- Android session lifecycle: Stop/restart handling prevents stale workers from changing the replacement session's state or retaining native session handles.
- Windows connections: QUIC attempts to an unresponsive address time out individually, leaving time to try another resolved address within the session deadline. Service lifecycle checks also account for active tasks during shutdown.
- Windows DNS cleanup: Service and uninstaller cleanup remove DNS policies identified as belonging to Mavi VPN, preserving unrelated policies that happen to use the same DNS servers.
- Linux package upgrades: Package removal hooks preserve the daemon during upgrades and stop/disable it only during removal.
- Server IPv6 configuration:
VPN_DISABLE_IPV6=trueexplicitly disables IPv6 tunnel setup and assignments. Windows rejects incomplete IPv6 tunnel configuration instead of silently falling back. - Transport dependencies: Updated branch-tracked
h2,quinn, andh3fork revisions since 1.0.0.
Upgrade notes
Windows requires complete IPv6 tunnel settings from the server. Keep VPN_DISABLE_IPV6=false and configure IPv6 networking and forwarding before connecting Windows clients.
CLI exit codes report failures observed by the command. Linux start acknowledges an asynchronous start request; Linux and Windows stop acknowledge a shutdown request. Check status for the subsequent tunnel state. Windows start retains its existing wait for tunnel readiness. Network repair remains best-effort cleanup inside the daemon/service; a successful IPC reply does not verify every route or DNS operation.
Android's version code increases to 3. Existing saved endpoints are not rewritten.
Full changelog: Changes since 1.0.0.
Mavi VPN 1.0 — More ways to connect
Mavi VPN 1.0 brings a choice of QUIC, HTTP/3 MASQUE, and HTTP/2 CONNECT-IP transports to a self-hosted VPN with Windows, Linux, and Android clients. This milestone focuses on connections that recover more reliably, authentication that stays current, and installers that set up the background services correctly.
Highlights
HTTP/2 when UDP is unavailable
The new end-to-end HTTP/2 CONNECT-IP transport carries VPN traffic over TLS/TCP, providing an alternative on networks that block UDP. QUIC remains the default, with optional HTTP/3 camouflage and MASQUE framing. Select HTTP/2 on the client and enable the server's TCP listener; this is an explicit transport choice, not automatic fallback.
More reliable connections and sign-in
- Android: Connection setup has an overall deadline and can be cancelled before a native session exists. An unresponsive address no longer blocks all subsequent connection attempts, and an old worker cannot cancel its replacement. Settings now include a dedicated split-tunneling screen.
- Linux: Keycloak token renewal continues through reconnect backoff. After an outage, the client renews an expired token before authenticating again, while coordinating refresh-token rotation between foreground and background tasks.
- Windows: The CLI passes Keycloak refresh credentials to the service so it can renew the session. Stopping an HTTP/2 tunnel also works when the upload queue is full, and reconnect cleanup removes stale VPN DNS rules.
Services and installers that work together
- Windows IPC permissions are refreshed on the already-listening named pipe after a user signs in or switches sessions, including when the service started before login.
- The Windows NSIS installer now includes the CLI and service, registers and starts the service, and handles service shutdown during upgrades and removal.
- Linux DEB/RPM packages configure the
mavivpnIPC group and restart the daemon with the appropriate permissions. The GUI source installer builds the bundled CLI first. - Linux DNS fallback updates preserve the resolver's symlink, inode, and permissions, work with the service sandbox, and retain a durable backup for recovery.
- The Keycloak Compose overlay resolves the realm import from the correct directory.
Authentication and network hardening
Server-side session-expiry enforcement and HTTP/2 authentication deadlines have been strengthened. This release also addresses JWKS refresh races, IPv6 leak races, and Windows privileged file and WinTUN loading paths. Dependency and CI updates accompany these changes.
Installation and upgrade
See the installation guide for platform setup and the README for server configuration.
- Windows: Use the MSI or NSIS installer once the 1.0.0 assets are attached. Installation requires administrator privileges to configure the VPN service.
- Linux: Choose either the GUI package or the CLI-only package. After installation, log out and back in to activate
mavivpngroup membership. If the package manager could not identify your desktop user, runsudo usermod -aG mavivpn USERfirst, substituting your trusted local username. - Android: Android 8.0 or newer is required. The current CI workflow produces a debug APK, not a production-signed release APK. Android only accepts an in-place update signed with the same certificate; a different signing key can require reinstalling the app and re-entering its configuration.
- Server: Back up configuration and persistent certificate/key data before upgrading. Use matching 1.0.0 server and client builds when enabling HTTP/2, and keep the configured TUN MTU aligned across peers.
For source builds, Rust 1.95 or newer is required. The h2, h3, and quinn forks continue to track their branch tips, with the resolved commits recorded in Cargo.lock.
Release status
This is a draft. Versioned distribution assets and their checksums must be attached and verified before publication. Android production distribution additionally requires a signing configuration and a verified HTTPS App Link for Keycloak redirects.
Mavi VPN has not been independently security-audited. The 1.0 version number does not change that status. Desktop ECH support is GREASE/camouflage; it does not provide end-to-end encrypted ClientHello confidentiality, and Android uses a cover SNI without an ECH extension.
Changes since 0.99.5: commit comparison.
0.99.5 Release
Highlights
More reliable connections
- Keycloak sessions are refreshed in the background on Windows and Linux. In most cases, reconnecting after an access token expires no longer requires signing in again.
- Connection setup and reconnect attempts can be cancelled cleanly, and status updates are more reliable.
- Improved IPv6 detection and setup, especially on hosts using Router Advertisements (for example, AWS Lightsail), with clear errors for non-recoverable configuration issues.
- Stricter MTU alignment between client and server, plus corrected ICMP Packet Too Big responses, prevent avoidable connection and throughput problems.
Security and privacy
- Extensive hardening of OAuth redirects, local IPC channels, and stored credentials across Windows, Linux, and Android.
- Desktop credentials are stored in the operating system's secure storage. Android now separates pre-shared keys from Keycloak tokens and validates its configuration more strictly.
- The server applies stronger authentication rate limiting, enforces pre-authentication timeouts, and supports overlapping certificate-pin rotation.
- Improved permissions for TLS keys, IPC tokens, installers, and systemd services, alongside more robust JWKS and Keycloak handling.
Networking and platforms
- Windows now uses the DNS server supplied by the server for NRPT rules; network cleanup, routes, and diagnostic capabilities have also improved.
- Linux writes
resolv.confatomically, cleans up network and IPC state more reliably, and is more resilient to invalid route configuration. - The server reliably returns IP leases after early disconnects, preventing address-pool exhaustion.
- Android session lifecycle and Keycloak configuration improvements address race conditions and repeated-connection issues.
Maintenance
- Expanded tests, supply-chain checks, and stricter CI quality gates.
- Rust 1.95 is now the documented minimum supported version.
Full Changelog: 0.99...0.99.5
0.99
What's Changed
Android
- fix(android): separate preshared key from Keycloak token storage by @zerox80 in #195
- Validate VPN MTU (1280–1360) in preferences and at the JNI boundary, failing fast before any socket/runtime setup, so corrupt persisted or out-of-range values are rejected without silent truncation (in #196).
Linux client
- Clear the stale assigned IP from daemon state during
RepairNetwork, so the GUI no longer shows a leftover address after a repair (in #196).
Build & tooling
- Remove the ignored per-crate
[profile.release]blocks fromlinux,windows,gui/src-tauri, and the Android Rust crate — only the workspace-root release profile applies in a Cargo workspace (in #196). - Rewrite
CLAUDE.mdwith repo-specific build, test, lint, and architecture guidance.
Hardening (#196)
Full Changelog: 0.98.1...0.99
0.98.1
What's Changed
- feat(keycloak): in-band token refresh + forced re-login on connect by @zerox80 in #182
- fix(keycloak): reuse stored refresh tokens and refresh in the background by @zerox80 in #183
- fix(windows): GUI owns Keycloak refresh token, service only holds access token by @zerox80 in #185
- [codex] Move Windows Keycloak refresh into service by @zerox80 in #186
- [codex] Add Windows client diagnostics by @zerox80 in #187
Full Changelog: 0.98...0.98.1
0.98
What's Changed
- chore(backend): remove dead h3_quinn datagram module and dedupe QUIC overhead const by @zerox80 in #164
- fix(shared): reject non-ASCII input in decode_hex instead of panicking by @zerox80 in #163
- fix(windows): classify deterministic IPv6 setup failures as permanent (H5) by @zerox80 in #162
- fix(backend): only evict a peer when the closed channel still owns the IP (H1) by @zerox80 in #160
- fix(windows): use server-pushed DNS in NRPT rule instead of hardcoded by @zerox80 in #146
- fix(linux): atomic resolv.conf write to prevent truncation on crash by @zerox80 in #148
- fix(client): make the reconnect backoff interruptible by Stop (H3) by @zerox80 in #161
- fix(windows): use try_from for allocate_send_packet length by @zerox80 in #151
- fix(mtu): require server MTU to match local TUN MTU and fix PTB value (K2) by @zerox80 in #159
- fix(linux): clean up IPC auth token file on daemon shutdown by @zerox80 in #152
- ci: enforce clippy with -D warnings and fix existing lint debt by @zerox80 in #165
- fix(android): guard native session handle adoption by generation (K1) by @zerox80 in #158
- fix(gui): refresh status immediately after vpn_connect by @zerox80 in #153
- chore: combine main cleanup and hardening PRs by @zerox80 in #169
- refactor(backend): dedupe handler tunnel setup and slim main() by @zerox80 in #171
- [codex] Improve code quality across clients by @zerox80 in #172
- refactor(backend): dedupe TUN reader routing and slim stats snapshot by @zerox80 in #173
- refactor(android): extract TUN builder config from MaviVpnService by @zerox80 in #174
- refactor(windows): extract session packet-pump loops into named functions by @zerox80 in #175
- Harden IPv6 setup with host verification and graceful fallback by @zerox80 in #176
- Improve sysctl persistence setup with auto-detected WAN interface by @zerox80 in #177
- fix(desktop): auto-connect + secure Keycloak token refresh (Windows + Linux) by @zerox80 in #178
- [codex] Refactor Windows service state handling by @zerox80 in #179
- [codex] refactor windows code quality by @zerox80 in #180
- refactor(windows): centralize Win32 table lifecycle and name magic values by @zerox80 in #181
Full Changelog: 0.97...0.98
0.97
What's Changed
- fix: unify auth-failure detection across all clients by @zerox80 in #144
- fix: use DEFAULT_TUN_MTU for QUIC transport budget when MTU is unset by @zerox80 in #145
- fix(backend): reclaim leased IPs on early disconnect to prevent pool exhaustion by @zerox80 in #157
- fix(backend): bound the pre-auth handshake phase with a timeout by @zerox80 in #156
- fix(backend): restrict TLS private key ACLs on Windows by @zerox80 in #155
- fix(windows-service): fully respecify IPC token ACLs to drop stale user ACEs by @zerox80 in #154
Full Changelog: 0.96...0.97