schweini has asked for the wisdom of the Perl Monks concerning the following question:
Salve!,
Somebody asked me to implement a porn-filering firewall for their company. I know that SQUID has a lot of features for stuff like that, but I recently played around with HTTP::Proxy and liked the fact that I could use my perl knowledge to implement filters and rules - so my initial idea is to simply block all outbound traffic on the masquerading router, and only allow HTTP traffic via a perl Proxy, which filters all traffic, blocking sites that contain any blacklisted words, or are on a blacklisted domain. Is this feasible, or am i overlooking something obvious? I know that no filter will ever be perfect, but would this work for a ca. 20 employee-company, running on some pentium 2 or 3 hardware, on a ca. 512kbps link?
Somebody asked me to implement a porn-filering firewall for their company. I know that SQUID has a lot of features for stuff like that, but I recently played around with HTTP::Proxy and liked the fact that I could use my perl knowledge to implement filters and rules - so my initial idea is to simply block all outbound traffic on the masquerading router, and only allow HTTP traffic via a perl Proxy, which filters all traffic, blocking sites that contain any blacklisted words, or are on a blacklisted domain. Is this feasible, or am i overlooking something obvious? I know that no filter will ever be perfect, but would this work for a ca. 20 employee-company, running on some pentium 2 or 3 hardware, on a ca. 512kbps link?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: using HTTP::PROXY instead of SQUID as a company firewall
by vagnerr (Prior) on Nov 07, 2005 at 10:27 UTC | |
by BooK (Curate) on Nov 07, 2005 at 10:56 UTC | |
Re: using HTTP::PROXY instead of SQUID as a company firewall
by Anonymous Monk on Nov 07, 2005 at 10:49 UTC |
Back to
Seekers of Perl Wisdom