<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> We may be able to talk the hotel into letting us put it at the head end and proxy the entire hotel.<br> <pre class="moz-signature" cols="72">Jeff Lawton Ideal Solution, LLC 517-485-2650 ext 220 <a class="moz-txt-link-abbreviated" href="mailto:jeff@idealso.com">jeff@idealso.com</a> <a class="moz-txt-link-freetext" href="http://www.idealso.com">http://www.idealso.com</a> </pre> <br> <br> Marshal Newrock wrote: <blockquote cite="mid20070425205919.3564cb6b@localhost" type="cite"> <pre wrap="">On Wed, 25 Apr 2007 20:38:47 -0400 Jeff Lawton <a class="moz-txt-link-rfc2396E" href="mailto:jeff@idealso.com"><jeff@idealso.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Lee is planning on attending next year I sure he would share his squid configuration files to make the lounge a safe place for kids. We could offer passwords to allow adults to bypass the filter if needed. Lee I don't mean to speak for you. would you be willing to take on the kid safe proxy filter for next year? </pre> </blockquote> <pre wrap=""> Such proxies tend to be both ineffective and too effective - that is, easy to bypass or find out the password, and they don't block everything they should, or tends to block sites that shouldn't be blocked. The main result will be annoying people who are just trying to look something up. There's also the liability issue again. I believe that if we attempt to block everything "bad" we become responsible for whatever gets through. On the other hand, a caching transparent web proxy is an excellent idea. I'd been thinking of this too. Next year, we should put everything behind a pfsense box with a proxy on it, and let it serve dhcp and dns to all non-terminal computers. </pre> </blockquote> </body> </html>