<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google Announces Password Lock for SafeSearch</title>
	<atom:link href="http://davidburt.us/2009/11/12/google-announces-password-lock-for-safesearch/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidburt.us/2009/11/12/google-announces-password-lock-for-safesearch/</link>
	<description>David Burt&#039;s website</description>
	<lastBuildDate>Thu, 03 May 2012 02:55:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Laticia</title>
		<link>http://davidburt.us/2009/11/12/google-announces-password-lock-for-safesearch/#comment-2456</link>
		<dc:creator><![CDATA[Laticia]]></dc:creator>
		<pubDate>Wed, 20 Jul 2011 14:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://filteringfacts.org/?p=756#comment-2456</guid>
		<description><![CDATA[Shoot, so that&#039;s that one supopses.]]></description>
		<content:encoded><![CDATA[<p>Shoot, so that&#8217;s that one supopses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suricou Raven</title>
		<link>http://davidburt.us/2009/11/12/google-announces-password-lock-for-safesearch/#comment-1459</link>
		<dc:creator><![CDATA[Suricou Raven]]></dc:creator>
		<pubDate>Fri, 08 Jan 2010 20:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://filteringfacts.org/?p=756#comment-1459</guid>
		<description><![CDATA[Nothing done at the client can possibly be secure, because any tech-savvy teen can just install another browser or use a linux CD. If they don&#039;t know how, they&#039;ll know someone who knows. The server end can&#039;t do much either, without a way to identify clients.

Sachin is right: The only way to impose a filter that cannot be trivially bypassed is on the network, with some sort of gateway device. But operating and maintaining one of these is beyond the skills of all but a few parents, and even they can be bypassed with a bit of work.]]></description>
		<content:encoded><![CDATA[<p>Nothing done at the client can possibly be secure, because any tech-savvy teen can just install another browser or use a linux CD. If they don&#8217;t know how, they&#8217;ll know someone who knows. The server end can&#8217;t do much either, without a way to identify clients.</p>
<p>Sachin is right: The only way to impose a filter that cannot be trivially bypassed is on the network, with some sort of gateway device. But operating and maintaining one of these is beyond the skills of all but a few parents, and even they can be bypassed with a bit of work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sachin Purohit</title>
		<link>http://davidburt.us/2009/11/12/google-announces-password-lock-for-safesearch/#comment-1424</link>
		<dc:creator><![CDATA[Sachin Purohit]]></dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://filteringfacts.org/?p=756#comment-1424</guid>
		<description><![CDATA[An even better option is to enforce safesearch at the Internet gateway itself, so that it applies to all the machines surfing through it.

Content Filtering Proxies like SafeSquid allows you to enforce safesearch at the gateway, so that no matter what an individual user sets his preference as, safesearch is still enforced to his search queries.

Reference: http://www.safesquid.com/html/portal.php?page=137]]></description>
		<content:encoded><![CDATA[<p>An even better option is to enforce safesearch at the Internet gateway itself, so that it applies to all the machines surfing through it.</p>
<p>Content Filtering Proxies like SafeSquid allows you to enforce safesearch at the gateway, so that no matter what an individual user sets his preference as, safesearch is still enforced to his search queries.</p>
<p>Reference: <a href="http://www.safesquid.com/html/portal.php?page=137" rel="nofollow">http://www.safesquid.com/html/portal.php?page=137</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://davidburt.us/2009/11/12/google-announces-password-lock-for-safesearch/#comment-1423</link>
		<dc:creator><![CDATA[Andy]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:10:35 +0000</pubDate>
		<guid isPermaLink="false">http://filteringfacts.org/?p=756#comment-1423</guid>
		<description><![CDATA[I think a better way to lock the safe search is to use K9 Web Protection. This will then apply to all users and all browsers on that computer.]]></description>
		<content:encoded><![CDATA[<p>I think a better way to lock the safe search is to use K9 Web Protection. This will then apply to all users and all browsers on that computer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

