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: <C40D8074-730B-11D8-BB73-000A95703418@improbable.org>
From: chris at improbable.org (Chris Adams)
Subject: Caching a sniffer

On Mar 10, 2004, at 13:13, Patricio Bruna V. wrote:
> How can i know if there a sniffer running in my network?

You might catch someone sloppy with tricks like DNS resolution (send 
data with a hostname / IP and see who resolves it) or bugs in the way 
the sniffing host handles things like ARP resolution (search for 
antisniff if you want a tool which does this) - other than that, 
there's really no way to find a sniffer. Your best bet is to use strong 
encryption so it no longer matters if someone is sniffing traffic.

Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040310/0ce75040/smime.bin