Re:Lans.py: capture usernames, passwords, messages and injec...
by gcb1 on Saturday November 09, 2013 @12:38AM
(#6700787)
doesnt all switches protect you from arp poisoning? or am i missing something on the attack vector? i understand the proxy part is cool... but the vector appears to be a non issue. i just skimmed the readme...
[ Parent
| on HN ]
Re:Lans.py: capture usernames, passwords, messages and injec...
by e12e on Saturday November 09, 2013 @12:45AM
(#6700799)
Most certainly not. Many enterprise switches can be/should be/are configured to protect against it -- but most consumer grade (home) switches I've seen don't.
Not sure what the status of various wireless routers/aps (eg: software ap on *bsd/linux).
Re:Lans.py: capture usernames, passwords, messages and injec...
by gcb1 on Sunday November 10, 2013 @01:45PM
(#6707824)
i think what you call home switches are hubs. they operate on different network layers, hence the different name.
Re:Lans.py: capture usernames, passwords, messages and injec...
by akx on Sunday November 10, 2013 @01:52PM
(#6707859)
I don't think hubs (ie. the sort of switch that indiscriminately transmits every packet to every port) have been in widespread use for ages anymore.
Re:Lans.py: capture usernames, passwords, messages and injec...
by victorhooi on Saturday November 09, 2013 @12:51AM
(#6700809)
Hi,
This is for wireless networks I believe.
Yes, some of those offer client isolation but it's often not the default. (Or maybe I'm thinking RADIUS keys per client since the isolation won't stop you sniffing?)
So assuming you've authenticated (I.e. you have the WEP or WPA key), you'll see all the traffic.
Cheers, Victor