I know this has already been asked, and I know Hendrik
said no dice. But I still don't understand why, so I'm
going to ask the same dumb question one more time:
I want to block a whole bunch of https: proxies. I
don't need to find them or to understand them - just
block them. I already have a list of them (thanks to
urlblacklist.com and DansGuardian).
It seems encryption isn't important in this case
because nobody needs to look inside the traffic at all
just to block it completely. Why won't it work if I
configure something like this:
acl proxy dstdomain "file_blacklist_of_proxies.txt"
http_access deny proxy
http_access deny all
Let me guess:
1) Is the problem that Squid provides no flavor of
access-list restriction to quash the connection
completely; that 'http_access' only quashes port 80?
2) Is the problem that the size of the blacklist might
be very large (~10,000) and performance suffers so
much this is unworkable?
Help me understand.
tia!
-Chuck Kollars
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Received on Sat Apr 28 2007 - 21:35:38 MDT
This archive was generated by hypermail pre-2.1.9 : Tue May 01 2007 - 12:00:01 MDT