<?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"
	>
<channel>
	<title>Comments on: Traversing the Web</title>
	<atom:link href="http://www.gnucitizen.org/blog/traversing-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/traversing-the-web/</link>
	<description>Information Security Think Tank</description>
	<pubDate>Fri, 29 Aug 2008 18:39:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Same Origin Bypassing Using Image Dimensions &#171; omg.wtf.bbq.</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-100050</link>
		<dc:creator>Same Origin Bypassing Using Image Dimensions &#171; omg.wtf.bbq.</dc:creator>
		<pubDate>Wed, 16 Jan 2008 03:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-100050</guid>
		<description>[...] has been a lot of research into ways of getting around the same origin policy. What if the browser sandbox we&#8217;re all [...]</description>
		<content:encoded><![CDATA[<p>[...] has been a lot of research into ways of getting around the same origin policy. What if the browser sandbox we&#8217;re all [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yahoo Site Explorer Spider &#124; GNUCITIZEN</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-35586</link>
		<dc:creator>Yahoo Site Explorer Spider &#124; GNUCITIZEN</dc:creator>
		<pubDate>Sun, 15 Jul 2007 21:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-35586</guid>
		<description>[...] from this page. I&#8217;ve being talking about client-side spiders for quite some time now over here and here and I even came up with POC based on Yahoo Pipes for my OWASP presentation on Advanced Web [...]</description>
		<content:encoded><![CDATA[<p>[...] from this page. I&#8217;ve being talking about client-side spiders for quite some time now over here and here and I even came up with POC based on Yahoo Pipes for my OWASP presentation on Advanced Web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GNUCITIZEN &#187; The Web has Betrayed Us</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-22325</link>
		<dc:creator>GNUCITIZEN &#187; The Web has Betrayed Us</dc:creator>
		<pubDate>Fri, 18 May 2007 06:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-22325</guid>
		<description>[...] I believe that this spider is a lot more stable then what JIKTO is using. Why? It is like that because the core component of JIKTO was the same origin unification hack which was initially described here. I repeat, it is a hack. By using a proper mashup service, we do not relay on hacks any more, we use actual service side components that can be scribed via client side technologies. In general, we can use publicly available services for their processing power and more over, we can use them in a distributed way and this is what is dangerous about them. I can talk on this subject for hours and still not be able to say everything that I have in my head. For that reason, let&#8217;s have a couple of examples of potentially destructive uses of public APIs, so you can see the big picture from the angle I see it. [...]</description>
		<content:encoded><![CDATA[<p>[...] I believe that this spider is a lot more stable then what JIKTO is using. Why? It is like that because the core component of JIKTO was the same origin unification hack which was initially described here. I repeat, it is a hack. By using a proper mashup service, we do not relay on hacks any more, we use actual service side components that can be scribed via client side technologies. In general, we can use publicly available services for their processing power and more over, we can use them in a distributed way and this is what is dangerous about them. I can talk on this subject for hours and still not be able to say everything that I have in my head. For that reason, let&#8217;s have a couple of examples of potentially destructive uses of public APIs, so you can see the big picture from the angle I see it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gar</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-20054</link>
		<dc:creator>Gar</dc:creator>
		<pubDate>Mon, 07 May 2007 01:20:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-20054</guid>
		<description>I'm probably very naive, but I just wish that browser implementors got rid of cookies in iframes.
The only sensible use would be doubleclick and urchin anyway.</description>
		<content:encoded><![CDATA[<p>I&#8217;m probably very naive, but I just wish that browser implementors got rid of cookies in iframes.<br />
The only sensible use would be doubleclick and urchin anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GNUCITIZEN &#187; The Attack of the TINY URLs</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-19546</link>
		<dc:creator>GNUCITIZEN &#187; The Attack of the TINY URLs</dc:creator>
		<pubDate>Thu, 03 May 2007 09:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-19546</guid>
		<description>[...] For the purpose of this exercise I employ a single technique that I discussed in detail over here. What this technique shows is that although parent documents cannot read the content of child iframes, child iframes can assign values to their parent&#8217;s fragment identifier. In conjunction with tinyurl storage capabilities and a simple trick, this technique can be used to make JavaScript agents live and bread on the web. [...]</description>
		<content:encoded><![CDATA[<p>[...] For the purpose of this exercise I employ a single technique that I discussed in detail over here. What this technique shows is that although parent documents cannot read the content of child iframes, child iframes can assign values to their parent&#8217;s fragment identifier. In conjunction with tinyurl storage capabilities and a simple trick, this technique can be used to make JavaScript agents live and bread on the web. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GNUCITIZEN &#187; Google AJAX Feed API Dangers</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-14947</link>
		<dc:creator>GNUCITIZEN &#187; Google AJAX Feed API Dangers</dc:creator>
		<pubDate>Thu, 19 Apr 2007 13:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-14947</guid>
		<description>[...] Although SOP works and it greatly improves the browser security, there are ways it can be circumvented to one degree or another. For example, I&#8217;ve demonstrated a simple technique where attackers can use publicly available anonymous proxies to unify the origins of two or more web resources. The techniques was used as a key component of Jikto, which was released by Billy Hoffman from SPI Dynamics as a Proof of Concept of how JavaScript can probe various websites for vulnerabilities and spread when XSS or SQL Injection holes are found. [...]</description>
		<content:encoded><![CDATA[<p>[...] Although SOP works and it greatly improves the browser security, there are ways it can be circumvented to one degree or another. For example, I&#8217;ve demonstrated a simple technique where attackers can use publicly available anonymous proxies to unify the origins of two or more web resources. The techniques was used as a key component of Jikto, which was released by Billy Hoffman from SPI Dynamics as a Proof of Concept of how JavaScript can probe various websites for vulnerabilities and spread when XSS or SQL Injection holes are found. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maluc</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-246</link>
		<dc:creator>maluc</dc:creator>
		<pubDate>Thu, 12 Oct 2006 14:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-246</guid>
		<description>Wow, the author of stripe snoop..? That code helped me more than you could know, so.. thanks ^^

-maluc</description>
		<content:encoded><![CDATA[<p>Wow, the author of stripe snoop..? That code helped me more than you could know, so.. thanks ^^</p>
<p>-maluc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Acidus</title>
		<link>http://www.gnucitizen.org/blog/traversing-the-web/#comment-230</link>
		<dc:creator>Acidus</dc:creator>
		<pubDate>Tue, 10 Oct 2006 18:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/traversing-the-web#comment-230</guid>
		<description>There are some really cool attacks you can do with Ajax Bridges/proxies/gateways. Most of the time it makes more sense for an attacker to use the bridge on www.example.com to attack api.datastore.com than to directly attack api.datastore.com

Check out slides 37 - 45 (ignore the slanting)

&lt;a href="http://www.spidynamics.com/spilabs/education/presentations/BillyHoffman-Ajax(in)security.pdf" rel="nofollow"&gt;http://www.spidynamics.com/spilabs/education/presentations/BillyHoffman-Ajax(in)security.pdf&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>There are some really cool attacks you can do with Ajax Bridges/proxies/gateways. Most of the time it makes more sense for an attacker to use the bridge on <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> to attack api.datastore.com than to directly attack api.datastore.com</p>
<p>Check out slides 37 - 45 (ignore the slanting)</p>
<p><a href="http://www.spidynamics.com/spilabs/education/presentations/BillyHoffman-Ajax(in)security.pdf" rel="nofollow"></a><a href="http://www.spidynamics.com/spilabs/education/presentations/BillyHoffman-Ajax" rel="nofollow">http://www.spidynamics.com/spi.....ffman-Ajax</a>(in)security.pdf</p>
]]></content:encoded>
	</item>
</channel>
</rss>
