Repository navigation
SupiVPN v0.4.4
SupiVPN v0.4.4
Changes since v0.4.3.
Changes
- Add optional
peer_ipandpeer_portto authorized tunnel establishment and disconnection audit events. Preserve the VPN address inaddressand the verified SAML identity inusername. - Retain the last valid daemon-observed endpoint per connection, including during status-based disconnect cleanup, without allowing a reused CID to inherit another connection's metadata.
- Validate IPv4/IPv6 addresses and ports, reject ambiguous or malformed metadata, and document NAT/proxy/NLB source-address preservation behavior.
Compatibility
The new fields are an additive extension to JSON log schema version 1. Collectors must tolerate missing fields on older nodes or when the daemon supplies no valid endpoint. Existing SQL/API schemas, authorization, connection limits and production timeouts are unchanged.
The peer is the address visible to OpenVPN, which can belong to a NAT, proxy or load balancer. It is the last valid observation, not a continuous history or proof of a device's identity. Apply the existing log access restrictions and retention to these fields. No AWS NLB deployment change is included.
Packages
Commit: 268c4f47683f8377db87738b91a2c50b999ebdd7. License: AGPL-3.0-only.
Verified native ARM64 and AMD64 builds from Checks for this signed tag. Both bundles use format 3.
GitHub build provenance was verified for both binary archives and Corresponding Source, including the tag commit and Checks run attempt 1.
Database schema: 9; compatible VM schemas: 7, 8, 9.
Isolated Lambda required schema: 9.
Corresponding Source accompanies the binaries. Verify SHA256SUMS.asc with the pinned SupiVPN release key, then verify the downloaded files against SHA256SUMS before use.