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: <00b701c40790$56f4def0$020aa8c0@bitchin>
From: mfratto at nwc.com (Mike Fratto)
Subject: Caching a sniffer

> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com 
> [mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of 
> Kenton Smith
> Sent: Thursday, March 11, 2004 11:50 AM
> To: pbruna@...ev.cl
> Cc: Full Disclosure; SECURITY-BASICS@...urityfocus.com
> Subject: Re: [Full-Disclosure] 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.

Your assuming that the attacker 1) has control of the switch and 2) is
sniffing either the uplink or has configured the switch to mirror all the
switch ports or VLAN to the mirror port. 

Neither of which may be the case.