1753290 Members
5396 Online
108792 Solutions
New Discussion юеВ

Re: Squid configuration

 
SOLVED
Go to solution
Stuart Browne
Honored Contributor

Re: Squid configuration

Whilst it's not a bad idea to limit based on workstation, the idea behind limiting to user is better.

All browsers these days have the ability to authenticate to the proxy server. This will then force the user to enter user/pass details in order to gain Web access.

This means that users A can go to any terminal and view their pages, and users B can also go to any terminal and access the same stuff they normally can, and user C can't access squat no matter where they go.

It's a more maulable way of doing things.
One long-haired git at your service...
Jerome Henry
Honored Contributor

Re: Squid configuration

Hi Stuart,

Here again is a time zone issue for you !

The idea was merely that the company I design this for is using DHCP and, as you say, users can change their connection machine easily.

Do you have this kind of user based configuration suggestion ?

J
You can lean only on what resists you...
Balaji N
Honored Contributor

Re: Squid configuration

i think then u can use the configuration sent by me.

do u have the username/password details ready already?

-balaji
Its Always Important To Know, What People Think Of You. Then, Of Course, You Surprise Them By Giving More.
Stuart Browne
Honored Contributor

Re: Squid configuration

*nod*nod* what Balaji said.

The ACL's themselves that the other guy pasted were fine, but instead of the user-list, you'd use Balaji's auth lines. They might be able to take a file-name list of user-names though.. I'm not sure.
One long-haired git at your service...
Jerome Henry
Honored Contributor

Re: Squid configuration

Just a way not to leave anyone out.

I getting to the Co. now, I'll pick up users and url lists there !

Have a nice day, I'm leaving all the points for you today :]]

J
You can lean only on what resists you...