Skip to content

Mavi VPN 1.3 - Android pause and more reliable connections

Latest

Choose a tag to compare

@zerox80 zerox80 released this 22 Oct 18:04

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 checked zerox80 branch commits recorded in Cargo.lock.

Upgrade notes

  • Versions are synchronized to 1.3.0 across the Rust workspace, desktop GUI,
    and Android app. Android's version code increases from 5 to 6.
  • 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 set VPN_DISABLE_IPV6=false before
    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.