full-disclosure - Caching a sniffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20040311035958.GA1000@sentinelchicken.org>
From: tim-security at sentinelchicken.org (Tim)
Subject: Caching a sniffer

> How can i know if there a sniffer running in my network?

There was a long thread on this subject in February on focus-ids:
  http://seclists.org/lists/focus-ids/2004/Feb/0028.html

One link to an interesting paper posted there:
  http://www.securityfriday.com/promiscuous_detection_01.pdf

There may be other ways, but the approach described in the paper would
probably work in most cases provided the interface in question was
configured with an IP.  Then again, I may not know what the hell I am
talking about...

tim