Firewall Wizards mailing list archives
RE: RE: Sniffing out a firewall problem
From: "M. Dodge Mumford" <dodge () nfr net>
Date: Fri, 9 Nov 2001 05:05:47 -0500 (EST)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 8 Nov 2001, Carl Friedberg wrote:
On a network exposed to the outside (internet) you should NEVER run a hub. A hub allows an intruder easy access to any device attached to the hub, including sniffing traffic between multiple nodes which would never be "visible" if you were using a switch.
I must respectfully disagree. Generally, switches are designed to move packets as rapidly as possible from port A to port B while bothering as few other ports as possible. It is generally _not_ the point of a switch to guarantee that traffic is not incorrectly sent out a port. Certainly they have a strong tendency to exhibit that behavior, but it cannot be relied upon for security reasons. On a handful of occasions I have plugged my laptop into arbitrary segments off switches and started tcpdump, filtering out out broadcast traffic. I have repeatedly found stray TCP PSH/ACKs incorrectly sent to me. Sorry, I can't say what makes & models were involved. At best, switches keep people honest. They keep people from "accidentally" sniffing the traffic that wasn't destined to them. I'm not quite sure how someone could accidentally run windump or tcpdump, but I suppose it's possible. If you believe that switches prohibit sniffing, I'd suggest looking at ettercap. (http://ettercap.sourceforge.net/). It uses ARP cache poisoning to reroute packets through a hostile host for monitoring, recording, and injection. Worse, though, is the possibility that an attack could be launched directly from a switch. I know of no instances where this has happened, so take this with some salt. But switches are smarter than hubs (ignoring managed hubs, please) and as such may have exploitable vulnerabilities. I like hubs because they are dumb as rocks. One other reason I prefer hubs there over switches is that I find it easier to debug network issues by sniffing the wire. Of course, I may have sniffed more traffic than many people at this point. ;-) Dodge -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvrqn8ACgkQNFi+2PpLB5H6fwCeLjuGMwUd1ZgzzLB6ItqzZ+b2 OWMAn3ZBvrrIqYDw2xcUh5KI24BYoBAs =mBY9 -----END PGP SIGNATURE----- _______________________________________________ firewall-wizards mailing list firewall-wizards () nfr com http://list.nfr.com/mailman/listinfo/firewall-wizards
Current thread:
- RE: RE: Sniffing out a firewall problem, (continued)
- RE: RE: Sniffing out a firewall problem Anton (Nov 13)
- Re: RE: Sniffing out a firewall problem Pierre-Yves BONNETAIN (Nov 09)
- Re: RE: Sniffing out a firewall problem Peter Lukas (Nov 05)
- RE: Sniffing out a firewall -SNORT blew up registrty Chiman (Nov 06)
- Re: RE: Sniffing out a firewall problem R. DuFresne (Nov 03)
- Re: RE: Sniffing out a firewall problem TDyson (Nov 03)
- Re: RE: Sniffing out a firewall problem Gregory Hicks (Nov 05)
- Re: RE: Sniffing out a firewall problem Barney Wolff (Nov 08)
- RE: RE: Sniffing out a firewall problem Carl Friedberg (Nov 09)
- Re: RE: Sniffing out a firewall problem Stephane Nasdrovisky (Nov 09)
- RE: RE: Sniffing out a firewall problem M. Dodge Mumford (Nov 09)
- RE: RE: Sniffing out a firewall problem Carl Friedberg (Nov 10)
