add: captured OpenVPN fixtures and a loopback capture lab #90
Loading…
Reference in a new issue
No description provided.
Delete branch "change/service-client"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The OpenVPN parsing units' only test lines were typed from memory — the exact failure mode that let the 2.7 DCO device-line break go unnoticed until a live session ran (#26). No real captures existed for the management stream at all, since it travels over the socket and is never logged.
Fix
tests/fixtures/: real OpenVPN 2.7.6 output. DCO session and auth failure came from the service's own field log (server IPs swapped for TEST-NET); userspace session, ping-restart reconnect and auth-failure management-stream transcripts came from a new loopback capture lab.tests/manual/ovpnlab/: the lab — a real 2.7.6 server+client pair over loopback insideunshare -rn, so no root, no VPN account, no network. Re-run after an OpenVPN upgrade and diff against the committed fixtures. Deterministic capture viamanagement-holdwith reactive release (the hold re-engages on every restart; an auth-failure session lives ~300ms).tun/tap device [tun0] opened, which the case-sensitive regex missed — nowre.IGNORECASE.mgmt.parse_event(event sequences per scenario, CRLF framing intact) and the session logs throughparse_tun_device.Verification
test_mgmtsocket tests need an unsandboxed run; unix sockets are blocked in the agent sandbox — not a code issue).>PASSWORD:Verification Failed: 'Auth'wording confirmed against the real interface, matching the parser's assumption.Refs #26.