On Mon, 2003-08-11 at 10:55, Jason Dixon wrote: > On Mon, 2003-08-11 at 10:51, Michael Gargiullo wrote: > > What ever you use to stop kazaa traffic will have to be able to read > > packet headers. If the default kazaa port is blocked, kazaa can operate > > on port 80 and appear as web traffic. It's possible, but kazaa is > > crafty. > > Is it crafty enough to defeat a layer-7 proxy like Squid running in > transparent mode? I think not. > > -- > Jason Dixon, RHCE > DixonGroup Consulting > http://www.dixongroup.net > Call me a hard case, but if this is a company, I would craft an advisory letter and have HR distribute it stating that it is against company policy to utilize software such as Kazaa on corporate machines. That it presents a security issue and anyone caught with Kazaa on their machines will be subject to immediate termination. We had to do such a thing when WebShots, Spinner, etc got out of hand. The company could only afford small bandwidth and all those users going to Spinner and downloading images from Webshots got to be too much. Not to mention the ones who were passing around mpgs that they had gotten from friends.
I don't even allow Kazaa on my home machines. I advised my step-son that there is security holes in that software that allows others to come in and look at files in other directories and he could be exposing his mothers financial information. He quickly erased it from the system. Fortunately, the machine in question is booted to Linux most of the time. He only boots to XP when he wants to play games. Ed. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
