On Wed, 25 Apr 2001, jakob wrote: > ... When you have some > time, install dsniff and run it on a busy network, and see how many > passwords it rips off of the wire. If that doesn't scare you, nothing will > :-) ... > Everyone's got something to hide (even if it's just their passwords, and > everyone should have the right to privacy, even if they aren't doing > something illegal. > jakob :-) I would like to warn people: running dsniff probably constitutes packet sniffing, which violates most contractual terms of use for isp's... I know the UO has an anti-sniffing policy. You must be CAUGHT, of course, which may not be likely, but then again, you might be friggin surprised. Anyway, UO Network Services says "don't", emphatically, but I do indeed want to learn networking in general, it is a crucial part of my greater focus... should I simply generate as much traffic as possible within my private subnet for such endeavors? Are any local isp's _allowing_ sniffing?? I understand that it can be abused, but most common tools can be abused or mis-used as well -- even my body can be :/ My understanding is that all these packets, between my firewall out to the next router (within some quantity of subnet anyway) are being broadcast to my jack. So my equipment is sifting through it all, already, just to see what I (me=person) am "allowed" to look at? Can someone help me understand what public policy actually is (or how we may temper it into making sense)? ben #*! no red flags raised -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- "slide" to www.euglug.org in lake'ch, my kin... 4 Ix Finally, I (this text) would be delighted to be included, in whole or in part, in your next discussion of self-reference. With that in mind, please allow me to appologize in advance for infecting you.
