<?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: Snippets of defense Pt.IV</title>
	<atom:link href="http://www.gnucitizen.org/blog/snippets-of-defense-ptiv/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/snippets-of-defense-ptiv/</link>
	<description>Information Security Think Tank</description>
	<lastBuildDate>Mon, 12 Dec 2011 19:56:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Content Injection: Hack the Hacker &#124; GNUCITIZEN</title>
		<link>http://www.gnucitizen.org/blog/snippets-of-defense-ptiv/comment-page-1/#comment-130863</link>
		<dc:creator>Content Injection: Hack the Hacker &#124; GNUCITIZEN</dc:creator>
		<pubDate>Fri, 13 May 2011 21:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/snippets-of-defense-ptiv#comment-130863</guid>
		<description>[...] I don&#8217;t know how realistic this would be but it could be fun concept to investigate. Imagine setting up modules on your reverse proxy. As user visits the site, different modules could get launched during different requests. One module could detect a user&#8217;s browser plugins. One module could detect Tor and other services with Tor. Put the results into a hashing algorithm and you have a semi-unique client fingerprint regardless of IP address (although privacy laws could restrict these kinds of requests). OR, our reverse proxy could inject random code snippets of defense, overwriting and hijacking JavaScript functions (i.e. alert) with our own action (i.e. logging, blocking etc). Check out some of Mario&#8217;s code snippets of defense for the idea: here, here, here, and here [...]</description>
		<content:encoded><![CDATA[<p>[...] I don&#8217;t know how realistic this would be but it could be fun concept to investigate. Imagine setting up modules on your reverse proxy. As user visits the site, different modules could get launched during different requests. One module could detect a user&#8217;s browser plugins. One module could detect Tor and other services with Tor. Put the results into a hashing algorithm and you have a semi-unique client fingerprint regardless of IP address (although privacy laws could restrict these kinds of requests). OR, our reverse proxy could inject random code snippets of defense, overwriting and hijacking JavaScript functions (i.e. alert) with our own action (i.e. logging, blocking etc). Check out some of Mario&#8217;s code snippets of defense for the idea: here, here, here, and here [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: seraph</title>
		<link>http://www.gnucitizen.org/blog/snippets-of-defense-ptiv/comment-page-1/#comment-63556</link>
		<dc:creator>seraph</dc:creator>
		<pubDate>Wed, 31 Oct 2007 18:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/snippets-of-defense-ptiv#comment-63556</guid>
		<description>pdp, I do not intend to sound ignorant, but wouldn&#039;t this also e bypassed if you simply declare a character encoding in your meta tags?

Please shed some light.</description>
		<content:encoded><![CDATA[<p>pdp, I do not intend to sound ignorant, but wouldn&#8217;t this also e bypassed if you simply declare a character encoding in your meta tags?</p>
<p>Please shed some light.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

