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
| ||
|
Message-ID: <84493B06BD47C141A94192546BCC41AC037C37F0@njrarsvr058b.GMS.COM> From: RMcElroy at mbe.com (RMcElroy@....com) Subject: Caching a sniffer http://www.securiteam.com/tools/5HP011F40E.html -----Original Message----- From: Simon Richter [mailto:Simon.Richter@...yros.de] Sent: Thursday, March 11, 2004 8:02 AM To: Patricio Bruna V. Cc: Full Disclosure Subject: Re: [Full-Disclosure] 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 _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Powered by blists - more mailing lists