Argusic could not verify that ecapture runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 6 errors on the way, and recorded the session.

How did Argusic test ecapture?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 08b25bab76fc. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test ecapture?

The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does ecapture take to install?

26 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 ecapture need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing ecapture?

6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for ecapture?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

ecapture

Capture SSL/TLS plaintext with eBPF, no MITM proxy or custom CA installation. Supports Linux and Android on x86_64 and arm64.

Could not verifysource: GitHubCApache-2.0commit 08b25bab76fc

C, Apache-2.0 licensed. The project labels itself: android, boringssl, ebpf, gnutls, golang, linux, mysql and network analysis.

Argusic could not get ecapture running. An Argusic agent installed it in 26 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

eCapture binary (bin/ecapture) built as a 41 MB statically-linked ELF on Linux x86_64, runs and prints help/version output, 21 test packages pass, but real probe capture requires root and was not verified.
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 65 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 65 / 100
cost of the verifying run: $0.20 (measured)
recorded runs: 2
last tested: 2026-10-10
stars: 15,491
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. 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 ecapture, 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.

Missing Go toolchain (go 1.26+ required)3 minutes
Missing libpcap build deps: flex, bison, m4, libsigsegv3 minutes
Missing LLVM/Clang 9+ and llc (eBPF compilation)2 minutes
Missing bpftool (eBPF BTF dump)1 minute
bison m4 subprocess failed at runtime without BISON_PKGDATADIR and M4 env vars1 minute
file command not found (make post-build check fails with exit 127)

Install time: 26 minutes
Cold machine to finish: 26 minutes
Errors hit and fixed: 6 hit, 6 fixed with no human help
How the result was proved: make all produced 41MB static ELF at bin/ecapture; ecapture --help prints full command/module list; ecapture version prints 'os_arch:v2.0.0-20260101-develop:default_kernel'; 74 eBPF objects (37 CO-RE + 37 non-CO-RE) generated
Model tokens used: 307,632
Exact commit tested: 08b25bab76fc
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

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

echo "Build time approx 19 minutes"
echo ""
echo "Testing done at:" && date +%H:%M:%S' in /work/repo
 succeeded in 0ms:
Start time analysis...
Build time approx 19 minutes
Testing done at:
09:08:25
All done. Here's the final result.
tokens used
307,632
All done. Here's the final result.

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

Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

An agent with no time limit did not get it running.
Took 26 minutes to install, slower than the median of the 21 comparable projects Argusic has measured.

Of the 22 android projects Argusic has installed and timed, ecapture was the 20th fastest to reach a running state, and 16 of 22 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Unverified	80.00	0.20	2026-10-10 09:08 UTC
Argusic Runner	1/3	Did not run	50.00	0.10	2026-10-10 07:37 UTC

Topics (from GitHub)

android boringssl ebpf gnutls golang linux mysql network-analysis network-security observability openssl packet-capture pcapng security-auditing ssl tls tls-decryptio uprobe wireshark

Embed the badge

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

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

Questions

Does ecapture run?: Argusic could not verify that ecapture runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test ecapture?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 08b25bab76fc. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ecapture?: The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ecapture take to install?: 26 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 ecapture need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ecapture?: 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ecapture compare with the alternatives?: Of the 22 android projects Argusic has installed and timed, ecapture was the 20th fastest to reach a running state, and 16 of 22 reached one at all.
Where is the evidence for ecapture?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.