Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
We all know and love Squid, the versatile HTTP caching proxy. Squid conserves bandwidth, speeds up Web surfing, and comes with all kinds of controls to rein in unruly users: bandwidth throttling, domain filtering, and user access controls, to name a few. But no matter how skillfully you configure your Squid server, it's easy to bypass it. All your users have to do is delete the references to it in their Web browser configurations. If all you're doing with Squid is caching, this makes no sense, but then some folks just like to get away with stuff. If you're using Squid for filtering, bandwidth control or any other restrictions, you will certainly have a rebel underground to deal with. Unless you set up Squid as a transparent proxy, that is.
In many organizations the firewall is going to be separate from the Squid box. A rule in the firewall to only allow web requests from the Squid box should enforce compliance from users.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
