OVPN

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

OpenVPN Config Preview.

At a glance


Purpose	An OpenVPN configuration (.ovpn): directives for the tunnel, remotes, crypto and routing, often with inline certificates and keys.
Extensions	`.ovpn`
Poka parser	`poka-openvpn`
Viewer	`poka-metadata-card-viewer`
Depth tier	Metadata card (see Depth tiers)
Breadth tier	B3 Core (see Breadth tiers)

How much Poka reads

B3 Core. Only the main content type or types are decoded (for example geometry but not materials, layers or annotations, or only one version family). The list of gaps is substantial.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-openvpn/src/main.rs (267 lines) and plugin.json. No unit tests or tests/samples.rs; the corpus has no .ovpn sample. Covers .ovpn. The card shows the role (client or server), device, protocol and remotes, the crypto settings (cipher, auth, NCP and data ciphers, minimum TLS, compression), routes and pushed DNS servers, and each inline block by name and size, redacted. Judgement: B3: the main connection and crypto settings are decoded, but other directives are ignored.

What Poka does not read

Directives outside the recognised set are ignored (port, verify-x509-name, redirect-gateway, auth-user-pass and many more)
Inline certificates and keys are redacted and not decoded (by design)
Only the first six remotes and routes are listed

Libraries

Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.

ovpnfile (candidate; MIT OR Apache-2.0; Rust; https://github.com/alexjg/rs-ovpnfile) — Parses OpenVPN 2.4 directives; stale (last release 2017, Rust 2015 edition, deprecated deps). Licence per lib.rs.

Sources

parsers/poka-openvpn/src/main.rs
parsers/poka-openvpn/plugin.json