Re: [squid-users] Define some users only can access to some website

On 13/07/10 1:16 PM, "Donny Christiaan" <dchristiaan_at_gmail.com> wrote:

> Dear Expert,
>
> I'm looking squid configuration to allow some user to access only listed urls.
>
> Let say I would like to define for user "donny" only can access
> www.yahoo.com
> www.google.com
> www.freshmeat.net
>
> So user "donny" only can access listed (3 url) above not more than that.
>
> I'm using:
> - Squid Cache: Version 2.6.STABLE6
> - mysql_auth
> - SquidGuard
>
> Best Regards,
> Donny Christiaan.
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________

Hi Donny,

This looks very similar to the same email you sent to this list last week.

This setup should work.

acl my_sites dstdomain www.yahoo.com www.google.com www.freshmeat.net
acl restricted_users proxy_auth donny

http_access allow restricted_users my_sites
http_access deny restricted_users

This setup should allow "restricted_users" to access "my_sites", then deny
"restricted_users" from accessing anything else.

References:
http://www.visolve.com/squid/squid30/accesscontrols.php#acl
http://www.visolve.com/squid/squid30/accesscontrols.php#http_access

This is, however untested in a proper configuration but seems fairly
logical. This is also certainly not the only approach to this problem.

Scott

This email and any files transmitted with it are confidential and intended
 solely for the use of the individual or entity to whom they are addressed.
Please notify the sender immediately by email if you have received this
email by mistake and delete this email from your system. Please note that
 any views or opinions presented in this email are solely those of the
 author and do not necessarily represent those of the organisation.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The organisation accepts no liability for any
damage caused by any virus transmitted by this email.
Received on Tue Jul 13 2010 - 03:40:04 MDT