Skip to content

v0.5.7 — getting the driver you need

Latest

Choose a tag to compare

@CaYatur CaYatur released this 17 Aug 21:02

Getting the packet driver, from inside the tool

An analysis machine is deliberately clean — so the most useful capture in CaYaTrace is
unavailable on exactly the machines that most need it, and "loopback capture was skipped"
written into a session log afterwards is not help.

Ticking Capture local conversations on a machine that cannot do it now says so
immediately, and offers the shortest honest route.

  • What is actually missing, distinguishing the two cases because they have different
    fixes. No driver at all means installing it. A driver with no loopback adapter means the
    installer's Support loopback traffic option was cleared during setup — it is on by
    default, so running the installer again and leaving it ticked is the entire fix.
  • A link to its authors, with the address as selectable text beside it, because a virtual
    machine with no browser is a normal state rather than an edge case.
  • A button to start an installer already on the machine. Getting a file into an isolated
    VM is the awkward part; hunting for it again in Explorer afterwards is busywork. It looks
    beside the executable, on the desktop, and in the profile and Downloads folders, newest
    version first.
  • Check again, which works without restarting — installing a driver while the tool is
    open is precisely what somebody does after being told it is absent, so a missing driver is
    no longer remembered for the life of the process.

What it deliberately does not do

CaYaTrace does not ship Npcap and never installs it unattended. Npcap's free licence covers
neither: redistributing it inside another product and installing it silently are both
reserved for their paid OEM licence, so a tool that quietly did either would put its user in
breach of terms they never read. The installer's own screens are also where those terms are
accepted and where the loopback option is chosen — a reason to send somebody through them
rather than around them.

Nothing is started on the strength of a file name

"Run the installer in your Downloads folder" is otherwise a way to be talked into running
whatever put a file called npcap-9.99.exe there — which, on a machine used to analyse
malware, is not a hypothetical arrangement.

  • A found installer is offered only after its Authenticode signature says who published it.
  • The publisher is shown next to the button, because that is the reason the button is safe to
    press.
  • The signature is verified again at the moment of launching, not trusted from when the file
    was found.
  • Starting it takes an explicit confirmation naming the signer, which also states that
    CaYaTrace passes no arguments of its own.

Tested against a file with the right name and no signature, and against a signed binary from
somebody else. Both refused.

Download

CaYaTrace.exe — self-contained, no .NET install needed. Windows 10/11 x64.

SHA-256: AA538060C5B7DDFF99FAD041EE33AF448B5612A9E865540931286F2A3412933B