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]

From: ksmith at chartwelltechnology.com (Kenton Smith)
Subject: Caching a sniffer

I skimmed through some of the articles and they all have some good
information. Are you running a switched network? If you are then the
easiest way is to look at your traffic stats and find the port that
*all* traffic is going to.
If this doesn't make sense to you, then you should do some more research
on sniffers.

Kenton

On Wed, 2004-03-10 at 14:13, Patricio Bruna V. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> How can i know if there a sniffer running in my network?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFAT4UNT29IM+6ptNcRAoKlAJ9Kbk2yH4MKrQRNaz6OVM2Jai8/+QCgoUnx
> IXCJDuMJxTU9r/E5AhjW1fc=
> =LiUx
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html