|maride ad42bc22ed||1 week ago|
|analyze||11 months ago|
|common||1 year ago|
|output||2 weeks ago|
|protocol||11 months ago|
|.drone.yml||1 year ago|
|.gitignore||1 year ago|
|CONTRIBUTORS.md||1 year ago|
|LICENSE||1 year ago|
|README.md||1 year ago|
|analyzer_test.go||1 year ago|
|file.go||1 year ago|
|go.mod||1 year ago|
|go.sum||1 year ago|
|main.go||1 week ago|
If you get access to a PCAP file, for example during a CTF or captured on your own, you usually have the problem of overlooking all the relevant information to get a basic idea of the capture file. This gets worse if the capture file includes lots of white noise or irrelevant traffic - often included in the capture file to cloak interesting packets in a bunch of packets to YouTube, Reddit, Twitter and others.
pancap addresses this problem. With multiple submodules, it analyzes the given PCAP file and extracts useful information out of it. In many cases, this saves you a lot of time and can point you into the right direction.
go get git.darknebu.la/maride/pancap
This will also build
pancap and place it into your
GOBIN directory - means you can directly execute it!
In any use case, you need to specify the file you want to analyze, simply handed over to pancap with the
pancap -file ~/Schreibtisch/mitschnitt.pcapng
This will give you a result similar to this:
nGB big pcap takes
... yes please! There are still a lot of modules missing.
If you are brave enough, you can even implement another Link Type. Pancap currently only supports
Ethernet (which, to be honest, fits most cases well), but
USB might be interesting, too. Especially sniffed keyboard and mouse packets are hard to analyze by hand...