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: <1079032673.17927.9.camel@Pow>
From: dfbarth at akiva.com (David Bartholomew)
Subject: Caching a sniffer

You can't hijack a switched environment with *only* the dsniff tools,
though. Arpspoof is very nifty for 'lying' to the wire and telling it
you are who you say you are. But if you're not *supposed* to be getting
all the network's packets *and* you arpspoof the gateway's IP with your
MAC address, you're going to give yourself away.

So, a simply iptables rule to route all traffic that comes in on your
interface to the IP address of the gateway handles that need nicely.

No one on your network will notice a difference, except if they list
their arp tables or traceroute, and notice that there's something fishy
going on. But why would they do that if there was no interruption of
service! *wink*

.dfbarth