AIVPN 1.2.0 Released With Dual-Stack Networking and InitialV2 Handshake

AIVPN has announced the release of version 1.2.0, introducing dual-stack networking, signed distribution protocols, application hardening, and an updated InitialV2 handshake mechanism. This release extends IPv6 support across the tunnel, adds large management messaging channels, and implements fixes for session, storage, and platform security issues.

Core Protocol and Networking Updates

• IPv6 Across Tunnel: Servers assign IPv6 addresses, prefixes, and MTUs via ServerHello. Both desktop and mobile clients handle these with source validation, client isolation, and Quality of Service (QoS).
• InitialV2 Handshake: Replaces older exchanges using separate Key Derivation Functions (KDF v2) and XChaCha20-Poly1305 with a random 24-byte nonce. This requires confirmed Perfect Forward Secrecy (PFS) for data and management commands.
• Adaptive Data Pacing: Queues respond dynamically to persistent delays instead of stalling at fixed packet rates, featuring selectable adaptive, full, or off shaping modes.

Security and Distribution Improvements

• Signed Distribution: Release artifacts and mask archives are signed using Ed25519. Mask delivery utilizes DNS TXT, PNG, Bitcoin OP_RETURN, Ethereum calldata, and email bootstrap via JMAP.
• Platform Client Enhancements: Includes an Android Material 3 interface with automatic network recovery, Linux Material/Breeze layouts, and Windows Fluent layouts alongside a persistent Windows kill switch.
• Server-Side Security: Site peers no longer receive pool databases or management rights. The update adds live revocation for inter-server nodes and dependency fixes.

Upgrade Considerations

This is a breaking release requiring simultaneous updates across servers, pool/site/chain nodes, and all clients, including embedded mobile cores. Operators must remove explicit `pool.transport=legacy` entries, configure client databases, and distribute trusted release and operator public keys before enabling signature enforcement. Verification steps and detailed settings are documented in the repository's `docs/RELEASE_1.2.0.md` file.