<?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/"
		>
<channel>
	<title>Comments on: Pitfalls of HTML Encryption</title>
	<atom:link href="http://michaeldaw.org/diary/htmlencryption/feed" rel="self" type="application/rss+xml" />
	<link>http://michaeldaw.org/diary/htmlencryption</link>
	<description>Weekly humour</description>
	<lastBuildDate>Thu, 07 May 2009 20:09:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stefan</title>
		<link>http://michaeldaw.org/diary/htmlencryption/comment-page-1#comment-48076</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Thu, 06 Sep 2007 03:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/diary/htmlencryption/#comment-48076</guid>
		<description>I cannot find answer to one simple question – how a HTML encryption effects contextual advertizing i.e. Google AdSense and Google PR?</description>
		<content:encoded><![CDATA[<p>I cannot find answer to one simple question – how a HTML encryption effects contextual advertizing i.e. Google AdSense and Google PR?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niels</title>
		<link>http://michaeldaw.org/diary/htmlencryption/comment-page-1#comment-46953</link>
		<dc:creator>Niels</dc:creator>
		<pubDate>Tue, 17 Jul 2007 09:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/diary/htmlencryption/#comment-46953</guid>
		<description>Hmmm htmlblock:

&lt;!--Protected with HTMLBlock.co.uk--&gt;

//</description>
		<content:encoded><![CDATA[<p>Hmmm htmlblock:</p>
<p><!--Protected with HTMLBlock.co.uk--></p>
<p>//</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david.kierznowski</title>
		<link>http://michaeldaw.org/diary/htmlencryption/comment-page-1#comment-30999</link>
		<dc:creator>david.kierznowski</dc:creator>
		<pubDate>Tue, 22 May 2007 13:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/diary/htmlencryption/#comment-30999</guid>
		<description>Sarah, well as I mentioned in my post (see my proof of concept picture above), it is still possible to get around HTML Encryption in many cases it all depends how its implemented. If its used alongside actual encryption with keys (or passwords) then chances are its alot more secure. If its simple obfuscation (hidden) then its easily reversible.</description>
		<content:encoded><![CDATA[<p>Sarah, well as I mentioned in my post (see my proof of concept picture above), it is still possible to get around HTML Encryption in many cases it all depends how its implemented. If its used alongside actual encryption with keys (or passwords) then chances are its alot more secure. If its simple obfuscation (hidden) then its easily reversible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Carter</title>
		<link>http://michaeldaw.org/diary/htmlencryption/comment-page-1#comment-30993</link>
		<dc:creator>Sarah Carter</dc:creator>
		<pubDate>Tue, 22 May 2007 12:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/diary/htmlencryption/#comment-30993</guid>
		<description>Their are advanced HTML encryptor on the Internet, we &#039;Cromer High School&#039; purchased www.htmlblock.co.uk and used their pre made software on our web site which works very well. Even better on our Intranet to divide teacher and student from accessing each others files. I think HTML Encryption can be a very powerful tool for any webmaster.</description>
		<content:encoded><![CDATA[<p>Their are advanced HTML encryptor on the Internet, we &#8216;Cromer High School&#8217; purchased <a href="http://www.htmlblock.co.uk" rel="nofollow">http://www.htmlblock.co.uk</a> and used their pre made software on our web site which works very well. Even better on our Intranet to divide teacher and student from accessing each others files. I think HTML Encryption can be a very powerful tool for any webmaster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david.kierznowski</title>
		<link>http://michaeldaw.org/diary/htmlencryption/comment-page-1#comment-28754</link>
		<dc:creator>david.kierznowski</dc:creator>
		<pubDate>Sun, 13 May 2007 21:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/diary/htmlencryption/#comment-28754</guid>
		<description>I guess there are two aspects here, first, the end-user security perspective (Nick, I think this is what you are referring to), second, the encryption of the actual site content to prevent source code theft and information leakage.</description>
		<content:encoded><![CDATA[<p>I guess there are two aspects here, first, the end-user security perspective (Nick, I think this is what you are referring to), second, the encryption of the actual site content to prevent source code theft and information leakage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://michaeldaw.org/diary/htmlencryption/comment-page-1#comment-28753</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sun, 13 May 2007 21:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/diary/htmlencryption/#comment-28753</guid>
		<description>Unless the site encrypts it&#039;s code using a password entered by the user, then it&#039;s still not optimal, but better.</description>
		<content:encoded><![CDATA[<p>Unless the site encrypts it&#8217;s code using a password entered by the user, then it&#8217;s still not optimal, but better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
