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: <20040311160212.GA2474@phobos.fs.tum.de>
From: Simon.Richter at hogyros.de (Simon Richter)
Subject: Caching a sniffer

Hi,

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

In the Good Old Days(tm), at LAN parties, we used to send out garbled
packets (that would make Windows' IP stack crash) to a nonexistant
hardware address, then looked who got a bluescreen. Of course, this
makes sense only in unswitched networks, which are rather seldom
nowadays.

   Simon

-- 
GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD  ADC6 18A0 CC8D 5706 A4B4