PAGES
← all tools
◆ Secure Access (VPN / SASE / ZTNA)

OpenVPN

v2.7.6 open-source

OpenVPN is an open source VPN daemon

Summary

OpenVPN is an open-source tunneling daemon that encrypts network traffic between a client and a server to create a secure remote-access VPN, free to download and build from source under the GPL. It runs as a background service: a daemon on the server side and a client install (desktop, mobile, or embedded) on the connecting end, configured through text files and a management interface rather than a GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands.-first workflow. It fits network and security administrators who need to grant remote users access to an internal network rather than end users wanting a commercial privacy app. It sits in the broader secure-access and VPN category, alongside other encrypted-tunneling protocols rather than any single named competitor, with features like TLS 1.3, kernel-level data channel offload (DCO), and per-platform DNS handling marking it as protocol-level infrastructure rather than a turnkey product.

OpenVPN is an open source VPN daemon

How OpenVPN helps

Can remote users reach a private network resource as if they were physically on it?

establishes an encrypted point-to-point or site-to-site tunnel over SSL/TLS between the client and the server's network, routing traffic through it as a virtual interface

Will a client's DNS queries leak outside the tunnel while connected?

pushes DNS configuration from the server to a per-platform script (or NRPT table on Windows) so lookups are handled through the tunnel, supporting split-DNS setups rather than only an all-or-nothing route

Can a server change routing or DNS for connected clients without dropping their sessions?

sends a control-channel update message that applies the new configuration in place, avoiding the reconnect a client would otherwise need

Is a large deployment's data channel protected against key-reuse limits over long-lived connections?

uses the newer data key and packet format, tracking usage and enforcing the cipher's safe limits so keys are rotated before that threshold is hit

Can a single process serve clients arriving over different addresses, ports, or protocols at once?

lets one server listen on multiple sockets concurrently, configured with repeated local-address statements, instead of running a separate process per listener

Who or what is connecting to this server, and from what kind of system?

records each client's OS release string and sends it to the server, giving an administrator a way to see what platform a given connection came from

all 12 features, with the evidence for each →

Languages

Not documented

Features

12 capabilities · 2 backed by code, an API document or a real run

Built from OpenVPN's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What OpenVPN offers you

  • Command-line interface1
  • Self-hosted deployment1
All capabilities 12 capabilities
TLS and cryptographic backend management shipped Manages TLS handshake details, certificate handling, OpenSSL errors, key material export, and switches between OpenSSL and mbedTLS backends including support for TLS 1.3. 9 releases · first seen Nov 2023

release 9 total

  • Adds TLS 1.3 support with bleeding-edge mbedTLS versions, including support for mbedTLS version 4. v2.7.0 · Feb 2026 · source · release history
  • Adds windows_ca_template support in the Windows Crypto-API to match certificates against active directory certificate templates. v2.6.11 · Jun 2024 · source · release history
  • Add new option --force-tls-key-material-export to enforce TLS keying material export for clients v2.6.9 · Feb 2024 · source · release history
  • Log incoming SSL alerts in a more readable format, lowering the verbosity threshold from --verb 8 to --verb 3 v2.6.9 · Feb 2024 · source · release history
  • Add support for building with mbedTLS 3.x.x v2.6.9 · Feb 2024 · source · release history
  • The --disable-dco flag must now be used when a 2.6.x client connects to a 2.4.0-2.4.4 server due to hard incompatibility with DATA_V1 packets v2.6.7 · Nov 2023 · source · release history
OpenVPN configuration verified Manages OpenVPN connection settings including URL, device type defaults, keepalive intervals, and socket flags. 6 releases · 2 other sources · first seen Nov 2023

release

  • --dev defaults to tun, allowing the option to be omitted from configuration for standard setups. v2.7.6 · Aug 2026 · source · release history
  • Omitting --dev from an OpenVPN config now defaults to --dev tun, removing a previously required boilerplate option for the common tun case. v2.7.6 · Aug 2026 · source · release history
  • TCP_NODELAY socket flag is now always enabled on the local socket; --tcp-nodelay in server mode now specifically pushes socket-flags TCP_NODELAY to clients that may not have this default. v2.7.6 · Aug 2026 · source · release history
  • The --ping and --keepalive options now reject values exceeding 86400 seconds (24 hours); configs with larger values will need to be updated. v2.7.6 · Aug 2026 · source · release history
  • TCP_NODELAY is now enabled by default on all sockets; previously it was opt-in via --tcp-nodelay. v2.7.6 · Aug 2026 · source · release history
  • Passes --timeout=0 to systemd-ask-password on Linux, removing the previous 90-second default timeout for console credential prompts. v2.6.13 · Jan 2025 · source · release history

command line

example

  • Work around the DATA_V1 incompatibility when connecting to an older server. openvpn --config legacy-client.ovpn --disable-dco v2.6.7 · Nov 2023 · source
Windows network configuration and driver support shipped Configures Windows networking components including WINS servers, manages DCO/wintun/win-dco driver interactions, handles on-demand adapter generation, and controls service privilege levels. 6 releases · 1 other source · first seen Aug 2023

release

  • Support for the wintun driver has been removed; win-dco is now the default Windows driver, with tap-windows6 as the fallback. v2.7.0 · Feb 2026 · source · release history
  • Windows network adapters are now generated on demand, reducing resource usage at startup. v2.7.0 · Feb 2026 · source · release history
  • Windows automatic service now runs as an unprivileged user, reducing attack surface. v2.7.0 · Feb 2026 · source · release history
  • New management interface commands push-update-broad and push-update-cid for server-side delivery of PUSH_UPDATE option updates. v2.7.0 · Feb 2026 · source · release history
  • Enforces block-local flag using WFP filters on Windows for stronger local traffic blocking. v2.7.0 · Feb 2026 · source · release history
  • set WINS server is now supported in the interactive service configuration to provide WINS resolution for DCO + wintun interfaces when no DHCP server is present. v2.6.6 · Aug 2023 · source · release history

example

  • Configure a static WINS server on Windows using DCO and wintun where DHCP is unavailable. set WINS server 192.0.2.1 v2.6.6 · Aug 2023 · source
Access Server deployment and Zero Trust Broker shipped Enables automated, guided deployment of Access Server instances on cloud providers with automatic DNS and SSL management, and introduces a Zero Trust Application Broker for per-application access mediation. 5 releases · 1 other source · first seen Sep 2026

Also counts toward: Self-hosted deployment

release

  • Access Server deployment through Access Server Link is now available from Access Server Hub. announced · Sep 2026 · source · release history
  • Introduces Access Server Link, a new guided browser-based setup for self-hosted ZTNA that requires only three inputs — hostname, cloud provider/region, and admin password — to deploy Access Server on AWS, Azure, or GCP without SSH, manual DNS configuration, or certificate management.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
  • Introduces a Zero Trust Application Broker that mediates per-application access using placeholder IP addresses scoped to a single authorized application configured by domain name, making lateral movement structurally impossible. announced · Sep 2026 · source · release history
  • Adds automatic IP-change detection and domain record updates through Access Server Link, keeping deployments reachable without manual DNS intervention after cloud IP changes. announced · Sep 2026 · source · release history
  • Adds automatic SSL certificate provisioning and renewal via Access Server Link, replacing self-signed certificates and eliminating certificate-expiry outages. announced · Sep 2026 · source · release history

example

  • Deploy a self-hosted Access Server instance on AWS, Azure, or GCP without SSH or manual DNS work — get ZTNA running in minutes from Access Server Hub. In Access Server Hub, select 'Deploy with Access Server Link', choose your cloud provider (AWS, Azure, or GCP) and region, enter a hostname and admin password, then launch — DNS and SSL certificates… announced · Sep 2026 · source
Client-side network and DNS enhancements shipped Adds support for new DCO Linux kernel modules, on-demand FreeBSD DCO interfaces, environment variables for gateway redirection, and client-side split DNS with DNSSEC. 4 releases · first seen Jun 2024

release

  • Introduces two new environment variables to communicate desired default gateway redirection to plugins such as Network Manager. v2.7.0 · Feb 2026 · source · release history
  • Supports the new ovpn DCO Linux kernel module (with backports available via ovpn-backports) for next-generation kernel-level data channel offload. v2.7.0 · Feb 2026 · source · release history
  • New client-side DNS implementations for Linux/BSD/macOS and Windows, adding split DNS and DNSSEC support on Windows. v2.7.0 · Feb 2026 · source · release history
  • Enables creation of pre-configured Data Channel Offload (DCO) interfaces on FreeBSD without requiring OpenVPN to set the interface mode. v2.6.11 · Jun 2024 · source · release history
Authentication and credential handling shipped Enhances authentication with username-only flags, long password support via management interface, in-memory protection of credentials on Windows, and OS release string transmission. 3 releases · first seen Jan 2025

Also counts toward: Command-line interface

release

  • Supports input of very long passwords in base64-encoded multiline format via the management interface, signalled to clients as management version 6. v2.7.2 · Apr 2026 · source · release history
  • Adds username-only flag to --auth-user-pass, letting clients send only a username (with a dummy password) to trigger server-side external challenge schemes. v2.7.1 · Mar 2026 · source · release history
  • Protects cached usernames, passwords, and tokens in Windows client memory using the CryptProtectMemory() Windows API. v2.6.13 · Jan 2025 · source · release history
Data channel security and protocol updates shipped Implements Epoch data keys, AES-GCM usage limits, PUSH_UPDATE control-channel messages for dynamic config without reconnects, and granular recursive routing checks. 3 releases · first seen Feb 2026

release

  • Introduces Epoch data keys and packet format for improved data channel security, including enforcement of AES-GCM usage limits. v2.7.0 · Feb 2026 · source · release history
  • Supports the new PUSH_UPDATE control-channel message, enabling servers to push routing and DNS config changes to clients without forcing a reconnect. v2.7.0 · Feb 2026 · source · release history
  • Makes the Recursive Routing check more granular, dropping in-tunnel packets only when destination IP, protocol, and port all match the VPN server's reach parameters. v2.7.0 · Feb 2026 · source · release history
Management interface and dynamic updates shipped Provides commands to push routing or DNS updates to clients without reconnects, either broadly or by connection ID. 1 release · 2 other sources · first seen Feb 2026

release

  • New management interface commands push-update-broad and push-update-cid for server-side delivery of PUSH_UPDATE option updates. v2.7.0 · Feb 2026 · source · release history

example

  • Push a routing or DNS config update to all connected clients without triggering reconnects, using the new management interface command. echo 'push-update-broad route 10.8.1.0 255.255.255.0' | nc 127.0.0.1 7505 v2.7.0 · Feb 2026 · source
  • Push an option update to a specific connected client by connection ID without forcing a reconnect. echo 'push-update-cid 42 dhcp-option DNS 1.1.1.1' | nc 127.0.0.1 7505 v2.7.0 · Feb 2026 · source
Server scaling and multi-socket handling shipped Enables handling multiple addresses, ports, and protocols simultaneously via multi-socket support and optimizes performance with increased hash map sizing. 2 releases · first seen Feb 2026

release

  • Increases default internal hash map sizing to 4 * --max-clients, improving performance on servers with large client counts. v2.7.1 · Mar 2026 · source · release history
  • Adds multi-socket server support, allowing a single server process to handle multiple addresses, ports, and protocols simultaneously. v2.7.0 · Feb 2026 · source · release history
Windows Crypto-API integration shipped Leverages Windows Crypto-API for certificate template matching and provides new non-exclusive control device APIs for driver version retrieval. 2 releases · first seen Jun 2024

release

  • Uses a new non-exclusive control device API to retrieve the dco-win driver version on Windows. v2.6.13 · Jan 2025 · source · release history
  • Adds windows_ca_template support in the Windows Crypto-API to match certificates against active directory certificate templates. v2.6.11 · Jun 2024 · source · release history
Change tracking verified Associates a change identifier with operations for traceability. 1 other source · first seen May 2025

command line

Testing infrastructure improvements shipped Enhances testing capabilities by supporting pre-tests and conditional block skipping in test suites. 1 release · first seen Mar 2024

release

  • t_client.sh now supports running pre-tests and skipping test blocks based on environment conditions v2.6.10 · Mar 2024 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for OpenVPN, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail OpenVPN puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

11 entries

  1. September 20261
  2. August 20261
  3. April 20261
  4. March 20261
  5. February 20261
  6. January 20251
  7. June 20241
  8. March 20241
  9. February 20241
  10. November 20231
  11. August 20231
    Show

    11 entries

    Project health

    Issue, contributor and maintainer activity in OpenVPN/openvpn, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 33 +3 vs prior 12 months
    2. Maintainers 5 +0 joined · −1 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 96% of issues opened, last 12 months
    5. Median time to close 3.8 days first maintainer reply 13 hours
    6. Open backlog 181 of 687 issues ever filed
    1. Issues opened / month 3 · 0 communitymaintainers
    2. Open backlog 181
    3. Contributors / month 7
    4. Commits / month 27
    5. Stars 14,550
    Issue themes, last 12 months
    • bugs 21%
    • features 17%
    • questions 4%
    • docs 1%
    • other 57%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →