wag

Simple Wireguard 2FA

Runs with mockssource: GitHubGoBSD-3-Clausecommit ff05f657364b

Go, BSD-3-Clause licensed. The project labels itself: 2fa, firewall, linux, management portal, mfa, network, networking and privacy.

wag runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Wag binary builds, all unit tests pass across 3 packages (data, routetypes, watcher), both frontend UIs compile, binary runs and prints help/version

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
1
last tested
stars
740
forks
55
open issues
14
watchers
11
size
12 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing wag, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • embed pattern dist/assets/*: no matching files found3 minutes
  • Go not found in PATH2 minutes
  • security/pam_appl.h: No such file or directory2 minutes
  • link: cannot find -lpam and undefined reference to audit_open2 minutes
Install time
12 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go test -count=1 ./internal/data/... ./internal/routetypes/... returned ok for 23 tests; ./wag version -local printed Version: dev
Model tokens used
464,909
Exact commit tested
ff05f657364b
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Errors encountered & fixed**:
1. **Go toolchain missing** — downloaded Go 1.23.1 tarball; Go toolchain self-managed to 1.25.5
2. **PAM header missing** (`security/pam_appl.h`) — extracted `libpam0g-dev` .deb to `/tmp/pam-dev`…
3. **Static libpam.a needs libaudit** — created symlinks to system shared libraries (`libpam.so`, `…
4. **Frontend embed files missing** — ran `npm install && npm run build` in both frontend directori…
**Verification**:
`go test -count=1 -timeout 120s ./internal/data/... ./internal/routetypes/...`
- 23 tests passed across 3 packages: data (etcd storage, DHCP, URL building, ACLs), watcher, routet…
- 0 failures
`./wag version -local` → `Version: dev`
`./wag --help` → all 8 commands listed with correct usage
**Cannot test without root**: `internal/router/...` needs `/var/run/wireguard` (UAPI socket directo…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 12 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed BSD-3-Clause, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 4 2fa projects Argusic has installed and timed, wag was the 2nd fastest to reach a running state, and 2 of 4 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.07

Topics (from GitHub)

2fafirewalllinuxmanagement-portalmfanetworknetworkingprivacysecurityself-hosteduivirtual-networkvpnvpn-serverwireguardwireguard-adminwireguard-vpn

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/wag.svg)](https://argusic.com/subject/wag)

Questions

Does wag run?
wag runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test wag?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ff05f657364b. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test wag?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does wag take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does wag need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing wag?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does wag compare with the alternatives?
Of the 4 2fa projects Argusic has installed and timed, wag was the 2nd fastest to reach a running state, and 2 of 4 reached one at all.
Where is the evidence for wag?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion